-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [Boost Mobile] For Discussion of Development for CM7 Only
- Thread starter hroark13
- Start date
-
- Tags
- zte warp (n860)
D
Deleted User
Guest
I'm having an issue with the build.
It says wpa_ctrl.h no such file, here's a pic
I'm a little lost, I get this everytime
It says wpa_ctrl.h no such file, here's a pic
I'm a little lost, I get this everytime
D
Deleted User
Guest
Nevermind 
D
Deleted User
Guest
Build completed, would not boot. Really tired so bear with me. I just noticed that hroark's build said 7_2 on it, my repository is gingerbread, not gingerbread 7.2. I'm still wondering if it's maybe the kernel that was in the source?
Also my update-script looked different than hroark's, I tried the way it was compiled, I tried using hroark's update-script, then again with his boot.img, I used the source from the zip that was posted. Any ideas?
Also my update-script looked different than hroark's, I tried the way it was compiled, I tried using hroark's update-script, then again with his boot.img, I used the source from the zip that was posted. Any ideas?
remove the libomecamera from the arthur folder
and change this in the boardconfig.mk
USE_CAMERA_STUB:=false
to
USE_CAMERA_STUB:=true
the update script I usually edit to format data and cache and I add all those messages in it
I hope you guys realize that I am trying to get hardware working
so my source is changing a lot
sometimes those changes cause more issues
it is really a lot of testing
try this driver, see if ti works, blah blah blah
I have stopped focusing on hardware like camera and stuff because I believe the major thing we are going to need to overcome is the RIL
and if we can not get the RIL working, then there is no point on doing anything else
so my source is changing a lot
sometimes those changes cause more issues
it is really a lot of testing
try this driver, see if ti works, blah blah blah
I have stopped focusing on hardware like camera and stuff because I believe the major thing we are going to need to overcome is the RIL
and if we can not get the RIL working, then there is no point on doing anything else
D
Deleted User
Guest
So libomecamera is prob my issue too?
D
Deleted User
Guest
I totally don't blame you for any issues
, you have helped us enormously! I'm just wanting to learn, and I'd hope my questions aren't a bother! Thanks again hroark
I totally don't blame you for any issues
no bother at all
I am just having issues using git hub
and I am not very good at version tracking, because I change a lot of things and test them to see if they work
I will put updated source on github that complies and boots this weekend
it will still have the problem with hardware not working
but it will boot
for now you if you make those changes I suggested it should compile and boot
D
Deleted User
Guest
Well as for my last build, it got past the green android logo, but wouldn't logcat, so I'll wait for the updated source 
Well as for my last build, it got past the green android logo, but wouldn't logcat, so I'll wait for the updated source
I did a build with this source and it compiles and boots
arthur-3-30-13.zip
let me know if it does not for you
D
Deleted User
Guest
Builds and boots! Thanks hroark!
Yup, worked for me too. FINALLY got to see what CM7 looks like... lol
I know BT and such aren't high priority ATM, but I found a couple files that are not in the arthur source that are called by init scripts. (listed below) I'll add them to my local source, but thought I'd mention them in case anyone else wants to add them as well.
/system/bin/hci_qcomm_init needed by: init.qcom.bt.sh
/system/bin/btwlancoex needed by: init.qcom.coex.sh
/system/bin/fm_qsoc_patches needed by: init.qcom.fm.sh
FINALLY got to see what CM7 looks like... lolI know BT and such aren't high priority ATM, but I found a couple files that are not in the arthur source that are called by init scripts. (listed below) I'll add them to my local source, but thought I'd mention them in case anyone else wants to add them as well.
/system/bin/hci_qcomm_init needed by: init.qcom.bt.sh
/system/bin/btwlancoex needed by: init.qcom.coex.sh
/system/bin/fm_qsoc_patches needed by: init.qcom.fm.sh
Yup, worked for me too.
I did have a ROM in the OP from day 1
D
Deleted User
Guest
Lol
the installer script the cm7 generates does not set all the needed permissions
I have created some CMW installer templates for CM7, stock and other things
I had to add these lines
set_perm(0, 0755, 0755, "/system/etc/init.qcom.bt.sh");
set_perm(0, 0755, 0755, "/system/etc/init.qcom.coex.sh");
set_perm(0, 0755, 0755, "/system/etc/init.qcom.fm.sh");
set_perm(0, 0755, 0755, "/system/etc/init.qcom.post_boot.sh");
set_perm(0, 0755, 0755, "/system/etc/init.qcom.sdio.sh");
set_perm(0, 0755, 0755, "/system/etc/init.qcom.wifi.sh");
http://androidforums.com/warp-all-t...ler-templates-updated-3-31-a.html#post4122690
you may want to replace the updater-script on any ROMS you compile
I have created some CMW installer templates for CM7, stock and other things
I had to add these lines
set_perm(0, 0755, 0755, "/system/etc/init.qcom.bt.sh");
set_perm(0, 0755, 0755, "/system/etc/init.qcom.coex.sh");
set_perm(0, 0755, 0755, "/system/etc/init.qcom.fm.sh");
set_perm(0, 0755, 0755, "/system/etc/init.qcom.post_boot.sh");
set_perm(0, 0755, 0755, "/system/etc/init.qcom.sdio.sh");
set_perm(0, 0755, 0755, "/system/etc/init.qcom.wifi.sh");
http://androidforums.com/warp-all-t...ler-templates-updated-3-31-a.html#post4122690
you may want to replace the updater-script on any ROMS you compile
Sure, but I chose not to use that as I wanted to build it myself. (regardless of the fact that you really did all the hard work to put together a working source) My primary concern has always been to have a working source that can be used as a baseline to test changes against. So actually seeing CM7 was a secondary concern, but still good to see after all the hours spent working on this.
Yup, worked for me too.
I know BT and such aren't high priority ATM, but I found a couple files that are not in the arthur source that are called by init scripts. (listed below) I'll add them to my local source, but thought I'd mention them in case anyone else wants to add them as well.
/system/bin/hci_qcomm_init needed by: init.qcom.bt.sh
/system/bin/btwlancoex needed by: init.qcom.coex.sh
/system/bin/fm_qsoc_patches needed by: init.qcom.fm.sh
i put those file in the patch file in the second post a while back
i have tried adding then to the source and having them copy during the compile, but CM7 seems to overwrite them with its own version and I have to use the patch update anyway
I just checked the md5sums of those 3 files before & after my build and they were the same. (modified device_arthur.mk to do the copy) Now I didn't do the make clean or make clobber steps though as I was just adding some additional files to test. Would that make any difference?
Couple questions...
Anyone have ideas as to why "ls" doesn't work when using adb shell from within CM7 unless you specify the full path? (/system/xbin/ls) Tried a couple other xbin files and they seem fine.
Other thing is, I see an error in logcat stating that /data/system/entropy.dat is missing and causes the entropy service to fail. However, it is in the correct spot on the phone so I'm assuming this is a permissions issue. Currently it's set r/w for system (user) only. Can I assume that the errors are being caused because root needs access instead? Not really asking about this case so much, but whether this is the correct logic when troubleshooting these types of errors.
Anyone have ideas as to why "ls" doesn't work when using adb shell from within CM7 unless you specify the full path? (/system/xbin/ls) Tried a couple other xbin files and they seem fine.
Other thing is, I see an error in logcat stating that /data/system/entropy.dat is missing and causes the entropy service to fail. However, it is in the correct spot on the phone so I'm assuming this is a permissions issue. Currently it's set r/w for system (user) only. Can I assume that the errors are being caused because root needs access instead? Not really asking about this case so much, but whether this is the correct logic when troubleshooting these types of errors.