• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Sprint] [OUDHS]SpeedBall Kernel for JB ONLY

Ok, whats happening is I am testing on a different version and from what I've seen, there are a few versions out there right now. The difference is in the wifi binaries that are being provided by Samsung for the different devices/carriers/versions. IDK why, but wifi modules are really picky about it. Modversion is a safety system that checks for driver/module/binary mismatches and breaks things if there are mismatches. I am on build# JRO03L.L300VPALJ9, which according to Samsung does not exist. I got a system dump from a Virgin device today that is JZO54K.L300VPAMA8. My Android version is 4.1.1, this other is 4.1.2 and most likely has new guts. Anyway, I've seen this happen on a ton of devices I've worked on. The solution is to find the matching elements and keep the working sets together in the zip, but that requires a bit of testing and there is ALWAYS some possibility of breaking something. Have you been able to restore your WIFI functionality with the stock kernel?
 
xInterlopeRx said:
Ok, whats happening is I am testing on a different version and from what I've seen, there are a few versions out there right now. The difference is in the wifi binaries that are being provided by Samsung for the different devices/carriers/versions. IDK why, but wifi modules are really picky about it. Modversion is a safety system that checks for driver/module/binary mismatches and breaks things if there are mismatches. I am on build# JRO03L.L300VPALJ9, which according to Samsung does not exist. I got a system dump from a Virgin device today that is JZO54K.L300VPAMA8. My Android version is 4.1.1, this other is 4.1.2 and most likely has new guts. Anyway, I've seen this happen on a ton of devices I've worked on. The solution is to find the matching elements and keep the working sets together in the zip, but that requires a bit of testing and there is ALWAYS some possibility of breaking something. Have you been able to restore your WIFI functionality with the stock kernel?
Click to expand...

Well, I didnt try the zip you made. my backup in twrp is what I used though and it worked fine after I restored it. Main reason I didn't use your kernel is I figured if it was the same build as your SpeedBall kernel, I'd have the same issue with WiFi.
 
Prinny said:
Well, I didnt try the zip you made. my backup in twrp is what I used though and it worked fine after I restored it. Main reason I didn't use your kernel is I figured if it was the same build as your SpeedBall kernel, I'd have the same issue with WiFi.
Click to expand...

Indeed it is made from the same source. I have had mixed results myself using it with different modifications. Sorry I can't release perfect stuff every time. The user base for this device is really small, so we all have to be the guinea pigs! ;)
 
Hey no worries. I know my way around phones enough ;)

Besides, whats rule #1? Always make a nandroid ;)

Rule 2: Not the devs fault if your phone explodes.
 
Oh, and as for the guinea pig part:

I have a nandroid. I will gladly flash kernel tests ;) I know if anything borks, I can restore my boot backup.

Just tossing that out there ;D
 
Ok, someone got on the IRC the other day a got me a system pull, but it seems VERY different and maybe lacking some files. So, as a second look into the Virgin depths, would either of you mind getting a stock system pull from Android 4.1.2? If you delete the /apps directory it'll only be around 300mb and dropbox will let me have it.
 
Interloper: I should be able to pull the /system later tonight/tomorrow. Just formatted my PC, so just need to set up ADB and whatnot.

I'll delete the /apps folder as you said that is not needed. mostly /libs and whatnot I assume are most important?

Uh. I assume you're on Linux? is a .tar.gz okay or do you want a .zip?
 
Alright, so its uploading now. I'll post a link in the morning if I remember. which I should...since I'm leaving DropBox open here...

Without the /apps folder its 514MB o.o Holy carp.
 
Well, I had big plans and even spent some time fulfilling those ideas only to find that the new and old kernel sources are identical. I have no idea why Samsung would do that, but they did. So, no new kernel yet, but it's bugging me that kernel source released for the VMU would fail the insmod on the wifi driver. I will not rest until all three of us are happily zipping along at 1.5+ stable! (or until I'm tired)
 
So the filesize is too large for DropBox.

So we need to figure out what I can remove. Uhm. How about I pull... /lib /bin /etc? /xbin is almost 400mb...
 
can I haz the build.prop for the files you posted. I have them DL'd and if you'd like, you can delete them from your dropbox.
 
Code: 
 # begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JZO54K
ro.build.display.id=JZO54K.L300VPAMC1
ro.build.version.incremental=L300VPAMC1
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Sat Mar  2 13:12:37 KST 2013
ro.build.date.utc=1362197557
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-118
ro.build.tags=release-keys
ro.product.model=SPH-L300
ro.product.brand=samsung
ro.product.name=goghvmu
ro.product.device=goghvmu
ro.product.board=MSM8960
ro.chipname=MSM8960
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product_ship=true
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=msm8960
# ro.build.product is obsolete; use ro.product.device
ro.build.product=goghvmu
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=goghvmu-user 4.1.2 JZO54K L300VPAMC1 release-keys
ro.build.fingerprint=samsung/goghvmu/goghvmu:4.1.2/JZO54K/L300VPAMC1:user/release-keys
ro.build.characteristics=chameleon
# Samsung Specific Properties
ro.build.PDA=L300VPAMC1
ro.build.hidden_ver=L300VPAMC1
ro.build.changelist=958802
# end build properties
# 8960 RIL Basic
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=dyn
debug.compbypass.enable=1
debug.hwui.render_dirty_regions=false
dalvik.vm.heapsize=36m
debug.enable.wl_log=1
debug.mdpcomp.maxlayer=3

#
# system props for the cne module
#
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
persist.cne.feature=0

ro.hdmi.enable=true
ro.yas.enable=true
ro.yas_softiron.goghspr=true
ro.yas-selftest.enable=true
lpa.decode=true
lpa.use-stagefright=true

#system props for the MM modules

media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true

# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=digital

# System prop to select audio resampler quality
af.resampler.quality=255
# System prop to select MPQAudioPlayer by default on mpq8064
mpq.audio.decode=true

#
# system prop for opengles version
#
# 131072 is decimal for 0x20000 to report version 2
ro.opengles.version=131072

#
# system property for Bluetooth Handsfree Profile version
#
ro.bluetooth.hfp.ver=1.6
#
#system prop for Bluetooth hci transport
ro.qualcomm.bt.hci_transport=smd
#
# system prop for requesting Master role in incoming Bluetooth connection.
#
ro.bluetooth.request.master=true
#
# system prop for Bluetooth Auto connect for remote initated connections
#
ro.bluetooth.remote.autoconnect=true
# system property for Bluetooth discoverability time out in seconds
# 0: Always discoverable
#debug.bt.discoverable_time=0

#system prop for switching gps driver to qmi
persist.gps.qmienabled=true

# System property for cabl
ro.qualcomm.cabl=1

#
# System prop for sending transmit power request to RIL during WiFi hotspot on/off
#
ro.ril.transmitpower=true

#
#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true
ro.hwui.text_cache_width=2048

#
# Supports warmboot capabilities
#
ro.warmboot.capability=1

ro.sf.lcd_density=240


# Use CDMALTE Phone
telephony.lteOnCdmaDevice=1

# Enable time services daemon
persist.timed.enable=true

# Keep SIM state on LPM mode
persist.radio.apm_sim_not_pwdn=1

# Don't wait the card state for RADIO POWER request
persist.radio.no_wait_for_card=1

# For sys info indication
persist.radio.add_power_save=1

# Snapshot Setting
persist.radio.snapshot_enabled=1
persist.radio.snapshot_timer=22

# Control EONS (true = EONS enabled, false = EONS disabled)
persist.eons.enabled=false

# Data modules
ro.use_data_netmgrd=true

# Default ECCList (Except USCC)
ro.ril.ecclist=112,911,#911,*911

# Chameleon Default Operator (VMU with Chameloen)
ro.cdma.default_numeric=000000
ro.cdma.default_alpha=Samsung

# Chameleon Default tethering disable
persist.sys.tether_data=1

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.vendor.extension_library=/system/lib/libqc-opt.so
ro.error.receiver.default=com.samsung.receiver.error
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.heaputilization=0.25
dalvik.vm.heapidealfree=8388608
dalvik.vm.heapconcurrentstart=2097152
ro.sec.fle.encryption=true
ro.hdcp2.rx=tz
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.ringtone=01_Over_the_horizon_Acoustic.ogg
ro.config.notification_sound=S_Whistle.ogg
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.setupwizard.mode=DISABLED
ro.com.google.apphider=off
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.gmsversion=4.1_r4
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
 
So, if 4.1.2 is coming for the Sprint Victory, does that mean that once you have that, perhaps an updated kernel will be coming?

The discrepancies between 4.1 and 4.1.2 might have been causing us VM users some issues, methinks, since our phones shipped with 4.1.2 automagically.

Not trying to ask an ETA or anything, just a curious question really ;)
 
Prinny said:
So, if 4.1.2 is coming for the Sprint Victory, does that mean that once you have that, perhaps an updated kernel will be coming?

The discrepancies between 4.1 and 4.1.2 might have been causing us VM users some issues, methinks, since our phones shipped with 4.1.2 automagically.

Not trying to ask an ETA or anything, just a curious question really ;)
Click to expand...

I just got word of a Sprint update to MC1, which might not make much sense to you. They did release a source package for it and I'm getting it now. If it's a significant version bump from what I'm already building I'll work on this again. Thing is, this kernel was already build on VM source. Since I don't have the device or the issue, it's hard for me to diagnose the problem. Once I'm not spending so much time on CM, I'll try to refocus on fixing this through testers. If you can, flash the kernel and use ADB to get a dmesg.
 
xInterlopeRx said:
I just got word of a Sprint update to MC1, which might not make much sense to you. They did release a source package for it and I'm getting it now. If it's a significant version bump from what I'm already building I'll work on this again. Thing is, this kernel was already build on VM source. Since I don't have the device or the issue, it's hard for me to diagnose the problem. Once I'm not spending so much time on CM, I'll try to refocus on fixing this through testers. If you can, flash the kernel and use ADB to get a dmesg.
Click to expand...

You're doing this without the phone? Geez ;) I'll see about getting a dmesg after work if i have time.

Although I'm more excited for CM. But yeah. I'm not familiar with MC1 or anything of that nature. But i do understand what you mean though.
 
You must log in or register to reply here.
Back
Top Bottom