Related
Had a wi-fi problem on my htc desire for a while now..
One time I went to turn wi-fi on and it just said "Unable to start wi-fi". It had worked totally fine up until that point.
I've tried doing a factory reset, rooted, updated rom but it's still not working.
When the problem happened I had not rooted the phone or changed anything really.. it just happened.
In logcat it says:
flg=0x10200000 cmp=com.android.settings/.wifi.WifiSettings bnds=[124,404][236,531] }
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
W/SyncAllWidget( 151): activeSynch is null false
I/ActivityManager( 79): Displayed activity com.android.settings/.wifi.WifiSettings: 495 ms (total 495 ms)
I/WifiHW ( 79): wifi_load_driver enter
D/SettingsWifiEnabler( 548): Received wifi state changed from Unknown to Enabling
D/dalvikvm( 1805): GC freed 3806 objects / 257536 bytes in 97ms
D/NetworkLocationProvider( 79): onCellLocationChanged [1363,22890]
I/WifiHW ( 79): wifi_load_driver end error 2
E/WifiService( 79): Failed to load Wi-Fi driver.
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
Anyone got any ideas on how to fix this?
h2o pete said:
Had a wi-fi problem on my htc desire for a while now..
One time I went to turn wi-fi on and it just said "Unable to start wi-fi". It had worked totally fine up until that point.
I've tried doing a factory reset, rooted, updated rom but it's still not working.
When the problem happened I had not rooted the phone or changed anything really.. it just happened.
In logcat it says:
flg=0x10200000 cmp=com.android.settings/.wifi.WifiSettings bnds=[124,404][236,531] }
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
W/SyncAllWidget( 151): activeSynch is null false
I/ActivityManager( 79): Displayed activity com.android.settings/.wifi.WifiSettings: 495 ms (total 495 ms)
I/WifiHW ( 79): wifi_load_driver enter
D/SettingsWifiEnabler( 548): Received wifi state changed from Unknown to Enabling
D/dalvikvm( 1805): GC freed 3806 objects / 257536 bytes in 97ms
D/NetworkLocationProvider( 79): onCellLocationChanged [1363,22890]
I/WifiHW ( 79): wifi_load_driver end error 2
E/WifiService( 79): Failed to load Wi-Fi driver.
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
Anyone got any ideas on how to fix this?
Click to expand...
Click to collapse
I have the same problem on a ROM i have made... That's just for Tattoo not Desire... But it's the same logcat... So can somebody help us??
Yeah I'm pretty stuck on what to do :/.
Added some information about my software to the first post.
i have same problem on my htc dream
BUMP...
-------------------------------------
Sent from my übercharged HTC Tattoo
Fixed it by setting a static IP address.
Wi-Fi > Menu Button > Advanced > Use static IP
i had yesterday the same problem on my desire,
i fixxed this with flash a "older" stock rom and update it with the build-in updater....
same problem with my desire. how to fix it?
It's broke again. Setting a static IP doesn't fix it any more. Any ideas?
got the same problem here
can any one help???
Bump
Sent from my HTC Desire using XDA App
seems like wlan.ko is not available in /system/lib/modules/
I've had similar problems in the past, but was unable to solve them. You can check several things though.
1) wlan.ko in /system/lib.modules <-- has to match up with the kernel that you are using
2) any entries for wifi and/or dhcp in the init.rc and init.devicenamehere.rc files that are in the ramdisk in the boot.img
3) wifi settings in the build.prop
4) files in /system/etc/wifi
5) I'm not sure about this one, but even some of the files in /system/etc/firmware might have something to do with wifi.
6) files in /system/etc/dhcpd
7) any files in /system/bin and/or /system/xbin that are called by *.rc from #2.
Just take a working ROM (stock is usually what I use), and compare the files with the corresponding files in your build. I use either WinMerge or N-way Folder Compare or just plain old 'diff' in Linux.
I had the same issue.
Flashed a new ROM with full wipe etc. Wifi OK.
Flashed a kernel update on top of the ROM. Wifi broken. Turning wifi on it would error and turn off again.
The only way I could fix it was to flash a full ROM and make sure I wiped everything from the recovery.
Any more info you can provide? Current ROM +version +any other mods applied like status bar or OC kernels?
Did anyone fix this?? I am stuck here, G1 Dream
CM 5.0.8 DS
Please help!!!
Are you getting the same error in logcat as others have? If so, I think .mak fixed it, but he never let us know how.
Same Issues...
Ive tried Reverting to CM 5.07, 5.07 and now the beta 6.0 and all have yet to fix the wifi issue. I also tried switching between the radio's and doing a full format/partition and wipe. Any fix to this yet?
That was Lovely Bro...Really Useful...I got my DESIRE today and could connect to WIFI but was unable to browse...This tip helped me...Thx a lot... Keep up the good work..
Trying to replace bcm4329.ko
I did the OTA update for my Desire today, and of course have the wi-fi problem.
However, when I enable wi-fi, I see the following appear at the end of dmesg:
Code:
<3>[ 8197.511535] bcm4329: version magic '2.6.32.15-g6a358a9 preempt mod_unload
ARMv7 ' should be '2.6.32.15-gf9c0527 preempt mod_unload ARMv7 '
The update zip (via thread 778852) contains a bsdiff patch file patch/system/lib/modules/bcm4329.ko.p... and from some examination of that file it appears just to patch the vermagic field of the .ko file.
I tried to use a hex editor to 'fix' bcm4329 and used adb pull/push to replace it, but I get
Code:
failed to copy 'bcm4329.ko.fix' to '/system/lib/modules/bcm4329.ko': Read-only
file system
Can anyone help me with this?
Update: I am a fool. I was using the wrong goldcard! Once I put the right goldcard in, then sdcard:update.zip applied correctly and wi-fi started working again.
@dleonard, could you please make step by step instructions of how to fix this wifi issue?
thanks
Mixu
BUG REPORTING:
This program was initially ineteded to generate a unique IMEI based on your device S/N and update Dev's install zip files... it has become so much more, and as such there are many functions involved in this process.
Due to the complexity the program has taken on... far beyond what I initially intended... to report bugs please try to use the following as a template:
Function attempting: i.e. Updating ROM... In Place Upgrade... Update framework saved on computer... etc.
Error Messages: any error message you receive... or the last message you saw prior to the issue.
End result: i.e. TelephonyManager updated, ROM not... TelephonyManager updated framework.jar not... etc....
Environment: ROM in same folder as !IMEIme.exe... ROM on same drive as IMEIme.exe... ROM on different drive... etc. (same for framework if updating framework instead)
!IMEIme.ini settings: you can put your entire ini file if you'd like.
If you could take notes of EXACTLY what buttons you click on which prompt it would be EXTREMELY helpful...
As I said, this program has taken on functions I initially had not imagined including... the more features added, the more complex testing and tracking bugs becomes... I don't want to include a bunch of messages just for the sake of letting you know where in the code you are... would not be beneficial to you... more buttons to click for no reason, etc.
The more detailed you can be, the quicker I can see what is happening... otherwise I have to try to duplicate what I think you are doing when you get the error.
Everyone should click "Thanks" on bug report posts... they have been instrumental in getting the program where it is so far.
RESERVED...
Adverse effects after running
First off, thanks for a wonderful application! Your app did in fact correctly give my Kindle a IDEI number, but it seems to have adverse effects.
Function attempting: Tried both in place Rom and update device and now attempting to use app with sound
Error Messages: Unfortunately DSP Manager has stopped (repeatably on any app)
End result: No sound and music apps crash. Some apps work but many do not. (I can provide logcat if needed)
Environment: Kindle Fire running cm9 using Hashcodes 3.0 Kernal latest (11) update.
!IMEIme.ini settings:
Use_In_Place = 0
Use_Previous_Patch = 0
Use_Serial_Number = 0
Use_MAC_Address = 0
Use_Manual_Input = 1
Encrypt_IMEI = 0
Use_IMEI(15) = 0
Use_ADB = 1
Use_ADB(usb) = 1
Use_ADB(WiFi) = 0
Clean_Up = 1
Include_Patch = 1
Device_Manufacturer = TI
Manufacturer_Device = Blaze
Device_Model = Full Android on Blaze or SDP
Build_Fingerprint = google/passion/passion:2.3.6/GRK39F/189904:user/release-keys
LCD_Density =
WiFi_IP_Address =
IMEI = 00127948612384612
Although I have tried multiple settings and configurations. I am sort of a noob so sorry if this is a silly problem.
Having looked into this... I can tell you there's nothing that the IMEI Generator does that would cause the issues you are seeing. I would recommend flashing a non-IMEI'd ROM for testing... then either do in place IMEI generation or running the IMEI Generator against the same ROM you flash.
For what you are doing... there are 2 files that are being modified, and neither should cause FC issues...
/sysem/build.prop for the manufacture, device, and build fingerprint
/system/framework/framework.jar is being extracted and edited to patch the IMEI in the GetDeviceID() function in android/telephony/TelephonyManager.smali and recompiled.
Clearing cache and dalvik cache may be something to try.
Thanks! Clearing both caches AFTER the install made it work great. I had been clearing all of the memory beforehand but it did not work. My apps now work great!
Motorola Razr GSM (SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF) ICS.
I deodexed framework.jar because application seems to not work on odex files (as stock is), anyway new deodexed framework have not /com/android/internal/telephony/gsm/GSMPhone.smali file?! (or dir!!) infact !IMEIme 2.2.0.2 tell me about this issue (no GSMPhone.smali found). framework patched do not present diffecence between original one. exactly the same. no /android/telephony/TelephonyManager.smali mod applied.
I tryied to patch framework by "update device" + adb usb, with no device connected i choosed my framework.jar in my pc.
[Settings]
Use_In_Place = 1
Use_Previous_Patch = 0
Use_Serial_Number = 1
Use_MAC_Address = 0
Use_Manual_Input = 1
Encrypt_IMEI = 0
New_Type = 1
Use_IMEI(15) = 0
Use_ADB = 1
Use_ADB(usb) = 1
Use_ADB(WiFi) = 0
Clean_Up = 1
Include_Patch = 0
Device_Manufacturer =
Manufacturer_Device =
Device_Model =
Build_Fingerprint =
LCD_Density =
WiFi_IP_Address =
IMEI = 02546451548481584
stock framework.odex, jar and my deodexed framework attached.
Yes... due to another user trying to use the generator on a device with a framework.odex file instead of framework.jar I am looking into the most effective method of handling that situation. As of now... the generator will not work for you to patch imei functionality into the framework on these devices.
i deodexed also framework.jar but no way to patch it, GSMPhone.smali is missing totally even in backsmalied odex too!!!!
I decided to apply the patch manually, but without this file and TelephonyManager.smali not regoular i was thinking about hard mod by motorola?! do you know something about?
Pls man, give me an hand, show me the way, backsmali it you too http://forum.xda-developers.com/attachment.php?attachmentid=1634550&d=1357865096
I'm looking into the method to implement the imei into this.
do you mean into TelephonyManager.smali? I'm looking on it too. Seems so strange this framework...
Actually... looking through to find the best call to implement the patch into... TelephonyManager was the original method... but there may be better places to patch it.
Code:
invoke-direct {p0}, Landroid/telephony/TelephonyManager;->getSubscriberInfo()Lcom/android/internal/telephony/IPhoneSubInfo;
move-result-object v2
invoke-interface {v2}, Lcom/android/internal/telephony/IPhoneSubInfo;->getDeviceId()Ljava/lang/String;
All does make sense now:
http://grepcode.com/file/repository...nternal/telephony/IPhoneSubInfo.java?av=f#174
BUT, where is com.android.internal.telephony.iphonesubinfo!?!?! seems not present... all "internal" dir is missing here, backsmali fault or my fault?!
hiiii
hi,
any news of this? =)
This is the best software for this!
I'm working on the best solution... I understand the desire for this... but I want to ensure the method I choose is the best overall... and to ensure I can properly detect which method to implement during the operation.
If you could zip your entire /system/framework folder and add your /system/build.prop file it would help me test some things I've been putting together for odexed systems.
attaching files
DizzyDen said:
If you could zip your entire /system/framework folder and add your /system/build.prop file it would help me test some things I've been putting together for odexed systems.
Click to expand...
Click to collapse
Hi, Im attaching my files.
You can download here: w w w . 4 s h a r e d . c o m / z i p / j Q n n 9 8 _ B / s y s t e m . h t m l
Thanks for the help
Error ...
Hi Dizzy
I tried to use your update, but have a error ... My device is Motorola Razr XT910 with 4.0.4
after I choose the "framework.jar" he return this error:
Line 3710 (File: ".....\IMEI\!IMEIme.exe");
Error: Variable used without being declared.
After this the program close without any click to exit ..
Im, attaching a print screen
Tnx a lot man
waldirsp11 said:
Hi Dizzy
I tried to use your update, but have a error ... My device is Motorola Razr XT910 with 4.0.4
after I choose the "framework.jar" he return this error:
Line 3710 (File: ".....\IMEI\!IMEIme.exe");
Error: Variable used without being declared.
After this the program close without any click to exit ..
Im, attaching a print screen
Tnx a lot man
Click to expand...
Click to collapse
fixed... I guess nobody has been using the "Use Previous Fix" option for a while. New version uploaded... thank you for the bug report. The screen shots really helped track it down.
another error...
Hi DizzyDen,
I want to add an IMEI to my "SUPERPAD 6", but after the window: "IMEI is..." is displayed, then popup an autoit error window:
Line 3710 (File "..."): Error: Variable used without being declared.
Can you help?
Ponozka said:
Hi DizzyDen,
I want to add an IMEI to my "SUPERPAD 6", but after the window: "IMEI is..." is displayed, then popup an autoit error window:
Line 3710 (File "..."): Error: Variable used without being declared.
Can you help?
Click to expand...
Click to collapse
Before I start looking into this... note that the IMEI generator does not support de-odexing odexed systems yet... I would suggest using it on the ROM then flashing it to the device and let the device odex it again.
Hi!
I am currently working on a CM 7.2 port for the Dell Streak 5, which I want to share soon (I can't post this in the dev forum because I don't have enough posts written just yet). Currently I am trying to find a fix or a workaround for the following problem:
Sometimes, the Streak immediately reboots and shows the Dell logo. It just shows the following kernel logs (also written to LogCat):
Code:
07-03 19:13:09.348 W/PrintK ( 83): ARM9 has CRASHED
07-03 19:13:09.348 W/PrintK ( 83): smd_diag, smem: DIAG ''
07-03 19:13:09.348 W/PrintK ( 83): ARM9 has CRASHED
07-03 19:13:09.348 W/PrintK ( 83): smd_diag, smem: DIAG ''
07-03 19:13:09.348 W/PrintK ( 83): ARM9 has CRASHED
07-03 19:13:09.348 W/PrintK ( 83): smd_diag, smem: DIAG ''
07-03 19:13:09.348 W/PrintK ( 83): ARM9 has CRASHED
07-03 19:13:09.348 W/PrintK ( 83): smd_diag, smem: DIAG ''
07-03 19:13:10.430 W/PrintK ( 83): ARM9 has CRASHED
07-03 19:13:10.430 W/PrintK ( 83): smd_diag, smem: DIAG ''
07-03 19:13:10.430 W/PrintK ( 83): ARM9 has CRASHED
07-0
When I searched the kernel source, it seems that the following lines in arch/arm/mach-msm/smd.c are responsible for this log output (ommitting the parts that are not compiled):
Code:
#if defined (CONFIG_QSD_ARM9_CRASH_FUNCTION)
void smd_diag(void)
{
char *x;
x = smem_find(ID_DIAG_ERR_MSG, SZ_DIAG_ERR_MSG);
if (x != 0)
{
SMD_CRASH_LOG( "%s, smem: DIAG '%s'\n", __func__, x);
queue_work(crash_work_queue, &smd_crash_worker);
}
}
#else /* CONFIG_QSD_ARM9_CRASH_FUNCTION */
/* ommitted (not compiled) */
#endif /* CONFIG_QSD_ARM9_CRASH_FUNCTION */
static void handle_modem_crash(void)
{
SMD_CRASH_LOG( "ARM9 has CRASHED\n");
smd_diag();
/* hard reboot if possible FIXME
if (msm_reset_hook)
msm_reset_hook();
*/
/* in this case the modem or watchdog should reboot us */
#ifndef CONFIG_QSD_ARM9_CRASH_FUNCTION /* return imediately for kernel to do something */
for (;;)
#endif /* CONFIG_QSD_ARM9_CRASH_FUNCTION */
;
}
It seems that the modem is crashing and forces the device to reboot. The severe problem is that sometimes the device ends up rebooting again and again, suddenly stuck in the Dell logo - so maybe the reboot performed by the modem is not correct. But in the optimal case the device should just reset the modem, and not reboot the entire device.
As the radio drivers are only available in binary form (of course) and the device already is EOL, I really need help to find a good workaround. Does anybody have a solution to this problem?
I discovered that there is a kernel driver available in arch/arm/mach-msm/reset_modem.c that sounds interesting. It should be able to reset the modem by writing the appropriate command to a kernel device, and which is compiled as a kernel module in the default Dell Streak kernel config. Has anybody tried this out yet?
Thanks in advance & regards
Marc
PS: I am using the Phoenix kernel by the DSC Team, added with some patches by _n0p_.
Hi Marc!
How severe this problem is?
Hi _n0p_!
It's very severe to me - I have a couple of these devices here, and it's really critical if they turn off during operation (and some of them don't even come back up again afterwards).
It would be better if the radio was reset on failure - I can afford that the devices do not have a radio connection for a couple of seconds. Or at least this is what I hope.
There's a "System Type -> Reset Modem Driver" module option in kernel.
May sound dumb, but maybe it needs it?
_n0p_ said:
There's a "System Type -> Reset Modem Driver" module option in kernel.
May sound dumb, but maybe it needs it?
Click to expand...
Click to collapse
I recompiled the kernel with this module built-in, but from what I read from the source code it's just providing a device /dev/reset_modem to enable users to reset the modem from userspace (as root). However, this will not be possible entirely if the kernel itself is rebooting already, leaving no chance to any userspace commands. I believe this has to be fixed in the kernel itself. Right now I am looking at the method smsm_reset_modem in the file smd.c which sounds quite interesting. Maybe I can deactivate the code for rebooting the device there and instead run code to reset the modem. Interestingly, setting CONFIG_QSD_ARM9_CRASH_FUNCTION to 'n' in the config leads to kernel compilation errors - so the Streak was never intented to resolve modem problems the better way...
By the way, a few minutes ago I was able to log a modem restart during the reboot loop with LogCat:
pastebin.com/9U3XPxdK (yay, I can not post links yet :/ )
This looks really ugly - but it could help during debugging the problem. It would be much nicer to know what actually forces the modem to restart... (is it possible to get the stack trace during runtime, maybe by using a special macro?)
cant you check on the build based on the cm7.2 that already at the dev section? if it is not all, at least some of it would help...
deysmacro said:
cant you check on the build based on the cm7.2 that already at the dev section? if it is not all, at least some of it would help...
Click to expand...
Click to collapse
I don't know exactly what triggers the problem - maybe the devices run fine for a long time, but crash when using GPS + network in some odd way, or when the network type switched from 2G to 3G or back - I really can't tell.
As for CM 7.2, I had to build from the sources (both Kernel and CM) in order to do fixes to the ROM etc. Maybe I could try out the CM 7.2 build, but even if the problem would (not) exist there, too, I would be back to the start.
At least yesterday I tried out the reset_modem kernel module and tried all commands I could find in the source on the device /dev/reset_modem - it just crashed the modem and the device all the time, instead of one command which was effectively doing nothing. So back to the start... :-(
man... that does sucks... well... i wish you all the best nonetheless... :good:
Where's an interesting module param:
msm_smd_debug_mask
--
Also, according to:
Code:
#define MODEM_CRASH_NOTIFY_USER
extern void qi2ccapkybd_set_led(unsigned int light);
#define MODEM_CRASH_NOTIFY_USER_0 do {qi2ccapkybd_set_led(0x0);} while(0)
#define MODEM_CRASH_NOTIFY_USER_1 do {qi2ccapkybd_set_led(0xFFFFFF);} while(0)
It should blink leds on going to reboot.
--
Marc, thank you! While looking at SMD i found the code that blinks leds on AMSS mismatch (finally!)
_n0p_ said:
Marc, thank you! While looking at SMD i found the code that blinks leds on AMSS mismatch (finally!)
Click to expand...
Click to collapse
wow...! a discovery... ! :victory:
This actually leads me to think that we now free of "Blinking LEDs problem" and maybe, just maybe changing AMSS (BB) might help with modem reset problem.
I'm currently using 366 (manics told that it has good voice quality).
_n0p_ said:
This actually leads me to think that we now free of "Blinking LEDs problem" and maybe, just maybe changing AMSS (BB) might help with modem reset problem.
I'm currently using 366 (manics told that it has good voice quality).
Click to expand...
Click to collapse
last time i downgraded from rom based on 407 to 366 and although the blinking led happens.. but phone continue to work like normal... :laugh:
and yeah... 366 does have a good voice quality... and not mention excellent cell tower reception... it is proven since i have been in the building where reception is pretty much poor.. but with 366... somehow it almost always full...
but since nobody make a custom ROM based on 366, i had to sadly use other ROM...
As it's a bit offtopic, let's continue here:
http://forum.xda-developers.com/showpost.php?p=28318630&postcount=4374
Hey _n0p_!
Yeah, that seems to be the code that leads to blinking LED sensor keys on wrong AMSS!
As for the AMSS/DSP1 partitions, I currently use the newest from the original Streak 407 firmware, which I flashed via 'fastboot flash amss amss.mbn' and 'fastboot flash dsp1 dsp1.mbn'. Maybe that leads to the problems.
So you would recommend downgrading to amss 366? Although it does not match the kernel version and Android version? Isn't this a bad idea in general?
And for the DSP1, which version do you recommend - also from 366? Or the complete 366 update.pkg?
I am currently testing the image I flashed after initially flashing the 407 package the correct way - maybe this fixes the problems. Otherwise I will try 366.
By the way: Is there a good overview available what all the other files do, e.g. fsbl.mbn, osbl.mbn, dbl.mbn and appsboot.mbn?
From what I know, DT.img is the bootloader, amss the baseband software and dsp1 the DSP software for audio. And I know it's dangerous to flash the files individually, as I was able to completely brick a device by just flashing one of these special partitions...
Well, i'm using 366 right now. Too early to tell a conclusion, but it seems like default audio output is lower then in 4062 BB.
So far no glitches.
And i'm using only AMSS.
--
AFAIK DT.mbn is firmware updater, but I might be wrong.
Also DSP also works for video processing as well.
--
Almost forgot: it seems simple to disable bb error reboot.
Maybe it's worth giving a test?
_n0p_ said:
Almost forgot: it seems simple to disable bb error reboot.
Maybe it's worth giving a test?
Click to expand...
Click to collapse
Do you mean disabling CONFIG_QSD_ARM9_CRASH_FUNCTION in the kernel config? I did this, recompiled (had to fix a small include error after that, too) and tried it out - so far it crashed again after some time of usage.
BTW, how did you disable the AMSS version check? I guess you disabled the option CONFIG_QSD_OEM_RPC_VERSION_CHECK - but it's good to know.
I thought of simply trimming that rpc probe proc.
And you are right, that's the conf value plus needs ifdefing undeclared version check (in this case), variable.
Marc, it seems like
#if 0
//#ifdef CONFIG_BUILDTYPE_SHIP
SMD_CRASH_LOG( "%s: restart system\n", __func__);
queue_delayed_work(restart_work_queue, &smd_crash_restart_worker,
MODEM_CRASH_RESTART_TIMEOUT);
#endif /* CONFIG_BUILDTYPE_SHIP */
would reboot device only if modem in reset state and camera button is pressed.
Hey n0p!
_n0p_ said:
Marc, it seems like
#if 0
//#ifdef CONFIG_BUILDTYPE_SHIP
SMD_CRASH_LOG( "%s: restart system\n", __func__);
queue_delayed_work(restart_work_queue, &smd_crash_restart_worker,
MODEM_CRASH_RESTART_TIMEOUT);
#endif /* CONFIG_BUILDTYPE_SHIP */
would reboot device only if modem in reset state and camera button is pressed.
Click to expand...
Click to collapse
I tried your code, as well as some other fixes. It always led to a kernel loop and the modem didn't come back, so in the end I just included a solution to detect the problem and continue to reboot the device.
From what I learned in the last few weeks, it seems the complete ARM processor goes down with the modem. In the end, it seems to be a hardware problem, because I noticed the following facts:
Even if I completely re-flash a device that shows an error, it still occurs - especially when the network is used.
Some devices do not show this problem and can run for a long time. Other devices that had this problem always continue to have this problem. Even after re-flashing and even using different amss/dsp1 versions and on the original software.
What's more: I also had the problem on a new device that never had a custom ROM on it. Yeah, using the original firmware.
So in the end everyone should be better off to throw away his device if this problem occurs.
All dev related posts for fixing cm9 will come here.
All ideas are welcome but dont post for eta and stuff like that..
Currently fixing: Bluetooth
ToDo:
Camera
Internal memory
Graphic flickering
Audio(partially working)
Anything else?
Fixed:Wifi
My device tree: https://github.com/hell-lock-xda/android_device_htc_protou
If you manage to fix anything then send me a pull request.
prototype-U said:
All dev related posts for fixing cm9 will come here.
All ideas are welcome but dont post for eta and stuff like that..
Currently fixing: WiFi
ToDo: Bluetooth
Camera
Internal memory
Graphic flickering
Audio(partially working)
Anything else?
My device tree: https://github.com/hell-lock-xda/android_device_htc_protou
If you manage to fix anything then send me a pull request.
Click to expand...
Click to collapse
Fixed:
Camera atis 112 fixed it (if permissions were granted )
Internal Memory ( same as above )
I'll try ti fix graphical glitches
And wait have you tried using stuff from lliors device trees/ github?
The Android Manual said:
Fixed:
Camera atis 112 fixed it (if permissions were granted )
Internal Memory ( same as above )
I'll try ti fix graphical glitches
And wait have you tried using stuff from lliors device trees/ github?
Click to expand...
Click to collapse
Where is the fix??
BTW @all the above device tree is not working properly.. pls dont compile it.. I will soon make a working device tree
prototype-U said:
Where is the fix??
BTW @all the above device tree is not working properly.. pls dont compile it.. I will soon make a working device tree
Click to expand...
Click to collapse
In atis112's guthub his cm9 build has a functioning camera and internal memory
The Android Manual said:
In atis112's guthub his cm9 build has a functioning camera and internal memory
Click to expand...
Click to collapse
I have his tree forked and camera is nt working.. dunno abt internal
Good news and bad news for ya all!
Bad news:Wifi is still not working properly
Good news:WiFi drivers are loading properly! But its showing probs with supplicant. I was able to replicate such problems on stock rom too so we are pretty close to fixing it!
Code:
23:26:55.120 Error WifiHW 294 Supplicant not running, cannot connect
23:26:44.093 Info logwrapper 4398 /system/bin/wpa_supplicant terminated by exit(255)
23:26:44.093 Error wpa_supplicant 4401 wlan0: Unsupported driver 'nl80211'
23:26:39.065 Error WifiStateMachine 294 Failed to setup control channel, restart supplicant
23:26:24.107 Error wpa_supplicant 3977 wlan0: Unsupported driver 'nl80211'
23:26:24.107 Info logwrapper 3974 /system/bin/wpa_supplicant terminated by exit(255)
Adding the commit to github and will work on that driver..
prototype-U said:
Good news and bad news for ya all!
Bad news:Wifi is still not working properly
Good news:WiFi drivers are loading properly! But its showing probs with supplicant. I was able to replicate such problems on stock rom too so we are pretty close to fixing it!
Code:
23:26:55.120 Error WifiHW 294 Supplicant not running, cannot connect
23:26:44.093 Info logwrapper 4398 /system/bin/wpa_supplicant terminated by exit(255)
23:26:44.093 Error wpa_supplicant 4401 wlan0: Unsupported driver 'nl80211'
23:26:39.065 Error WifiStateMachine 294 Failed to setup control channel, restart supplicant
23:26:24.107 Error wpa_supplicant 3977 wlan0: Unsupported driver 'nl80211'
23:26:24.107 Info logwrapper 3974 /system/bin/wpa_supplicant terminated by exit(255)
Adding the commit to github and will work on that driver..
Click to expand...
Click to collapse
can you upload the built you made??
mhb92 said:
can you upload the built you made??
Click to expand...
Click to collapse
I hate posting here, but if you want the build, check out the sources.
Sent from my awesome, stock, Nexus7!
i will be able to check source from my main pc next week..thats why i want the built rom...i wanna check something about supplicant file
mhb92 said:
i will be able to check source from my main pc next week..thats why i want the built rom...i wanna check something about supplicant file
Click to expand...
Click to collapse
I will upload it in few hrs from now..
new build is compiling
Ok..! Waiting for link
Sent from my HTC Desire X using xda app-developers app
So guys here is the latest build. Sorry I cant put it on d-h.st cuz my connection is slow and I will prefer github until we fix all the bugs.
https://github.com/hell-lock-xda/cm9-packages
Just click on zip.
And the kernel is here..
http://d-h.st/zSS
prototype-U said:
So guys here is the latest build. Sorry I cant put it on d-h.st cuz my connection is slow and I will prefer github until we fix all the bugs.
https://github.com/hell-lock-xda/cm9-packages
Just click on zip.
And the kernel is here..
http://d-h.st/zSS
Click to expand...
Click to collapse
https://raw.github.com/hell-lock-xda/cm9-packages/master/cm-9-20130505-UNOFFICIAL-protou.zip
Error: blob is too big
BTW:
init.rc, that loads the wpa_supplicant service, also specifies nl80211.
WiFi almost fixed. It gets turned on but still few errors left to fix(scanning and stuff not working till now).
Code:
18:47:17.788 Info wpa_supplicant 2988 rfkill: Cannot open RFKILL control device
18:47:17.898 Info wpa_supplicant 2988 WPS: Converting push_button to virtual_push_button for WPS 2.0 compliance
18:47:18.007 Error WifiConfigStore 298 Error parsing configurationjava.io.FileNotFoundException: /data/misc/wifi/ipconfig.txt: open failed: ENOENT (No such file or directory)
18:47:18.007 Error wpa_supplicant 2988 wpa_driver_nl80211_driver_cmd: failed to issue private commands
18:47:18.007 Error WifiStateMachine 298 Failed to set country code in
18:47:18.007 Error wpa_supplicant 2988 wpa_driver_nl80211_driver_cmd: failed to issue private commands
18:47:18.007 Info wpa_supplicant 2988 wlan0: CTRL-EVENT-DRIVER-STATE HANGED
18:47:18.007 Error WifiStateMachine 298 Failed to set frequency band 0
18:47:18.007 Debug CommandListener 137 Clearing all IP addresses on wlan0
18:47:18.007 Info wpa_supplicant 2988 wlan0: CTRL-EVENT-TERMINATING
18:47:18.224 Debug SoftapController 137 Softap fwReload - Ok
18:47:18.224 Debug CommandListener 137 Setting iface cfg
18:47:18.224 Debug CommandListener 137 Trying to bring down wlan0
When I press on "ON", it turns on and then off... this keeps on happening.. so we did something productive today
Wifi fixed!!!!!!!!!!yeyeyeyeyey!!
YEAAAHHHH!
prototype-U said:
Wifi fixed!!!!!!!!!!yeyeyeyeyey!!
Click to expand...
Click to collapse
I love you lol Lets apply it on PA! What do you say?
The Android Manual said:
I love you lol Lets apply it on PA! What do you say?
Click to expand...
Click to collapse
tomorrow :highfive:
prototype-U said:
tomorrow :highfive:
Click to expand...
Click to collapse
Copy That :highfive:
so is wifi fully working now???
mhb92 said:
so is wifi fully working now???
Click to expand...
Click to collapse
Yes
Not sure what I am doing wrong here. Even after I get it booted, with gapps. No baseband. I flashed the dev pre 5 baseband through recovery and it succeeds. When I try to use fastboot to send the same files, it says pre flash validation failed. I'm confused as I have a working build sans baseband, which is kinda important.
shamu_Baseband_D4.01-9625-05.34+FSG-9625-02.111
shamu_Bootloader_moto-apq8084-71.21
Not sure what more information you need about my environment, but I'm happy for any discussion to help me get this resolved so I can share my work.
(MODS: if this is the wrong place, please place it in the right section)
It appears I was missing libxml2
running a new build now. Will remove this post, if that fixes it.
added libxml2-dev and it still recompiled without a baseband. I am not sure what i am doing wrong here. :/
Stramondroid said:
added libxml2-dev and it still recompiled without a baseband. I am not sure what i am doing wrong here. :/
Click to expand...
Click to collapse
I've been trying to figure this out for a week still a no go.
Stramondroid said:
added libxml2-dev and it still recompiled without a baseband. I am not sure what i am doing wrong here. :/
Click to expand...
Click to collapse
The good news is you aren't doing anything wrong!
Wondered why there is no 7.0 OTA or Factory Images for the Nexus 6 yet? Baseband issues!
Unfortunately, this makes AOSP almost useless on the Nexus 6.
did you extract the binary blobs into the source?
https://developers.google.com/android/nexus/blobs-preview
Right now there are two N AOSP ROMS in the N6 forum, one in general and one in development.
I tried both, one has the issue you described with my N6, no signal and no asking for SIM-card PIN. The other had working baseband and it was also shown correctly in About Phone. I think the one not working was the one from the guy konrad, not sure though.
Have you tried both? Maybe get in touch with those guys and find out what they did differently in their builds.
Stramondroid said:
added libxml2-dev and it still recompiled without a baseband. I am not sure what i am doing wrong here. :/
Click to expand...
Click to collapse
was you able to figure this out yet ? Thanks
hedgehogmd said:
was you able to figure this out yet ? Thanks
Click to expand...
Click to collapse
I stopped trying, everyone I talked too said to attempt a compile of the M branch, which was successful, so I know my dev box is good. It has to do with the source. I have no clue.
A solution
I'm the author of the 7.0 ROM in General. On a closer look, it seems that my initial build is actually not a clean 7.0.0_r1 build. I checked out the master branch for a handful of repositories when playing around, and that mistake coincidentally made RIL work.
tl;dr The ICU library is the culprit. Do "cd external/icu && git fetch aosp master && git checkout aosp/master" and rebuild.
Full explanation:
I did a couple of proper builds first, since I got branches messed up in my build:
Proper 7.0.0_r1 build: No baseband
Proper AOSP master build: Working
That gave me a little hope Apparently 7.0.0_r1 has issues preventing RIL from working. Relevant logs:
Code:
01-02 04:51:11.207 D/RILD ( 319): **RIL Daemon Started**
01-02 04:51:11.207 D/RILD ( 319): **RILd param count=1**
01-02 04:51:11.352 E/RILD ( 319): dlopen failed: dlopen failed: cannot locate symbol "UCNV_FROM_U_CALLBACK_STOP_57" referenced by "/system/lib/libxml2.so"...
01-02 04:51:15.371 D/RILD ( 833): **RIL Daemon Started**
01-02 04:51:15.371 D/RILD ( 833): **RILd param count=1**
01-02 04:51:15.420 E/RILD ( 833): dlopen failed: dlopen failed: cannot locate symbol "UCNV_FROM_U_CALLBACK_STOP_57" referenced by "/system/lib/libxml2.so"...
(and so on)
At the first glance it may be related to libxml2, but UCNV_FROM_U_CALLBACK_STOP is actually related to Unicode conversion. It appears in platform/external/icu.
Building 7.0.0_r1 with external/icu at AOSP master solves the issue. Does that work for you? Hope it helps!
---------- Post added at 04:06 PM ---------- Previous post was at 04:05 PM ----------
Zhaofeng Li said:
I did a couple of proper builds first, since I got branches messed up in my build
Click to expand...
Click to collapse
... And yes, I'll update my ROM to a clean build.