Hi folks,
Have a peek at posts #27 and #30 over in the Q&A thread about spontaneous call drop/reconnects which appear to be due to segfaulting of the "rild" daemon in Froyo ROMs
At this point, it is speculative whether or not the Sprint Hero version of libhtc_ril.so has something to do with the problem or not (the "rild" daemon is also different in Froyo ROMs from the most recent Eris 2.1 OTA release), but it seems like that would be the first thing to look at (experimentally, since we don't have the source code for it.)
Your feedback would be appreciated - in particular - are you using the Sprint Hero version of libhtc_ril.so in all of your Froyo ROMs for the Eris?
bftb0
bftb0 said:
Hi folks,
Have a peek at posts #27 and #30 over in the Q&A thread about spontaneous call drop/reconnects which appear to be due to segfaulting of the "rild" daemon in Froyo ROMs
At this point, it is speculative whether or not the Sprint Hero version of libhtc_ril.so has something to do with the problem or not (the "rild" daemon is also different in Froyo ROMs from the most recent Eris 2.1 OTA release), but it seems like that would be the first thing to look at (experimentally, since we don't have the source code for it.)
Your feedback would be appreciated - in particular - are you using the Sprint Hero version of libhtc_ril.so in all of your Froyo ROMs for the Eris?
bftb0
Click to expand...
Click to collapse
Shouldn't be a problem if the person who compiles CM6 was using the extract-files.sh script in the device repo. It contains most/all of all the proprietary libraries necessary for a fully functional device.
Extracted from a working 2.1 build and then pre-linked(http://github.com/darchstar/android_device_htc_heroc/blob/froyo/prelink-linux-arm-heroc.map) for functionality.
Check conaps device repo: http://github.com/Conap30/android_device_htc_desirec
I don't see one for KaosFroyo, I just see and update.zip(?).
Either way, there's a lot of differences because of the proc type. Something we found out the hard way when we tried to merge the Hero(GSM) and the Hero(CDMA) device repos together.
There would be a lot of erroneous bugs until we finally decided it would be best to split them apart again.
Seeing as TazzFroyo is a direct port from the CM6 nightlies for HeroC, it's very likely that you guys are facing the same issues.
One of the things that Conap has been working on is fixing up the prelink map, something that you guys could help out on and finally have the most stable and functional froyo.
(Man, I really kill conversations)
Thank you Decad3nce - I learn a great deal from every one of your posts.
I unpacked a number of recent Eris Froyo (and legacy) ROMs for comparison:
Code:
[email protected]:~/Android/tmp$ md5sum `find . -name libhtc_ril.so -print`
939ed5e367b1291492c25915ce793a4b ./original1.17.605.1/system/lib/libhtc_ril.so
2857bca5b51163004d2254a1b13ab0cd ./21_julOTA/system/lib/libhtc_ril.so
2857bca5b51163004d2254a1b13ab0cd ./21_leak_v3/system/lib/libhtc_ril.so
e921186c8e5342fdf8c2fccac9f9f632 ./htc_sprint_hero_mr_2.27.651.6/system/lib/libhtc_ril.so
e921186c8e5342fdf8c2fccac9f9f632 ./update-cm-6.0.0-Heroc-RC1/system/lib/libhtc_ril.so
2857bca5b51163004d2254a1b13ab0cd ./CELBFroyo2.6/system/lib/libhtc_ril.so
fa6f724144bdb7b08c340fa264ecad27 ./kaosfroyo-V34/system/lib/libhtc_ril.so
e921186c8e5342fdf8c2fccac9f9f632 ./TazzFroyo-Vanilla-6.0/system/lib/libhtc_ril.so
e921186c8e5342fdf8c2fccac9f9f632 ./TazzFroyo-2.0/system/lib/libhtc_ril.so
e921186c8e5342fdf8c2fccac9f9f632 ./nonsensikal_v5.4/system/lib/libhtc_ril.so
64b4e08d3d34a3b662f3ba820c6bc306 ./tenzomonk_Vanilla2.0.3/system/lib/libhtc_ril.so
It looks like the TazzFroyo & nonsensikal ROMs have been using the Sprint Hero Vendor RIL;
KaosFroyo uses something I don't recognize - perhaps an earlier Sprint Hero Vendor RIL ? (it is internally timestamped "HTC-RIL 2.0.0053HM (Feb 24 2010,00:01:16)" - just two days earlier than the Sprint Hero MR2 version) ;
tenzomonk is using an older RIL in his AOSP Vanilla - "HTC-RIL 1.6.1045G (Nov 12 2009,11:19:21)" ;
Only Conap's CELBFroyo2.6 seems to be using an Eris Vendor RIL library.
( Note the last Eris 1.5 release ("MR2" or "1.17.605.1") had a version number of "HTC-RIL 1.5.1030H (Oct 27 2009,22:14:44)" - I don't know if tenzomonk is using a Leak-V{1,2} Eris library or a Sprint library.
bftb0
bftb0 said:
Thank you Decad3nce - I learn a great deal from every one of your posts.
I unpacked a number of recent Eris Froyo (and legacy) ROMs for comparison:
Code:
[email protected]:~/Android/tmp$ md5sum `find . -name libhtc_ril.so -print`
939ed5e367b1291492c25915ce793a4b ./original1.17.605.1/system/lib/libhtc_ril.so
2857bca5b51163004d2254a1b13ab0cd ./21_julOTA/system/lib/libhtc_ril.so
2857bca5b51163004d2254a1b13ab0cd ./21_leak_v3/system/lib/libhtc_ril.so
e921186c8e5342fdf8c2fccac9f9f632 ./htc_sprint_hero_mr_2.27.651.6/system/lib/libhtc_ril.so
e921186c8e5342fdf8c2fccac9f9f632 ./update-cm-6.0.0-Heroc-RC1/system/lib/libhtc_ril.so
2857bca5b51163004d2254a1b13ab0cd ./CELBFroyo2.6/system/lib/libhtc_ril.so
fa6f724144bdb7b08c340fa264ecad27 ./kaosfroyo-V34/system/lib/libhtc_ril.so
e921186c8e5342fdf8c2fccac9f9f632 ./TazzFroyo-Vanilla-6.0/system/lib/libhtc_ril.so
e921186c8e5342fdf8c2fccac9f9f632 ./TazzFroyo-2.0/system/lib/libhtc_ril.so
e921186c8e5342fdf8c2fccac9f9f632 ./nonsensikal_v5.4/system/lib/libhtc_ril.so
64b4e08d3d34a3b662f3ba820c6bc306 ./tenzomonk_Vanilla2.0.3/system/lib/libhtc_ril.so
It looks like the TazzFroyo & nonsensikal ROMs have been using the Sprint Hero Vendor RIL;
KaosFroyo uses something I don't recognize - perhaps an earlier Sprint Hero Vendor RIL ? (it is internally timestamped "HTC-RIL 2.0.0053HM (Feb 24 2010,00:01:16)" - just two days earlier than the Sprint Hero MR2 version) ;
tenzomonk is using an older RIL in his AOSP Vanilla - "HTC-RIL 1.6.1045G (Nov 12 2009,11:19:21)" ;
Only Conap's CELBFroyo2.6 seems to be using an Eris Vendor RIL library.
( Note the last Eris 1.5 release ("MR2" or "1.17.605.1") had a version number of "HTC-RIL 1.5.1030H (Oct 27 2009,22:14:44)" - I don't know if tenzomonk is using a Leak-V{1,2} Eris library or a Sprint library.
bftb0
Click to expand...
Click to collapse
You'll always have the best stability with your specific proprietary libraries created for your board, which as you've just presented means that the best stability may be in CELBFroyo2.6.
KaosFroyo RIL could be from anywhere; since he 'optimizes' his libs(still not sure what that means).
Hope that helps. Wasn't sure if you were asking a question with your response but oh well lol.
Decad3nce said:
Wasn't sure if you were asking a question with your response but oh well lol.
Click to expand...
Click to collapse
No questions. At this point I'm just going to use Tazz 2.0 with the lib replacement to see if the problem disappears or not. Hopefully I will get some help, either of the form "I tried the lib replacement, and still had the same problems", or "it used to happen to me all the time and has stopped since I started using the Eris library".
bftb0
bftb0 said:
No questions. At this point I'm just going to use Tazz 2.0 with the lib replacement to see if the problem disappears or not. Hopefully I will get some help, either of the form "I tried the lib replacement, and still had the same problems", or "it used to happen to me all the time and has stopped since I started using the Eris library".
bftb0
Click to expand...
Click to collapse
FWIW: I switched to CELBFroyo2.6 from KaosFroyo and have not had that problem any more...
eldouche said:
FWIW: I switched to CELBFroyo2.6 from KaosFroyo and have not had that problem any more...
Click to expand...
Click to collapse
That seems consistent with what Decad3nce is saying, although I don't know specifically what Conap might have done for his CM6 builds. He was aware of the problem with his CM5.0.8 builds - a couple of people reported it directly in his dev thread for his (CELB 2.8-CMS5.0.8) ROM, so maybe he took some measures in his CM6 builds.
As for my hypothesis about the libhtc_rild.so vendor library being the source of the problem - I experienced the same problem less than 8 hours after replacing only that library - again, a crash of "rild" was reported exactly at the moment of failure.
At this time, I am running a CM6 ROM with both "rild" and "libhtc_ril.so" replaced by the HTC Eris 2.1 (July 17 OTA) versions of the code to see if the problem will disappear.
bftb0
bftb0 said:
That seems consistent with what Decad3nce is saying, although I don't know specifically what Conap might have done for his CM6 builds. He was aware of the problem with his CM5.0.8 builds - a couple of people reported it directly in his dev thread for his (CELB 2.8-CMS5.0.8) ROM, so maybe he took some measures in his CM6 builds.
As for my hypothesis about the libhtc_rild.so vendor library being the source of the problem - I experienced the same problem less than 8 hours after replacing only that library - again, a crash of "rild" was reported exactly at the moment of failure.
At this time, I am running a CM6 ROM with both "rild" and "libhtc_ril.so" replaced by the HTC Eris 2.1 (July 17 OTA) versions of the code to see if the problem will disappear.
bftb0
Click to expand...
Click to collapse
I have had reports of this with my 2.2 rom as well....and this is not just a problem with the eris...other phones have reported it also...specifically someone with an DI running cm6 has the same issue...
bftb0 said:
That seems consistent with what Decad3nce is saying, although I don't know specifically what Conap might have done for his CM6 builds. He was aware of the problem with his CM5.0.8 builds - a couple of people reported it directly in his dev thread for his (CELB 2.8-CMS5.0.8) ROM, so maybe he took some measures in his CM6 builds.
As for my hypothesis about the libhtc_rild.so vendor library being the source of the problem - I experienced the same problem less than 8 hours after replacing only that library - again, a crash of "rild" was reported exactly at the moment of failure.
At this time, I am running a CM6 ROM with both "rild" and "libhtc_ril.so" replaced by the HTC Eris 2.1 (July 17 OTA) versions of the code to see if the problem will disappear.
bftb0
Click to expand...
Click to collapse
Take note if you see the linker library crapping out though. Replacing libraries seems kind of iffy if you want to conduct a proper experiment. The best way to go about it would be to compile with those replaced RIL libraries prelinked.
Conap said:
I have had reports of this with my 2.2 rom as well....and this is not just a problem with the eris...other phones have reported it also...specifically someone with an DI running cm6 has the same issue...
Click to expand...
Click to collapse
Might be bad prelink map
Decad3nce said:
Might be bad prelink map
Click to expand...
Click to collapse
i'll look at that...
Edit: They don't seem to be prelinked...
bftb0 said:
At this time, I am running a CM6 ROM with both "rild" and "libhtc_ril.so" replaced by the HTC Eris 2.1 (July 17 OTA) versions of the code to see if the problem will disappear.
Click to expand...
Click to collapse
How did you replace them ? Can you just 'adb push' them to the phone and reboot ?
Conap said:
i'll look at that...
Edit: They don't seem to be prelinked...
Click to expand...
Click to collapse
libhtc_ril.so is prelinked.
Ours:
Code:
# libraries for specific hardware
libgsl.so 0xA2E00000 # [~1M]
libhtc_acoustic.so 0xA2D00000 # [<64K]
libhtc_ril.so 0xA2C00000 # [~1M]
liblvmxipc.so 0xA2B00000 # [~1M] for vendor/nxp
libreference-cdma-sms.so 0xA2A00000 # [<64K] for hardware/ril
hallstevenson said:
How did you replace them ? Can you just 'adb push' them to the phone and reboot ?
Click to expand...
Click to collapse
You can do it with the OS running (I did). But, you do need to be careful about file permissions and owner/group ownership on all files you fool around with - "adb push" won't set those correctly. (In particular "rild" seems to have user/group = root/shell, mode 755 on Tazz 2.0). It is probably safest to do it offline (meaning, with Amon_RA booted, using adb and "mount /system").
I think I did something like this (interactively, with the regular OS booted):
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
adb push libhtc_ril.so /system/lib/libhtc_ril.so.Eris
adb push rild /system/bin/rild.Eris
adb shell
md5sum /system/bin/rild.Eris /system/lib/libhtc_ril.so.Eris [COLOR=grey]( safety check )[/COLOR]
chmod 755 /system/bin/rild.Eris
chgrp shell /system/bin/rild.Eris
chmod 644 /system/lib/libhtc_ril.so.Eris
mv /system/lib/libhtc_ril.so /system/lib/libhtc_ril.so.CM6
cp /system/lib/libhtc_ril.so.Eris /system/lib/libhtc_ril.so
mv /system/bin/rild /system/bin/rild.CM6
cp -p /system/bin/rild.Eris /system/bin/rild
ps | grep rild
kill -HUP <pid of the rild process>
logcat -d [COLOR=grey]( look for any complaints about rild failing ) [/COLOR]
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
reboot
Or something close to that
Note I did it this way so that it would be easy to revert - there seems to be plenty of space in /system with Froyo ROMs
bftb0
Decad3nce said:
Take note if you see the linker library crapping out though. Replacing libraries seems kind of iffy if you want to conduct a proper experiment. The best way to go about it would be to compile with those replaced RIL libraries prelinked.
Click to expand...
Click to collapse
I agree with you - I recursively walked through all the dependencies
Code:
arm-eabi-objdump -x $obj | grep NEED
and thought, "dlopen() is going to barf immediately", based on all the libraries that potentially get demand-loaded - but it didn't.
Sort of a low cost experiment in the meantime. Too bad we don't know how to force the segfault deterministically - getting any sort of result experimentally takes friggin forever because the incidence of the problem is sporadic. (Anybody want to run rild under strace for several days? - LOL)
I'm trying to keep my eyes on it. (In the meantime, I'll also try to figure out what "prelink map" means)
bftb0
Decad3nce said:
libhtc_ril.so is prelinked.
Ours:
Code:
# libraries for specific hardware
libgsl.so 0xA2E00000 # [~1M]
libhtc_acoustic.so 0xA2D00000 # [<64K]
libhtc_ril.so 0xA2C00000 # [~1M]
liblvmxipc.so 0xA2B00000 # [~1M] for vendor/nxp
libreference-cdma-sms.so 0xA2A00000 # [<64K] for hardware/ril
Click to expand...
Click to collapse
Maybe i'm checking the prelink wrong...i am using isprelink. I type ./isprelink libgps.so...it gives me the number. When i do it on the libhtc_ril it says its not prelinked...is there another way to do it?
bumpitty bump. I really want to figure this out. Any way for me to help.
Well, conap and I looked into it.
The first thing we noticed is that, even though libhtc_ril.so is in the prelink.map, it doesn't get linked properly.
One of two things could cause this:
1. The libraries being mapped before it(address wise), exceed their bounds and thusly don't leave enough allocated memory for libhtc_ril.so
Conap and I looked further into this and we noticed that libhtc_acoustic.so ALSO doesn't get mapped correctly, even though it is in the prelink map.
To fix this, we'd have to just simply restructure the prelink map.
2. Now this one would be a bit more tricky, and I think this may be what the cause is.
When the prelink map sets up all the addresses, everything gets mapped correctly. You can tell that it does because everything following libhtc_acoustic.so/libhtc_ril.so gets mapped properly. The thing that MAY be happening is that libhtc_acoustic.so(most likely) or something before it, exceeds its allocated bounds when it's ACTIVE. This is a problem that just about every Froyo compile has faced. Currently, libhtc_acoustic is mapped with \\ libhtc_acoustic.so 0xA2D00000 # [<64K] \\
At less than 64k space. If it exceeds that bound, while active, then it could offset libhtc_ril.so.
I haven't tested any of this, as I don't really mess with the froyo compilation side of things.
I went through all the libs in my build and found ten that are not prelinked but are on the prelink map.....
lib/libhtc_acoustic.so: not prelinked
lib/libhtc_ril.so: not prelinked
lib/libjpeg.so: not prelinked
lib/libmm-adspsvc.so: not prelinked
lib/libmm-omxcore.so: not prelinked
lib/libOmxCore.so: not prelinked
lib/libOmxH264Dec.so: not prelinked
lib/libOmxMpeg4Dec.so: not prelinked
lib/libOmxVidEnc.so: not prelinked
lib/libspeech.so: not prelinked
I guess off to google to figure out how to correctly change the prelink map so that these libs get prelinked...
I haven't had any call drop issues other than the normal amount being in the basement surrounded be concrete kills cell reception
Sent from my FroyoEris using XDA App
Related
Captivate / Vibrant Hybrid
Confirmed Working on the Captivate
How-to Apply Lagfix to My Rom " Do Not Use another Lagfix as it Breaks my PLaylogos1 Script..."
adb shell
su
mv /system/bin/userinit.sh /system/bin/used
reboot
Click to expand...
Click to collapse
Then
adb shell
su
busybox dd if=/dev/zero of=/data/dataimg bs=1024 count=1048576
busybox mknod /dev/loop0 b 7 0
busybox losetup /dev/loop0 /data/dataimg
busybox mkfs.ext2 /dev/loop0
mkdir /data/data1
mv /system/bin/used /system/bin/userinit.sh
reboot
Click to expand...
Click to collapse
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Download > Captivate_Hybrid_r3.zip
*Changelog*
~ GPS Issue's ( Disable GPS & Enable Wireless Location if you need Location working )
~ WyContactMod added
~ Edits of Framework Anim
~ lbstestmode added & selectable in app's
~ Added MMS-Mod
~ Fixed MMs Sending Issue
~ removed LockBot Free ( Memory Hog )
~ No kernel included for letting User's choose what they want..
~ Stock Build / Mix of TouchWiz UI
~ Auto Rotation / Sensors should work
~ Process Bar status fixed in Recovery.. Not that big of issue, but I like to see the Flashing status.
~ Launcher 2 edited for are default Apps
~ Sim Card Initializing bug Fixed
~ Stock Dailer Added
~ Stock incall Dialer Kept, Has better Options for in call status BT / Headset / Speaker & a huge End button..
~ Stock Android Contacts added
~ Contacts do not Show Google contact status until you log into Gtalk ( This is default, I don't like people seeing me on Gtalk and not know it )...
~ Removed Shadows for Puzzle
~ Stock Calendar ( White bar bug Fixed )
~ Trim down un-need Samsung app's
~ GPS loads from etc/gps.cfg file now
~ Added CM APN list
~ Added IME_Mod keyboard
~ Updated to Current Maps
~ Vibrant9 Theme
~ MobileAP Mod included ( WiFi Tether in Settings )
~ Lagfix Supported, but not installed... See Post & link at the Top of the is ( How-to Apply Lagfix to My Rom )
~ Super Audio Package ( a huge Mix of Ringtones )
~ Smali edits of App's
~ Removed Facebook
~ TW Camera
~ TW Gallery
hero 10char
I'm assuming that means there is no kernel flashing in the update.zip or anything required after running it?
How do you apply this? Odin or clockworkmod or how?
cropythy said:
How do you apply this? Odin or clockworkmod or how?
Click to expand...
Click to collapse
ClockworkMod.
Does this have the captivate camera or the vibrant camera? I've heard of vibrant users loading the captivate camera but never dug deeper to find out why.
Also, has anyone here flashed this yet? Eugene's roms are supposed to be pretty good. I'm debating on installing this or waiting for a froyo rom.
Sent from my SAMSUNG-SGH-I897 using XDA App
lpfansether said:
Does this have the captivate camera or the vibrant camera? I've heard of vibrant users loading the captivate camera but never dug deeper to find out why.
Also, has anyone here flashed this yet? Eugene's roms are supposed to be pretty good. I'm debating on installing this or waiting for a froyo rom.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yes it has the Captivate Camera app..
junkboy said:
awesome work! i just flashed this to my captivate.
Click to expand...
Click to collapse
This person is the one that Confirmed it working.
lpfansether said:
Does this have the captivate camera or the vibrant camera? I've heard of vibrant users loading the captivate camera but never dug deeper to find out why.
Also, has anyone here flashed this yet? Eugene's roms are supposed to be pretty good. I'm debating on installing this or waiting for a froyo rom.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I really want to, but he hasn't answered my question about kernel flashing yet
edit: in the change log it says "includes stock kernel" which I assume is just a part of the direct copy/paste from the vibrant thread, so is therefore the stock vibrant kernel... meaning that there is a kernel flash to which we could theoretically follow up with an SRE flash
FYI It does have the autorotate but so you have to go into settings and uncheck orientation under sound and display
Edit: I am guessing I need to install vibrant drivers?
cropythy said:
FYI It does have the autorotate but so you have to go into settings and uncheck orientation under sound and display
Edit: I am guessing I need to install vibrant drivers?
Click to expand...
Click to collapse
if you could, try following it up with an SRE flash (which I believe will change the notification bar) or flash the stock captivate kernel with odin (which won't have a working mobile AP or overclock)
You might want to try flashing a stock captivate kernel on top of it, or if he's got the lagfix baked in you might want to use unhelpful's kernel so that it maintains init.d support. I'm still working on flashing back to try this so I can't say for sure =P
Trying SRE right now, will report back momentarily
So don't think that worked, Linpack scores of 7.6 which is much lower than it should be, lag is unbelievable and I can't get adb to recognize my phone anymore, making it pretty close to unusable...going back to JH3 until smarter people than I can figure something out...
One more thing, this worked as advertised until I tried SRE, but just with the known issues of using a vibrant kernel in the captivate
I don't know if I've ever hit F5 this many times back to back, come on crop and Zilch!
Let me know how this works... I can change out what ever need edited, but I don't have an at&t phone to further fix things...
eugene373 said:
Let me know how this works... I can change out what ever need edited, but I don't have an at&t phone to further fix things...
Click to expand...
Click to collapse
I believe the only thing that would really need to be fixed (according to crop) would be to use either the stock kernel (http://koush.tandtgaming.com//test/kernel-captivate-stock.tar.md5) or Unhelpful's kernel (http://forum.xda-developers.com/showthread.php?t=762171) instead of the vibrant kernel
cropythy said:
Trying SRE right now, will report back momentarily
So don't think that worked, Linpack scores of 7.6 which is much lower than it should be, lag is unbelievable and I can't get adb to recognize my phone anymore, making it pretty close to unusable...going back to JH3 until smarter people than I can figure something out...
One more thing, this worked as advertised until I tried SRE, but just with the known issues of using a vibrant kernel in the captivate
Click to expand...
Click to collapse
I guess I'll just start flashing back to JH3 stock tomorrow morning and try either unhelpful's kernel or the stock kernel. Need my phone as an alarm so can't risk losing it before tomorrow
Kaik541 said:
I believe the only thing that would really need to be fixed (according to crop) would be to use either the stock kernel (http://koush.tandtgaming.com//test/kernel-captivate-stock.tar.md5) or Unhelpful's kernel (http://forum.xda-developers.com/showthread.php?t=762171) instead of the vibrant kernel
Click to expand...
Click to collapse
okay.. Thanks...
but, my understanding is it works fine with the kernel that is pre-included.
just finished flashing and phone booted up will update soon.
initial reaction phone is quite slow , lots of lag
just performed a factory reset now and check it out.
also it takes more time than usual while booting at the Samsung logo.
I just flashed XWJM7, then Unhelpful's kernel (v1.1 via Odin), and then a repackaged version of Vibrant-Hybrid, removing the kernel specific stuff from the update-script.
All is working fine so far.
Great job Eugene!
eugene373 said:
okay.. Thanks...
but, my understanding is it works fine with the kernel that is pre-included.
Click to expand...
Click to collapse
he said there's a bug with auto-rotation (we get this bug using the i9000 kernels too because apparently we're all about using anything but the AT&T ROM) and I'm willing to bet he didn't test the bluetooth which is also another common problem area when not using the captivate kernels
It does work fine, the only thing you need to do is turn off auto rotate =P Haven't tried GPS though. Also I just flashed the JG8 modem file to this for HSUPA lovin'
GPS starts, but I'm indoors and it's midnight so I'm not going out for a stroll to test if it gets a lock =P
This is a continuation of the "Compiling CM6 for Eris" thread - http://forum.xda-developers.com/showthread.php?t=856215. But since Team ADX has really come together on this, we are releasing it in it's new form.
Thanks to workshed for working to get the Eris on the Official CM list and merged into the main repo. And also, thanks to workshed for most of the v6 --> v7 changes to EasyDev!
This script will grab CM7 source and compile a CM7 ROM for you using the official vendor tree that is built-in to the CM source. You have the option of including Google Apps or not.
Uses:
CM source - https://github.com/CyanogenMod/android.git
Conap's CFS kernel that's built-in to CM source - https://github.com/Conap30/htc_kernel_desirec_cfs
Requirements
-------------
1) 64- bit Linux -tested on Debian, Ubuntu 10.04, Linux Mint (if you have a different flavor of linux and easydev worked for you, please let us know so we can update this list)
2) An existing Eris ROM that the script will pull the proprietary files from.
INSTRUCTIONS
1) Download the script
2) 'chmod a+x easydev-v9.sh'
3) copy it to the directory of your choice or leave it where it is
4) copy an existing ROM to the same directory (tested with GSB, but most should work)
5) run it ('sudo ./easydev-v9.sh')
Possilbe future features:
Done.
Changelog
v1 - initial release
v2 - added squisher, made 'make clean' optional, added installation of dependencies, cleaned up output
v3 - uses existing ROM to pull proprietary files, renamed to 'easydev' for case sensitive linux admins
v4 - fixed file missing from list in unzip-files.sh in vendor tree, fixed move/rename of existing ROM, change 'make clean' option to default to no instead of yes
v5 - added 'apt-get update' to refresh repo list (should install dependencies now), swapped order of extract-files and unzip-files to fix 'chmod akmd' issue, tried not to break anything else
v6 - moved questions to beginning of script, added check to only init repo the first time, added check for existing ROM, modded vendor tree to fix compile issues
v7 - removed CM6 stuff, removed kernel compilation code, removed vendor tree code, changed from CM6 to CM7, fixed path bug, added 32-bit libs to dep list
v8 - added ALL official CM devices (mostly untested), minor update to dependency installer code (4-21-11)
v9 - added an extra check for correct Java version, fixed .zip rename issue
Download links:
v7+ --> https://github.com/gnarlyc/EasyDev-Eris
NOTE: If you have issues with google setup or not being able to pass andy the android at the beginning of setup, please delete Provisions.apk for system/app you shouldn't have a problem, but just incase, this will remedy it. -workshed
I'm all over this sh*t
Oh damn, I'm excited for this. good thing I use ubuntu!
Sent from my ERIS using XDA App
this should be fun once i get my new laptop.
Nice! I will be trying this later.
This is awesome! Thanks alot. What does the 'make clean' option do?
Skrip037 said:
This is awesome! Thanks alot. What does the 'make clean' option do?
Click to expand...
Click to collapse
The make clean removes everything that has been compile so far leaving only the original source.
Skrip037 said:
This is awesome! Thanks alot. What does the 'make clean' option do?
Click to expand...
Click to collapse
It removes any previously built ROMs, etc. It's not needed every time, so I've made it optional in the next version. The problem was that sometimes the script would be broken in some way and wouldn't build a ROM. But, there's so much text displayed to the screen, it's not always easy to notice. So, I was actually flashing the same test ROM over and over instead of getting a new build...
Great work guys. Going to try it out on Arch Linux and if anyone's interested I'll give details about how to get it working there (or just modify the script to detect Arch as opposed to Ubuntu and work accordingly.
<gripe>One complaint: commands (including scripts) should *always* start with a lowercase letter </gripe>
good work gnarlyc & conap.
this sounds great and i will be trying this when i get home. I have just one question. Why would i want to run this instead of conap's rom? Both being pure CM. I see alot of the other cm6 roms have stuff themed, but conap's rom doesn't. I'm assuming this is complete pure cm without little tweaks done by devs of the respective roms. Thanks in advance.
ngc604 said:
this sounds great and i will be trying this when i get home. I have just one question. Why would i want to run this instead of conap's rom? Both being pure CM. I see alot of the other cm6 roms have stuff themed, but conap's rom doesn't. I'm assuming this is complete pure cm without little tweaks done by devs of the respective roms. Thanks in advance.
Click to expand...
Click to collapse
Some people just like to "roll their own", more or less. If you like having someone else make improvements and fix issues for you, then you'll probably want to stick with another ROM.
I would love to make my own fixes and tweaks but i dont have the knowledge nor the time to gain said knowledge. guess i will just stick with the devs roms. thanks
Very very exciting. I am installing Ubunto 10.4 now. So does EasyDev-v2 pull from the CM6 nightlies or the stable version and can we change where it pulls from for the CM6 source. This is great.
Will have to check this out later. Always wanted to understand the compile process, always to busy with other software projects. Thanks for building this resource for the rest of us.
morrisdan said:
Very very exciting. I am installing Ubunto 10.4 now. So does EasyDev-v2 pull from the CM6 nightlies or the stable version and can we change where it pulls from for the CM6 source. This is great.
Click to expand...
Click to collapse
Hmmm. Someone correct me if I'm wrong, but I'm pretty sure that this is currently grabbing 'stable'.
Code:
repo init -u git://github.com/CyanogenMod/android.git -b froyo
I'm thinking that to get the nightly, we'll have to change that to:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b master
I'll try it as soon as I can. You got me to thinking that we could add that as an option, if I understand this correctly.
Nightly vs Stable
Yes, you answered my question regarding nightly and stable. I am having fun so far. I got all the necessary packages installed. That was pretty easy using the Ubunto package manager deal. So where do I find the proprietary.zip now? I am almost there to cook this sucker up.
morrisdan said:
Yes, you answered my question regarding nightly and stable. I am having fun so far. I got all the necessary packages installed. That was pretty easy using the Ubunto package manager deal. So where do I find the proprietary.zip now? I am almost there to cook this sucker up.
Click to expand...
Click to collapse
I was apparently wrong about the "-b master" switch, but I think I mostly got it right...
Right now, you'll have to grab the files listed in the OP and zip them up into a file called 'proprietary.zip'. Then place it in the same directory that you run the script from.
I'm working on a way that you can just place an existing ROM there, and it will extract the proprietary files for you. That should be in v3.
Proprietary.zip Files
Can I download CELB Froyo 3.8 and uncompress it and do searches for those files and pull them out and zip them up?
morrisdan said:
Can I download CELB Froyo 3.8 and uncompress it and do searches for those files and pull them out and zip them up?
Click to expand...
Click to collapse
Yes, that should work fine. Here's a list with the paths -
https://github.com/Conap30/android_device_htc_desirec/blob/master/extract-files.sh
I am Developing an AOSP Froyo build for the Samsung Captivate.
It is being built from the ground up and will be missing many of the
bells and whistles that this community has grown accustom to.
NO samsung or att bloat
although that also means no samsung goodies.
I also won't be including google apps. (this can easily be added in later)
This is not a CM build. although a lot of help comes from that arena.
I feel it would be better to build from a pure AOSP base.
knowing that it was created and fully compatible with the device that
it is being used on.
from there, all the optional extras can be added.
for now it will need to be built from source
here is some reading material for those that don't know how...
http://forum.xda-developers.com/showpost.php?p=6243873&postcount=1
http://help.github.com/
http://www.cmsgs.com/mediawiki/index.php?title=Howto:_Install_the_Android_SDK
http://developer.android.com/sdk/index.html
http://source.android.com/source/index.html
some helpful sources
www.github.com/CyanogenMod
www.github.com/teamhacksung
www.github.com/cmsgs
these are just a few I had immediately available.
IF ANYONE HAS BETTER SUGGESTIONS PLEASE LET ME KNOW AND I WILL ADD IT HERE.
what doesn't work:
cell network...( probably just needed to flash a modem)
wifi...
bluetooth
sdcard (internal & external)
audio
camera
gps
accelerometer/sensors
keymapping incorrect Fixed 4/21/2011
what works:
boots up
most apps that I had installed (I didn't wipe data so it kept all my apps)
live wallpapers
crazy fast graphics (next time I will run some benchmarks to compare)
the dim settings for brightness was a TON dimmer than stock (most likely better on battery)
touchscreen very responsive/accurate.
I am looking for any assistance on this. I have a lot that I plan on doing still but I don't have a lot of time to work on it.
So the more help I get the faster it gets done.
HOW TO BUILD FROYO FOR CAPTIVATE
After reading the reference material above
I use Ubuntu 10.04 32bit at ubuntu.com
10.04 is a LTS release (long term support) so even though there are newer releases I would stick to that one.
you will need java5 NOT 6 so if you have 6 installed already you should uninstall it.
(there is a way to have both at the same time but I don't recall the steps at the moment)
Code:
sudo apt-get install sun-java5-jdk
some extra stuff you will need
Code:
sudo apt-get install git-core gnupg flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev valgrind
make sure you are in your home directory (~/ = home directory)
Code:
cd ~/
create a working directory and go into it
Code:
mkdir mydroid
cd mydroid
copy my repo to your computer
Code:
git clone git://github.com/aosp4captivate/froyo.git
once that is done. (takes a while)
download this captivate_update.zip
and this initramfs.zip
Place the captivate_update.zip in the ~/mydroid/froyo folder.
Extract the initramfs folder from the initramfs.zip into ~/mydroid/froyo/device/samsung/captivate
there seems to be a permissions issue transferring from github
for now here is a quick fix for this
Code:
cd ~/mydroid
chmod -R 777 froyo
go into the captivate folder and run unzip script
Code:
cd ~/mydroid/froyo/device/samsung/captivate
. unzip-files.sh
yes that is a period before unzip-files.sh
now from the froyo directory setup the build
Code:
cd ~/mydroid/froyo
. build/envsetup.sh
lunch
select the captivate build
then
Code:
make -j4
I use 4 because my computer can handle 4 Jobs at once
just leave the -j4 off if you have a slow single processor.
this takes a LOOOOOOOONG time
for me an initial build takes about 1 hour.
subsequent builds are faster.
the result is in ~/mydroid/froyo/out/target/product/captivate
this is just off the top of my head so again
IF YOU HAVE ANY BETTER BUILD INSTRUCTIONS PLEASE LET ME KNOW...
Hey Man before you put all of this work in, why dont you make a gingerbread asop rom. I dont see the point in putting all of this work into an outdated os
bpodz34 said:
Hey Man before you put all of this work in, why dont you make a gingerbread asop rom. I dont see the point in putting all of this work into an outdated os
Click to expand...
Click to collapse
why don't you?
bpodz34 said:
Hey Man before you put all of this work in, why dont you make a gingerbread asop rom. I dont see the point in putting all of this work into an outdated os
Click to expand...
Click to collapse
Froyo is easier at this point.. and im sure some people prefer aosp over touchwiz
a.vandelay said:
why don't you?
Click to expand...
Click to collapse
No need to be a ****, just trying to help
bpodz34 said:
Hey Man before you put all of this work in, why dont you make a gingerbread asop rom. I dont see the point in putting all of this work into an outdated os
Click to expand...
Click to collapse
I already addressed this statement in the OP...
a.vandelay said:
why don't you?
Click to expand...
Click to collapse
bpodz34 said:
No need to be a ****, just trying to help
Click to expand...
Click to collapse
please don't clutter this up with this nonsense!!!
An AOSP Froyo build would be an important step for the Captivate community, good luck with your work!
good luck, look forward to it.
Appreciate your work. Good luck.
Awesome. Looking forward to it.
Sent from my liberated Captivate via XDA App.
Good idea ! I can help with testing if you like.
Sent from my SGH-I897 using XDA App
Sign me up for testing I actually am in the minority for working GPS so I can test that
I'm glad to hear that!
I'm in for testing as well if you need help.
Good luck!
Yes please.
And I'm DTT.
Down To Test.
not a troll, or hater, or dev but I thought an asop build was not possible because the touchwiz framework is tied in to deep and no open source drivers..
best of luck to you, im here to help test if needed
Grandelama said:
An AOSP Froyo build would be an important step for the Captivate community, good luck with your work!
Click to expand...
Click to collapse
I fail to understand this statement please explain ?
g0dzilla32 said:
not a troll, or hater, or dev but I thought an asop build was not possible because the touchwiz framework is tied in to deep and no open source drivers..
Click to expand...
Click to collapse
everything is possible , not that I understnad the need for it ...
mnjm9b said:
I was going to get involved with the CM builds but
I feel it would be better to build from a pure AOSP base.
knowing that it was created and fully compatible with the device that
it is being used on.
Click to expand...
Click to collapse
Maybe im misquoting you , and dont get me wrong here , any captivate development is good , but I fail to understand why starting form CM is a bad idea and even why we need to work of ( like fork roms of ) something that was AOSP build for samsung while you already stated that :
mnjm9b said:
the only captivate roms are actually hacks from the samsung builds.
Click to expand...
Click to collapse
we woudl then be makin roms 'ripped ' from CM like sooooo many other phone ..
IMHO , your work is redoing what CM is doing for many phones already , wouldnt it be much easier / not to mention rewarding for the community to just try and build cm 'from source' for the samsung captivate ?
g0dzilla32 said:
not a troll, or hater, or dev but I thought an asop build was not possible because the touchwiz framework is tied in to deep and no open source drivers..
Click to expand...
Click to collapse
Naw, I'm running an AOSP build myself right now. While the drivers aren't opensource for the Captivate, do you remember that there is a little phone called the Nexus S that has almost IDENTICAL hardware? Everything from the Nexus is opensource (pretty sure...) and the drivers are compatible with our Captivates. The only thing that we have that they don't is the second SD Card, which is an easy hack-in, and the audience noise-canceling mic (also easy, as the Nexus 1 has the same mic/chip.)
did the OP's cappy blow up or something, the accounts disabled >,> ~inches back~ joke aside, if you do have any thing needed testing give me a shout looking for something built off the cappys them selfs to though I must admit there is a (explicit) ton of roms for nomage as it is from the vibs source that are all well and good. Good luck, well back to flashing
EDIT: This tutorial is outdated. We have a massive problem with the touchscreen
Hi to all!
I am the owner of an Archos 101 and I thought, why not port Honeycomb?
So I've used the SDK images that Google published and I've booted Honeycomb on the Archos 101. But anything works
Some screens http://twitter.com/licuende/statuses/36070541160878081
As I said, anything works. The system blocks and you can't make anything. The biggest problem is that ADB isn't working neither, so I can't debug the problems. I have tried a lot of things in the init.rc without success.
So I claim your help, Android veterans!
Here the steps for having Honeycomb on the Archos 101 (would be the same for other gen8 devices):
Install UrukDroid 0.6
Download http://megaupload.com/?d=UBC0FFZ1 and place it on /tmp
Booting into stock Android, mount SD and run these commands (replace /dev/sdc2 and /feb/sdc3 with the second and third partition of your SD card):
# cd /tmp
# mkdir sdcard
# mount /dev/sdc2 sdcard
# mkdir honeycomb
# cd honeycomb
# unzip ../honeycomb.zip
# cp -rf sdkramdisk/* ../sdcard
# cp -rf sdksystem/* ../sdcard/system
# umount ../sdcard
# cd ..
# mount /dec/sdc3 sdcard
# rm -rf sdcard/*/*
# umount sdcard
Reboot and boot the Developer Edition
Wait some time and... you'll get the unlock screen of Honeycomb!
I am a novice in Android ROMs so help is welcomed.
Thanks to deeper-blue (XDA) and @dm8tbr (OpenAOS) for helping me and $auron for UrukDroid
EDIT: Google will not release Honeycomb source code until Ice Cream release at the end of the year. That isn't good :-(
Well, even though I have absolutely 0 (i.e. none) dev skills, I thank you for getting the ball started on this much needed port.
Maybe this should be put in the Dev section though. You might get more responses from people who know what they're talking about instead of lookers-on like me.
Yeah it's true but I cannot write in the development forum due to permissions problem (I have less than 10 posts or something similar ). If an admin can move it..
Are you running stock kernel with it or one or custom? I watched some of the nook videos and it looks like they were just using some custom kernels but nothing specific.
Sent from my ADR6300 using XDA App
Can you post a picture of the device information screen showing Honeycomb? I don't mean to be a skeptic, but you can download a Honeycomb lock screen for Froyo and below Android.
I am running the stock UrukDroid kernel.
I cannot shown more screens because the system crashes and I think the touchscreen is not working. But you can test it, simply see the instructions and you'll get a beautiful locked Honeycomb Only works the lockscreen clock and the shutdown dialog that don't require touchscreen.
If we get ADB working all the porting will be easier.
Respect!
It is so good to see that developers are working on it
Good luck porting.
I wish you the best. If I knew what I was doing I would help, but I’m fairly inept at the whole ROM thing. I can troubleshoot and beta test, but that is about it.
After a lot of time talking with Archos gurus at the OpenAOS IRC channel I think the problem is in the init binary. We haven't the Honeycomb source code so we'll have to mix the Honeycomb init binary with the UrukDroid binary. Any help is appreciated
Great work! its good news that someone is trying to port this to our devices and as someone stated earlier it will probably need a custom kernel to be able to run. would it be possible to download the nooks working kernel and patch it by applying archos's drivers for say filesystem, battery, touchscreen etc
Congratulation for your work, I`m very interested in the development of the Uruk-Droid but with Honeycomb it would be much better !
I wish I knew more to help guys. I haven't even tried uruk yet cause I didn't see an advantage unless we could flash gb or honeycomb. Now I see I should have so i could be helpful. I guess I'm more of a follower than a leader when it comes to this stuff. Love it all though and appreciate the people that can create!
Sent from my ADR6300 using XDA App
Oh my god thank you for start this absolutly perfect project!!
But i haven't any help for you,sorry..
but why you don't ask $auron, if he would work with you together?
An Urukdroid release with 3.0 ? That would be simply amazing!
Hope,Hope,Hope
Sorry for my bad english, i'm from germany
dont we need the source code of honeycomb before we can even hope for a port to the archos
nimrodity said:
dont we need the source code of honeycomb before we can even hope for a port to the archos
Click to expand...
Click to collapse
that's what I thought. it will be a lot easier (despite being hard anyway) to port it when you have the sources.
Yes much easier with source code however I was running gingerbread on my dinc before it was ever released. So it can definitely be done.
chulri said:
that's what I thought. it will be a lot easier (despite being hard anyway) to port it when you have the sources.
Click to expand...
Click to collapse
Sent from my ADR6300 using XDA App
Keep up the good work. Would be much appreciated!
New SDK is finalized and ready for download: http://developer.android.com/sdk/android-3.0.html
But when will the sources be released? Git repository has only up to 2.3.x yet.
The source normaly comes after the first device gets it.
So hope that Moto holds there words and the xoom gets out soon.
Good news but my question is: how to do a porting from SDK? I wont try honeycomb on my tablet...
For developers only!! We are not supporting users yet
The instructions to build Gingerbread are on http://cmsgs.com
If you intend to develop for Captivate, you are welcome to use the instructions to build from source and test/debug/fix. This is not for the average user right now and we ask that you do not post binaries for users because things are unstable and we'd really rather not be dealing with users who've managed to screw up their phones.
There are two steps initially - first is to flash and convert filesystems, update recovery, kernel and CM7, but after that you can just install the CM7 zip if you have done another rebuild as you do development.
There is no easy way of going back to froyo - you would have to flash to stock via Odin one-click and let it blow away the filesystem etc. This is why it is for developers only - it is very alpha and you will find yourself going back and forth a lot.
Warning - this will eat your kitties and possibly your doggies and goldfish too!
-Atin
I dont mean to ruin the thead but, just want to say thanks to all devs working on cm7! And look foward to running cyanogen again after using on my htc magic a couple years ago!
Building right now...I am the excite.
good stuff.
can't wait to see the first gingerbread rom on captivate.
Trusselo said:
i hope your ROM building is better than your sentence building
Click to expand...
Click to collapse
Why the hate? Take a chill pill.....
shawn122 said:
Why the hate? Take a chill pill.....
Click to expand...
Click to collapse
Because he likes to act like a little kid in just about any thread that he can.
There's always gotta be one douchebag.
Anyways, let's keep this thread clean.
That **** isn't needed here. Building now and pretty stoked. Thanks!
I am the excite.
Im interested in trying to impliment voodoo sound. Ive been following this http://code.google.com/p/cyanogenmod7-for-samsung-galaxys/issues/detail?id=16 and it looks like it wouldnt be too hard. Any ideas on how easy or hard this really is or what i could try to do on my end to try to add from supercurio's repo? *see his nexus S thead from the link above*
Thanks in advance for all those who cook up some GREAT ROMS!!!
atinm said:
For developers only, the instructions to build Gingerbread are on http://cmsgs.com
If you intend to develop for Captivate, you are welcome to use the instructions to build from source and test/debug/fix. This is not for the average user right now and we ask that you do not post binaries for users because things are unstable and we'd really rather not be dealing with users who've managed to screw up their phones.
Warning - this will eat your kitties!,
-Atin
Click to expand...
Click to collapse
Getting errors on sync. 'Bad head' not at my computer so can't get exact error
cchant said:
Getting errors on sync. 'Bad head' not at my computer so can't get exact error
Click to expand...
Click to collapse
Try again - seems to be working here.
bamonkey said:
Im interested in trying to impliment voodoo sound. Ive been following this http://code.google.com/p/cyanogenmod7-for-samsung-galaxys/issues/detail?id=16 and it looks like it wouldnt be too hard. Any ideas on how easy or hard this really is or what i could try to do on my end to try to add from supercurio's repo? *see his nexus S thead from the link above*
Click to expand...
Click to collapse
Since all the code is on github, both for voodoo sound and for CM7, you just need kernel/android smarts to pull in the changes. Clone the repos, take what you need . . . sorry I can't help more, I haven't looked at voodoo sound but there are others who have that could help I'm sure.
cchant said:
Getting errors on sync. 'Bad head' not at my computer so can't get exact error
Click to expand...
Click to collapse
Error in line 1380 of project.py, in GetHead fd = open(path, 'rb')
I got this error.
Code:
error: revision refs/heads/master in manifests not found
I got both of those. Clean repo
ballz0iron said:
Error in line 1380 of project.py, in GetHead fd = open(path, 'rb')
Click to expand...
Click to collapse
this is an error with repo/your machine, not CM7. try syncing again after a while (possibly after a reboot) or clearing out the folder (including your .repo folder) and trying again
ih4ckback said:
I got this error.
Code:
error: revision refs/heads/master in manifests not found
Click to expand...
Click to collapse
Actually I should clarify, I got that error trying to init the GB initial flash repo. Any assistance? I need to start there since I don't have it or do I not really need it?
ih4ckback said:
Actually I should clarify, I got that error trying to init the GB initial flash repo. Any assistance? I need to start there since I don't have it or do I not really need it?
Click to expand...
Click to collapse
Sorry guys - there should be a -b gingerbread on the repo init -u git://github.com/teamhacksung/android.git -b gingerbread, I've fixed the wiki page with the instructions for the initial flash.
atinm said:
Sorry guys - there should be a -b gingerbread on the repo init -u git://github.com/teamhacksung/android.git -b gingerbread, I've fixed the wiki page with the instructions for the initial flash.
Click to expand...
Click to collapse
I seeeeeee. Syncing now lol.