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
Code:
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
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
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:
Code:
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) {
^
Last edited by QuietStorm1785; June 7th, 2012 at 09:31 AM.
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:
Code:
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
The Following User Says Thank You to joestone For This Useful Post:
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 .
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 joestone
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.
Last edited by QuietStorm1785; June 7th, 2012 at 11:37 PM.
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
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).
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 downthemachine
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.
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.
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 joestone
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.
Code:
#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:
Code:
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:
Code:
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): )
Last edited by QuietStorm1785; June 8th, 2012 at 03:52 PM.
[EDIT]
back to cm9 developement... Getting this error when activating bluetooth:
Code:
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:
Code:
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.
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
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.
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
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...
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
The Following User Says Thank You to Fishyer777 For This Useful Post:
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 Fishyer777
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
The Following User Says Thank You to QuietStorm1785 For This Useful Post:
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
If someone has helped hit theTHANKS, if you see a post that needs aMODsattention hit !REPORT
If you need a dropbox here you go! DROPBOX Join us in the Undead Den you'll have a BLOODY good time
-------------------------------------------------------------------- My Work-
[ROM] StarScream TeaM GlitcH<--CLick me!!! Wanna theme? check THISout Maybe your into Fallout New Vegas/ Fallout 3/ Skyrim, well maybe you should keep and eye on THIS
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
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.
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
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.
The Following 2 Users Say Thank You to QuietStorm1785 For This Useful Post:
Device(s): Rooted Warp, Oc'd and tweaked. Asus TF300 with dock. Galaxy S2
Carrier: Not Provided
Thanks: 32
Thanked 35 Times in 22 Posts
Quote:
Originally Posted by hroark13
If you guys only knew how much time I was spending on this stuff, you would not be impressed with what I have accomplished.
Thats all relative to perspective. To my rudimentary knowledge of these phones programming and interworkings you've done a great job hacking our warp without any help from zte.
The Following User Says Thank You to Kroegs For This Useful Post:
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
building a 3.0 kernel now, going to see if it works too. Havent tested RIL fixes yet, having problem building after RIL fixes.. gotta debug the errors and try again.
The Following 4 Users Say Thank You to QuietStorm1785 For This Useful Post:
building a 3.0 kernel now, going to see if it works too. Havent tested RIL fixes yet, having problem building after RIL fixes.. gotta debug the errors and try again.
are you just build the CAF kernel source.
to get it to work on our phone would be a lot of work, you would have to port all the drivers and stuff, I am not saying it can not be done, but I do not think that I would be able to do it
Device(s): ZTE Warp (retired)
LG Optimus G (rooted and unlocked)
Carrier: Sprint
Thanks: 2,260
Thanked 1,746 Times in 1,160 Posts
Quote:
Originally Posted by hroark13
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.
You have done an amazing job helping our community with your hard work and efforts. I appreciate everything you have sacrificed for our benefit and and their/your costs. I feel guilty and responsible for asking so much of you, if not personally, then just wishing for it. I hope you straighten everything out and come back to us whenever you can and have free time. We really appreciate all you have done for us and this amazing community.
If I had extra funds I would pay your power bill just to ensure we can have you sometime in the next month. (not saying you need it).
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
are you just build the CAF kernel source.
to get it to work on our phone would be a lot of work, you would have to port all the drivers and stuff, I am not saying it can not be done, but I do not think that I would be able to do it
I almost got the build to finish, only like 3 errors with stuff. As for the RIL, wasnt able to test it thoroughly enough to say yes it's fixed.. needed my phone for work and couldnt install my cm9.
I have a rooted warp. I dont write code but have been playing with software for years. Can test roms. I am not afraid of bricking. My second warp this month. Just tell me anything i can do. Just let me know.
Last edited by shinru2004; June 23rd, 2012 at 10:12 PM.
I have updated the ril java file . Now it is based on qualcomsharedril , and it uses nv_not_ready and nv_ready instead of ruim. It is a single file not as the old one.
On gsm it works as expected .
The new file downloadable from my github. It's name is ZTERIL so dont forget to change in system.prop.
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
well, im back, finally got a day off to make a build of cm9 with joe's new RIL in it, Hopefully it works. if not, ima do some edits to it and pray it works.
on a side note, still cant get my miui working, My old port was working, BUT had a flipped screen. still gotta play with it some more.... -.-
The Following 2 Users Say Thank You to QuietStorm1785 For This Useful Post:
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
well joe, you da man. Apparently, no more RUIM errors in adb logcat, just haveta add a few lines in build.prop to see if data works. just getting the "Needs Provisioning" error in logcat. It finds all the info for the phone in NV, which is badassness (pure and epic badassness). basically meaning... DUDES WE HAVE PROGRESS!
The Following 7 Users Say Thank You to QuietStorm1785 For This Useful Post:
Well, get this... Im getting data, but it's shutting itself off due to apn unavailability. basically meaning that it cant find the apn for boost mobile in the default apn list. BUT i like this error, means theres a chance data could work:
Code:
D/CDMA ( 583): [CdmaDCT] Data not possible. No coverage: dataState = FAILED
D/RILB ( 583): getLteOnCdmaMode=0 curVal=-1 product_type='' lteOnCdmaProductType=''
Progress being made...
The Following 3 Users Say Thank You to QuietStorm1785 For This Useful Post:
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 shinru2004
Is there a new build version of this I can check out?
coming soon, Im doing some more testing with data, ima need some help from someone who paid their bill... I couldnt do that cuz of bills and wife wanting a bit too much out of my wallet...-.-
[EDIT]
ok guys, this is like the super beta beta beta test build, practically NOTHING works, just testing data. hadta deodex it for it to load since i added a couple of things to it after building... so it's gonna take a bit to start up...
-~!-PREWARNING-!~
I am in no way to be held responsible for any damages incurred by this software. I am in no way to be held responsible for the following:
Bricking, Phone Exploding, Unexplained sounds gurgling from your buttcrack from the icycoolness of ics, Natural disasters, Nuclear Explosions, and any other problems that could occur from use of this software.
coming soon, Im doing some more testing with data, ima need some help from someone who paid their bill... I couldnt do that cuz of bills and wife wanting a bit too much out of my wallet...-.-
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
ok, currently trying to build a build with some audio fixes, and some attempts at fixing wifi. Data is still not working as of yet, still trying to figure out whats going on with data and why it's not connecting.
The Following User Says Thank You to QuietStorm1785 For This Useful Post:
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 shinru2004
This runs very slow, and launcher has to restart after you hit the home button. Is it a graphics issue?
yea it's a graphics issue, Im still working out all the kinks in it... updating opengl drivers, fixing audio, and testing the wifi fixes i did. luckily theres a phone out there alot like ours. even uses the same wifi chip. Im also working on gps too. doing too much in so little time. once i work out all those kinks, cm9 should be almost fully functional.
The Following 3 Users Say Thank You to QuietStorm1785 For This Useful Post: