Root [Boost Mobile] CM9 for Warp Development thread

[hroark13]

I have been messing around and copied all the mentioned files from your smarttab_common folder and it is still booting and I am getting this in the log file, this is a bit farther than what I was getting trying to use the libs from my stock GB ROM

I/CameraService(  104): CameraService started (pid=104)

E/CameraHAL(  104): CameraHAL_GetNum_Cameras:

D/CameraHAL(  104): CameraHAL_GetNum_Cameras: loading libcamera at 0xb000e9c4

I/QualcommCameraHardware(  104): getCameraInfo: IN

I/QualcommCameraHardware(  104): getCameraInfo: loading libqcamera at 0xb000eadc

E/mm-camera(  104): mm_camera_get_camera_info: controlfd is invalid No such file or directory

I/QualcommCameraHardware(  104): getCameraInfo: numOfCameras = 0

V/QualcommCameraHardware(  104): getCameraInfo: dlclose(libqcamera)

I/QualcommCameraHardware(  104): getCameraInfo: OUT

D/CameraHAL(  104): CameraHAL_GetNum_Cameras: numCameras:0

 

[QuietStorm1785]

sorry i been gone for a bit hroark, wife ended up washing my phone and i hadta let it sit in rice a few days to get it working again.... couldnt test my RIL test build, I did some edits to the cdmaservicestatetracker.java file that i did on cm7 to get the lgeqcom ril class working there.. it was a simple edit, but i think it may work on cm9 too. the java files are alot alike, just different imports.

[EDIT]

Upon trying to build the zte ril classes under the cyanogenmod ics branch, I noticed that there were alot of missing imports in the ztequalcomm ril classes that were made. Also noticed that in hardware/qcom/media, there were quite a few build errors, so to fix those I deleted the hardware/qcom/media folder, and copied the one from the CAF source, and it builds fine now. for the ztequalcomm ril imports, I copied the imports from the LGEStar ril class, and a couple from the LGEQualcomm ril class too, here are the imports that are missing for those who wanna know:

import android.text.TextUtils;

and

import android.os.SystemProperties;

these will fix these errors during building:

frameworks/base/telephony/java/com/android/internal/telephony/ZTEQualcommRIL.java:911: cannot find symbol
symbol  : variable SystemProperties
location: class com.android.internal.telephony.ZTEQualcommRIL
        dataCall.dnses[0] = SystemProperties.get("net."+dataCall.ifname+".dns1");
;
                                      ^
frameworks/base/telephony/java/com/android/internal/telephony/ZTEQualcommRIL.java:948: cannot find symbol
symbol  : variable SystemProperties
location: class com.android.internal.telephony.ZTEQualcommRIL
        if (SystemProperties.get("ro.cm.device").indexOf("e73") == 0) {
            ^

 

[joestone]

sorry i been gone for a bit hroark, wife ended up washing my phone and i hadta let it sit in rice a few days to get it working again.... couldnt test my RIL test build, I did some edits to the cdmaservicestatetracker.java file that i did on cm7 to get the lgeqcom ril class working there.. it was a simple edit, but i think it may work on cm9 too. the java files are alot alike, just different imports.

[EDIT]

Upon trying to build the zte ril classes under the cyanogenmod ics branch, I noticed that there were alot of missing imports in the ztequalcomm ril classes that were made. Also noticed that in hardware/qcom/media, there were quite a few build errors, so to fix those I deleted the hardware/qcom/media folder, and copied the one from the CAF source, and it builds fine now. for the ztequalcomm ril imports, I copied the imports from the LGEStar ril class, and a couple from the LGEQualcomm ril class too, here are the imports that are missing for those who wanna know:

import android.text.TextUtils;

and

import android.os.SystemProperties;

these will fix these errors during building:

frameworks/base/telephony/java/com/android/internal/telephony/ZTEQualcommRIL.java:911: cannot find symbol
symbol  : variable SystemProperties
location: class com.android.internal.telephony.ZTEQualcommRIL
        dataCall.dnses[0] = SystemProperties.get("net."+dataCall.ifname+".dns1");
;
                                      ^
frameworks/base/telephony/java/com/android/internal/telephony/ZTEQualcommRIL.java:948: cannot find symbol
symbol  : variable SystemProperties
location: class com.android.internal.telephony.ZTEQualcommRIL
        if (SystemProperties.get("ro.cm.device").indexOf("e73") == 0) {
            ^

It is strange , I just copy the two files to my repo (ICS branch -b ics , last synced on 06.05) and it compiles without issues. For me it seems the error comes from an older version of datacall . Do you use latest zte ril files , because lge and qualcomm ril files were changed in cm9 and I made some modification not to extend them.Now zte ril files should only extend ril.java.
"public class ZTEQualcommRIL extends RIL implements CommandsInterface {"

It is in LGE ril to detect the model "if (SystemProperties.get("ro.cm.device").indexOf("e73") == 0) {" , to use different datacall setup for it. Because we have our own datacall it is not needed .
About media compile errors , you will find my modified header files under bionic and device include folder . I pushed my changes to github.

If datacall is not working You should push log entries to the datacall routines to see what happens .
It should look like this ( I forgot to remove )
if (RILJ_LOGD) riljLog("responseSetupDataCall type(unknwn5) = " + unknown5);
and dont forget to turn on logging by enabling verbose logging in ril.java and in zte ril java files
boolean RILJ_LOGD = true;
boolean RILJ_LOGV = true;

I changed logd_write.c too to see the messages in ddms and filtered them by tag RILJ

 

[joestone]

I have been messing around and copied all the mentioned files from your smarttab_common folder and it is still booting and I am getting this in the log file, this is a bit farther than what I was getting trying to use the libs from my stock GB ROM

Sorry for the late answer , I paused the BT and camera for a short time , because I work on twrp recovery to the tab. It is a nice graphical recovery and it can handle both the internal and external sd of the tab as install from and backup to location .

 

[QuietStorm1785]

Sorry for the late answer , I paused the BT and camera for a short time , because I work on twrp recovery to the tab. It is a nice graphical recovery and it can handle both the internal and external sd of the tab as install from and backup to location .

yea im working on twrp for the warp right now too, thanks to shabby for referring me to someone who knows how to debug it.. my only problem is programming the BOARD_HAS_FLIPPED_SCREEN function into it.... from what the makers of twrp told me, their function doesnt have support for 32 bit interfaces, sooo instead of flipping the whole screen correctly, it only flips half of the screen, the other half remains upside down and in wierd colors....

[EDIT]

another problem I had with RIL, is that the cdma service state tracker keeps saying that its disabling data due to ruim not being loaded... which is confusing considering I have NV only setup in the build.prop in order to avoid the NV being wiped when messing with settings.

 

[Deleted User]

Well I did some research on ruim( removable user identity module, ie sim card), basically a sim card for cdma that allows you to switch between cdma and gsm cards. So basically it's looking for all the specific data on what network type, cdma or gsm, then all the specifics from there. Why this wipes the nam, no clue. Our phone stores all the information in the nv(non volatile memory).

 

[QuietStorm1785]

Well I did some research on ruim( removable user identity module, ie sim card), basically a sim card for cdma that allows you to switch between cdma and gsm cards. So basically it's looking for all the specific data on what network type, cdma or gsm, then all the specifics from there. Why this wipes the nam, no clue. Our phone stores all the information in the nv(non volatile memory).

because i guess it writes information to the nam in the process, just taking ruim off the build.prop removes the risk of wiping nam so i did it, ruim isnt necessary since we dont have ruim. Whats wierd is, even when taking ruim off the build.prop, cdmasst and cdmadst look for ruim to connect for data. (CdmaServiceStateTracker.java and CdmaDataStateTracker.java for those who wanna know what Im talking about)

when running the rom, hook your phone up to pc, then open a command prompt and type adb logcat -b radio and you will see what Im talking about (for the people who dont know). Linux is preferred for logcatting in my opinion because you can set the scrolling to unlimited and track the entire logcat from start to finish. Cant do that in windows i think.

 

[joestone]

because i guess it writes information to the nam in the process, just taking ruim off the build.prop removes the risk of wiping nam so i did it, ruim isnt necessary since we dont have ruim. Whats wierd is, even when taking ruim off the build.prop, cdmasst and cdmadst look for ruim to connect for data. (CdmaServiceStateTracker.java and CdmaDataStateTracker.java for those who wanna know what Im talking about)

when running the rom, hook your phone up to pc, then open a command prompt and type adb logcat -b radio and you will see what Im talking about (for the people who dont know). Linux is preferred for logcatting in my opinion because you can set the scrolling to unlimited and track the entire logcat from start to finish. Cant do that in windows i think.

on windows you can scroll if using ddms , or if you run logcat to save messages to a file . adb shell logcat -b radio > radiolog.txt
it will log until you dont break it with ctrl+c.

Twrp is working fine on smarttab.

 

[QuietStorm1785]

on windows you can scroll if using ddms , or if you run logcat to save messages to a file . adb shell logcat -b radio > radiolog.txt
it will log until you dont break it with ctrl+c.

Twrp is working fine on smarttab.

#ifdef BOARD_HAS_FLIPPED_SCREEN
    /* flip buffer 180 degrees for devices with physicaly inverted screens */
    unsigned int i;
    for (i = 1; i < (vi.xres * vi.yres); i++) {
        unsigned short tmp = gr_mem_surface.data[i];
        gr_mem_surface.data[i] = gr_mem_surface.data[(vi.xres * vi.yres * 2) - i];
        gr_mem_surface.data[(vi.xres * vi.yres * 2) - i] = tmp;
    }
#endif

this bit of code in twrp doesnt work on the warp, the warp comes stock with a flipped screen. I have to figure out a way to flip the screen on the warp and make it work in twrp, Im having that same problem in cwm for cm9 too, the screen is flipped and the Board_has_Flipped_screen flag aint working... being a pain in my ass too.....

[EDIT]
back to cm9 developement... Getting this error when activating bluetooth:

E/BluetoothEventLoop.cpp(  171): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)

That is stopping bluetooth service from starting, after that error, I get this:

E/bluetooth_common.cpp(  171): dbus_func_args_timeout_valist: D-Bus error in Register: org.freedesktop.DBus.Error.UnknownMethod (Method "Register" with signature "ss" on interface "org.bluez.NetworkServer" doesn't exist
E/bluetooth_common.cpp(  171): )

 

[ztewarpcm7]

does anyone have a more stable version everytime i play music and press home it exits out of apollo app

 

[joestone]

[EDIT]
back to cm9 developement... Getting this error when activating bluetooth:

E/BluetoothEventLoop.cpp(  171): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)

That is stopping bluetooth service from starting, after that error, I get this:

E/bluetooth_common.cpp(  171): dbus_func_args_timeout_valist: D-Bus error in Register: org.freedesktop.DBus.Error.UnknownMethod (Method "Register" with signature "ss" on interface "org.bluez.NetworkServer" doesn't exist
E/bluetooth_common.cpp(  171): )

I have the same error . Replacing bluetoothd , libbluetoothd , libbluetooth from compiled one to the stock one does not help even if the plugins are replaced too. Only the compiled brcm_patchram_plus is working and loads the hcd file , but on tab it needs an extra option :
--no2bytes beside the stock ones.

 

[ztewarpcm7]

every apps exits out when home button is pressed and mass storage isnt working are the new builds that you guys are working on have these fixes

 

[Deleted User]

every apps exits out when home button is pressed and mass storage isnt working are the new builds that you guys are working on have these fixes

It's a development test build. Not in anyway a release build

 

[ztewarpcm7]

no i am aware of that i just wanted to know if there is a test build thats more updated than the one in the op

 

[QuietStorm1785]

no there arent any, we are currently working on getting the important stuff working, apps closing when home button is pressed isnt exactly as important to us as getting RIL, wifi, bluetooth working. Im trying on wifi and RIL, so's joe, hroark is working on camera, and bluetooth is up in the air right now.

 

[DragonDGG]

Are the issues with the oc kernal or just the stock one hroark is making

 

[jetx2x]

I have a question.... if I were to take the cm9 dialer and replace it with stock would it work? I'm working on theming my phone from top to bottom.

Sent from my N860 using Tapatalk 2 Beta-5

 

[Kroegs]

CM9 Code Freeze Has Started | CyanogenMod

They are saying they are still working on device support. Possibly a good thing for warp? I know they have many ics native handsets to trudge through.

 

[QuietStorm1785]

Well, I started working on the ics_release branch of cm9, found that a bit more is working, for example the language for keypad.... found out problem with the ZTEQualcommRIL, it's looking for RUIM in the ril code, not NV. The warp has NO ruim, so Im replacing all the references to RUIM with NV like RUIM_NOT_READY with NV_NOT_READY and RUIM_READY with NV_READY. I also have to figure out a way to make my RIL code look for the NV.

[EDIT]
building now to see if my edits to the ztequalcommril.java worked. I hope it did, because if so.. thatd be badass...

 

[Fishyer777]

Well, I started working on the ics_release branch of cm9, found that a bit more is working, for example the language for keypad.... found out problem with the ZTEQualcommRIL, it's looking for RUIM in the ril code, not NV. The warp has NO ruim, so Im replacing all the references to RUIM with NV like RUIM_NOT_READY with NV_NOT_READY and RUIM_READY with NV_READY. I also have to figure out a way to make my RIL code look for the NV.

[EDIT]
building now to see if my edits to the ztequalcommril.java worked. I hope it did, because if so.. thatd be badass...

I thought this thread was abandoned, THANK YOU for the update. I am working on learning how do work on this kind of stuff and should hopefully be able to help out soon

 

[QuietStorm1785]

I thought this thread was abandoned, THANK YOU for the update. I am working on learning how do work on this kind of stuff and should hopefully be able to help out soon

Im not abandoning this project, I want to see ICS on the warp. Just been busy with work, family. As for learning this stuff, GOOGLE WAS MY FRIEND... lol I started this with NO experience. Just waiting on this build to finish to see if my edits worked on fixing audio, RIL, and wifi. If they do, all that will be left is bluetooth, and camera, and a few fixes to make UI faster, and to stop the applications from crashing. Probably some kernel pmem issues to work out.. I might just try adding some stuff to the CAF 3.0 kernel source and pray it works... lol

 

[StarScream2109]

Im not abandoning this project, I want to see ICS on the warp. Just been busy with work, family. As for learning this stuff, GOOGLE WAS MY FRIEND... lol I started this with NO experience. Just waiting on this build to finish to see if my edits worked on fixing audio, RIL, and wifi. If they do, all that will be left is bluetooth, and camera, and a few fixes to make UI faster, and to stop the applications from crashing. Probably some kernel pmem issues to work out.. I might just try adding some stuff to the CAF 3.0 kernel source and pray it works... lol

Keep up the good work

 

[Fishyer777]

Im not abandoning this project, I want to see ICS on the warp. Just been busy with work, family. As for learning this stuff, GOOGLE WAS MY FRIEND... lol I started this with NO experience. Just waiting on this build to finish to see if my edits worked on fixing audio, RIL, and wifi. If they do, all that will be left is bluetooth, and camera, and a few fixes to make UI faster, and to stop the applications from crashing. Probably some kernel pmem issues to work out.. I might just try adding some stuff to the CAF 3.0 kernel source and pray it works... lol

Can you give me a hint at where I need to start I have no idea what to begin looking up

 

[hroark13]

I thought this thread was abandoned, THANK YOU for the update. I am working on learning how do work on this kind of stuff and should hopefully be able to help out soon

I am not abandoning this either, the problem is I was spending so much time on Android stuff, with the kernel, CM7 and CM9 that I have started neglecting other areas of my life.

I am taking a break for a little while, but will resume it again soon.

If you guys only knew how much time I was spending on this stuff, you would not be impressed with what I have accomplished.

 

[QuietStorm1785]

I am not abandoning this either, the problem is I was spending so much time on Android stuff, with the kernel, CM7 and CM9 that I have started neglecting other areas of my life.

I am taking a break for a little while, but will resume it again soon.

If you guys only knew how much time I was spending on this stuff, you would not be impressed with what I have accomplished.

Same here... wife was getting pissed at me... lol. BTW, I may have fixed the data issues, still running tests to see if i did. I'll post the diff of my edits later when it is all confirmed.