[LTE][ROM-AOSP] Unofficial CM10.2 (JB 4.3) [08/07 LTE TEST #3]

Search This thread

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,424
23,730
The new rom has a Mobile networks settings, but no signal. Maybe this park is for the smartphone hardware and not for tablets. Cuz I see Network Operater doesn't show up at status bar, just a triangle with nothing. And when I was in the network operations setting, it scan for network, manage mobile plan doesn't recognize sim (the stock 8.4.3 does). Or maybe it just setup for AT&T network?

I don't know why I can't get the log file, my computer does recognize as ADB, but when I tried to log, it said waiting for device.

Your rom is improved every update ^^
thanks for your work, bro.

This is the "bringup" phase where none of the OS settings will work correctly, because the modem and/or network haven't been established correctly (yet).
 
  • Like
Reactions: tethien

tethien

Member
Feb 19, 2010
19
4
I'm seeing lines like this in your radio logcat:
W/use-Rlog/RLOG-RIL_VDR( 134): ril_oem.c:194 Failed to set mtu::rc=1,0, cmd=[echo 1400 > /sys/class/net/rmnet0/mtu]
E/use-Rlog/RLOG-RIL_ODL( 134): pktio.c:271 cant open device: device=/dev/ttyUSB0, errno=13

Can you check the following in adb and post it for me?
ls -l /sys/class/net/
ls -l /dev/ttyUSB*

Thanks

Code:
root@android:/ # ls -l /sys/class/net/
ls -l /sys/class/net/
lrwxrwxrwx root     root              2013-08-08 17:30 ifb0 -> ../../devices/virtual/net/ifb0
lrwxrwxrwx root     root              2013-08-08 17:30 ifb1 -> ../../devices/virtual/net/ifb1
lrwxrwxrwx root     root              2013-08-08 17:30 ip6tnl0 -> ../../devices/virtual/net/ip6tnl0
lrwxrwxrwx root     root              2013-08-08 17:30 lo -> ../../devices/virtual/net/lo
lrwxrwxrwx root     root              2013-08-08 17:30 sit0 -> ../../devices/virtual/net/sit0
lrwxrwxrwx root     root              2013-08-08 17:30 tunl0 -> ../../devices/virtual/net/tunl0
lrwxrwxrwx root     root              2013-08-08 14:32 wlan0 -> ../../devices/platform/omap/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/net/wlan0

Code:
root@android:/ # ls -l /dev/ttyUSB*
ls -l /dev/ttyUSB*
/dev/ttyUSB*: No such file or directory
 
  • Like
Reactions: laopai

laopai

Member
Apr 11, 2013
49
3
for whatever reason, my adb does not recognize my kfhd 8.9 lte. android sdk is already updated to the latest version. Nexus 4 and 7 work just fine, but not KFHD 8.9 lte.

Did I forget something?
 
Last edited:

stevenmirabito

Senior Member
Jan 22, 2011
74
42
Camillus, NY
about.me
for whatever reason, my adb does not recognize my kfhd 8.9 lte. android sdk is already updated to the latest version. Nexus 4 and 7 work just fine, but not KFHD 8.9 lte.

Did I forget something?

Nexus devices use the drivers that come with the SDK tools, Kindles require special drivers and a tweak to ADB's environment configuration to be recognized properly. Look for a sticky in one of the other sections of this forum with the drivers, should be near where the rooting instructions are.

Sent from my Nexus 4 using xda app-developers app
 
  • Like
Reactions: laopai

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,424
23,730
On the latest ROM test (CM10.2) I need the following command to be run on a jem LTE device:
/system/xbin/strace -ff -F -tt -s 200 -o /cache/trace/wankit.pid /system/bin/wankit cond_start_ril

This creates a log in /cache/trace that I need either a pastebin link to or a PM.

Thanks.
 

laopai

Member
Apr 11, 2013
49
3
On the latest ROM test (CM10.2) I need the following command to be run on a jem LTE device:
/system/xbin/strace -ff -F -tt -s 200 -o /cache/trace/wankit.pid /system/bin/wankit cond_start_ril

This creates a log in /cache/trace that I need either a pastebin link to or a PM.

Thanks.

at your service.
 

Attachments

  • wankit.rar
    30.5 KB · Views: 34

laopai

Member
Apr 11, 2013
49
3
Nexus devices use the drivers that come with the SDK tools, Kindles require special drivers and a tweak to ADB's environment configuration to be recognized properly. Look for a sticky in one of the other sections of this forum with the drivers, should be near where the rooting instructions are.

Sent from my Nexus 4 using xda app-developers app

thanks a lot! I will give a try.
 

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,424
23,730
Yep, sorry this hasn't worked out better. I was never able to borrow a device to get this ROM off the ground.

Sent from my XT926 using Tapatalk
 

stevenmirabito

Senior Member
Jan 22, 2011
74
42
Camillus, NY
about.me
Yep, sorry this hasn't worked out better. I was never able to borrow a device to get this ROM off the ground.

Sent from my XT926 using Tapatalk

If you're still willing to work on this, I'm willing to provide any testing, etc. that you need to get this working. Just tell me what you need done. If you need the physical device in order to properly work on it, I'm sure we can work something out, but we'll cross that bridge when we come to it.

Sent from my Nexus 4 using xda app-developers app
 

drexvil

Member
Jul 20, 2010
35
4
What's the difference between this and the non-LTE CM 10.2 by hashcode? I mean, if LTE doesn't work on this build, can we just flash the regular rom? Does GPS work on this one?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 13
    Ugh, I've been working on this one for 3 days straight now. Reverting back to as close as the original kernel as I can get in hopes of seeing where I can fix the USB modem driver in the kernel.

    So far no luck at all. I'm getting the exact same error today using a 3.0.21 reverted kernel to boot up cm11 with, as I get on the latest 3.0.72 kernel.

    I'm going to reinstall the Kindle OS and try debugging that a bit to see if I can get a better idea of how things init on stock.
    9
    I have a loaner KFireHD 8.9 LTE device now, thanks for @galearned.

    After running some initial tests laster night, I'm kind of surprised at how different the device is from the standard KFire HD 8.9.

    Some notes:
    - GSM LTE modem in the device (obviously) -- Not sure on the bands available. I'll be testing this later.
    - PIC12LF1822 Proximity Sensor is present (not in the other HD devices)
    - AMI306 hardware compass module is present in the Invensense sensor package (not in the other HD devices)

    To fully support the HD LTE model, I'll need to add those sensors to the HAL sources. (They will silently fail on the standard models).
    8
    Unofficial CyanogenMod 10.2 for the Kindle Fire HD 8.9 LTE

    THIS THREAD IS SPECIFIC TO THE LTE VARIANT OF THE KINDLE FIRE HD 8.9". IF YOU HAVE A STANDARD 8.9" MODEL USE THIS THREAD:
    http://xdaforums.com/showthread.php?t=2388352

    *** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***


    **** I DO NOT OWN THE LTE VARIANT OF THE KINDLE FIRE HD 8.9", SO THIS ROM WILL BE A WORK IN-PROGRESS. IF YOU'RE THE EASILY FRUSTRATED TYPE, YOU MAY WANT TO HOLD OFF. ****


    BEFORE YOU BEGIN MAKE SURE YOU HAVE A 2ND-BOOTLOADER INSTALLED CORRECTLY AND CAN SEE THE BLUE LOGO DURING BOOTUP:
    http://xdaforums.com/showthread.php?t=2128175

    LTE MODEL Download Information:
    [LATEST][08/07 #3] BETA CM10.2 + 3.0.50+ KERNEL
    Mirror 1: http://goo.im/devs/Hashcode/jemlte/cm10.2/cm-10.2-20130807-UNOFFICIAL-jemlte.zip
    md5sum: d499384a940dffb3ca7e6ac512fcf370

    Older builds can be found in the same folder on goo.im:
    http://goo.im/devs/Hashcode/jemlte/cm10.2/

    Download Google Apps:
    http://goo.im/devs/Hashcode/gapps
    (For Android 4.3)

    PLEASE BE SURE TO WIPE SYSTEM & DATA/CACHE (FACTORY RESET) WHEN COMING FROM AMAZON STOCK SOFTWARE.
    (It's the "Wipe" button and then "System" and then "Factory Reset" button in TWRP -- this does NOT clear your sdcard space)

    Be aware that the "sdcard" space has changed slightly from ICS to JB4.2. You will find your stock amazon OS files in /data/media/ or "sdcard" on the Stock OS. But CM10.1 will create a sub directory "/data/media/0" and call that "sdcard". And in TWRP it will also use "data/media/0" as "sdcard". This has to do with multi-user settings. So when placing files on the "sdcard" be sure to check both locations before wondering why that file is missing.

    CHANGES:
    • [08/04] First CM10.2 build for Jem LTE
    • [07/31] Added RIL setup for LTE
    • [07/31] First CM10.2 build for Jem

    FEATURES:
    • 3.0.50 kernel (up from a stock 3.0.21 kernel). This includes updates from Texas Instruments, Google and Kernel.org.
    • PowerVR Graphics Drivers: DDK 1.9@2291151 for Android (Jellybean compatible)
    • Updated bltsville libs to 2.2.2.0 (this is partial screen update code which enables smoother / faster screen draws)
    • Audio
    • Camera
    • Wifi
    • Bluetooth
    • Sensors
    • HWAcceleration
    • HD Codecs for YouTubeHD and Netflix
    • HDMI video out is now correct and work across several resolutions. YMMV


    DEVS
    BUILDING THIS ROM:

    First, read through Google's Android website about "how to setup a build environment":
    http://source.android.com/source/initializing.html

    [ COMING SOON ]

    SCREEN SHOTS:
    6
    I would happily loan him my KFHD8.9LTE to work with, although I live in the UK. I'm not too worried about the Android version, I just want the GPS to work.

    I have a device that was loaned to me. And I've spent quite a bit of time debugging the modem device crash that's holding up lte support.

    I'll get it eventually. :/

    Sent from my KFTHWI using Tapatalk
    5
    Another update:

    I located the 1st BIG reason why the modem isn't working.

    Below is a snippet of the kernel boot. You can see that the USB Modem hits an issue during the init and then totally bails and removes itself.

    Without the "rmnet" interface there is no WWAN connection. Period. No real reason yet why this happens, it'll take a bit of debugging.

    Code:
    <6>[   85.040174] usb usb1: >>> usb_resume_both: resuming usb
    <4>[   85.061079] usbhs: L2: IO pad wake [disable] hcd->state = 1, d0-mux=1090109
    <4>[   85.061079] 
    <6>[   85.085310] usb usb1: usb_resume_device: status 0
    <6>[   85.193922] usb usb1: >>> usb_resume_both: resumed usb finished
    <6>[   85.318952] usb 1-2: new high speed USB device number 2 using ehci-omap
    <6>[   85.482893] usb 1-2: New USB device found, idVendor=1949, idProduct=9003
    <6>[   85.483106] usb 1-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
    <6>[   85.483290] usb 1-2: Product: Android
    <6>[   85.483381] usb 1-2: Manufacturer: Android
    <6>[   85.483473] usb 1-2: SerialNumber: 0123456789ABCDEF
    <4>[   85.483656] Disconnect time elapsed=-1767872298 ms:
    <6>[   85.487623] option 1-2:1.0: GSM modem (1-port) converter detected
    <6>[   85.491957] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB0
    <6>[   85.493025] option 1-2:1.1: GSM modem (1-port) converter detected
    <6>[   85.496839] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB1
    <6>[   85.498213] option 1-2:1.2: GSM modem (1-port) converter detected
    <6>[   85.499830] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB2
    <6>[   85.509168] qmi 1-2:1.3: rmnet0: register 'qmi' at usb-ehci-omap.0-2, RmNet Ethernet Device, ca:1d:0c:99:d7:d3
    <6>[   85.617292] healthd: battery l=76 v=3922 t=28.8 h=2 st=3 c=-284 chg=u
    <3>[   85.754499] init: sys_prop: permission denied uid:1001  name:persist.ril.stat.lastboot
    [B]<3>[   85.931928] do_get_encap_rsp: Get encap rsp timed out
    <3>[   85.932172] do_get_encap_rsp: usb_control_msg() timed out. err = -32
    [/B]<3>[   86.246809] init: sys_prop: permission denied uid:1001  name:persist.ril.stat.usb.reset
    <3>[   86.254896] do_get_encap_rsp: Get encap rsp timed out
    <3>[   86.255109] do_get_encap_rsp: usb_control_msg() timed out. err = -32
    <6>[   86.512098] qmi_misc_release: released qmi file (0)
    <6>[   86.551465] usb 1-2: USB disconnect, device number 2
    <6>[   86.553724] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
    <6>[   86.554212] option 1-2:1.0: device disconnected
    <3>[   86.555097] option: option_instat_callback: error -108
    <6>[   86.555890] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
    <6>[   86.556409] option 1-2:1.1: device disconnected
    <3>[   86.559247] option: option_instat_callback: error -108
    <6>[   86.560773] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
    <6>[   86.561262] option 1-2:1.2: device disconnected
    [B]<6>[   86.562147] qmi 1-2:1.3: rmnet0: unregister 'qmi' usb-ehci-omap.0-2, RmNet Ethernet Device[/B]
    <4>[   86.775434]  >>> PHY Reset
    <4>[   86.776868]  >>> PHY in low power