Database Users

Wi-Fi "Unable to start Wi-Fi"

Hi everyone,
I'm having a problem with my G1.
Each time i try to turn the Wi-Fi on, i follow this steps (spoil !!) :
- Settings -> Wireless controls -> and the i click on Wi-Fi,
wich changes the lower text to "Turning on..."
Ok, but this step take something like 1 minute and after all this time, i can read : "Unable to stop Wi-Fi" (or sometimes "Unable to start Wi-Fi"),
I got this problem 5 days ago, and this is really a pain in the arse, because the only way i can download applications is using Wi-Fi (I'm french) and i can't !
I have tried everything :
- Turn Off/On G1
- Remove/Replace battery
- Reset to factory data
- Back to RC29 (thx to you )
- Root my G1 with JF1.41 mod (Thx so much !!)
But the problem is still there,
And i can't get it back to T-Mobile, because i bought it on eBay and i live in France...
So... can anybody help ?
Thx

Hi,
Same problem here. Edit: It does this 4 times on 5. And even if if finally starts, it hangs some time after.
Additionally I've googled (almost) all night long to find some clues but nothing concrete
First, an issue is open here: http://code.google.com/p/android/issues/detail?id=1124
I get this line in logcat:
Code:
D/wlan_loader( 574): ConfigMge start rc = -1
that shows a problem. Normally it should be "rc = 0".
I've digged into the code but it is very complicated (state machine, etc...) so I could not figure where the problem resides.
I also have this in dmesg:
Code:
<4>[ 1425.145012] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 1425.145867] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
I don't know if this means a hardware problem.
I also suspect a bug in the proprietary file "/system/etc/wifi/Fw1251r1c.bin" but I've not found any other version on the net, even in "not so clean ways".
The size of the file on my G1 is 194188 bytes.
I have installed RC33 ADP1 by Jesus Freke but it did not solved the problem.
Can anyone look at the size of this file on his G1 and tell me if it is different? And if it is the case possibly send it to me?
The only solution I've seen on the net is to send back the phone to T-Mobile for a replacement but unfortunately I live in France and I got it from US by unusual ways so it is not a possibility for me .
Any clue / advice will be gladly accepted
Thanks in advance.
Mid'.

I have the same problem...
I was wondering if either of you figured out what to do to get around this. I'm in the US and am having the same problem. I was also working for about a week before this behavior started ("Unable to start Wi-Fi", "Unable to stop Wi-Fi").
I have seen other posts where this is intermittent. It isn't with me. Once it quit working, I haven't been able to get anything but the error messages.
If someone has found a way around this, I would appreciate any help you can provide.
Regards
Steve

You three should post what third party apps you have installed.

I am having this same issue after flashing the new google ION R2

I'm also having this issue after flashing Ion.

Same Issue
I started having this issue before the Ion rom. It wasn't intermittent, just stopped working.

Same problem here
Code:
<4>[ 1425.145012] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 1425.145867] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
CRB43, factory reset, nothing works.
Does anybody have an idea on how to solve this? It seems to be a known problem bij T-Mobile.

I'm running JF1.51 and WiFi is horribly flaky. It will work great for a few seconds then go deaf.
If I toggle it off and on it will work for a little bit again.
EDIT: I'm also getting the "low voltage" error message.

I've looked at this a little bit, and it looks like a ring buffer problem.
As I said before, my WiFi will work great for a while then go deaf.
Disabling/enabling through the Settings GUI will restore operation for a couple of minutes, tops.
Here's what I think might be relevant dmesgs:
Code:
<6>[88157.446136] request_suspend_state: sleep (0->3) at 88153591964926 (2009-06-27 20:57:10.146884034 UTC)
<4>[88157.467956] deinit sharp panel
<4>[88157.996398] select 4913 (app_process), adj 15, size 3053, to kill
<4>[88157.996734] send sigkill to 4913 (app_process), adj 15, size 3053
<4>[88158.236358] save exit: isCheckpointed 1
<6>[88282.505401] request_suspend_state: wakeup (3->0) at 88278651260580 (2009-06-27 20:59:15.206149170 UTC)
<6>[88282.615966] rev_crc_err_count 1, INT 23a001
<6>[88282.616332] rev: unknown reverse packet: len=0009 type=0049 CURR_REV_PTR=1617500b
<6>[88282.616851]
<6>[88282.617126] 09<6> 00<6> 49<6> 00<6> 00<6> 80<6> 00<6> 60<6> 00<6> 80<6> 0a<6>
<6>[88282.620574] mddi: resetting rev ptr
<6>[88282.621154] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val e curr_rev_ptr 1617500b
<4>[88282.666717] init sharp panel
<4>[88287.779876] select 4943 (app_process), adj 15, size 2991, to kill
<4>[88287.780731] send sigkill to 4943 (app_process), adj 15, size 2991
<4>[88295.748840] select 4951 (app_process), adj 15, size 2992, to kill
<4>[88295.749694] send sigkill to 4951 (app_process), adj 15, size 2992
<6>[88298.065185] TIWLAN: Driver unloading
<4>[88298.066314] sdio_reset_comm():
<7>[88298.154388] TIWLAN: Releasing SDIO resources
<7>[88298.158172] TIWLAN: SDIO resources released
<4>[88298.160217] wifi_remove
<4>[88298.160552] trout_wifi_set_carddetect: 0
<7>[88298.160827] mmc0: card_present 0
<6>[88298.161346] mmc0: Slot status change detected (1 -> 0)
<4>[88298.161712] trout_wifi_reset: 1
<6>[88298.172302] mmc0: card 0002 removed
<4>[88298.233215] trout_wifi_power: 0
<6>[88298.996520] TIWLAN: Driver unloaded

Here's a little more that I'm getting when the WiFi stops. Is this driver OSS or a proprietary blob?
Code:
<3>[ 1097.459899] init: untracked pid 364 exited
<4>[ 1101.746643] wds: 0020 @ 01
<6>[ 1101.747192] qmi: wds: got handle 0x17aaafb0
<4>[ 1101.747711] wds: 0022 @ ff
<6>[ 1101.748168] qmi: wds: CONNECTED
<4>[ 1101.750244] wds: 002d @ 01
<4>[ 1101.750701] qmi: got network profile
<6>[ 1101.752502] rmnet_open()
<6>[ 1685.105285] request_suspend_state: wakeup (3->0) at 1679298966064 (2009-06-27 21:55:33.740494873 UTC)
<6>[ 1685.217498] rev_crc_err_count 1, INT 23a001
<6>[ 1685.218078] rev: unknown reverse packet: len=0009 type=0049 CURR_REV_PTR=1617500b
<6>[ 1685.218383]
<6>[ 1685.218658] 09<6> 00<6> 49<6> 00<6> 00<6> 80<6> 00<6> 60<6> 00<6> 80<6> 0a<6>
<6>[ 1685.222137] mddi: resetting rev ptr
<6>[ 1685.222595] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val e curr_rev_ptr 1617500b
<4>[ 1685.288696] init sharp panel
<4>[ 1692.515502] wds: 0021 @ 01
<6>[ 1692.515838] qmi: wds: network stopped
<6>[ 1692.546508] rmnet_stop()
<4>[ 1693.342254] wds: 0022 @ ff
<6>[ 1693.342864] qmi: wds: DISCONNECTED
<6>[ 1704.187591] TIWLAN: Driver unloading
<4>[ 1704.188781] sdio_reset_comm():
<7>[ 1704.266632] TIWLAN: Releasing SDIO resources
<7>[ 1704.267944] TIWLAN: SDIO resources released
<4>[ 1704.270568] wifi_remove
<4>[ 1704.271057] trout_wifi_set_carddetect: 0
<7>[ 1704.272521] mmc0: card_present 0
<6>[ 1704.272979] mmc0: Slot status change detected (1 -> 0)
<6>[ 1704.276489] mmc0: card 0002 removed
<4>[ 1704.280487] trout_wifi_reset: 1
<4>[ 1704.332305] trout_wifi_power: 0
<6>[ 1704.543151] TIWLAN: Driver unloaded
<4>[ 1705.308166] wds: 0020 @ 01
<6>[ 1705.308715] qmi: wds: got handle 0x17aaafb0
<4>[ 1705.309234] wds: 0022 @ ff
<6>[ 1705.309661] qmi: wds: CONNECTED
<4>[ 1705.311370] wds: 002d @ 01
<4>[ 1705.311798] qmi: got network profile
<6>[ 1705.313690] rmnet_open()
<6>[ 1709.503326] TIWLAN: Driver loading
<4>[ 1709.504211] wifi_probe
<4>[ 1709.504486] trout_wifi_power: 1
<4>[ 1709.714965] trout_wifi_reset: 0
<4>[ 1709.766632] trout_wifi_set_carddetect: 1
<7>[ 1709.767303] mmc0: card_present 1
<6>[ 1709.767608] mmc0: Slot status change detected (0 -> 1)
<3>[ 1712.275085] mmc0: Command timeout
<4>[ 1712.282226] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 1712.283081] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
<6>[ 1712.290405] mmc0: new SDIO card at address 0001
<6>[ 1712.296447] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 1712.302520] TIWLAN: Driver initialized (rc 0)
<4>[ 1712.303436] TIWLAN: 1251 PG 1.2
<6>[ 1712.303863] TIWLAN: Driver loaded
<4>[ 1721.950164] wds: 0021 @ 01
<6>[ 1721.950500] qmi: wds: network stopped
<6>[ 1721.976440] rmnet_stop()
<4>[ 1726.546569] select 151 (app_process), adj 15, size 3009, to kill
<4>[ 1726.547149] select 158 (app_process), adj 15, size 3081, to kill
<4>[ 1726.547454] select 311 (app_process), adj 15, size 3246, to kill
<4>[ 1726.547973] send sigkill to 311 (app_process), adj 15, size 3246
<4>[ 1730.936798] wds: 0022 @ ff
<6>[ 1730.937652] qmi: wds: DISCONNECTED

I had the problem, i redid everything. just flashing the phone didn't help. downloaded the jf1.51 and did it again. logs would say wifi drivers not found. and guess what i checked and there were not there... I don't know 'who' or 'what' deleted them...
The only thing II suspect is the Backup program available on market for root users...or the "Privacy for rooted phones" prog

Same problem
Experiencing the same problem with my UK T-Mobile G1 (JF v1.51). Tried wiping, reseting, turning device off and on and removing battery, nothing has worked.
Is there any solution yet? I don't have any new apps installed and it is a fresh update, the problem was there prior to updating to jf v1.51
Any help will be appreciated

Did anyone manage to fix this? could it be related to the SDCard you are using?
Does everyone with non-working wifi on a G1 have this?

3 days ago, after I apply a chinese character sorting patch, i met this problem. So I wiped my phone, repartitioned my sdcard, reflashed the CM404 rom. And finnally got my wifi back.
But today I had this problem back again. I'm thinking is it because the sdcard I'm using is taking up to much battery power, so that the wifi module could not acquire enough power? This recalls me that I changed my sdcard exactly 3 days ago, right before I met this problem for the first time.

I am from India and G1 is very expensive over here. So, a friend bought me G1 from US and it reached in my hand yesterday . It is a T-Mobile G1. Was having same issue with Wifi and was showing "WiFi unable to start" . I tried rooting it and flashing with various ROM - issue remained. Lastly I downloaded a application from Market and installed. Named : WiFi Fixer by Zanshin-g1 .that software is written for completely different reason.
Code:
Does your wifi "hang" while still connected? Wifi Fixer keeps wifi working automatically, with optional wifi lock.
0.3.1 Cupcake, Disable function, warning if Wifi Notification is on
0.2.9 Added support for Landscape
*Wifi Fixer Classic also available*
But somehow it fixed my issue
Thanks Zanshin-g1.

bidhata said:
I am from India and G1 is very expensive over here. So, a friend bought me G1 from US and it reached in my hand yesterday . It is a T-Mobile G1. Was having same issue with Wifi and was showing "WiFi unable to start" . I tried rooting it and flashing with various ROM - issue remained. Lastly I downloaded a application from Market and installed. Named : WiFi Fixer by Zanshin-g1 .that software is written for completely different reason.
Code:
Does your wifi "hang" while still connected? Wifi Fixer keeps wifi working automatically, with optional wifi lock.
0.3.1 Cupcake, Disable function, warning if Wifi Notification is on
0.2.9 Added support for Landscape
*Wifi Fixer Classic also available*
But somehow it fixed my issue
Thanks Zanshin-g1.
Click to expand...
Click to collapse
Thanks Bidhata ,
but it tried that application and initially at first run it worked . but then once i got dc , the problem came back. since then i am not able to have the wifi truned on .
so the issue remains ..

Did you check the permission of this file: /data/misc/wifi/wpa_supplicant.conf

osoft said:
Did you check the permission of this file: /data/misc/wifi/wpa_supplicant.conf
Click to expand...
Click to collapse
This gave me the idea of how to fix, and its relativley simple... please correct me if I have made a grave error, but it seems to work so meh:
enter your terminal emulator and type the following:
su
(allow the request when asked)
chmod 777 /data/misc/wifi/wpa_supplicant.conf
exit the terminal
try powering up your wifi, it seems to be pretty stable as of now. This began occuring after I left my home's wireless range without turning wifi off and having the Wireless Helper app installed from the market...needless to say I have uninstalled said app and done this mod.

Whats funny about my situation is that if i use the DREAIMG.nbh file to flash back to rc29 my wifi works fine if i then upgrade to jf 1.5 still works fine upgrade to the latest cyanogen stable still works fine. Then a couple of days later poof "Unable to start wifi" intermittently and then a few days later permanently. Even if i downgrade to jf again still no wifi until i re-flash rc29 again. Weird thing is before i downgrade to jf 1.5 i run a fastboot erase on all the pertinent partitions. The only one that doesn't get flashed or erased in the downgrade to 1.5 is the radio rom. This leads me to believe that either my hardware is on it's way out or something that gets set in the radio rom from cyanogen 4.0.4 gets carried over no matter what rom you flash until the radio is erased and re-flashed. Mind you the second one is a totally just a guess with no proof to back it up. I also tried to chmod 777 /data/misc/wifi/wpa_supplicant.conf like said in the last post but to no avail.

Flashed a kernel? Now your xoom is on fire...

I think the most common problem we are seeing is people not clearing the old files. Before you download a new kernel and extract it, delete the old files from your SDK directory on your computer. Everyone that has had a problem so far, either screwed up a step or flashed a combo of new files and old files (ie the wifi not working after). So again BEFORE you extract the new kernel, REMOVE all old kernel files from the SDK directory on your computer.
List of files:
boot.img
/system/lib/modules/bcm4329.ko
/system/lib/modules/tun.ko
/system/lib/modules/scsi_wait_scan.ko
/system/lib/modules/cifs.ko
/system/etc/vold.fstab
You may ask why i didn't post this in the development forum, cause i'm not developing anything.

upgrading from Tiaman 1.1.6 to 1.3.1 just overwrites them ... you mean changing kernels completely right?

MitchRapp said:
upgrading from Tiaman 1.1.6 to 1.3.1 just overwrites them ... you mean changing kernels completely right?
Click to expand...
Click to collapse
No i mean the files on your computer, not the xoom. People are extracting the files into the SDK directory. Then leaving them there to mix with the new files. The xoom will overwrite what it needs to.

bwcorvus said:
I think the most common problem we are seeing is people not clearing the old files. Before you download a new kernel and extract it, delete the old files from your SDK directory on your computer. Everyone that has had a problem so far, either screwed up a step or flashed a combo of new files and old files (ie the wifi not working after). So again BEFORE you extract the new kernel, REMOVE all old kernel files from the SDK directory on your computer.
List of files:
boot.img
/system/lib/modules/bcm4329.ko
/system/lib/modules/tun.ko
/system/lib/modules/scsi_wait_scan.ko
/system/lib/modules/cifs.ko
/system/etc/vold.fstab
You may ask why i didn't post this in the development forum, cause i'm not developing anything.
Click to expand...
Click to collapse
This is why I always copy my files into a temp directory as shown in this post

Or just use a different folder for each version, and cd to the directory before you flash.
Also, you can do adb push system /system, and it'll put them in the right folders if you have it mirrored in your PC's folders.

Mine doesn't power up after following the procedure, it stays in the Motorola Dual Core logo..
I guess no XOOM for me until tomorrow
dmesg output:
Code:
<4>[ 18.182391] Primary GPT is invalid, using alternate GPT.
<6>[ 18.182577] mmcblk1: p1 (ebb) p2 (pdsb) p3 (misc) p4 (logo.bin) p5 (kpanic) p6 (recovery) p7 (boot) p8 (system) p9 (cache) p10 (userdata)
<6>[ 18.567134] android_usb gadget: high speed config #1: android
<6>[ 18.572291] EXT4-fs (mmcblk1p8): INFO: recovery required on readonly filesystem
<6>[ 18.572602] EXT4-fs (mmcblk1p8): write access will be enabled during recovery
<6>[ 18.603790] EXT4-fs (mmcblk1p8): recovery complete
<6>[ 18.606421] EXT4-fs (mmcblk1p8): mounted filesystem with ordered data mode. Opts: (null)
<6>[ 18.682391] EXT4-fs (mmcblk1p10): recovery complete
<6>[ 18.683460] EXT4-fs (mmcblk1p10): mounted filesystem with ordered data mode. Opts: (null)
<6>[ 18.701587] EXT4-fs (mmcblk1p9): recovery complete
<6>[ 18.702643] EXT4-fs (mmcblk1p9): mounted filesystem with ordered data mode. Opts: (null)
<4>[ 18.740397] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
<3>[ 18.745288] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
<6>[ 18.844887] enabling adb
<6>[ 18.861463] adb_open
<6>[ 18.924122] warning: `rild' uses 32-bit capabilities (legacy support in use)
<6>[ 18.928677] gps_brcm4750_ioctl: Setting gps gpio reset pin: 0
<6>[ 18.928769] stingray_gps_reset_gpio: setting GPS Reset GPIO to 0
<6>[ 18.928937] gps_brcm4750_ioctl: Setting gps gpio standby pin to: 0
<6>[ 18.929026] stingray_gps_standby_gpio: setting GPS standby GPIO to 0
<6>[ 18.930479] gps_brcm4750_ioctl: Setting gps gpio reset pin: 1
<6>[ 18.930572] stingray_gps_reset_gpio: setting GPS Reset GPIO to 1
<6>[ 19.003124] adb_release
<6>[ 19.003397] adb_open
<6>[ 19.028708] gps_brcm4750_ioctl: Setting gps gpio standby pin to: 1
<6>[ 19.029017] stingray_gps_standby_gpio: setting GPS standby GPIO to 1
<6>[ 19.261164] android_usb gadget: high speed config #1: android
<6>[ 19.577060] tear_down_dma
<6>[ 19.577183] setup_dma
<6>[ 37.780346] gps_brcm4750_ioctl: Setting gps gpio standby pin to: 0
<6>[ 37.780512] stingray_gps_standby_gpio: setting GPS standby GPIO to 0

[Android] TouchPad Android kernel mini howto

It seems there is little information on the internet regarding how to compile the kernel and how to convert to the correct image format so the boot loader will recognise and how to transfer it over to the touchpad. I ended up spent a few hours and finally figured out. I hope this will be useful for someone. I will try to make it concise as this is mainly aimed for developers.
What you will need
A linux development machine with uboot mkimage tool installed.
Sourcery G++ Lite 2010q1-188 for ARM EABI cross compile tool chain
https://sourcery.mentor.com/sgpp/lite/arm/portal/release1294
Touchpad kernel source
https://github.com/CyanogenMod/hp-kernel-tenderloin
CM7 Alpha 3 image (zip file)
http://goo-inside.me/roms/cmtouchpad/alpha3/update-cm-7.1.0-tenderloin-a3-fullofbugs-signed.zip
Prepare
Download CM7 Alpha 3 image and extract the boot.img to a temporary place.
Download Sourcery G++ Lite and install it. Add the G++ Lite tool chain binaray path to the PATH env variable. Get the kernel source from git hub and extract to local disk and change directory to the kernel source.
Compile the kernel
Still in the kernel source directory run
Code:
make ARCH=arm CROSS_COMPILE=arm-none-eabi- tenderloin_android_defconfig
make ARCH=arm CROSS_COMPILE=arm-none-eabi- uImage
Prepare the initramfs U-boot image
Extract the initramfs from the boot.img saved in temporary folder and convert it to uboot-image format
Code:
dd if=boot.img bs=1 skip=3577748 of=img.gz
mkimage -A arm -O linux -T ramdisk -C none -a 0x60000000 -e 0x60000000 -n "Image" -d ./img.gz arch/arm/boot/uRamdisk
(The dd offset for alpha 2.1 image is 3561152)
Combine the kernel and initramfs into a single U-boot image
Create a combined U-boot image (kernel and initramfs)
Code:
mkimage -A arm -O linux -T multi -a 0x40208000 -e 0x40208000 -C none -n "multi image" -d arch/arm/boot/uImage:arch/arm/boot/uRamdisk uImage.CyanogenMod.new
Transfer it to the device
Boot your touchpad into recovery mode and run
Code:
adb shell mount /dev/block/mmcblk0p13 /boot
adb push uImage.CyanogenMod.new /boot/uImage.CyanogenMod.new
adb shell umount /boot
adb shell reboot
After it reboot you should be able to see a new CyanogenMod.new item from the boot menu.
That's it!
Optimisation
For those who wants to experiment with GCC build options you can update the entry "arch-$(CONFIG_CPU_32v7" in file arch/arm/Makefile and I set mine to
Code:
arch-$(CONFIG_CPU_32v7) :=-D__LINUX_ARM_ARCH__=7 -mtune=cortex-a8 -mfpu=neon -ftree-vectorize -mfloat-abi=softfp -O2 $(call cc-option,-march=armv7-a,-march=armv5t -Wa$(comma)-march=armv7-a)
Warning
Please be aware you are working on the bleeding edge kernel for touchpad and there is no guarantee that the latest git version will work for you. Please try an earlier version if that's the case.
As of 2011-11-23 you will need the latest kernel source to build kernel for alpha 3. Please do not mix the kernel with an initramfs from a different version, i.e. don't use initramfs extracted from alpha 2.1 and use it with alpha3.

Thanks for this. Last weekend spent a while trying to figure this out.
Sent from my HP Touchpad using Tapatalk

x2. Huge thanks

Thank you soooooo much for this guide. Quick question if you don't mind though.. I am using an mkimage that goes back to my nook kernel days. Is there anything newer out, or would this still be ok,?

Divine_Madcat said:
Thank you soooooo much for this guide. Quick question if you don't mind though.. I am using an mkimage that goes back to my nook kernel days. Is there anything newer out, or would this still be ok,?
Click to expand...
Click to collapse
As long as the mkimage can generate a standard U-boot image it should be fine.
You can always try it yourself. In worst case you have to hard reboot the touchpad by pressing the power button and home button at the same time for more than 10 minutes. As long as you keep the original image files (UImage.*) untouched I don't think you can brick it even if you want to.

S7
I have been trying to compile the kernel for some time now, and was hopeful reading your guide (and this last post) However, still following the steps to merge the ramdisk, i cannot make a booting kernel. I can get it flashed, as i am using the update.zip method, but moboot always gives me a crc error when booting it.
Though, before i totally go nuts, i think i need to try the source forgery toolchain, as i am using the Android ndk r6b...

Divine_Madcat said:
S7
I have been trying to compile the kernel for some time now, and was hopeful reading your guide (and this last post) However, still following the steps to merge the ramdisk, i cannot make a booting kernel. I can get it flashed, as i am using the update.zip method, but moboot always gives me a crc error when booting it.
Though, before i totally go nuts, i think i need to try the source forgery toolchain, as i am using the Android ndk r6b...
Click to expand...
Click to collapse
Could you check the md5sum of the u-boot image crated on disk and the one installed by update.zip file? Do they match? If they do then you probably will need to upgrade your mkimage tool.

s7mx1 said:
Could you check the md5sum of the u-boot image crated on disk and the one installed by update.zip file? Do they match? If they do then you probably will need to upgrade your mkimage tool.
Click to expand...
Click to collapse
I will give it a check; just in case, know where to get a newer mkimage?

Thanks so much for this guide
s7mx1 said:
You can always try it yourself. In worst case you have to hard reboot the touchpad by pressing the power button and home button at the same time for more than 10 minutes.
Click to expand...
Click to collapse
It feels like 10 mins.. doesn't it

WEll, i checked the MD5 sums, and it looks good. So, i guess it is time to try again with the toolchain listed here, and perhaps a new mkimage (if there is a "modern" one i should using, please point me to it...)
edit: Never mind.. in all my looking, i never saw that ubuntu had a nice one waiting for me.... doh
edit2: Woo! After getting the probably correct mkimage, and the CS toolchain, looks like i finally got it to pass the crc check. Now, lets see if it finishes booting. Thanks again for the guide!
Nope.. no boot. I get a dmesg with this:
<3>[ 69.978716] init: untracked pid 224 exited
<6>[ 70.086076] android_usb gadget: high speed config #1: android
<6>[ 70.086209] gadget_event: schedule host_connected
<6>[ 70.096953] max8903b_current_setup: CURRENT_500MA
<6>[ 70.097040] gadget_event: source=bus mA=500 (no change)
<4>[ 70.910953] UDC-CHG (2-2-2): usb_multi_chg_detect (591) : USB host Adaptor
(500mA)!
<6>[ 70.912805] gadget_event: schedule host_disconnected
<6>[ 70.925482] max8903b_current_setup: CURRENT_ZERO
<6>[ 71.164066] android_usb gadget: high speed config #1: android
<6>[ 71.164220] gadget_event: schedule host_connected
<6>[ 71.173640] max8903b_current_setup: CURRENT_500MA
<6>[ 71.178212] gadget_event: source=bus mA=500 (no change)
<6>[ 72.160955] gadget_event: host_connected=1 (no change)
<6>[ 74.142224] request_suspend_state: wakeup (0->0) at 74121495501 (2011-11-1
1 22:49:33.378031648 UTC)
<3>[ 74.143675] init: untracked pid 266 exited
<3>[ 74.155217] init: untracked pid 273 exited
<6>[ 79.285016] request_suspend_state: wakeup (0->0) at 79264287462 (2011-11-1
1 22:49:38.520824942 UTC)
The last three lines repeat alot, with different pid's .
Alrighty.. figured this one out - You cannot use the latest repository commits with the 2.1 alpha build. However, i was able to build commit fd70bb7aae, and it builds and actually boots. Now, i can actually play around and tweak it. Thank you again for the guide, and sorry for the edit spamming.. heh.

myn said:
x2. Huge thanks
Click to expand...
Click to collapse
Myn, do you have a touchpad???!!!? God I hope so!

vinscuzzy said:
Myn, do you have a touchpad???!!!? God I hope so!
Click to expand...
Click to collapse
He does
Sent from my PG86100 using Tapatalk

Divine_Madcat said:
WEll, i checked the MD5 sums, and it looks good. So, i guess it is time to try again with the toolchain listed here, and perhaps a new mkimage (if there is a "modern" one i should using, please point me to it...)
edit: Never mind.. in all my looking, i never saw that ubuntu had a nice one waiting for me.... doh
edit2: Woo! After getting the probably correct mkimage, and the CS toolchain, looks like i finally got it to pass the crc check. Now, lets see if it finishes booting. Thanks again for the guide!
Nope.. no boot. I get a dmesg with this:
<3>[ 69.978716] init: untracked pid 224 exited
<6>[ 70.086076] android_usb gadget: high speed config #1: android
<6>[ 70.086209] gadget_event: schedule host_connected
<6>[ 70.096953] max8903b_current_setup: CURRENT_500MA
<6>[ 70.097040] gadget_event: source=bus mA=500 (no change)
<4>[ 70.910953] UDC-CHG (2-2-2): usb_multi_chg_detect (591) : USB host Adaptor
(500mA)!
<6>[ 70.912805] gadget_event: schedule host_disconnected
<6>[ 70.925482] max8903b_current_setup: CURRENT_ZERO
<6>[ 71.164066] android_usb gadget: high speed config #1: android
<6>[ 71.164220] gadget_event: schedule host_connected
<6>[ 71.173640] max8903b_current_setup: CURRENT_500MA
<6>[ 71.178212] gadget_event: source=bus mA=500 (no change)
<6>[ 72.160955] gadget_event: host_connected=1 (no change)
<6>[ 74.142224] request_suspend_state: wakeup (0->0) at 74121495501 (2011-11-1
1 22:49:33.378031648 UTC)
<3>[ 74.143675] init: untracked pid 266 exited
<3>[ 74.155217] init: untracked pid 273 exited
<6>[ 79.285016] request_suspend_state: wakeup (0->0) at 79264287462 (2011-11-1
1 22:49:38.520824942 UTC)
The last three lines repeat alot, with different pid's .
Alrighty.. figured this one out - You cannot use the latest repository commits with the 2.1 alpha build. However, i was able to build commit fd70bb7aae, and it builds and actually boots. Now, i can actually play around and tweak it. Thank you again for the guide, and sorry for the edit spamming.. heh.
Click to expand...
Click to collapse
That's because dalingrin has updated the default configuration to use the HIGHMEM which seems to kill all the apps. The latest git actually works if you disable all the HIGHMEM related stuff.

decalex said:
Thanks so much for this guide
It feels like 10 mins.. doesn't it
Click to expand...
Click to collapse
Absolutely
I just hope there is a rest button as the touchscreen occasionally will not respond at all after wake up and I have to reboot to webos and then reboot back to get the touchscreen back.

Great guide and I got the kernel all built, but how do you change the kernel arguments for booting? e.g. where does moboot get its whole root=/dev/ram0 ro fb...stuff, and how does the CyanogenMod kernel know where to look for the rootfs partition?

crimsonredmk said:
Great guide and I got the kernel all built, but how do you change the kernel arguments for booting? e.g. where does moboot get its whole root=/dev/ram0 ro fb...stuff, and how does the CyanogenMod kernel know where to look for the rootfs partition?
Click to expand...
Click to collapse
The root parameter (root=/dev/ram0) that passed to kernel is not useful to you. The root / is mere extracted initramfs in memory. I assume you are looking for system, data partitions etc. With TP we have LVM partitions which you can do really fancy stuff with. The actual mount device and mount point is defined (hard coded) in file init.tenderloin.rc which you can find in the initramfs (i.e. the img.gz which is a gzipped cpio file). You can extract all the contents out from img.gz and modify init.tenderloin.rc to suit your need and then create an updated initramfs file to go with the kernel.
Since Android (at least CM7 on TP) does not use pivot_root any changes made to the initramfs will appear automatically when you boot up the device.
You can google if you are not sure how to work with initramfs file.

Eris msm_pm_wait_state reboot syndrome?

Hi folks,
Long time since I popped in here.
I'm wondering if you've seen behavior similar to this before:
Spontaneous reboots during suspend/resumes (that is, an app running but the screen is off) which *sometimes* result in output like this at the tail end of /proc/last_kmsg
Code:
[ 2331.773132] msm_pm_wait_state(80, 0, 0, 0) failed 10d29
[ 2331.773132] msm_sleep(): msm_pm_wait_state failed, 10d29
[ 2331.929382] msm_pm_wait_state(80, 0, 0, 0) failed 10d29
[ 2331.929382] msm_sleep(): msm_pm_wait_state failed, 10d29
No errors detected
I can manage to run logcat as a background process (the syndrome seems to involve the kernel PM (Power Management) suspend/resume function, as it refuses to occur when plugged in to USB); sometimes I also see
Code:
09-01 21:07:58.371 273 416 E RPC : error writing RPC packet: 22 (Invalid argument)
as the last line in the logcat. I don't know what is lost in the logcat output after that due to buffering, but the "No errors detected" in /proc/last_kmsg seems to point away from a kernel panic. And yet the phone reboots in a decidedly ungraceful fashion... if all filesystems were flushed I would expect to see something in the logcat about a reboot.
Test conditions:
Kernel: 2.6.29-DecaFuctCFS-dirty-9ff84b92 ([email protected]) (gcc version 4.4.0 (GCC) ) #5 PREEMPT Thu Jan 27 22:14:44 EST 2011
ROM: Condemned Soul's CCM7-V21 Vanilla
CM CPU min/max: 245/729 (* I don't think this matters)
Governor: ondemand
Other: Screen must be off and phone disconnected from external (USB) power for this reboot to occur; my test condition also includes the phone in Airplane mode. (I do not know if the latter is necessary for bug expression).
I can add more detail, but I didn't want my post to get too long. I can cause this to happen deterministically (a delay of one to several minutes before the phone reboots). The app involved uses the GPS hardware...
Anyhow... does this syndrome sound familiar at all?
bftb0
PS Yes this is a real-world scenario - I want to do GPS track recording in areas without cell/wifi service, so... running without USB power and no radios (for battery conservation) is a priority.

S5 Screen black (but worked in download mode)

Hi,
so my S5(SM-900F) shows a black screen, but is otherwise functional. I don't know if it's a software or hardware issue, neither really makes sense to me.
Here's whats happened:
I wanted to flash cyanogenmod, phone seemed functional
Tried to flash twrp (3.0.1) with heimdall, got a bunch of errors
Tried a bunch of stuff, got it to flash twrp using heimdall-git
Phone got stuck in a boot loop
At this point I was annoyed and decided to reset it, which I did with kies
Here's where the screen issue started. After booting the screen was black. Phone showed S5 logo upon startup, download mode worked fine.
Touchscreen worked (managed to activate Talkback. In Hungarian), so the hardware seemed fine.
Googled and tried the million tips to fix a black screen, nothing worked
Screen randomly worked until reboot/lock
Fully charged the battery, screen worked until battery was at 70%, then black screen after locking with power button
Here's a kernel log from around that time:
dmesg
Nothing sticks out to me, log shows the backlight being adjusted which might be related.
This is the log I saved however, when I looked at it in the console I saw a few more things (see below)
Hoping it was a weird software issue I tried to flash cyanogenmod again, this time got into recovery (had to hold Vol Up+Home for more than half a minute), but got "kernel not seandroid enforcing" upon boot, then black screen and periodical vibration
Reset again
Wanted to see whether the screen would fail after some time in download mode, worked until battery was empty
Suddenly the screen's black in download mode, too, even though it worked for days
Here's a current bugreport.txt containing
Code:
***
<6>[ 157.910750] mipi_samsung_disp_send_cmd: get_my_check(0)!
<6>[ 157.910764] mipi_samsung_disp_send_cmd: get_my_check(0)!
<3>[ 157.910772] [mdnie lite] is negative Mode On = 0
<6>[ 157.910780] mdss_dsi_cmds_send: get_my_check(0)!
<3>[ 157.910791] [mdnie lite] mDNIe_Set_Mode end , UI_MODE(0), DYNAMIC(0), OUTDOOR_OFF_MODE(0), ACCESSIBILITY_OFF(0)
<6>[ 157.910801] mdss_dsi_panel_on : --
<6>[ 157.911850] mipi_samsung_disp_send_cmd: get_my_check(0)!
<6>[ 157.911858] mipi_samsung_disp_send_cmd: get_my_check(0)!
<6>[ 157.911867] mdss_dsi_cmds_send: get_my_check(0)!
<6>[ 157.911874] mdss_dsi_cmds_send: get_my_check(0)!
<6>[ 157.911880] mdss_dsi_cmd_receive: get_my_check(0)!
<6>[ 157.911887] read_reg : A[1] : .
<3>[ 157.911893] Error reading LCD NV data count(-19), read_size(1)!!!!
<6>[ 157.911900] mipi_samsung_disp_send_cmd: get_my_check(0)!
<3>[ 157.912839] Panel has gone bad, sending uevent - PANEL_ALIVE=0
<6>[ 157.912847] DISPLAY_ON
<6>[ 157.912862] mdss_mdp_overlay_on: mdss_mdp_overlay_on: --
<6>[ 157.912890] mdss_fb_blank_sub: FB_NUM:0, MDSS_FB_UNBLANK --
<6>[ 157.928517] __mdss_fb_perform_commit: kickoff done!
<6>[ 157.928534] mdss_fb_update_backlight: mfd->bl_level (255), bl_updated (0)
<6>[ 157.928546] mipi_samsung_disp_send_cmd: get_my_check(0)!
<6>[ 157.946943] mdss_fb_blank_sub: FB_NUM:1, MDSS_FB_UNBLANK ++
<6>[ 157.946959] mdss_mdp_overlay_on: mdss_mdp_overlay_on: ++
<6>[ 157.946977] mdss_mdp_overlay_on: mdss_mdp_overlay_on: --
<6>[ 157.947007] mdss_fb_blank_sub: FB_NUM:1, MDSS_FB_UNBLANK --
<6>[ 157.950265] hdmi_edid_sysfs_rda_modes: '4,19,32,33,34,3,18,1'
<6>[ 157.951605] hdmi_tx_get_vic_from_panel_info: 1920x1080 p30 16/9 is supported
<6>[ 157.951622] mdss_fb_blank_sub: FB_NUM:1, MDSS_FB_BLANK ++
<6>[ 157.951799] mdss_fb_blank_sub: FB_NUM:1, MDSS_FB_BLANK --
<6>[ 157.951809] mdss_fb_blank_sub: FB_NUM:1, MDSS_FB_UNBLANK ++
<6>[ 157.951819] mdss_mdp_overlay_on: mdss_mdp_overlay_on: ++
<6>[ 157.951831] mdss_mdp_overlay_on: mdss_mdp_overlay_on: --
<6>[ 157.951964] mdss_fb_blank_sub: FB_NUM:1, MDSS_FB_UNBLANK --
***
<4>[ 158.012453] WARNING: at /home/dpi/qb5_8814/workspace/KLTE_EUR_OPEN/android/kernel/drivers/video/msm/mdss/mdss_mdp_util.c:105 mdss_mdp_set_intr_callback+0x10c/0x12c()
<6>[ 158.012461] replacing current intr callback for ndx=8
Those I also saw before the previous dmesg.
The -19 read bytes seems especially dubious, from a quick look at the source it does not seem like an errno, don't know if it's related to the problem anyway.
Current Android version: 6.0.1
Kernel: 3.4.0
Build: MMB29M.G900FXXS1CPG9
So what's going on? Is this some weird hardware issue? Do the ways download mode and android control the screen differ? What difference does the battery make?
Is it software? Both?
I've searched the forum and found e.g this, but nothing that helped me out.
Thank you for your help,
NoR8quoh1r

heimdall?
Flash stock ROM from here with ODIN
http://updato.com/firmware-archive-select-model?r=BTU&v=&q=G900F

Heimdall is broken thw cm wiki is outdated use odin next time
Sent from my SM-G900F using Tapatalk

azooz95 said:
Heimdall is broken thw cm wiki is outdated use odin next time
Click to expand...
Click to collapse
It isn't broken, it's just iffy. Still would recommend Odin though, I use arch Linux and just find a Windows laptop and do whatever needs to be done there.
Sent from my Galaxy S5 using XDA Labs

*Detection* said:
heimdall?
Flash stock ROM from here with ODIN
Click to expand...
Click to collapse
Tried it, did not make a difference
Rakuu said:
It isn't broken, it's just iffy. Still would recommend Odin though, I use arch Linux and just find a Windows laptop and do whatever needs to be done there.
Sent from my Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
Yeah, had no problems with the newest version, tho. Fellow Archlinux user here .