Device(s): ZTE Warp (Sugar Kang), Samsung Prevail, HTC Evo Design, LG Optimus Elite, OG Droid
Carrier: Boost Mobile
Thanks: 1,157
Thanked 1,492 Times in 772 Posts
Holy crap, I got telephone to work, problem is I made so many changes I don't know what did it. It also doesn't work the first minute after boot. Anyways I copied the /lib folder from my /system dump into the prebuilt. Also copied files to the /etc, but only the files that were a different size. And then I used the system.prop from quietstorm's cwm sources. I was able to make calls and "Boost Mobile" showed up as the carrier in the notifications pull down. I'll clean out my source and find exact reason it started working
Edit:
I still can't find the specific reason, it can't find the baseband, some reason su keeps force closing. Anyways there is alot of work here
Holy crap, I got telephone to work, problem is I made so many changes I don't know what did it. It also doesn't work the first minute after boot. Anyways I copied the /lib folder from my /system dump into the prebuilt. Also copied files to the /etc, but only the files that were a different size. And then I used the system.prop from quietstorm's cwm sources. I was able to make calls and "Boost Mobile" showed up as the carrier in the notifications pull down. I'll clean out my source and find exact reason it started working
Edit:
I still can't find the specific reason, it can't find the baseband, some reason su keeps force closing. Anyways there is alot of work here
Device(s): ZTE Warp (Sugar Kang), Samsung Prevail, HTC Evo Design, LG Optimus Elite, OG Droid
Carrier: Boost Mobile
Thanks: 1,157
Thanked 1,492 Times in 772 Posts
Yep
i'll just post it. Warning! This is for development only. Do not download.
Sorry, had to put that in there since i can't pm you
anyways here's the link, Ril starts up atleast a min after booting all the way up, no 3g, and it doesn't show any signal, but i was able to make calls. *nandroid form as requested*
PM me if you want the build zip http://dl.dropbox.com/u/67621231/Cm7-tele.zip
Last edited by downthemachine; April 1st, 2012 at 06:05 PM.
The Following User Says Thank You to downthemachine For This Useful Post:
I have tried to compile it from hroark's source (fork'd it), didn't work. I removed liboemcamera, made that one line = true in boardconfig.mk, recompiled it, didn't work. I then downloaded arthur-3-30-13.zip and overrode the files from the device folder with the ones in that zip, recompiled it, and it didn't work.. I'm not sure what to do at this point. The output is generally like this, with more or less /build/core/* warnings at the beginning
Code:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=2.3.7
TARGET_PRODUCT=ZTE_Warp
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=false
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=GINGERBREAD
============================================
Checking build tools versions...
build/core/base_rules.mk:474: warning: overriding commands for target `out/target/product/arthur/system/lib/libaudioalsa.so'
build/core/base_rules.mk:474: warning: ignoring old commands for target `out/target/product/arthur/system/lib/libaudioalsa.so'
build/core/prebuilt.mk:63: warning: overriding commands for target `out/target/product/arthur/obj/lib/libaudioalsa.so'
build/core/dynamic_binary.mk:141: warning: ignoring old commands for target `out/target/product/arthur/obj/lib/libaudioalsa.so'
find: `out/target/common/docs/gen': No such file or directory
find: `out/target/common/docs/gen': No such file or directory
find: `out/target/common/docs/gen': No such file or directory
find: `out/target/common/docs/gen': No such file or directory
find: `out/target/common/docs/gen': No such file or directory
build/core/base_rules.mk:162: *** hardware/msm7k/libaudio-msm7x30: MODULE.TARGET.SHARED_LIBRARIES.libaudiopolicy already defined by device/zte/arthur/libaudio. Stop.
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=2.3.7
TARGET_PRODUCT=ZTE_Warp
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=false
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=GINGERBREAD
============================================
Checking build tools versions...
build/core/base_rules.mk:474: warning: overriding commands for target `out/target/product/arthur/system/lib/libwpa_client.so'
build/core/base_rules.mk:474: warning: ignoring old commands for target `out/target/product/arthur/system/lib/libwpa_client.so'
build/core/dynamic_binary.mk:141: warning: overriding commands for target `out/target/product/arthur/obj/lib/libwpa_client.so'
build/core/prebuilt.mk:63: warning: ignoring old commands for target `out/target/product/arthur/obj/lib/libwpa_client.so'
find: `out/target/common/docs/gen': No such file or directory
find: `out/target/common/docs/gen': No such file or directory
find: `out/target/common/docs/gen': No such file or directory
find: `out/target/common/docs/gen': No such file or directory
find: `out/target/common/docs/gen': No such file or directory
build/core/base_rules.mk:162: *** hardware/ril/libril: MODULE.TARGET.SHARED_LIBRARIES.libril already defined by device/zte/arthur/libril. Stop.
:c
edit: I'll just try your second suggestion.. by arthur source you mean download hroark's repo in zip format or arthur-3-30-13.zip?
I was getting the same thing. Hroark zipped up my current arthur folder and copied the folder containing his 3-30 source in there and renamed it arthur. That got me past all the shared library errors I was getting.
Device(s): ZTE Warp (Sugar Kang), Samsung Prevail, HTC Evo Design, LG Optimus Elite, OG Droid
Carrier: Boost Mobile
Thanks: 1,157
Thanked 1,492 Times in 772 Posts
No the update script, the one in the outputted zip from the build. I changed the system.prop to match the warp's build.prop. Those are two different things
Device(s): ZTE Warp (Sugar Kang), Samsung Prevail, HTC Evo Design, LG Optimus Elite, OG Droid
Carrier: Boost Mobile
Thanks: 1,157
Thanked 1,492 Times in 772 Posts
so as far as the radio goes, is it possible that cm7 is not mounting the radio partition correctly, or not copying the drivers correctly, now i managed to get the telephony to work, no data though, and it doesn't correctly see the baseband, which makes me think either the radio partition is not getting called at the correct point. i have printouts of all the init files and the files they call for partitions and scripts. i'll have to boot into the last build i made and make the same printouts and compare the files, maybe there is something getting missed? on the other hand, i thought that the files in /prebuilt , were just getting copied to the build. can anyone else confirm?
I can't really help much as far as the radio stuff goes. I've been doing my own builds and even tried yours and can't see much difference as far as the logs go. (though the phone at least works with yours) So I'm really at a loss as far as troubleshooting this stuff goes. Anyway, I believe that files in prebuilt are not copied to the ROM unless you specify to do so in device_arthur.mk.
i thought that the files in /prebuilt , were just getting copied to the build. can anyone else confirm?
If you are compiling CM7 from source, you have to have a .mk file that tells the cyanogenmod build environment what files you want and the paths to where you want them to go.
Device(s): ZTE Warp (Sugar Kang), Samsung Prevail, HTC Evo Design, LG Optimus Elite, OG Droid
Carrier: Boost Mobile
Thanks: 1,157
Thanked 1,492 Times in 772 Posts
Quote:
Originally Posted by JBrd400
I can't really help much as far as the radio stuff goes. I've been doing my own builds and even tried yours and can't see much difference as far as the logs go. (though the phone at least works with yours) So I'm really at a loss as far as troubleshooting this stuff goes. Anyway, I believe that files in prebuilt are not copied to the ROM unless you specify to do so in device_arthur.mk.
It's not mounting the radio stuff in ueventd.rc well in winmerge there is alot that's not done, also init.qcom.sh is completely missing which makes calls to ril(radio layer interface)
The Following User Says Thank You to downthemachine For This Useful Post:
I did add the missing init scripts, but never considered ueventd.rc. Depending on what's not loading, that could potentially cause a lot of problems. I'll look around and see what I can find.
Also, just a suggestion as far as editing device_arthur.mk if you didn't think of it already. It would be a good idea to create a new section in the file to do all your local file copies. That way it'll be easy to differentiate between hroark's source and any changes you make.
The ueventd files are part of the ramdisk so they shouldn't really need to be copied manually. I looked in /dev on my build and see the vast majority of the stuff specified in ueventd.rc so I'm not sure what to think. Anyway, it'll be there for you tomorrow.
Holy crap, I got telephone to work, problem is I made so many changes I don't know what did it. It also doesn't work the first minute after boot. Anyways I copied the /lib folder from my /system dump into the prebuilt. Also copied files to the /etc, but only the files that were a different size. And then I used the system.prop from quietstorm's cwm sources. I was able to make calls and "Boost Mobile" showed up as the carrier in the notifications pull down. I'll clean out my source and find exact reason it started working
Edit:
I still can't find the specific reason, it can't find the baseband, some reason su keeps force closing. Anyways there is alot of work here
Device(s): ZTE Warp (Sugar Kang), Samsung Prevail, HTC Evo Design, LG Optimus Elite, OG Droid
Carrier: Boost Mobile
Thanks: 1,157
Thanked 1,492 Times in 772 Posts
I'll do some tests tonight if I get time, kids and work leave me about an hour to get to it every night
Reply, part 2: (ie, edit)
Cm7 is building su itself. I'm having trouble finding rom manager, but I agree, it should be removed. Currently on another building with some changes to the /root in sources, there seems to be alot of differences in those files and what's in b08c, hroark, Woodstock posted a nandroid of b08c. You should check it out and compare
Edit 2: fell asleep after i got a good build goinging. I was at a loss on why my builds were coming out 70megs,was a issue with my sources
Sources were missing, back to normal, I really don't know what damaged it, but a repo sync fixed it
Last edited by downthemachine; April 5th, 2012 at 10:25 AM.
Device(s): ZTE Warp (Sugar Kang), Samsung Prevail, HTC Evo Design, LG Optimus Elite, OG Droid
Carrier: Boost Mobile
Thanks: 1,157
Thanked 1,492 Times in 772 Posts
Did another build changing the stuff in the /root folder and the funniest damn thing happened, boot animation is upside down, wouldn't boot, I know why, I just thought it was hilarious
well I spent a lot of time this weekend trying to get this RIL to work properly
if you do not have this setting in the build.prop CM7 treats the phone as a GSM phone
ro.telephony.default_network=4
when you get CM7 functioning as a CDMA phone with that setting and other ways of doing it, the RIL starts but you can not make phone calls
if you do not have that setting and the CM7 treats the phone as GSM, you can make phone calls
I have tried using all the available RIL classes that are built into CM7 and have unsuccessfully tried to make some new ones
I have de-complied the RIL.Java from the stock framework.jar and tried to make a new RIL class with the commands that I found in it, and I failed at this
I am almost ready to put this project to the side and maybe start trying to fix the kernel source code, so that I can try to get CM9 working
CM9 handles RIL stuff differently and may be easier
Last edited by hroark13; April 9th, 2012 at 12:40 AM.
The Following 11 Users Say Thank You to hroark13 For This Useful Post:
Has anyone tried the android source tweaks listed in this blog? According to the author, the android source is buggy too and that certain changes are required in order for the ril to build right. I made the required changes to the android source and did a build. It finished okay, but won't be able to do any further testing until later. Just curious if anyone else has already tried this.
Has anyone tried the android source tweaks listed in this blog? According to the author, the android source is buggy too and that certain changes are required in order for the ril to build right. I made the required changes to the android source and did a build. It finished okay, but won't be able to do any further testing until later. Just curious if anyone else has already tried this.
you will see the valid RIL classes you can specify in the Build.prop
//reads the system properties and makes commandsinterface
String sRILClassname = SystemProperties.get("ro.telephony.ril_class");
Log.i(LOG_TAG, "RILClassname is " + sRILClassname);
if("samsung".equals(sRILClassname))
{
Log.i(LOG_TAG, "Using Samsung RIL");
sCommandsInterface = new SamsungRIL(context, networkMode, cdmaSubscription);
} else if ("htc".equals(sRILClassname)) {
Log.i(LOG_TAG, "Using HTC RIL");
sCommandsInterface = new HTCRIL(context, networkMode, cdmaSubscription);
} else if("lgestar".equals(sRILClassname)) {
Log.i(LOG_TAG, "Using LGE Star RIL");
sCommandsInterface = new LGEStarRIL(context, networkMode, cdmaSubscription);
} else if ("semc".equals(sRILClassname)) {
Log.i(LOG_TAG, "Using Semc RIL");
sCommandsInterface = new SemcRIL(context, networkMode, cdmaSubscription);
} else if ("lgeqcom".equals(sRILClassname)) {
Log.i(LOG_TAG, "Using LGE Qualcomm RIL");
sCommandsInterface = new LGEQualcommRIL(context, networkMode, cdmaSubscription);
} else if ("mototegra".equals(sRILClassname)) {
Log.i(LOG_TAG, "Using Motorola Tegra2 RIL");
sCommandsInterface = new MotoTegraRIL(context, networkMode, cdmaSubscription);
} else if ("motow3g".equals(sRILClassname)) {
Log.i(LOG_TAG, "Using Motorola Wrigley 3G RIL");
sCommandsInterface = new MotoWrigley3GRIL(context, networkMode, cdmaSubscription);
} else {
sCommandsInterface = new RIL(context, networkMode, cdmaSubscription);
CM9 does this differently than CM7, so this info is for CM7 only
So if you want to add a new RIL class you would need to edit the PhoneFactory.java and add a file BlahBlahRIL.java
But there must be something else you need to do, because when I tried doing this I was getting symbol errors during the compile
I tried modding the QualcommNoSimReadyRIL.java with some of the stuff I found in the de-compiled RIL.java that I pulled from the stock framerwork.jar as show in the link below
as you can see de-compiled java files are pretty useless, but you can look at them and get a hint of what is going on
I was trying to add the RIL_REQUEST and RIL_UNSOL commands and make my own RIL class, but as I mentioned before I failed at this, CM7 would not finish compiling and would stop when it got to that file and complain about symbols and other crap
I am not a programmer and do not know any programming languages, so this stuff baffles me
Last edited by hroark13; April 9th, 2012 at 07:46 PM.
The Following 2 Users Say Thank You to hroark13 For This Useful Post:
I have some java experience, as I have done a bit programming in my life (all the way to learning ASM fundamentals). I may be rusty but I think I can give it ago. I do remember most java syntax of what I learned from it. What is it your trying to figure out? What is your basic problem and where is it happening (so I know where to look)? There's a significant chance however that I may not be able to figure it out but I will apply logical reasoning to try to figure out whats happening in here.
Great explanation... Have a couple possibly stupid questions. If stock uses the RIL.java, shouldn't CM7 be able to use it as well? (or is the issue that Zte customized RIL.java so it is different than the CM7 source)
Second thing is related to creating custom classes. Did you try using a known-good/unmodified classfile when creating a custom class just to see if the build finishes? If you copy/rename an existing .java file (unmodified) and associate it in PhoneFactory.java as a new class, the build *should* finish okay. Just a test to see whether it's something missing in class creation process or an issue with the contents of the classfile itself.
Great explanation... Have a couple possibly stupid questions. If stock uses the RIL.java, shouldn't CM7 be able to use it as well? (or is the issue that Zte customized RIL.java so it is different than the CM7 source)
Second thing is related to creating custom classes. Did you try using a known-good/unmodified classfile when creating a custom class just to see if the build finishes? If you copy/rename an existing .java file (unmodified) and associate it in PhoneFactory.java as a new class, the build *should* finish okay. Just a test to see whether it's something missing in class creation process or an issue with the contents of the classfile itself.
The RIL.java from stock and RIL.java for CM7 is different, and they have different RIL commands to talk to the modem and stuff, the RIL.java from stock was made by ZTE but should be similar to other Qualcom based phones RIL.java
You can add an entry to the PhoneFactory.java for say ztewarp and then copy one of the other class files, but you do have to change the section at the top of the file that looks like this
public class SamsungRIL extends RIL implements CommandsInterface {
I have some java experience, as I have done a bit programming in my life (all the way to learning ASM fundamentals). I may be rusty but I think I can give it ago. I do remember most java syntax of what I learned from it. What is it your trying to figure out? What is your basic problem and where is it happening (so I know where to look)? There's a significant chance however that I may not be able to figure it out but I will apply logical reasoning to try to figure out whats happening in here.
well the first thing I would ask you to look at, is to see if you can get the RIL.java from the stock ROM, so that it can be used in CM7 as a RIL class
can you de-compile the stock RIL.java a better way that I did ? so it is more useable
This is everything I know about CDMA and Sprint. This is from my work on ICS for the Samsung Intercept. Some of this won't apply but some might be helpful.
Device(s): Samsung Galaxy Prevail- running cm9
HTC Inspire 4g- running Miui
Zte Warp- Stock B08c rom, working o
Carrier: Boost Mobile
Thanks: 68
Thanked 320 Times in 106 Posts
did u try using the original system.prop that came with the phone? Im building cm7 using your source as I type to test that out, if that doesnt work ima try a few other things. Im still trying to figure out why the kernel isnt booting, I got about as far as you did hroark. Wouldnt mount partitions, was able to start adb.. etc etc. mind racking crap here..
did u try using the original system.prop that came with the phone? Im building cm7 using your source as I type to test that out, if that doesnt work ima try a few other things. Im still trying to figure out why the kernel isnt booting, I got about as far as you did hroark. Wouldnt mount partitions, was able to start adb.. etc etc. mind racking crap here..
yeah, I have tried everything
this is my latest cm7 source, some minor corrections, and all the pre built files are B06, the B06 RIL files seem to start quicker, and also BlueToothe works
Device(s): Samsung Galaxy Prevail- running cm9
HTC Inspire 4g- running Miui
Zte Warp- Stock B08c rom, working o
Carrier: Boost Mobile
Thanks: 68
Thanked 320 Times in 106 Posts
Quote:
Originally Posted by hroark13
yeah, I have tried everything
this is my latest cm7 source, some minor corrections, and all the pre built files are B06, the B06 RIL files seem to start quicker, and also BlueToothe works
Device(s): Samsung Galaxy Prevail- running cm9
HTC Inspire 4g- running Miui
Zte Warp- Stock B08c rom, working o
Carrier: Boost Mobile
Thanks: 68
Thanked 320 Times in 106 Posts
Quote:
Originally Posted by hroark13
were you able to get to adb, before, or did you use my new test ramdisk with your zImage
I was able to do it before, I did the same edits to init.arthur.rc that you did. I really dont understand why it wont mount partitions at boot. I didnt do a mount command tho, so didnt really test. I feel like building the kernel again and checking if the default config has ext4 modules built in. Last time I built the kernel using the .config that was on the phone, it didnt have the ext4 modules selected. That might be the issue, but I really dont know. I wonder if sebastian got a hold of zte, cuz that would really help right about now.
Last edited by QuietStorm1785; April 17th, 2012 at 03:17 AM.