Related
Edit: 13 October 2012
Today I got enough time and internet access so I want to inform you people on what I have achieved!
I didn't want to open a new thread just for this, so I'll use this one again.
I've made a booting CM9 port using the stable cm9 build from this LG phone here: http://download.cyanogenmod.com/?device=e730&type=stable
The .zip file is in the link below.
This .zip will only boot up and then you will receive a constant error that phone.apk crashed or sth like that.
I also provide the logcat I got from this .zip in case someone wants to read it before it tests it. It is in the attachments below.
This .zip uses the logcat boot.img created by qwerty12 and also uses some libs from Depth OS by Shendu (since that rom is also based on CM9).
I have not tested the ROM further since I don't have much free time and because my phone is at service right not...
Anyway. Feel free to test it for yourself and why not correct bugs and make a fully working CM9 for our community
WARNING:
I'm NOT responsible for ANY kind of DAMAGE this rom may cause to your phone. You and only you are responsible if you choose to flash it!!! I removed the battery to shut down my phone when I've booted up this ROM and then my phone was bricked!!! Proceed at your own RISK!!!!
Download link:
http://www.mediafire.com/?ezcixwlzlz6neyj
---------------------------------------------------Old Thread starts here- Don't read------------------------------------------------------------------------------------------------
Code:
Ok people. Let me explain first.
I made this .zip file in about 20 minutes. It is a CM9 based "port" of this rom:
[url]http://forum.xda-developers.com/showthread.php?t=1429215[/url]
I choose HTC Desire S because it has the same CPU + GPU with U8800 Pro + that this CM9 is based on .35 kernel, much like Aurora from sakura does. I thought that it wouldn't be too hard to port.
[B][U]
WARNING!!![/U][/B]
I must warn you that this rom doesn't even boot up properly. I just stucks at bootanimation.
However, I only changed the boot.img (using the one from latest aurora), modified updater-script(in order to install the rom correctly in the appropriate blocks),got some extra files from aurora /system/lib/hw folder and dropped them in cm9 and modified the build.prop (device model etc). I also removed some apps in order to make the rom smaller and upload it faster.
Since I don't have much free time available to spend trying to successfully port this ROM I uploaded my 20 minutes work here, in case someone wants to try to even make it boot. Even this is a success I believe :)
So there it is.
To install from CWM:
1) Wipe data/factory reset
2) wipe dalvik
3) install .zip from sd card
Again saying! This rom just stucks at bootanimation. Download it and mod it only if you want to spend time just to make it boot.
I couldn't get logcat to see what's wrong but maybe someone here can make it.
Good luck everyone!
[B][U]
Download:[/U][/B]
[url]http://www.mediafire.com/?5oym09jyzs78s09[/url]
-------------------------------------------------------------------------------------Old Thread End--------------------------------------------------------------------------------------
hi, logcat enabler is in boot.img
p.s. don't understand why you published not booting version and even the logcat there is not working?
i bricked my pro with trying rils to work. of course rom boots up, and i don't published there that version, because i just got it to boot and in less than hour bricked the phone.
and whats the purpose of this thread you have started? there is no nothing. empty... without working logcat there is no posibility to find out why it's not booting.
Sent from not my ragelis
bronxitas said:
hi, logcat enabler is in boot.img
p.s. don't understand why you published not booting version and even the logcat there is not working?
i bricked my pro with trying rils to work. of course rom boots up, and i don't published there that version, because i just got it to boot and in less than hour bricked the phone.
and whats the purpose of this thread you have started? there is no nothing. empty... without working logcat there is no posibility to find out why it's not booting.
Sent from not my ragelis
Click to expand...
Click to collapse
hi broxnitas
boot.img is debuggable
the thing is that my android sdk isn't installed correctly so neither my adb or logcat work as they should.Since I don't have time to even try make the rom boot, I also don't have time to correct my sdk installation.
I started this thread because I believe in the power of the community. If someone can't achieve something (in this case logcat) maybe some else can. I made a start in case someone wants to make a try to port CM9.
If you managed to boot your CM9 port why not share it on this thread?
Maybe someone finds why ril doesn't work or suggest a fix for this.
If we work all together maybe we make something actually one day except from cooking ROMS. We can't rely on Geno and Chinese forever.
try with libril-qc-1.so
try my boot.img http://www.mediafire.com/?sy3dyds8kkh358q
or cahange init.rc from cm9
Moihack: you know wich rom i take as base and you know what have i've done ant what reached (i have writed to you all more than week earlyer). so why you asking to do that again?
my pro ir now in Hungary service and on monday i will start to useing sgs2.
i'm not afraid of bricking pro again so i will try to finish my earlyer port.
Sent from not my ragelis
@ oguzhan mobile thanks for trying to help. sadly with your boot.img the phone didn't even reach boot animation.
@ broxnitas
I tried to do the same for 2 reasons:
1) Because I thought you wouldn't try to complete your port since your phone was bricked. I was wrong as it seems from your previous post.
2) Because if I recall your base correctly it was a pretty unstable ROM, far from reaching stable. The base for this one has less issues according to its dev.
I just gave it a shoot and because I reached boot animation somehow easily I decided to share it just in case someone wants to continue this.
@ everyone
can someone confirm if logcat is working? my sdk installation is corrupt and can't even run adb or logcat in working roms that I've successfully ran adb in the past.
maybe true, but phone boots up issues and stability is for later.
what you posted is absolutely 0. i think of posting some work, especialy ROM, it must boot at first then could be shared to others for solving isues
the meaning: this thread should be started in general section, because there is not even start of porting, it's a suggestion to do that from desire s port
yes cm9/10 is what we waiting for, but why to start from ilusion?
Sent from not my ragelis
Could this be useful? http://forum.xda-developers.com/showthread.php?t=1598713
bronxitas said:
maybe true, but phone boots up issues and stability is for later.
what you posted is absolutely 0. i think of posting some work, especialy ROM, it must boot at first then could be shared to others for solving isues
the meaning: this thread should be started in general section, because there is not even start of porting, it's a suggestion to do that from desire s port
yes cm9/10 is what we waiting for, but why to start from ilusion?
Sent from not my ragelis
Click to expand...
Click to collapse
Maybe you are right in the end. Maybe general section fits better till phone boot.
Lack of time though made me act like that.Hope when I have some time to test again, I make this rom boot
@MyNameIsKappa
I'm aware of this guide. I didn't follow it when making this .zip file. Will again have a look at it and try to make the ROM boot. Thanks for reminding it to me
Moihack said:
Maybe you are right in the end. Maybe general section fits better till phone boot.
Lack of time though made me act like that.Hope when I have some time to test again, I make this rom boot
@MyNameIsKappa
I'm aware of this guide. I didn't follow it when making this .zip file. Will again have a look at it and try to make the ROM boot. Thanks for reminding it to me
Click to expand...
Click to collapse
Thank you for your work and your try to port the CM9 =)
We don't need people that waste time only talking and saying ****s, we need people like you, who work hard for the community
this could be really helpful https://github.com/jesus1o1
MyNameIsKappa: I agree with you, thats why i'm saying that this thread must be in general section because at this time here is no work puted in port, just talks
Sent from not my ragelis
why not use the cm9 devoleped for this phone http://www.gsmarena.com/lg_optimus_sol_e730-4067.php ?
same hardware specs of our phone.....http://download.cyanogenmod.com/?type=nightly&device=e730
we could use these sources to build cm9 (but they belong to the gingerbread branch):
android_device_huawei_u8800pro https://github.com/jesus1o1/android_device_huawei_u8800pro
android_vendor_huawei_u8800pro https://github.com/jesus1o1/android_vendor_huawei_u8800pro
another thing to make the rom correctly booting:
PHP:
Copyright (C) 2008 The Android Open Source Project
# Copyright (C) 2012 The SuperTeam Developer Group
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
$(call inherit-product, device/common/gps/gps_eu_supl.mk)
$(call inherit-product, $(SRC_TARGET_DIR)/product/small_base.mk)
$(call inherit-product, vendor/SuperTeam/products/common_full.mk)
$(call inherit-product, vendor/SuperTeam/products/bcm_fm_radio.mk)
$(call inherit-product, vendor/huawei/u8800pro/u8800pro-vendor.mk)
DEVICE_PACKAGE_OVERLAYS := device/huawei/u8800pro/overlay
PRODUCT_NAME := team_u8800pro
PRODUCT_DEVICE := u8800pro
PRODUCT_MODEL := huawei u8800pro
PRODUCT_MANUFACTURER := Huawei
BUILD_FINGERPRINT := Huawei/U8800Pro/hwu8800Pro:2.3.5/HuaweiU8800Pro/C00B540G001:user/ota-rel-keys,release-keys
PRODUCT_BUILD_PROP_OVERRIDES += BUILD_ID=GRI40 BUILD_DISPLAY_ID=GWK74 PRODUCT_NAME=U8800Pro BUILD_FINGERPRINT=Huawei/U8800Pro/hwu8800Pro:2.3.5/HuaweiU8800Pro/C00B540G001:user/ota-rel-keys,release-keys TARGET_BUILD_TYPE=userdebug BUILD_VERSION_TAGS=ota-rel-keys,release-keys PRIVATE_BUILD_DESC="U8800Pro-user 2.3.5 HuaweiU8800Pro C00B540G001 ota-rel-keys,release-keys"
PRODUCT_PACKAGES += \
overlay.default \
gps.u8800pro \
lights.u8800pro \
gralloc.msm7x30 \
overlay.default \
libOmxCore \
libOmxVdec \
libOmxVenc \
dexpreopt \
DSPManager \
hcitool \
FM \
Torch
# proprietary side of the device
$(call inherit-product-if-exists, vendor/huawei/u8800pro/u8800pro-vendor.mk)
DISABLE_DEXPREOPT := false
# Init
PRODUCT_COPY_FILES += \
device/huawei/u8800pro/init.huawei.rc:root/init.huawei.rc \
device/huawei/u8800pro/init.rc:root/init.rc \
device/huawei/u8800pro/init:root/init \
device/huawei/u8800pro/initlogo.rle:root/initlogo.rle
# keylayout
PRODUCT_COPY_FILES += \
device/huawei/u8800pro/qwerty.kl:system/usr/keylayout/qwerty.kl
# fstab
PRODUCT_COPY_FILES += \
device/huawei/u8800pro/vold.fstab:system/etc/vold.fstab
# enhanced.conf
PRODUCT_COPY_FILES += \
device/huawei/u8800pro/enhanced.conf:system/etc/enhanced.conf
PRODUCT_COPY_FILES += \
device/huawei/u8800pro/init.qcom.bt.sh:system/etc/init.qcom.bt.sh \
device/huawei/u8800pro/wpa_supplicant.conf:system/etc/wifi/wpa_supplicant.conf \
device/huawei/u8800pro/dhcpcd.conf:system/etc/dhcpcd/dhcpcd.conf \
# Install the features available on this device.
PRODUCT_COPY_FILES += \
frameworks/base/data/etc/handheld_core_hardware.xml:system/etc/permissions/handheld_core_hardware.xml \
frameworks/base/data/etc/android.hardware.camera.autofocus.xml:system/etc/permissions/android.hardware.camera.autofocus.xml \
frameworks/base/data/etc/android.hardware.telephony.gsm.xml:system/etc/permissions/android.hardware.telephony.gsm.xml \
frameworks/base/data/etc/android.hardware.location.gps.xml:system/etc/permissions/android.hardware.location.gps.xml \
frameworks/base/data/etc/android.hardware.wifi.xml:system/etc/permissions/android.hardware.wifi.xml \
frameworks/base/data/etc/android.hardware.sensor.proximity.xml:system/etc/permissions/android.hardware.sensor.proximity.xml \
frameworks/base/data/etc/android.hardware.sensor.light.xml:system/etc/permissions/android.hardware.sensor.light.xml \
frameworks/base/data/etc/android.hardware.touchscreen.multitouch.distinct.xml:system/etc/permissions/android.hardware.touchscreen.multitouch.distinct.xml
#WIFI Modules
PRODUCT_COPY_FILES += \
device/huawei/u8800pro/prebuilt/dhd.ko:/system/wifi/dhd.ko \
PRODUCT_PROPERTY_OVERRIDES += \
ro.build.baseband_version=129005 \
ro.telephony.default_network=0 \
ro.telephony.call_ring.multiple=false \
ro.ril.hsxpa=1 \
ro.ril.gprsclass=10 \
PRODUCT_PROPERTY_OVERRIDES += \
rild.libpath=/system/lib/libril-qc-1.so \
rild.libargs=-d /dev/smd0 \
ro.telephony.ril_class=semc \
wifi.interface=eth0 \
wifi.supplicant_scan_interval=150 \
ro.config.wifi_chip_is_bcm=true \
ro.com.android.dataroaming=false
PRODUCT_PROPERTY_OVERRIDES += \
ro.sf.lcd_density=240 \
PRODUCT_PROPERTY_OVERRIDES += \
ro.config.hwfeature_slavecamera=yes \
ro.config.hwcameraset=63 \
hw.secondary_mic=0 \
ro.config.hw_addsettingsdbex=1 \
ro.config.hw_gcf_mms=true \
ro.config.wifi_chip_is_bcm=false \
ro.config.hwft_PNN_function=true \
persist.cust.tel.adapt=1 \
persist.cust.tel.eons=1 \
ro.config.hwfeature_gps_test=0 \
ro.config.hwfeature_ecc=true \
ro.config.lowbattery_shutdown=1 \
ro.config.hwfeature_wakeupkey=1 \
ro.config.endkeybehavior=true \
ro.config.hw_menu_unlockscreen=false \
ro.media.enc.lprof.duration=30 \
ro.config.PicMaxSize=5mp \
ro.config.hw_temperature_warn=true \
ro.config.hw_clocksetting=0 \
ro.additionalmounts=/HWUserData \
ro.vold.switchablepair=/mnt/sdcard,/HWUserData \
ro.vold.umsdirtyratio=20 \
# u8800pro uses high-density artwork where available
PRODUCT_LOCALES += hdpi
# we have enough storage space to hold precise GC data
PRODUCT_TAGS += dalvik.gc.type-precise
# This should not be needed but on-screen keyboard uses the wrong density without it.
PRODUCT_PROPERTY_OVERRIDES += \
qemu.sf.lcd_density=240
PRODUCT_PROPERTY_OVERRIDES += \
ro.com.google.locationfeatures=1 \
ro.setupwizard.enable_bypass=1 \
ro.media.dec.jpeg.memcap=20000000 \
dalvik.vm.lockprof.threshold=500 \
dalvik.vm.dexopt-flags=m=y \
dalvik.vm.heapsize=32m \
dalvik.vm.execution-mode=int:jit \
dalvik.vm.dexopt-data-only=1 \
ro.opengles.version=131072 \
ro.compcache.default=0
[email protected] \
ro.config.play.bootsound=0v
$(call inherit-product-if-exists, device/huawei/u8800pro/wifi/wifi.mk)
matteof93: have you tryed you're self to port cm9 to pro? try it
marsilinio has no sucsses - bootloop on boot animation.
kamatozko went further and maked logcat working and has bootloop at bootanimation.
i have made that cm9 boots up, but no camera, no wifi, no bluetooth, no rils, but rom boots and i managed to walk throw menu, apps, worked realy fast, but with trying to enable rils (after that i thought that the rom will be ready to share for further development and fixes) i've got brick
thats why i'm saying that this thread must be in general section (in general section is just talkings, thinkings, maybe someones dreams, suggestions, findings etc. etc.).
Sent from not my ragelis
bronxitas said:
matteof93: have you tryed you're self to port cm9 to pro? try it
marsilinio has no sucsses - bootloop on boot animation.
kamatozko went further and maked logcat working and has bootloop at bootanimation.
i have made that cm9 boots up, but no camera, no wifi, no bluetooth, no rils, but rom boots and i managed to walk throw menu, apps, worked realy fast, but with trying to enable rils (after that i thought that the rom will be ready to share for further development and fixes) i've got brick
thats why i'm saying that this thread must be in general section (in general section is just talkings, thinkings, maybe someones dreams, suggestions, findings etc. etc.).
Sent from not my ragelis
Click to expand...
Click to collapse
i will try
There is oficial ICS kernel with working logcat:
http://forum.xda-developers.com/showpost.php?p=30364431&postcount=102
AOKP (Android Open Kang Project) isn't Cyanogen Mod, but look simalar and really very interesting.
There is AOKP for Honor:
http://narod.ru/disk/60340186001.13...58/it168_honor_FlyRazer2.0_superB977.zip.html
On u8800pro (with ics official kernel) dont work camera, Internet, maybe other. Work GSM, sd card, sensors. Lots of free ram.
There is AOKP port for u8800:
http://bbs.anzhi.com/thread-5552232-1-1.html
https://disk.yandex.net/disk/public/?hash=94nHyth775fWt1ZLNaS/mMn6uQ9QlDMClRauvK36eUE=&final=true
Yes, LG look very similar to u8800pro. Other similar device is Ideos X6:
http://devdb.ru/pda/compare/huawei_u9000_ideos_x6/huawei_u8800_ideos_x5_pro/
Ideos X6 custom roms cm9 &10, AOKP:
http://forum.xda-developers.com/forumdisplay.php?f=1292
Is there any way that the problem is that your trying to port a 4.0 rom to 2.3 base??maybe if you try over 4.0 base you will have better results...just saying!!
Wow. Glad to see that you people are interested in helping port the ROM correctly.
I'll try to find some time during the weekend to test all your ideas!
@matteof93
I just did a little research on msm8255 and saw htc desire s. Maybe an LG CM9 port(which is also officially supported as I see) can work. I think it the phone you suggested also worths a try to port.
I'll also try with your build.prop to see if the device boots any further.
As for the device tree, I'm of aware of this (thanks to pika) but it's that I don't have any github knowledge and can't compile easily from source + that I ask myself why didn't someone made an at least cm9 booting rom from this device tree during the past 5 months?
Anyway, I hope that you manage to build from sources though! Good luck with that! Keep us informed
@bronxitas
again maybe you are right about general section. a mod may move it if he finds it more suitable there.
@pikachukaki
I'm porting over 2.3 base for 2 reasons
1) Still can't install official ics due to error
2) kernel series is the same so I thought it wouldn't be a prob due to base.
anyway can't test due to reason1
@giris
damm qwerty12
why does he hide all the good stuff in others people threads and doesn't start a new one?
I'm not gonna try porting ideos x6 again (I've had a heart attack when my 1st test with an ideos x6 port didn't boot )
Maybe aokp of honnor worths also a shoot. The bad thing is that I can't repartition my system(step1 of official ics errors) and I can't flash most of ics roms around here..... Well my bad
I've even made a booting B977 port in the past with wifi working but due to small system partition I can't test any further because if I just enter another file the rom won't boot
Anyway people. Keep suggesting stuff and why not? even develop and present us a working port of yours
Ivansomething has posted devicetree for cm9 but when i try to compile it it gave me errors for kernel..it has to kernel files inside...i think one for 3.0.8 and one for .35 but i could do anything more...i think that if it was easy someone will make it until now...there is a reason that geno releases miui and not cm9/10!!who knows!!!
also i see that oguzhan mobile that posted here is making a cm9 for non pro (port then will be easy) so maybe we can compine with non pro devs to make something...everyone that has knowlage!also Mlopik is going to release cm10 for non pro also and bluefish is making cm9 but maybe he is abandon his project!!
Hey guys,
I finally built omni 4.4 for Gtab2 10.1
My wifi is turned On, but can't find any network.
I used latest blobs from samsung stock rom 4.2.2 to be sure.
logcat:
http://pastebin.com/xm6un9Tg
During the build process i faced an error :
Code:
out/target/common/obj/APPS/framework-res_intermediates/src/com/android/internal/R.java
out/target/common/obj/APPS/framework-res_intermediates/src/android/R.java
expected "}"
public static final class string-array{ }
^
this is not the exact error code but it was almost this.
To bypass this error i just comented both class, i wonder if this can be related?
thanks
I'd suggest looking at other device bringup commits first.
4.4 requires wifi configuration changes and storage configuration changes.
Entropy512 said:
I'd suggest looking at other device bringup commits first.
4.4 requires wifi configuration changes and storage configuration changes.
Click to expand...
Click to collapse
mmhh still no luck.
I don't have any error message in logcat now but still scanning for network and can't find any.
I based my change on aries bring up commit.
Now my ext sdcard work if i'm root, i may need to change some permission in fstab,
and i add edit this line in init.espresso10.rc
Code:
service wpa_supplicant /system/bin/wpa_supplicant \
-Dnl80211 -iwlan0 -e/data/misc/wifi/entropy.bin [email protected]:wpa_wlan0 \
-c/data/misc/wifi/wpa_supplicant.conf -O/data/misc/wifi/sockets
and if I try to add an ssid by hand i got this error in logcat:
Code:
E/WifiConfigStore( 441): failed to set SSID: "mywifi"
E/WifiConfigStore( 441): Failed to set a network variable, removed network: 0
E/WifiStateMachine( 441): Failed to save network
thanks.
Did you add it, or change the one that was already there?
Entropy512 said:
Did you add it, or change the one that was already there?
Click to expand...
Click to collapse
I add it to try, there is no wifi network, it loop on "searching network"
I wonder if my error can be related to what i said earlier
sevenup30 said:
During the build process i faced an error :
Code:
out/target/common/obj/APPS/framework-res_intermediates/src/com/android/internal/R.java
out/target/common/obj/APPS/framework-res_intermediates/src/android/R.java
expected "{"
public static final class string-array{ }
^
this is not the exact error code but it was almost this.
To bypass this error i just comented both class, i wonder if this can be related?
thanks
Click to expand...
Click to collapse
Do you face this error while building omni? can it be because of my java version? i'm on java 6
finally got it working, it was related in init conf file like you said.
Does someone just know how can I disable hardwar keyboard at first boot?
Because of that keyboard never show up so i have to skip the first settings and disable it in language & input.
sevenup30 said:
finally got it working, it was related in init conf file like you said.
Click to expand...
Click to collapse
Could you precise which mod you did in init conf file ?
Because I've the same problem with a build for Acer A200 : loop on AP scan, no results, no possibilities to configure an AP manually....
Thanks
sevenup30 said:
finally got it working, it was related in init conf file like you said.
Does someone just know how can I disable hardwar keyboard at first boot?
Because of that keyboard never show up so i have to skip the first settings and disable it in language & input.
Click to expand...
Click to collapse
Fix or remove the broken kernel driver that's reporting a keyboard as being present when it's not.
Another possibility is you're missing KL/IDC files for some input device that is being treated as a hardware keyboard when it's not. (See the galaxys2-common family - the sii9234 or whatever it is IDC file was needed to keep that input device from being detected as a HW keyboard)
For 4.4 goto 2'nd post
This is for JB 4.3.1
If you like me have the problem of : ( wifi + sim_card ) = wifi not working
here is the fix : credits to HTCZ715E
http://forum.xda-developers.com/showthread.php?t=2368501
but just 1 more step , after making the new "telephony-common.jar" and adb push , and chmod 644
you HAVE TO wipe dalvik+cache
without wipe dalvik+cache it never worked for me.
HTC MyTouch 4G
[ROM] CM-10.2 | AOSP 4.3 Jellybean [KANG] [Oct-11]
cm-10.2-20131011-Albinoman887-glacier
Well heads up to the android 4.4
non of the previous solutions is not working :crying:
today i tried ROM Legacy Carbon 4.4
so i started to use my knowledge about cracking from the old MS-dos ages !!!!!!!!! and i cracked the bcmdhd.ko file
using IDA dissembler and HexEdit the bcmdhd.ko file.
Now wifi works again. :good:
The problem is that , in this method i cannot provide a universal file and you have to make your own cracked driver ".ko" file.
Or the developers of each Rom should use the working source code for the wifi driver which has the complete support for all languages.
refer to this post:
http://forum.xda-developers.com/showthread.php?t=1077329
and also here are some lines from logcat (i changed my mcc , mnc and country to XX ) with the cracked driver.
(i prefer to use cracking instead of patching because it was previously we called it)
Code:
D/Tethering( 1874): Exception adding default nw to upstreamIfaceTypes: java.lang.NullPointerException
E/wpa_supplicant( 2047): wpa_driver_nl80211_driver_cmd: failed to issue private commands
E/WifiStateMachine( 1874): Failed to set country code XX
D/MccTable( 2051): updateMccMncConfiguration: mcc=XXX, mnc=XX
D/MccTable( 2051): getLocaleFromMcc to null_ir mcc=XXX
D/MccTable( 2051): getLocaleForLanguageCountry: skipping no language
D/MccTable( 2051): WIFI_COUNTRY_CODE set to ir
I/WifiService( 1874): WifiService trying to set country code to XX with persist set to true
D/MccTable( 2051): updateMccMncConfiguration updateConfig config={1.0 XXXmccXXmnc ?locale ?layoutDir ?swdp ?wdp ?hdp ?density ?lsize ?long ?orien ?uimode ?night ?touch ?keyb/?/? ?nav/? themeResource=null}
I/ActivityManager( 1874): Config changes=3 {1.0 XXXmccXXmnc en_US ldltr sw384dp w384dp h615dp 200dpi nrml long port finger -keyb/v/h tball/v s.6 themeResource=null}
The whole problem started from the "wldev_set_country" function in "C" code in a ".h" file of wifi driver.
i don't have the knowledge to manipulate the source code of the wifi driver and compile compile the ".ko" file.
This method is not for pplz who don't know about reverse engineering.
So i opened the "bcmdhd.ko" in IDA disassembler and select the ARM Architecture.
Then searched for the "wldev_set_country" function and in the disassembled code there is some Branches which should be re-routed.
for example: (these are the OP-Codes of ARM cpu)
BNE loc_206E4 in the hex view window "08-00-00-0A"
BNE = Branch if not Equal , (and must have to change to just Branch no matter what is the result of compare )
0A = BNE
EA = B (Branch)
AA = BGE (Branch if Greater or Equal)
..... and etc
The important thing is that in IDA hex-view for examaple it shows : 000206BC 08 00 00 1A
but at the bottom of window it shows: 000206F0 <= this is the address which u needs to find and change in your hex-ediotor
and in hex editor we will change that 1A to 0A
The whole process i re-route 4 branches to get success.
Also i've checked it , and there is no need to appliy the previous patch "telephony-common.jar"
Only the bcmdhd.ko driver needs to patch
I attached the cracked version of my bcmdhd.ko file.
you can try it , BUT IT MAY NOT FOR YOUR COUNTRY AND/OR YOUR SIM CARD and for sure it only works in some Roms
this is the driver version from dmesg
Dongle Host Driver, version 5.90.195.114
Compiled in drivers/net/wireless/bcmdhd on Nov 18 2013 at 17:0
Click to expand...
Click to collapse
i made the attachment for this Rom
[ROM][UNOFFICIAL] LegacyCarbon 4.4 \\ 18.11.2013 \\ Built From Source
you should unzip it and use "adb push" and "chmod 644 "
Code:
adb root
adb push bcmdhd.ko /system/lib/modules/
adb shell
su
cd /system/lib/modules/
chmod 644 bcmdhd.ko
and reboot
----------------------------------------------
HTC MyTouch 4G
[ROM][UNOFFICIAL] LegacyCarbon 4.4 \\ 18.11.2013 \\
I test this file on [ROM][Official][4.4] Evervolv Nightlies
It's compatible And works 100% :good:
BobZombiE said:
I test this file on [ROM][Official][4.4] Evervolv Nightlies
It's compatible And works 100% :good:
Click to expand...
Click to collapse
Did you use it? Bug important? I want to know some information. Thanks!
Sure , i'm using this patched driver almost on all Roms i'm testing and never had any wifi problems.
Sent from my myTouch 4G using xda app-developers app
BobZombiE said:
I test this file on [ROM][Official][4.4] Evervolv Nightlies
It's compatible And works 100% :good:
Click to expand...
Click to collapse
Camera, cam recording, and Browser? What any problem?
If I want back Rom 4.3 after install 4.4. Can I back?!
Thank so much your infomation!
hdhthed said:
Camera, cam recording, and Browser? What any problem?
If I want back Rom 4.3 after install 4.4. Can I back?!
Thank so much your infomation!
Click to expand...
Click to collapse
go to the related thread and take a look , or make a nandroid backup and try.
anyway:
Evervolv 4.0: at this moment: Camera does not work at all . but stock browser is ok :good:
Carbon 4.4 Rom : at this moment : Camera & Cam recording is ok. but stock browser does not work. u have to use other browsers like firefox
Yea! Make a nandroid backup ,after I can restore in Recovery. Have lost root?
hdhthed said:
Yea! Make a nandroid backup ,after I can restore in Recovery. Have lost root?
Click to expand...
Click to collapse
i don't think so
BobZombiE said:
i don't think so
Click to expand...
Click to collapse
Mean? You think lose root or cant restore a backup nandroid ?
hdhthed said:
Mean? You think lose root or cant restore a backup nandroid ?
Click to expand...
Click to collapse
i'm root and s=off , HBOOT 75
and flashed, backed up, restored my phone more than 100 times last week . and never lost root
This is my old phone... Fun to be back here.
I am asking about this modified driver. I need to find out first if my phone uses this driver (looks like a broadcom driver), but if it is, I am going to try it.
My question to the author is: do the changes you made make this driver location agnostic? Because you changed the BNE, to just branch, it seems that you are allowing it to function regardless of the country (in the MMC).
I have an HTC One running 4.4 and my issue is that I really need to use channel 13. My router is set to 13, but no matter what changes I make to the wi-fi region encoding (the region encoding change is successful), I still am limited to only channels 1 to 11.
So I just thought I'd ask to get your input on this...
Thanks,
Paul
help me solve my wifi issue
BobZombiE said:
For 4.4 goto 2'nd post
This is for JB 4.3.1
If you like me have the problem of : ( wifi + sim_card ) = wifi not working
here is the fix : credits to HTCZ715E
http://forum.xda-developers.com/showthread.php?t=2368501
but just 1 more step , after making the new "telephony-common.jar" and adb push , and chmod 644
you HAVE TO wipe dalvik+cache
without wipe dalvik+cache it never worked for me.
HTC MyTouch 4G
[ROM] CM-10.2 | AOSP 4.3 Jellybean [KANG] [Oct-11]
cm-10.2-20131011-Albinoman887-glacier
Click to expand...
Click to collapse
Hey guys ... I'am a normal user having sony xperia ion Lt28h .... I've just flashed CM11 unofficial rom but I have a wifi problem ..... can you teach me how to solve my regional wifi issue as I am in syria and have faced this problem earlier so i know it's a regional problem ..... thx for help
Two steps forward, one step back. IBSS/AdHoc WiFi networking support does not seem to be present in CM-11.
(Or perhaps a better way to describe this is that the Settings and Base class mods and wpa_supplicant patch sets were never committed to the the CM-11 branch)
So here's my question: has anyone seen this discussed someplace on the 'net by the CM dev team at a high level? That is, does CM have some sort of official position about IBSS/AdHoc support? Or is it more just a matter of needing a couple of devs to dive in and submit a set of patches against the CM-11 branch?
(I'm not sure at this point but I think that the CM10.2 patches might intersect with recent P2P/WiDi features in the CM-11 branch)
History:
The CM10.2 branch had support so that the non-hardware-dependent portions of CM (e.g. Settings Menus) would handle hardware with and without IBSS support, e.g.:
CM-10.2 WifiSettings.java
Code:
for (ScanResult result : results) {
// Ignore hidden networks.
if (result.SSID == null || result.SSID.length() == 0) {
continue;
}
// Ignore IBSS if chipset does not support them
if (!mIbssSupported && result.capabilities.contains("[IBSS]")) {
continue;
}
versus CM11 : WifiSettings.java :
Code:
for (ScanResult result : results) {
// Ignore hidden and ad-hoc networks.
if (result.SSID == null || result.SSID.length() == 0 ||
result.capabilities.contains("[IBSS]")) {
continue;
}
There's more to it than just that, of course.
I have a temporary tethering workaround for CM11 - using USB tethering and RNDIS, but it would be nice to be able to place my phone on a charger and have long-duration tethering as a possibility ... rather than trying a Y-cable/OTG hack. (I can't use BT tethering with my old phone, it panics the kernel on that device)
Any commentary is welcome.
FWIW I went and built both the full CM-11 tree (and also a RNDIS-enabled version of Metallice's a64 kernel). I think the CM 11 repo tree took up 22 GB of disk space when the sync was complete, and the build tree (without CCACHE) ended up at 50+ GB. I really didn't have enough RAM to avoid swap - one of the link steps runs up to 4.5 GB of virtual memory space... but with 6 gigs of swap space, 3 cores, and only 1.5GB of RAM dedicated to a VM, the build completed... slowly. I guess I need some RAM for Christmas
Hi, I just ported the changes to CM-11 and uploaded it for review:
see review.cyanogenmod.org change # 61020 (sorry, I'm not allowed to post URLs)
Any latest update on this IBSS mode on grouper? Thanks in advance .
I have Omni booting and running on a E210K (It is a SGS3 Korean variant, only changes are LTE, 2GB and DMB antenna), but some major bugs need fixing. There not much if any device trees for these out there so I have just been modifying the i9300 and it works.
These are probably the major two issues I have for now:
1. without manually adding ro.zygote.disable_gl_preload=1 to the build prop, it won't boot. I noticed this line wasn't in the i9300 builds either, but it's definitely referenced in my builds:
/android/omni/device/samsung/smdk4412-common/common.mk
# Set default USB interface
PRODUCT_DEFAULT_PROPERTY_OVERRIDES += \
persist.sys.usb.config=mtp \
ro.zygote.disable_gl_preload=true
Click to expand...
Click to collapse
2. Can't adjust the vibration in advanced settings, when I do I get the logcat message below, there is no (very light) feedback because it seems the value is set very low.
If I manually edit the values (by putting it up to 10+) I can get feedback, so it is working.
Code:
I/ActivityManager( 2466): Displayed org.omnirom.device/.DeviceSettings: +428ms
W/DeviceSettings_Utils_Read( 5375): file /sys/vibrator/pwm_val: 2
W/DeviceSettings_Utils( 5375): file /sys/vibrator/pwm_val not found: java.io.FileNotFoundException: /sys/vibrator/pwm_val: open failed: EACCES (Permission denied)
W/DeviceSettings_Haptic( 5375): key: vibrator_tuning
but I have no idea where/how to proceed.
My device tree is up over at:
https://github.com/kaijura/android_device_samsung_e210k
I am using the same omni sources for smdk4412-common and kernel.
Thanks in advance
kaijura said:
I have Omni booting and running on a E210K (It is a SGS3 Korean variant, only changes are LTE, 2GB and DMB antenna), but some major bugs need fixing. There not much if any device trees for these out there so I have just been modifying the i9300 and it works.
These are probably the major two issues I have for now:
1. without manually adding ro.zygote.disable_gl_preload=1 to the build prop, it won't boot. I noticed this line wasn't in the i9300 builds either, but it's definitely referenced in my builds:
2. Can't adjust the vibration in advanced settings, when I do I get the logcat message below, there is no (very light) feedback because it seems the value is set very low.
If I manually edit the values (by putting it up to 10+) I can get feedback, so it is working.
Code:
I/ActivityManager( 2466): Displayed org.omnirom.device/.DeviceSettings: +428ms
W/DeviceSettings_Utils_Read( 5375): file /sys/vibrator/pwm_val: 2
W/DeviceSettings_Utils( 5375): file /sys/vibrator/pwm_val not found: java.io.FileNotFoundException: /sys/vibrator/pwm_val: open failed: EACCES (Permission denied)
W/DeviceSettings_Haptic( 5375): key: vibrator_tuning
but I have no idea where/how to proceed.
My device tree is up over at:
https://github.com/kaijura/android_device_samsung_e210k
I am using the same omni sources for smdk4412-common and kernel.
Thanks in advance
Click to expand...
Click to collapse
LTE screams "qcom modem" to me - perhaps look at the i9305 tree?
Figured it out, for anyone searching for this problem - the issue has to do with the ramdisk portion of a (custom) kernel as it wasn't matching up omni's init setups.
Entropy512 said:
LTE screams "qcom modem" to me - perhaps look at the i9305 tree?
Click to expand...
Click to collapse
Tried a i9305 build it was a little worse off (no mobile connection), haha. I'm thinking of submitting for an official build after I figure out the build for a working stock omni kernel.
Since this device gets few attention (maybe less than 50 in the sgs3 forum) is it possible that you guys could set the jenkins buildbot to build like every week or other week?
kaijura said:
Figured it out, for anyone searching for this problem - the issue has to do with the ramdisk portion of a (custom) kernel as it wasn't matching up omni's init setups.
Tried a i9305 build it was a little worse off (no mobile connection), haha. I'm thinking of submitting for an official build after I figure out the build for a working stock omni kernel.
Since this device gets few attention (maybe less than 50 in the sgs3 forum) is it possible that you guys could set the jenkins buildbot to build like every week or other week?
Click to expand...
Click to collapse
Hmm, that might be a possibility...
kaijura said:
I have Omni booting and running on a E210K (It is a SGS3 Korean variant, only changes are LTE, 2GB and DMB antenna), but some major bugs need fixing. There not much if any device trees for these out there so I have just been modifying the i9300 and it works.
These are probably the major two issues I have for now:
1. without manually adding ro.zygote.disable_gl_preload=1 to the build prop, it won't boot. I noticed this line wasn't in the i9300 builds either, but it's definitely referenced in my builds:
2. Can't adjust the vibration in advanced settings, when I do I get the logcat message below, there is no (very light) feedback because it seems the value is set very low.
If I manually edit the values (by putting it up to 10+) I can get feedback, so it is working.
Code:
I/ActivityManager( 2466): Displayed org.omnirom.device/.DeviceSettings: +428ms
W/DeviceSettings_Utils_Read( 5375): file /sys/vibrator/pwm_val: 2
W/DeviceSettings_Utils( 5375): file /sys/vibrator/pwm_val not found: java.io.FileNotFoundException: /sys/vibrator/pwm_val: open failed: EACCES (Permission denied)
W/DeviceSettings_Haptic( 5375): key: vibrator_tuning
but I have no idea where/how to proceed.
My device tree is up over at:
https://github.com/kaijura/android_device_samsung_e210k
I am using the same omni sources for smdk4412-common and kernel.
Thanks in advance
Click to expand...
Click to collapse
This says u r building a rom.Is it working fine?
thanks