Guest boogyboo Posted August 6, 2014 Report Share Posted August 6, 2014 hi i'm stayboogy@github and androidforums (sorry for all the questions but i'm not a beginner and i'm trying to get to some straight fact regarding the device i just bought to dev with) i just ordered an Open C, US version, and trying to figure out exactly what the Open C is so that i can start gathering the sources i need to start building for it i've already got the latest B2G source ready to go but i'd rather make my own build of jb/kitkat. i realize B2G for the open c is kitkat based, but i'm interested in backporting to the device as well... i've only seen two people working with this device and KonstaT is one of them. the zte kernel source link refuses to download for me and i've yet to find a relialble mirror. are the kis 3, the avail/roamer 2, and the open c built on the same platform? anyone have an exact mirror of the zte open c kernel source? will generically building for msm8x10, kernel and otherwise, work? i've seen it mentioned somewhere that the open c didn't have a proximity sensor, but the spec sheet says otherwise. does this mean the proximity driver source is missing from the msm8610 kernel source on github or is it missing in the zte source too? what are the device specific files i will need for building kitkat for the device? any specific branch i need to be working with and any specific proprietary vendor sources i need to obtain in the process? thanks in advance for the information. And let me say, I'm admirer of the work i've seen come from several of you who frequent the boards here. sebastion404 and konstat in particular. Link to comment Share on other sites More sharing options...
Guest hecatae Posted August 6, 2014 Report Share Posted August 6, 2014 the kernel is here on Konstat's github https://github.com/KonstaT/android_kernel_zte_msm8610 The Virgin UK Stock Rom mentions a proximity sensor , and has the configuration files for it, the Generic UK one does not. Yet to test to see if it makes the proximity sensor work. B2G for the Open C is JB 4.3 based. Link to comment Share on other sites More sharing options...
Guest KonstaT Posted August 6, 2014 Report Share Posted August 6, 2014 are the kis 3, the avail/roamer 2, and the open c built on the same platform? No, Open C (Kis 3 is the same device, different OS) has msm8210 chipset which is a modern Qualcomm budget platform. ZTE roamer2/avail/etc have ancient and EOL'ed msm7x2xa chipset. anyone have an exact mirror of the zte open c kernel source? There's no Open C (Jelly Bean based Firefox OS) source. Only for Kis 3 (Android KitKat). Lifting it from my github from commit 02f2259c787cf2e81f9e0e97c1f4ece0bf6e3215 is exactly what you'd get downloading it from ZTE site. https://github.com/KonstaT/android_kernel_zte_msm8610/archive/02f2259c787cf2e81f9e0e97c1f4ece0bf6e3215.zip will generically building for msm8x10, kernel and otherwise, work? No, it never does on any Android device. There's always modifications that the OEM/ODM has made. i've seen it mentioned somewhere that the open c didn't have a proximity sensor, but the spec sheet says otherwise. does this mean the proximity driver source is missing from the msm8610 kernel source on github or is it missing in the zte source too? Device doesn't have a proximity sensor. There's three or four proximity/als sensor drivers included in the ZTE kernel source but none of them are even compiled for the device. Doesn't help much when there's no hardware on board. :P what are the device specific files i will need for building kitkat for the device? any specific branch i need to be working with and any specific proprietary vendor sources i need to obtain in the process? Yes, you need to prepare both device and vendor trees if you're planning to do this right now. I have already all device specific trees set up and I will continue to work on this as soon as I receive my device (it should be waiting for me in the post office when I get back home next week :)) Link to comment Share on other sites More sharing options...
Guest boogyboo Posted August 6, 2014 Report Share Posted August 6, 2014 (edited) No, Open C (Kis 3 is the same device, different OS) has msm8210 chipset which is a modern Qualcomm budget platform. ZTE roamer2/avail/etc have ancient and EOL'ed msm7x2xa chipset. There's no Open C (Jelly Bean based Firefox OS) source. Only for Kis 3 (Android KitKat). Lifting it from my github from commit 02f2259c787cf2e81f9e0e97c1f4ece0bf6e3215 is exactly what you'd get downloading it from ZTE site. https://github.com/KonstaT/android_kernel_zte_msm8610/archive/02f2259c787cf2e81f9e0e97c1f4ece0bf6e3215.zip No, it never does on any Android device. There's always modifications that the OEM/ODM has made. Device doesn't have a proximity sensor. There's three or four proximity/als sensor drivers included in the ZTE kernel source but none of them are even compiled for the device. Doesn't help much when there's no hardware on board. :P Yes, you need to prepare both device and vendor trees if you're planning to do this right now. I have already all device specific trees set up and I will continue to work on this as soon as I receive my device (it should be waiting for me in the post office when I get back home next week :)) mine should be in the box tomorrow :D thanks for the info. and thanks you guys for actually taking the time to reply. i've got credibility just not on these forums :P still i think there's some misinformation regarding the proximity sensor... the zte open (not c; eu version) does not have a proximity, and it does not have a dual core cpu; the open c however, according to device specs has both a proximity sensor (capella/cm i believe instead of a taos like most zte phones) and the dual core cpu. there is a B2G bug report of the proximity not working in firefox os however. i looked over your device tree and it seems you don't have a sensor source included which means you probably can't access the sensor if it's there (using sensors.so as a blob has never worked for me when building android for a device from source). i guess i'll have to wait until tomorrow to be certain, but i believe there's a proximity sensor on the device... and yeah, zte's site says the open c is msm8210, but looking through your kernel source i saw an 8610 config so that's why i asked. my assumption was that all the 8x10 variants were nothing more than dual 7627's or 7x27a's, but cpu archietcture is not something i'm not all that familiar with really. what toolchain are you building kernels with for the kis 3? well, i'd like to extend my hand in saying that i'll be working on the device in my free time starting tomorrow, so, i'd like to work with you guys any way i can. nice to meet you guys, and again, thanks. Edited August 6, 2014 by boogyboo Link to comment Share on other sites More sharing options...
Guest KonstaT Posted August 8, 2014 Report Share Posted August 8, 2014 still i think there's some misinformation regarding the proximity sensor... the zte open (not c; eu version) does not have a proximity, and it does not have a dual core cpu; the open c however, according to device specs has both a proximity sensor (capella/cm i believe instead of a taos like most zte phones) and the dual core cpu. there is a B2G bug report of the proximity not working in firefox os however. i looked over your device tree and it seems you don't have a sensor source included which means you probably can't access the sensor if it's there (using sensors.so as a blob has never worked for me when building android for a device from source). There's is no proximity sensor, believe me. There's no hardware for it - there's no software for it. I haven't pushed anything device specific to my github yet. Device tree is just a clean CAF msm8610 tree from the same tag our kernel is based on. and yeah, zte's site says the open c is msm8210, but looking through your kernel source i saw an 8610 config so that's why i asked. my assumption was that all the 8x10 variants were nothing more than dual 7627's or 7x27a's, but cpu archietcture is not something i'm not all that familiar with really. Second number in Qualcomm platform naming scheme is the radio. msmx0xx - no integrated radio (can have external modem) msmx2xx - GSM msmx6xx - CDMA msmx9xx - LTE Because this device is a GSM variant, it's msm8210. Because Qualcomm calls this platform internally msm8610, we're going to do that as well. Dual core msm7x27a is msm8x25 (and quad-core is msm8x25q). This is nowhere close. msm8610 is a modern platform and it's in the same 'family' as msm8226 and msm8974. what toolchain are you building kernels with for the kis 3? Regular AOSP gcc 4.7 toolchain. No need for silly toolchains. Link to comment Share on other sites More sharing options...
Guest boogyboo Posted August 8, 2014 Report Share Posted August 8, 2014 just so you know, the bootloader unlock method did not work using the upgrade tool and the firmware from comebuy. bootloader is still locked; device not recognized by fastboot devices... haven't tried the eu version, only the us. i'm wondering if i can just update to eu kitkat, reboot to bootloader and run fastboot oem unlock and go from there? i really want to make a backup of the device how it is right this very moment though before i do anything. Link to comment Share on other sites More sharing options...
Guest boogyboo Posted August 9, 2014 Report Share Posted August 9, 2014 There's is no proximity sensor, believe me. There's no hardware for it - there's no software for it. I haven't pushed anything device specific to my github yet. Device tree is just a clean CAF msm8610 tree from the same tag our kernel is based on. Second number in Qualcomm platform naming scheme is the radio. msmx0xx - no integrated radio (can have external modem) msmx2xx - GSM msmx6xx - CDMA msmx9xx - LTE Because this device is a GSM variant, it's msm8210. Because Qualcomm calls this platform internally msm8610, we're going to do that as well. Dual core msm7x27a is msm8x25 (and quad-core is msm8x25q). This is nowhere close. msm8610 is a modern platform and it's in the same 'family' as msm8226 and msm8974. Regular AOSP gcc 4.7 toolchain. No need for silly toolchains. i'm having a hard time seeing the open c as the same device as this: http://www.ztedevices.com/product/smart_phone/9404cb09-6a44-4e25-a334-c00bd0b9b825.html they don't even look the same. hardware is obviously nowhere near the same and i've been trying to build with your kernel source using the base default config from B2G for the open c and there are several headers missing, and some problems with the led driver code. i'm working on getting that fixed though. i was hoping this device wouldn't turn into a nightmare like most zte devices but... this is probably the last time i'll support zte. it seems that the whole idea of the "open" is to provide an open platform for develops, yet they can't even release a fully intact kernel source for the device. always got to jump through hoops frankensteining something together lol Link to comment Share on other sites More sharing options...
Guest hecatae Posted August 10, 2014 Report Share Posted August 10, 2014 i'm having a hard time seeing the open c as the same device as this: http://www.ztedevices.com/product/smart_phone/9404cb09-6a44-4e25-a334-c00bd0b9b825.html they don't even look the same. hardware is obviously nowhere near the same and i've been trying to build with your kernel source using the base default config from B2G for the open c and there are several headers missing, and some problems with the led driver code. i'm working on getting that fixed though. i was hoping this device wouldn't turn into a nightmare like most zte devices but... this is probably the last time i'll support zte. it seems that the whole idea of the "open" is to provide an open platform for develops, yet they can't even release a fully intact kernel source for the device. always got to jump through hoops frankensteining something together lol wrong one that's the msm7225a version, the msm8210 version is here http://www.ztedevices.co.uk/kis-3-android-smartphone.html Link to comment Share on other sites More sharing options...
Guest KonstaT Posted August 11, 2014 Report Share Posted August 11, 2014 the bootloader unlock method did not work using the upgrade tool and the firmware from comebuy. bootloader is still locked; device not recognized by fastboot devices... haven't tried the eu version, only the us. Bootloader is accessible with fastboot even out-of-the box when it's 'locked'. You're just doing it wrong (most likely a driver issue). i'm having a hard time seeing the open c as the same device as this: http://www.ztedevices.com/product/smart_phone/9404cb09-6a44-4e25-a334-c00bd0b9b825.html they don't even look the same. hardware is obviously nowhere near the same Because it's obviously not the same device. If I'm not mistaken that is the Android version of the original ZTE Open. There's too many variants of that device to keep track though. and i've been trying to build with your kernel source using the base default config from B2G for the open c and there are several headers missing, and some problems with the led driver code. You can't build it using B2G defconfig because it's from the wrong Android version. There's no missing headers either. Stand alone kernel building is a bit different than building it in line as part of Android system where headers are exported. There's a defconfig to use in my github and inclusion of headers is fixed as well. i was hoping this device wouldn't turn into a nightmare like most zte devices but... this is probably the last time i'll support zte. it seems that the whole idea of the "open" is to provide an open platform for develops, yet they can't even release a fully intact kernel source for the device. always got to jump through hoops frankensteining something together lol Never had too many problems with any of my previous ZTE devices. Both have actually been amazing devices for deving. Their support isn't the greatest (partly because of language barrier) but they've usually released appropriate kernel sources after requesting few times. If people want the Firefox OS specific kernel source released, they should start emailing ZTE to get the message through - I've already sent a few. Link to comment Share on other sites More sharing options...
Guest KonstaT Posted August 11, 2014 Report Share Posted August 11, 2014 Bootloader is accessible with fastboot even out-of-the box when it's 'locked'. We can actually stop this nonsense about locked bootloaders etc. ZTE has left this device completely open. All I needed to do is boot with power down pressed to bootloader and fastboot flashed my CWM build to recovery partition. My custom kernel build also works fine with CWM. CM11 is next. :P ~ # cat /proc/version Linux version 3.4.0-gfbb298f (tuomas@hope) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Mon Aug 11 17:28:21 EEST 2014 Link to comment Share on other sites More sharing options...
Guest KonstaT Posted August 11, 2014 Report Share Posted August 11, 2014 CM11 is next. :P BOOM, and this happened. Highly functional first CM11 build. Some storage troubles, camera doesn't work due to some missing ZTE symbols, all good otherwise (RIL, wifi, bluetooth, GPS, FM, audio, sensors, LEDs - all major things working). :D Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now