Related
"Wi-Fi unable to start" error appeared couple weeks ago.
I have tried everything - reflashing different images, radio, formatting ... etc.
Nothing helped.
In a desperate moment I tried something.
Here are the steps:
I made some progress and it seams that is pure software problem.
Currently I'm with G1/black Cyanogen 3.6.8.1, Recovery 1.4 and 8GB SD/class 4.
What I did is reformatting the SD card in 2 partitions 1st FAT32 and 2nd ext2 ~ 460MB.
Wiped before flashing cyanogen build and also I made sure that there is nothing on the ext2 partition.
When flashing finished I waited the phone to fully set up itself on the first boot ~5-7 min.
Then I tried the WiFi - it didn't start
The important and desperate thing I did was to go to su console in /system/lib/modules and tried to load wlan.ko manually (insmod wlan.ko) - it failed the 1st time.
Then I tried 2 times more and it loaded itself successfully (of course wifi connection is not established in that moment, because loading the module is just one step of the process).
I unloaded successfully (rmmod wlan) the module and tried to start WiFi again - gues what - It worked!
That is just partial solution of the problem, but shows that it is just a software problem.
I guess some timeouts appear and WiFi starting procedure is not so patient to wait for the module to start up and it's not retrying to unload and load again the module.
Good luck
Hope it will work on yours G1.
Cheers
this has been up on a google code bug report page for a while now. I had the same result when trying to start the module in the terminal
cyanogen's new 3.9.1 scary experimental build shows that he used a new wifi driver in the changelog but that hasn't helped me with this issue at all. I thought it might be a software conflict so I used a clean sd card, flashed my update.zip, and still had the same problem
I have tried Cyanogen 3.9.1 with the same result - it doesn't work for me.
I can't explain why it started to work again in 3.6.8.1
Anyway, try to copy all your important files (not system/applications created like thumbnails folder) to your PC, put the SD card to card reader connected to a PC and then do a full reformat to FAT32.
Partition the newly formatted SD card to FAT32 and EXT2 partitions.
Reformat partitions again, copy update.zip to your SD card.
Start up your G1 holding home button and do wipe ( I wiped 2-3 times just to be sure )
Do ext2 system repair from the repair menu.
Do not convert it to ext3.
Apply the update.zip and continue to the next steps I wrote above.
Hope that's info is useful for you.
Post the output of "dmesg" after you try to install the module. It will tell us whats going wrong. This is not normal at all and might be hardware related.
cssvb94 said:
but shows that it is just a software problem.
Click to expand...
Click to collapse
I don't see how you come to the conclusion that it is a software problem. Intermittence is typically a sign of a HARDWARE problem.
lbcoder said:
I don't see how you come to the conclusion that it is a software problem. Intermittence is typically a sign of a HARDWARE problem.
Click to expand...
Click to collapse
Simple, it works somethimes on some builds and it doesn't at all on others - same hardware, different software.
Anyway, I realy hope it's not hardware related ...
cyanogen said:
Post the output of "dmesg" after you try to install the module. It will tell us whats going wrong. This is not normal at all and might be hardware related.
Click to expand...
Click to collapse
Is that request for me or airmaxx?
I really don't want to reflash now when it's working.
In the moment when something goes wrong I'll post dmesg.
I've noticed "D/wlan_loader( 228): ConfigMge start rc = -1" couple times in dmesg output when it wasn't working and "D/wlan_loader( 228): ConfigMge start rc = 0" when it works.
after a clean install of cyanogen 3.9.1, i tried to start with in the gui, through settings menu. after it reported "unable to start wifi" this is my dmesg output....
Code:
<6>[ 695.675048] TIWLAN: Driver loading
<4>[ 695.679168] wifi_probe
<4>[ 695.681762] trout_wifi_power: 1
<4>[ 695.888366] trout_wifi_reset: 0
<4>[ 695.943084] trout_wifi_set_carddetect: 1
<7>[ 695.947265] mmc0: card_present 1
<6>[ 695.950744] mmc0: Slot status change detected (0 -> 1)
<3>[ 698.464202] mmc0: Command timeout
<4>[ 698.474548] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 698.484191] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
<6>[ 698.497955] mmc0: new SDIO card at address 0001
<6>[ 698.508758] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 698.517639] tiwlan0 (): not using net_device_ops yet
<6>[ 698.530426] TIWLAN: Driver initialized (rc 0)
<3>[ 698.535705] mmc0: Data CRC error
<3>[ 698.539276] msmsdcc_data_err: opcode 0x00000035
<3>[ 698.544128] msmsdcc_data_err: blksz 4, blocks 1
<3>[ 698.549621] SDIO_SyncWrite: failed (-84)
<3>[ 698.554016] mmc0: Data CRC error
<3>[ 698.557586] msmsdcc_data_err: opcode 0x00000035
<3>[ 698.562713] msmsdcc_data_err: blksz 4, blocks 1
<3>[ 698.567718] SDIO_SyncWrite: failed (-84)
<3>[ 701.399383] mmc0: Data timeout
<3>[ 701.403289] SDIO_SyncRead: failed (-110)
<4>[ 701.407623] TIWLAN: invalid chip id = 0x 0 0 0 0!
<6>[ 701.412933] TIWLAN: Driver loaded
<4>[ 701.820495] select 226 (app_process), adj 15, size 3301, to kill
<4>[ 701.826873] send sigkill to 226 (app_process), adj 15, size 3301
<3>[ 704.165802] mmc0: Data timeout
<3>[ 704.169311] SDIO_SyncRead: failed (-110)
<3>[ 704.174041] TIWLAN: TIWLAN: Failed to start config manager
<6>[ 710.698730] RPC_TIME_TOD_SET_APPS_BASES:
<6>[ 710.698760] tick = 38620607
<6>[ 710.698760] stamp = 48907518449025024
<4>[ 735.120178] select 480 (app_process), adj 15, size 4338, to kill
<4>[ 735.126464] send sigkill to 480 (app_process), adj 15, size 4338
something i remembered earlier was that long ago, many roms and flashes prior (when I was still chasing after Hero and Rosie) i saw a wpa supplicant file had been installed on my fat32 partition, no system folder or anything just on the root of the card. i remember thinking at the time how odd this was and manually deleting the file prior to my next flash.
My problem may have started shortly thereafter but honestly don't remember, just grasping for straws here
cssvb94 said:
Simple, it works somethimes on some builds and it doesn't at all on others - same hardware, different software.
Anyway, I realy hope it's not hardware related ...
Click to expand...
Click to collapse
Really? That's not what you said before...
cssvb94 said:
I have tried everything - reflashing different images, radio, formatting ... etc.
Nothing helped.
Click to expand...
Click to collapse
Clearly, it is NOT related to the software since you TRIED CHANGING the software and it didn't help, and the SAME SOFTWARE works fine for everybody else, which means that it MUST be either USER ERROR, or HARDWARE DEFECT.
lbcoder said:
Really? That's not what you said before...
Clearly, it is NOT related to the software since you TRIED CHANGING the software and it didn't help, and the SAME SOFTWARE works fine for everybody else, which means that it MUST be either USER ERROR, or HARDWARE DEFECT.
Click to expand...
Click to collapse
Listen, I'm not here to argue and I don't have anything against you.
Why you are so catchy about that simple details?
I'm trying to help and share what I've been through.
If you are offended of something I said then - sorry.
Don't be such arrogant, capital letters don't work on me. =)
----------------------------------------------------------------------
This is cut from my dmesg :
WiFi starting OK
--- cut ---
<6>[ 268.613555] TIWLAN: Driver loading
<4>[ 268.617797] wifi_probe
<4>[ 268.620758] trout_wifi_power: 1
<4>[ 268.830261] trout_wifi_reset: 0
<4>[ 268.884521] trout_wifi_set_carddetect: 1
<7>[ 268.888824] mmc0: card_present 1
<6>[ 268.892303] mmc0: Slot status change detected (0 -> 1)
<3>[ 271.400268] mmc0: Command timeout
<4>[ 271.410339] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 271.419982] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
<6>[ 271.436584] mmc0: new SDIO card at address 0001
<6>[ 271.446960] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 271.455352] tiwlan0 (): not using net_device_ops yet
<6>[ 271.464538] TIWLAN: Driver initialized (rc 0)
<4>[ 271.469909] TIWLAN: 1251 PG 1.2
<6>[ 271.473693] TIWLAN: Driver loaded
<3>[ 271.863403] mmc0: Data CRC error
<3>[ 271.866851] msmsdcc_data_err: opcode 0x00000035
<3>[ 271.871551] msmsdcc_data_err: blksz 512, blocks 1
<4>[ 271.877441] SDIO Write failure (-84)
<3>[ 271.883209] TIWLAN: TIWLAN: Failed to start config manager
--- cut ---
<6>[ 689.787445] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 689.795745] tiwlan0 (): not using net_device_ops yet
<6>[ 689.804901] TIWLAN: Driver initialized (rc 0)
<4>[ 689.810150] TIWLAN: 1251 PG 1.2
<6>[ 689.813690] TIWLAN: Driver loaded
<3>[ 690.153045] mmc0: Data CRC error
<3>[ 690.156463] msmsdcc_data_err: opcode 0x00000035
<3>[ 690.161163] msmsdcc_data_err: blksz 4, blocks 1
<4>[ 690.168182] SDIO Write failure (-84)
<3>[ 690.173889] TIWLAN: TIWLAN: Failed to start config manager
--- cut ---
Now new case: "Unable to stop Wi-Fi"
rmmod wlan throws back: "rmmod: delete_module 'wlan' failed (errno 11)"
lsmod returns: "wlan 566844 1 - Live 0xbf480000"
lbcoder, was there anything in my dmesg that confirmed it is indeed hardware, or anything useful at all in there?
after reading the reports on googlecode pages, i was leaning to hardware issue only because the problem is so rare and those people sent their g1's back in. I was really hoping this wasn't the case though.
I'd be happy with intermittent at this point, my wifi has not turned on in like 2 months my phone was purchased used (wifi worked fine at the time though) on craigslist so I can't return it to TMO
The CRC errors on mmc0 means that your sdcard is dying. It might seem unrelated but because how the way the G1 hardware works, this could be the problem. Yank your card and try it again.
No more WiFi
"Unable to stop" or "Unable to start" after reboot.
Tried with different SD card - no CRC errors and still no WiFi
for me the wifi turned on but it cant connect with a router... just write obtain ip address.. and after.. no connection
this is my log
<6>[ 175.583831] ept #2 out max:512 head:ffc0c100 bit:2
<6>[ 175.584289] ept #0 in max:64 head:ffc0c040 bit:16
<6>[ 175.585083] ept #1 in max:512 head:ffc0c0c0 bit:17
<6>[ 175.585510] ept #2 in max:512 head:ffc0c140 bit:18
<6>[ 175.586059] usb: notify offline
<6>[ 175.594207] usb: suspend
<6>[ 175.813262] usb: reset
<6>[ 175.815673] usb: portchange USB_SPEED_HIGH
<6>[ 175.967803] usb: reset
<6>[ 175.970092] usb: portchange USB_SPEED_HIGH
<6>[ 176.164825] usb_mass_storage usb_mass_storage: config #1
<6>[ 187.209259] request_suspend_state: wakeup (3->0) at 180968491210 (2009-07-
29 16:16:01.570098877 UTC)
<6>[ 188.333618] TIWLAN: Driver loading
<4>[ 188.334503] wifi_probe
<4>[ 188.334777] trout_wifi_power: 1
<4>[ 188.536346] trout_wifi_reset: 0
<4>[ 188.586914] trout_wifi_set_carddetect: 1
<7>[ 188.587432] mmc0: card_present 1
<6>[ 188.587738] mmc0: Slot status change detected (0 -> 1)
<3>[ 191.095031] mmc0: Command timeout
<4>[ 191.102386] mmc0: card claims to support voltages below the defined range.
These will be ignored.
<4>[ 191.103210] mmc0: SDIO card claims to support the incompletely defined 'lo
w voltage range'. This will be ignored.
<6>[ 191.112518] mmc0: new SDIO card at address 0001
<6>[ 191.118377] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 191.123901] TIWLAN: Driver initialized (rc 0)
<4>[ 191.125244] TIWLAN: 1251 PG 1.2
<6>[ 191.125701] TIWLAN: Driver loaded
<6>[ 192.657897] snd_set_volume 256 0 5
<6>[ 192.747344] snd_set_volume 256 0 5
<3>[ 198.871185] init: sys_prop: permission denied uid:1000 name:ro.config.noc
heckin
<6>[ 244.551879] TIWLAN: Driver unloading
<4>[ 244.553070] sdio_reset_comm():
<7>[ 244.631011] TIWLAN: Releasing SDIO resources
<7>[ 244.632324] TIWLAN: SDIO resources released
<4>[ 244.634918] wifi_remove
<4>[ 244.635406] trout_wifi_set_carddetect: 0
<7>[ 244.636199] mmc0: card_present 0
<6>[ 244.636627] mmc0: Slot status change detected (1 -> 0)
<6>[ 244.639465] mmc0: card 0002 removed
<4>[ 244.643585] trout_wifi_reset: 1
<4>[ 244.699401] trout_wifi_power: 0
<6>[ 244.905883] TIWLAN: Driver unloaded
<6>[ 246.548492] TIWLAN: Driver loading
<4>[ 246.549377] wifi_probe
<4>[ 246.549652] trout_wifi_power: 1
<4>[ 246.754119] trout_wifi_reset: 0
<4>[ 246.805236] trout_wifi_set_carddetect: 1
<7>[ 246.805786] mmc0: card_present 1
<6>[ 246.806060] mmc0: Slot status change detected (0 -> 1)
<3>[ 249.310638] mmc0: Command timeout
<4>[ 249.318481] mmc0: card claims to support voltages below the defined range.
These will be ignored.
<4>[ 249.319335] mmc0: SDIO card claims to support the incompletely defined 'lo
w voltage range'. This will be ignored.
<6>[ 249.326782] mmc0: new SDIO card at address 0001
<6>[ 249.332794] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 249.338226] TIWLAN: Driver initialized (rc 0)
<4>[ 249.339141] TIWLAN: 1251 PG 1.2
<6>[ 249.339599] TIWLAN: Driver loaded
<6>[ 994.061614] request_suspend_state: sleep (0->3) at 987820816650 (2009-07-2
9 16:29:28.422424317 UTC)
<4>[ 994.083801] deinit sharp panel
<4>[ 994.762908] save exit: isCheckpointed 1
<4>[ 994.765380] save exit: isCheckpointed 1
If you want help, get your details straight! If you contradict yourself all over the place, then nobody can possibly know what is going on and you won't get anywhere.
cssvb94 said:
Listen, I'm not here to argue and I don't have anything against you.
Why you are so catchy about that simple details?
Click to expand...
Click to collapse
You mention having tried flashing different software...
Have you tried flashing IMAGES (fastboot) or just update scripts (i.e. update.zip)?
If you haven't tried already, I suggest flashing the stock *engineering* bootloader 0.95.3000, ADP1-CRC1 images from www.htc.com -- the one that's labeled as "system image" (not the one labeled "recovery image", which is just an update.zip), and radio v2_22_19_26I (also from htc.com), write everything to the phone using fastboot, pull the battery, wait 10 minutes, and see what happens. IF it is a software problem, then this will *definitely* fix it. If it is a HARDWARE problem, then this will *definitely NOT* fix it. If the wifi starts working right after you write these things, *do not* conclude that it was a software problem since it could simply have gone intermittent-on. Keep the software like that and run it for at least a week to make sure the problem doesn't come back before making your conclusions.
Went back to stock 1.0 RC29 with original SPL, radio and bootloader and started from scratch.
Also formated SD card - only one partition FAT32.
Now I'm with ADP1.5 JF and WiFi is working most of the time.
So angry lbcoder what's your great verdict now? SOFTWARE or HARDWARE?
lbcoder said:
You mention having tried flashing different software...
Have you tried flashing IMAGES (fastboot) or just update scripts (i.e. update.zip)?
If you haven't tried already, I suggest flashing the stock *engineering* bootloader 0.95.3000, ADP1-CRC1 images from www.htc.com -- the one that's labeled as "system image" (not the one labeled "recovery image", which is just an update.zip), and radio v2_22_19_26I (also from htc.com), write everything to the phone using fastboot, pull the battery, wait 10 minutes, and see what happens. IF it is a software problem, then this will *definitely* fix it. If it is a HARDWARE problem, then this will *definitely NOT* fix it. If the wifi starts working right after you write these things, *do not* conclude that it was a software problem since it could simply have gone intermittent-on. Keep the software like that and run it for at least a week to make sure the problem doesn't come back before making your conclusions.
Click to expand...
Click to collapse
which is the commands for push the radio and the the adp1-crc1 image via fastboot?
i can t find ADP1-CRC1 images can you give me a url please?
success!!!!!!
the problem was the radio... i flashed 2 times the radio and now work!!!!!
thanks guyssss i love you aahahah
rock187 said:
the problem was the radio... i flashed 2 times the radio and now work!!!!!
thanks guyssss i love you aahahah
Click to expand...
Click to collapse
Great =)
Would you please post full step-by-step what you did.
10x in advance
It didn't work for me. I'm going to return my G1 back to the store I bought it, it's still under warranty.
Anyway to get CD or DVD to play on honeycomb with root at the moment? Driver limitations I believe stop the use on the stock ROM.
I would like to get this working as well... I bought an external CD/DVD burner assuming it would work (was only $26)... When I connect it, I get the "Preparing..." message to pop up, but it insantly goes away and nothing ever gets mounted. So, I did a "dmesg" from the command line afterwards, and you surely see that it knows what kind of device it is and it even looks like it creates some new device files for it, but I have not been able to find a way to mount it. Basically, I just want to be able to read CD's and DVD's with my Transformer in case i need to...
Here is the dmesg output;
<6>[ 2875.321152] usb 1-1.2: new high speed USB device using tegra-ehci and address 3
<6>[ 2875.359359] usb 1-1.2: New USB device found, idVendor=0930, idProduct=0c08
<6>[ 2875.359400] usb 1-1.2: New USB device strings: Mfr=10, Product=11, SerialNumber=3
<6>[ 2875.359432] usb 1-1.2: Product: TOSHIBA SuperMulti Dr
<6>[ 2875.359458] usb 1-1.2: Manufacturer: TOSHIBA <6>[ 2875.359481] usb 1-1.2: SerialNumber: 000000000355
<4>[ 2875.359507] device: '1-1.2': device_add
<4>[ 2875.361676] device: '1-1.2:1.0': device_add
<6>[ 2875.364136] scsi0 : usb-storage 1-1.2:1.0
<4>[ 2875.364411] device: 'host0': device_add
<4>[ 2875.366176] device: 'host0': device_add
<4>[ 2875.367695] device: 'ep_81': device_add
<4>[ 2875.367859] device: 'ep_02': device_add
<4>[ 2875.368073] device: 'usbdev1.3': device_add
<4>[ 2875.370140] device: 'ep_00': device_add
<4>[ 2875.754655] Light sensor: al3000a_interrupt_handler
<4>[ 2875.755235] lux value is : 3
<5>[ 2876.373527] scsi 0:0:0:0: CD-ROM TOSHIBA SuperMultiPA3834 7.5A PQ: 0 ANSI: 0
<4>[ 2876.373551] device: 'target0:0:0': device_add
<4>[ 2876.373729] device: '0:0:0:0': device_add
<4>[ 2876.411891] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
<6>[ 2876.411927] cdrom: Uniform CD-ROM driver Revision: 3.20
<4>[ 2876.411972] device: '11:0': device_add
<4>[ 2876.412337] device: 'sr0': device_add
<7>[ 2876.412974] sr 0:0:0:0: Attached scsi CD-ROM sr0
<4>[ 2876.413015] device: '0:0:0:0': device_add
<4>[ 2876.413335] device: 'sg0': device_add
<5>[ 2876.413750] sr 0:0:0:0: Attached scsi generic sg0 type 5
<6>[ 2888.113412] EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
<4>[ 2896.109293] bq20z45_get_psp val->intval =Full ret =e0 charging=0
<4>[ 2896.112566] bq20z45_get_psp voltage_now =8368
<4>[ 2896.113221] bq20z45_get_capacity val->intval=100 ret=100
<4>[ 2896.113971] bq20z45_get_psp temp=305
<4>[ 2896.119207] bq20z45_get_capacity val->intval=100 ret=100
<4>[ 2896.120111] bq20z45_get_psp voltage_now =8368
<4>[ 2896.121006] bq20z45_get_psp temp=305
<4>[ 2896.121890] bq20z45_get_psp val->intval =Full ret =e0 charging=0
Does anyone know if there is any possibility of getting this to work??
Thanks!
Sent from my Transformer TF101 using Tapatalk
jtrosky said:
I would like to get this working as well... I bought an external CD/DVD burner assuming it would work (was only $26)... When I connect it, I get the "Preparing..." message to pop up, but it insantly goes away and nothing ever gets mounted. So, I did a "dmesg" from the command line afterwards, and you surely see that it knows what kind of device it is and it even looks like it creates some new device files for it, but I have not been able to find a way to mount it. Basically, I just want to be able to read CD's and DVD's with my Transformer in case i need to...
Here is the dmesg output;
<6>[ 2875.321152] usb 1-1.2: new high speed USB device using tegra-ehci and address 3
<6>[ 2875.359359] usb 1-1.2: New USB device found, idVendor=0930, idProduct=0c08
<6>[ 2875.359400] usb 1-1.2: New USB device strings: Mfr=10, Product=11, SerialNumber=3
<6>[ 2875.359432] usb 1-1.2: Product: TOSHIBA SuperMulti Dr
<6>[ 2875.359458] usb 1-1.2: Manufacturer: TOSHIBA <6>[ 2875.359481] usb 1-1.2: SerialNumber: 000000000355
<4>[ 2875.359507] device: '1-1.2': device_add
<4>[ 2875.361676] device: '1-1.2:1.0': device_add
<6>[ 2875.364136] scsi0 : usb-storage 1-1.2:1.0
<4>[ 2875.364411] device: 'host0': device_add
<4>[ 2875.366176] device: 'host0': device_add
<4>[ 2875.367695] device: 'ep_81': device_add
<4>[ 2875.367859] device: 'ep_02': device_add
<4>[ 2875.368073] device: 'usbdev1.3': device_add
<4>[ 2875.370140] device: 'ep_00': device_add
<4>[ 2875.754655] Light sensor: al3000a_interrupt_handler
<4>[ 2875.755235] lux value is : 3
<5>[ 2876.373527] scsi 0:0:0:0: CD-ROM TOSHIBA SuperMultiPA3834 7.5A PQ: 0 ANSI: 0
<4>[ 2876.373551] device: 'target0:0:0': device_add
<4>[ 2876.373729] device: '0:0:0:0': device_add
<4>[ 2876.411891] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
<6>[ 2876.411927] cdrom: Uniform CD-ROM driver Revision: 3.20
<4>[ 2876.411972] device: '11:0': device_add
<4>[ 2876.412337] device: 'sr0': device_add
<7>[ 2876.412974] sr 0:0:0:0: Attached scsi CD-ROM sr0
<4>[ 2876.413015] device: '0:0:0:0': device_add
<4>[ 2876.413335] device: 'sg0': device_add
<5>[ 2876.413750] sr 0:0:0:0: Attached scsi generic sg0 type 5
<6>[ 2888.113412] EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
<4>[ 2896.109293] bq20z45_get_psp val->intval =Full ret =e0 charging=0
<4>[ 2896.112566] bq20z45_get_psp voltage_now =8368
<4>[ 2896.113221] bq20z45_get_capacity val->intval=100 ret=100
<4>[ 2896.113971] bq20z45_get_psp temp=305
<4>[ 2896.119207] bq20z45_get_capacity val->intval=100 ret=100
<4>[ 2896.120111] bq20z45_get_psp voltage_now =8368
<4>[ 2896.121006] bq20z45_get_psp temp=305
<4>[ 2896.121890] bq20z45_get_psp val->intval =Full ret =e0 charging=0
Does anyone know if there is any possibility of getting this to work??
Thanks!
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
It's because honeycomb still doesn't have a decent driver support for optical drivers
in fact it tries to mount the device but in reality it doesn't work
Only a few drives work
But it does see it as a CDROM (one line even says "uniform cdrom driver - version..." - how can it see a device that it has no drivers for? If it is missing from the kernel, is that something that a hacker could add or would that need to be done by ASUS first?
Thanks!
jtrosky said:
But it does see it as a CDROM (one line even says "uniform cdrom driver - version..." - how can it see a device that it has no drivers for? If it is missing from the kernel, is that something that a hacker could add or would that need to be done by ASUS first?
Click to expand...
Click to collapse
I edited the post
actually there is kernel support but it supports only few devices
I think that the patch should be done by google or at least specifically from asus
Obviously an hackr could adapt another linux driver... but i'm not sure how it would work
iMko92 said:
It's because honeycomb still doesn't have a decent driver support for optical drivers
in fact it tries to mount the device but in reality it doesn't work
Only a few drives work
Click to expand...
Click to collapse
Anyone happen to know of a drive that works currently? I was hoping that since it detected my device (and detected it as a CD-ROM), that it would work! I would be willing to return it and buy one that is known to work, since you say that there are some deivices that do work...
What abut the actual devices it creates (/dev/sr0 ad /dev/sg0, I think) - nothing we can do with those?
Thanks!
Sent from my Transformer TF101 using xda premium
jtrosky said:
Anyone happen to know of a drive that works currently? I was hoping that since it detected my device (and detected it as a CD-ROM), that it would work! I would be willing to return it and buy one that is known to work, since you say that there are some deivices that do work...
What abut the actual devices it creates (/dev/sr0 ad /dev/sg0, I think) - nothing we can do with those?
Click to expand...
Click to collapse
mount point is a start (/dev/sr0 ad /dev/sg0), but i dont't think this will help devs to add the support
jtrosky said:
Anyone happen to know of a drive that works currently? I was hoping that since it detected my device (and detected it as a CD-ROM), that it would work! I would be willing to return it and buy one that is known to work, since you say that there are some deivices that do work...
What abut the actual devices it creates (/dev/sr0 ad /dev/sg0, I think) - nothing we can do with those?
Thanks!
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Have you tried to mount it manually?
# mkdir /mnt/cdrom
# mount /dev/sg0 /mnt/cdrom
of course you most likely will have to be root for this to work properly.
Yes, I've tried mounting with these commands ( I must specify the filesystm type with -t fstype, but I'm not sure what fstype should be):
# mount -oro -t cdrom /dev/block/sr0 /mnt/cdrom
# mount -oro -t cdrom /dev/sg0 /mnt/cdrom
Both report:
mount: no such device
I have no idea if "-t cdrom" is correct or not - just a guess.... Anyone have any other ideas?
Thanks for the help!!
Sent from my Transformer TF101 using xda premium
Ok, I'm getting closer! I can at least get the mount command to succeed if I specify -t tmpfs. Obviusly, I still couldn't read the CD, but at least I am communicating with the drive now. Now I just need to know what the correct "type" would be for a CD. I tried -t cdrom, -t cd-rom, -t iso9660 - none of those are known types though...
Anyone have any ideas of what the CD filesystem "Type" string woud be in android?? Or maybe there isn't one and that is the problem? So close....
Sent from my Transformer TF101 using xda premium
Ok, here is the problem - apparently, the kernel would need to support "iso9660" filesystem type in order to mount a CD/DVD. Unfortuantly, here is what my verision of Revolver supports (Revolver 2.5):
Looks like no CD-ROM support in the kernel... Oh well, was worth a shot! If you had an ext4 format DVD, I could read it, I guess....
/ #
/ # cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev debugfs
nodev sockfs
nodev usbfs
nodev pipefs
nodev anon_inodefs
nodev devpts
ext3
ext2
ext4
nodev ramfs
vfat
nodev cifs
nodev fuse
fuseblk
nodev fusectl
nodev mtd_inodefs
tntfs
Sent from my Transformer TF101 using xda premium
ISO support needs to be built into the kernel. When one of the developers builds the kernel, they can add it at that time.
Actually, I got fabio to chime in (Revolver ROM creator) - apparently, they need source code from ASUS before they can add this - but he said he would be glad to add it when the source is released....
Sent from my Transformer TF101 using xda premium
Anyone have any luck with this now that ICS is out?
bump
transformer prime, ziboo zipad: sata harddrive and sata optical enclosure, pc sees harddrive and dvd in slim DVDRW (pulled out my laptop) via usb, tab only sees harddrive (dvd spins but not detected)
Hi,
My 9023 cannot suspend when I push power off,and the kernel log like this,how to fix it?
<6>[ 2489.830938] s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
<6>[ 2489.831057] s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
<6>[ 2489.831251] s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
<6>[ 2489.831361] s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
<6>[ 2489.832271] PM: suspend of devices complete after 129.671 msecs
<3>[ 2489.832572] pm_noirq_op(): platform_pm_suspend_noirq+0x0/0x40 returns -11
<3>[ 2489.832763] PM: Device power.0 failed to suspend late: error -11
<6>[ 2489.832909] PM: early resume of devices complete after 0.038 msecs
<3>[ 2489.833166] PM: Some devices failed to power down
<6>[ 2489.902915] fsa9480 7-0025: dev1: 0x0, dev2: 0x0
<6>[ 2489.903321] s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
<3>[ 2489.903462] [ wm8994_samsung.c (wm8994_resume,3157) ] ------WM8994 Revision = [3]-------
<6>[ 2489.903678] PM: resume of devices complete after 70.405 msecs
<4>[ 2489.903986] Restarting tasks ...
<6>[ 2489.905150] wakeup wake lock: secril_fmt-interface
<4>[ 2489.910144] done.
you might have used the wrong rom?
so i recomand you to use a difrent rom,and see what happens.
does the other rom work?
than find the right working 2.3.6 rom.
i currently am using the 2.3.7 oxygen rom.
its a td better than stock.
but not much of a change.
Now I have tried 5 roms:
google 2.3.4
google 2.3.6
google 2.3.3 ota to 2.3.6
cm7.1
lucid kernel+2.3.4
and My phone is gt-i9023
modem:9023kf1
One XL/AT&T/Rogers One X/One S 1.8GHz overclock module
Please let me know about the module's compatibility with your phone. It has been reported to work on the latest AT&T version kernel, and I have a Rogers device myself.
Hey guys! I've created a kernel module that overclocks the MSM8960 Qualcomm Krait to over 1.8GHz. It also allows you to specify a custom voltage and frequency instead of 1.8GHz. This method works on ANY MSM8960-based rooted HTC One X, even on locked bootloader devices. This allows AT&T users to overclock, and others to overclock without necessarily needing to unlock the bootloader. This overclock makes the already tremendously fast MSM8960 about 20% faster.
Note that this mod is ONLY for the Qualcomm MSM8960-based Krait HTC One X and HTC One XL. This includes the AT&T HTC One X, Rogers HTC One X, and any phone branded as the HTC One XL. It has also been confirmed to work on the One S (see this thread: http://forum.xda-developers.com/showthread.php?t=1670904) and MIGHT work on the EVO 4G LTE.
The module is loaded using this command: insmod /data/local/krait_oc.ko pll_l_val=67 vdd_uv=1300000
The pll_l_val parameter determines how high the overclock is. Multiply this number by 27 to get the final clock speed in MHz. For example, 67*27 is 1809000, which is what the module defaults to.
The vdd_uv parameter determines the voltage used at the overclocked speed, in microvolts. The default for 1.5GHz is 1200000, and I was able to get a stable overclock at 1300000 at 1.8GHz. Raise the vdd_uv parameter if the overclock is unstable. The current maximum for this field is 1300000, so don't go higher than this. If your system crashes or is unstable at this frequency/voltage, lower the pll_l_val one by one until you reach stability. You can run rmmod krait_oc and then insmod krait_oc.ko with different parameters without having to reboot.
You'll also need a custom, tweaked thermald.conf. This thermald.conf raises thermal tolerances slightly (I've found that they're a little too strict, even at stock clocks and voltages). I've included this in the package, and instructions for installing it are below.
Video, demonstrating the overclock on a Rogers HTC One X:
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Source code is included in the package. If anyone has an HTC One S, this method will work on that, too. Please post below a dump of /system/lib/modules and I should be able to add support for any MSM8960-based HTC device with just that.
Instructions
First, determine which kernel module to use. Do an adb shell cat /proc/version and choose a ko file that matches your version number (these instructions assume you've renamed it to krait_oc.ko). 21/05/2012: If you don't see your kernel version here, try loading the module anyway. If it fails to load, please post a file from /system/lib/modules (any file) here and I will add support.
Install the overclock (only once):
1. Push the kernel module to your device:
Code:
adb push krait_oc.ko /data/local
2. Install the new thermald.conf, making sure to back up the old one, and reboot. The thermald.conf is included in the download. If you want to target a frequency other than 1809000 KHz, you should edit the thermald.conf and replace "1809000" to whatever frequency you want to target.
Code:
adb push thermald.conf /data/local
adb shell
su
mount -o rw,remount /system
cp /system/etc/thermald.conf /system/etc/thermald.conf.bak
rm -r /system/etc/thermald.conf
cp /data/local/thermald.conf /system/etc
reboot
Load the overclock (every time you reboot):
1. Load the kernel module (replace pll_l_val and vdd_uv with your desired voltages and L value as explained above. It defaults to 67 and 1300000 if you don't give it any parameters):
Code:
adb shell
su
insmod /data/local/krait_oc.ko pll_l_val=67 vdd_uv=1300000
2. Bring core 1 temporarily offline so it gets updated with the new max frequency:
Code:
echo 0 > /sys/devices/system/cpu/cpu1/online
3. You'll now have an additional CPU frequency! SetCPU can configure your maximum frequency up to this speed. You can also choose to keep running at 1.5GHz at any time - this method doesn't eliminate any available frequencies. Set the max at 1.8GHz to verify it's stable here.
4. Restart thermald by running "ps". Look for "thermald" in the list, and find thermald's pid (it's usually a number in the low hundreds, higher up in the list). Run "kill [thermald's PID]" in adb shell. The kernel does not currently have kernel-level temperature throttling turned on, so thermald is important for now.
Remove the overclock by restoring your backup of thermald.conf:
Code:
adb shell
su
mount -o rw,remount /system
rm -r /system/etc/thermald.conf
cp /system/etc/thermald.conf.bak /system/etc/thermald.conf
rm -r /system/etc/thermald.conf.bak
reboot
Rebooting clears any kernel modules that are loaded, so you're now clean. You can then delete anything left over in /data/local, but it doesn't matter.
If the module loads but the overclock doesn't seem to have any effect, even after putting max and min at 1.8GHz, your device might use a different SoC bin than the "nominal," and the kernel module is looking at the wrong place. Please reboot your device and post an adb shell dmesg right after the reboot so I can look at it.
Download current pack of modules:
http://www.setcpu.com/files/krait_oc_v2.zip (current)
http://www.setcpu.com/files/krait_oc.zip (old)
Finally, it'd be great if we as a community tried to work harder to encourage HTC to hurry up and 1. Release kernel source on time, all the time and 2. NOT cave into carrier pressure and stick to their written bootloader policy! S-OFF would be nice, too.
Thanks for sharing! Hard!
can we not use both cores with your mod?
ignore my ignorance it comes online fine
Sorry for being a noob but I don't understand how to do step 4 for restarting the thermald?
As it currently stands the OC works but as soon as I restart the phone, the overclock goes away.
Doesn't it say that you have to re-load the Overclock everytime your reboot ? (Post #1)
My bad, I thought those steps meant that the overlock will load everytime the phone reboots.
Confirmation
Hey, just wanted to confirm that this overclock is working for RUU_Evita_UL_Cingular_US_1.82.502.3 (version 3.0.8-01150-g31e8587) on the AT&T HTC One X. Also, thanks so much for the mod!
Zarboz said:
can we not use both cores with your mod?
ignore my ignorance it comes online fine
Click to expand...
Click to collapse
Yeah, you just have to bring core 1 temporarily offline. The overclock fully works with both cores.
jojojohnson7410 said:
Hey, just wanted to confirm that this overclock is working for RUU_Evita_UL_Cingular_US_1.82.502.3 (version 3.0.8-01150-g31e8587) on the AT&T HTC One X. Also, thanks so much for the mod!
Click to expand...
Click to collapse
Thanks for confirming this! I wasn't sure because I compiled it so that it works on my Rogers ROM, and some symbol versions might have differed. Guess not. Modversions is turned on in this kernel (yay), so there's no need to compile a different module for every kernel version.
gtung99 said:
My bad, I thought those steps meant that the overlock will load everytime the phone reboots.
Click to expand...
Click to collapse
Nope, but a script to do it automatically upon every reboot should be very trivial to write. I might leave that to the ROM devs though.
gtung99 said:
Sorry for being a noob but I don't understand how to do step 4 for restarting the thermald?
Click to expand...
Click to collapse
"adb shell ps" gives a list of the running processes on the system in rows. Find thermald's row (if you are on Linux or Mac OS X you can just do an "adb shell ps | grep thermald" to find the row quickly), and make a note of the first number - this is the PID. Now do "adb shell", "su", and then "kill [thermald's PID]". thermald will now be restarted automatically and will be aware of the overclocked speed. I want to find a way to enable kernel-level temperature throttling so we can disable thermald, as it's not very good.
"If the module loads but the overclock doesn't seem to have any effect, even after putting max and min at 1.8GHz, your device might use a different SoC bin than the "nominal," and the kernel module is looking at the wrong place. Please reboot your device and post an adb shell dmesg right after the reboot so I can look at it.
"
Looks like this is happening to me. Here is my dmesg:
<6>[ 35.453074] [FD92][PID=530][wake_unlock][sys]
<6>[ 35.453197] [FD93][PID=530][state][sys]
<6>[ 35.453288] [FD94][PID=437][SettingsProvider.apk][system]
<6>[ 35.453349] [FD95][PID=437][SettingsProvider.apk][system]
<6>[ 35.453471] [FD96][PID=524][][pipe:]
<6>[ 35.453532] [FD97][PID=524][][pipe:]
<6>[ 35.453654] [FD98][PID=524][[eventpoll]][anon_inode:]
<6>[ 35.453715] [FD99][PID=530][[eventpoll]][anon_inode:]
<6>[ 35.453776] [FD100][PID=530][inotify][anon_inode:]
<6>[ 35.453898] [FD101][PID=530][][pipe:]
<6>[ 35.453960] [FD102][PID=530][][pipe:]
<6>[ 35.454082] [FD103][PID=530][][pipe:]
<6>[ 35.454143] [FD104][PID=530][][pipe:]
<6>[ 35.454204] [FD105][PID=530][[eventpoll]][anon_inode:]
<6>[ 35.454326] [FD106][PID=531][][pipe:]
<6>[ 35.454387] [FD107][PID=531][][pipe:]
<6>[ 35.454448] [FD108][PID=531][[eventpoll]][anon_inode:]
<6>[ 35.454570] [FD109][PID=534][][pipe:]
<6>[ 35.454631] [FD110][PID=533][ashmem][dev]
<6>[ 35.454692] [FD111][PID=533][ashmem][dev]
<6>[ 35.454814] [FD112][PID=534][][pipe:]
<6>[ 35.454906] [FD113][PID=534][[eventpoll]][anon_inode:]
<6>[ 35.454967] [FD114][PID=531][ashmem][dev]
<6>[ 35.455028] [FD115][PID=561][][pipe:]
<6>[ 35.455089] [FD116][PID=536][event6][dev]
<6>[ 35.455211] [FD117][PID=437][][socket:]
<6>[ 35.455302] [FD118][PID=537][][pipe:]
<6>[ 35.455363] [FD119][PID=537][][pipe:]
<6>[ 35.455424] [FD120][PID=537][[eventpoll]][anon_inode:]
<6>[ 35.455486] [FD121][PID=538][][pipe:]
<6>[ 35.455547] [FD122][PID=538][][pipe:]
<6>[ 35.455669] [FD123][PID=538][[eventpoll]][anon_inode:]
<6>[ 35.455730] [FD124][PID=539][][pipe:]
<6>[ 35.455821] [FD125][PID=539][][pipe:]
<6>[ 35.455943] [FD126][PID=539][[eventpoll]][anon_inode:]
<6>[ 35.456004] [FD127][PID=543][][pipe:]
<6>[ 35.456065] [FD128][PID=543][][pipe:]
<6>[ 35.456188] [FD129][PID=543][[eventpoll]][anon_inode:]
<6>[ 35.456249] [FD130][PID=564][][pipe:]
<6>[ 35.456371] [FD131][PID=533][ashmem][dev]
<6>[ 35.456432] [FD132][PID=564][][pipe:]
<6>[ 35.456493] [FD133][PID=565][][pipe:]
<6>[ 35.456615] [FD134][PID=536][event3][dev]
<6>[ 35.456706] [FD135][PID=536][event2][dev]
<6>[ 35.456767] [FD136][PID=533][ashmem][dev]
<6>[ 35.456889] [FD137][PID=564][[eventpoll]][anon_inode:]
<6>[ 35.456951] [FD138][PID=536][event1][dev]
<6>[ 35.457012] [FD139][PID=536][event0][dev]
<6>[ 35.457164] [FD140][PID=536][event8][dev]
<6>[ 35.457225] [FD141][PID=536][event7][dev]
<6>[ 35.457286] [FD142][PID=561][][pipe:]
<6>[ 35.457408] [FD143][PID=561][[eventpoll]][anon_inode:]
<6>[ 35.457469] [FD144][PID=560][][socket:]
<6>[ 35.457591] [FD145][PID=562][][pipe:]
<6>[ 35.457652] [FD146][PID=562][][pipe:]
<6>[ 35.457714] [FD147][PID=562][[eventpoll]][anon_inode:]
<6>[ 35.457836] [FD148][PID=563][][pipe:]
<6>[ 35.457897] [FD149][PID=563][][pipe:]
<6>[ 35.457988] [FD150][PID=563][[eventpoll]][anon_inode:]
<6>[ 35.458110] [FD151][PID=565][][pipe:]
<6>[ 35.458171] [FD152][PID=565][[eventpoll]][anon_inode:]
<6>[ 35.458293] [FD153][PID=437][Infinite.apk][system]
<6>[ 35.458354] [FD154][PID=566][][pipe:]
<6>[ 35.458415] [FD155][PID=566][][pipe:]
<6>[ 35.458538] [FD156][PID=566][[eventpoll]][anon_inode:]
<6>[ 35.458599] [FD157][PID=567][][pipe:]
<6>[ 35.458660] [FD158][PID=567][][pipe:]
<6>[ 35.458782] [FD159][PID=567][[eventpoll]][anon_inode:]
<6>[ 35.458843] [FD160][PID=568][][pipe:]
<6>[ 35.458904] [FD161][PID=568][][pipe:]
<6>[ 35.459026] [FD162][PID=568][[eventpoll]][anon_inode:]
<6>[ 35.459117] [FD163][PID=569][][pipe:]
<6>[ 35.459240] [FD164][PID=569][][pipe:]
<6>[ 35.459301] [FD165][PID=569][[eventpoll]][anon_inode:]
<6>[ 35.459362] [FD166][PID=570][][pipe:]
<6>[ 35.459484] [FD167][PID=570][][pipe:]
<6>[ 35.459575] [FD168][PID=570][[eventpoll]][anon_inode:]
<6>[ 35.459636] [FD169][PID=573][][pipe:]
<6>[ 35.459758] [FD170][PID=573][][pipe:]
<6>[ 35.459819] [FD171][PID=573][[eventpoll]][anon_inode:]
<6>[ 35.459942] [FD172][PID=579][][pipe:]
<6>[ 35.460003] [FD173][PID=577][][pipe:]
<6>[ 35.460064] [FD174][PID=577][][pipe:]
<6>[ 35.460125] [FD175][PID=577][[eventpoll]][anon_inode:]
<6>[ 35.460247] [FD176][PID=575][][socket:]
<6>[ 35.460308] [FD177][PID=579][][pipe:]
<6>[ 35.460430] [FD178][PID=579][[eventpoll]][anon_inode:]
<6>[ 35.460491] [FD179][PID=580][][pipe:]
<6>[ 35.460582] [FD180][PID=580][][pipe:]
<6>[ 35.460674] [FD181][PID=580][[eventpoll]][anon_inode:]
<6>[ 35.460766] [FD182][PID=437][userbehavior.db][data]
<6>[ 35.460857] [FD183][PID=437][ashmem][dev]
<6>[ 35.460949] [FD184][PID=607][][socket:]
<6>[ 35.461010] [FD185][PID=607][][socket:]
<6>[ 35.461132] [FD186][PID=607][][socket:]
<6>[ 35.461193] [FD187][PID=607][][socket:]
<6>[ 35.461254] [FD188][PID=608][][pipe:]
<6>[ 35.461376] [FD189][PID=608][][pipe:]
<6>[ 35.461437] [FD190][PID=608][[eventpoll]][anon_inode:]
<6>[ 35.461498] [FD191][PID=543][][socket:]
<6>[ 35.461620] [FD192][PID=543][][socket:]
<6>[ 35.461681] [FD193][PID=610][][pipe:]
<6>[ 35.461742] [FD194][PID=610][][pipe:]
<6>[ 35.461864] [FD195][PID=610][[eventpoll]][anon_inode:]
<6>[ 35.461925] [FD196][PID=611][][pipe:]
<6>[ 35.462017] [FD197][PID=611][][pipe:]
<6>[ 35.462108] [FD198][PID=611][[eventpoll]][anon_inode:]
<6>[ 35.462200] [FD199][PID=613][][pipe:]
<6>[ 35.462322] [FD200][PID=617][ashmem][dev]
<6>[ 35.462383] [FD201][PID=613][][pipe:]
<6>[ 35.462444] [FD202][PID=613][[eventpoll]][anon_inode:]
<6>[ 35.462566] [FD203][PID=437][lightsensor][dev]
<6>[ 35.462627] [FD204][PID=614][][pipe:]
<6>[ 35.462688] [FD205][PID=614][][pipe:]
<6>[ 35.462810] [FD206][PID=614][][pipe:]
<6>[ 35.462871] [FD207][PID=614][][pipe:]
<6>[ 35.462933] [FD208][PID=614][[eventpoll]][anon_inode:]
<6>[ 35.463055] [FD209][PID=531][ashmem][dev]
<6>[ 35.463116] [FD210][PID=531][ashmem][dev]
<6>[ 35.463177] [FD211][PID=531][][pipe:]
<6>[ 35.463299] [FD212][PID=531][][pipe:]
<6>[ 35.463390] [FD213][PID=531][][pipe:]
<6>[ 35.463451] [FD214][PID=531][][pipe:]
<6>[ 35.463573] [FD215][PID=531][HtcLockScreen.apk][system]
<6>[ 35.463634] [FD216][PID=531][HtcLockScreen.apk][system]
<6>[ 35.463757] [FD217][PID=531][HtcLockScreen.apk][system]
<6>[ 35.463818] [FD218][PID=615][][pipe:]
<6>[ 35.463879] [FD219][PID=615][][pipe:]
<6>[ 35.464001] [FD220][PID=615][[eventpoll]][anon_inode:]
<6>[ 35.464062] [FD221][PID=616][][pipe:]
<6>[ 35.464184] [FD222][PID=616][][pipe:]
<6>[ 35.464245] [FD223][PID=616][[eventpoll]][anon_inode:]
<6>[ 35.464306] [FD224][PID=437][GoogleBackupTransport.apk][system]
<6>[ 35.464459] [FD225][PID=437][][socket:]
<6>[ 35.464520] [FD226][PID=701][ashmem][dev]
<6>[ 35.464642] [FD227][PID=617][ashmem][dev]
<6>[ 35.464703] [FD228][PID=531][ion_share_fd][anon_inode:]
<6>[ 35.464764] [FD229][PID=531][genlock][anon_inode:]
<6>[ 35.464886] [FD230][PID=531][ion][dev]
<6>[ 35.464947] [FD231][PID=531][genlock][dev]
<6>[ 35.465008] [FD232][PID=617][ashmem][dev]
<6>[ 35.465130] [FD233][PID=885][][pipe:]
<6>[ 35.465191] [FD234][PID=429][][pipe:]
<6>[ 35.465283] [FD235][PID=429][][pipe:]
<6>[ 35.465374] [FD236][PID=617][ashmem][dev]
<6>[ 35.465466] [FD237][PID=806][][pipe:]
<6>[ 35.465527] [FD238][PID=806][][pipe:]
<6>[ 35.465649] [FD239][PID=885][][pipe:]
<6>[ 35.465710] [FD240][PID=885][[eventpoll]][anon_inode:]
<6>[ 35.465832] [FD241][PID=617][ashmem][dev]
<6>[ 35.465893] [FD242][PID=418][][pipe:]
<6>[ 35.465954] [FD243][PID=418][][pipe:]
<6>[ 35.466076] [FD244][PID=531][ion_share_fd][anon_inode:]
<6>[ 35.466137] [FD245][PID=531][genlock][anon_inode:]
<6>[ 35.466229] [FD246][PID=531][genlock][dev]
<6>[ 35.466351] [FD247][PID=418][Browser.apk][system]
<6>[ 35.466412] [FD248][PID=429][][pipe:]
<6>[ 35.466534] [FD249][PID=429][][pipe:]
<6>[ 35.466595] [FD250][PID=418][Calendar.apk][system]
<6>[ 35.466656] [FD251][PID=429][][pipe:]
<6>[ 35.466778] [FD252][PID=701][][pipe:]
<6>[ 35.466870] [FD253][PID=701][][pipe:]
<6>[ 35.466931] [FD254][PID=701][[eventpoll]][anon_inode:]
<6>[ 35.467053] [FD255][PID=701][][socket:]
<6>[ 35.467144] [FD256][PID=705][][pipe:]
<6>[ 35.467205] [FD257][PID=705][][pipe:]
<6>[ 35.467327] [FD258][PID=705][[eventpoll]][anon_inode:]
<6>[ 35.467419] [FD259][PID=701][][socket:]
<6>[ 35.467480] [FD260][PID=706][][pipe:]
<6>[ 35.467602] [FD261][PID=706][][pipe:]
<6>[ 35.467663] [FD262][PID=706][[eventpoll]][anon_inode:]
<6>[ 35.467785] [FD263][PID=704][][pipe:]
<6>[ 35.467846] [FD264][PID=704][][pipe:]
<6>[ 35.467907] [FD265][PID=704][[eventpoll]][anon_inode:]
<6>[ 35.468029] [FD266][PID=701][][pipe:]
<6>[ 35.468090] [FD267][PID=701][][pipe:]
<6>[ 35.468151] [FD268][PID=701][diag][dev]
<6>[ 35.468274] [FD269][PID=437][settings.db-wal][data]
<6>[ 35.468335] [FD270][PID=437][databases][data]
<6>[ 35.468426] [FD271][PID=784][][pipe:]
<6>[ 35.468518] [FD272][PID=437][htcCheckin.db][data]
<6>[ 35.468609] [FD273][PID=784][][pipe:]
<6>[ 35.468670] [FD274][PID=784][[eventpoll]][anon_inode:]
<6>[ 35.468792] [FD275][PID=429][][pipe:]
<6>[ 35.468853] [FD276][PID=418][HtcContacts+CRC_VIE_EVA_ENR_PRO_S40.apk][syst
em]
<6>[ 35.468976] [FD277][PID=437][GoogleBackupTransport.apk][system]
<6>[ 35.469037] [FD278][PID=437][GoogleBackupTransport.apk][system]
<6>[ 35.469159] [FD279][PID=418][HtcMusic.apk][system]
<6>[ 35.469220] [FD280][PID=418][HtcNotes.apk][system]
<6>[ 35.469342] [FD281][PID=418][Mail.apk][system]
<6>[ 35.469403] [FD282][PID=418][Message+CRC_1.apk][system]
<6>[ 35.469525] [FD283][PID=418][Music2.apk][system]
<6>[ 35.469586] [FD284][PID=418][PDF_Viewer_F_A.apk][system]
<6>[ 35.469647] [FD285][PID=418][PureC_ApplicationsProvider.apk][system]
<6>[ 35.469769] [FD286][PID=418][Settings.apk][system]
<6>[ 35.469830] [FD287][PID=418][Twitter.apk][system]
<6>[ 35.469952] [FD288][PID=418][VoiceSearch.apk][system]
<6>[ 35.470044] [FD289][PID=418][Watch.apk][system]
<6>[ 35.470135] [FD290][PID=418][YouTube.apk][system]
<6>[ 35.470227] [FD291][PID=418][com.android.vending-1.apk][data]
<6>[ 35.470349] [FD292][PID=418][com.google.android.apps.maps-1.apk][data]
<6>[ 35.470410] [FD293][PID=418][com.google.android.gm-1.apk][data]
<6>[ 35.470532] [FD294][PID=418][com.google.android.videos-1.apk][data]
<6>[ 35.470593] [FD295][PID=418][com.google.android.apps.books-1.apk][data]
<6>[ 35.470715] [FD296][PID=418][com.yellowpages.android.ypmobile-1.apk][data]
<6>[ 35.470837] [FD297][PID=418][com.twitter.android-1.apk][data]
<6>[ 35.470898] [FD298][PID=418][com.quoord.tapatalkxda.activity-1.apk][data]
<6>[ 35.471020] [FD299][PID=418][net.zedge.android-1.apk][data]
<6>[ 35.471081] [FD300][PID=418][com.handcent.nextsms-1.apk][data]
<6>[ 35.530352] [FD] 301 files print end
<6>[ 36.954768] genlock: genlock_release_lock: Releasing a handle that still h
olds lock (2)
<6>[ 36.955012] mdp4_overlay_pipe_free: pipe=c0c81828 ndx=2 stage 4 mixer 0
<6>[ 36.955898] genlock: genlock_release_lock: Releasing a handle that still h
olds lock (2)
<4>[ 36.963467] mdp4_overlay_update_layers: unstaging pipe ndx=2
<4>[ 36.963558] mdp4_overlay_update_layers: mask=0000F000 new layermixer_cfg=0
0000132
<6>[ 37.272943] msm_etb msm_etb.0: etb disabled
<6>[ 37.273035] msm_tpiu msm_tpiu.0: tpiu disabled
<6>[ 37.276148] msm_etb msm_etb.0: etb enabled
<6>[ 37.276239] msm_funnel msm_funnel.0: funnel port mask 0x3 enabled
<4>[ 37.276545] ------------[ cut here ]------------
<4>[ 37.276636] WARNING: at /home/aa/Project/Evita_ATT_WWE_ICS_CRC_Stable_2549
31/kernel/arch/arm/mach-msm/qdss-ptm.c:250 ptm_trace_enable+0x3b8/0x450()
<4>[ 37.276758] timeout while clearing prog bit
<4>[ 37.276880] Modules linked in: prima_wlan(P)
<4>[ 37.277094] [<c010c744>] (unwind_backtrace+0x0/0x12c) from [<c0179aec>] (w
arn_slowpath_common+0x4c/0x64)
<4>[ 37.277247] [<c0179aec>] (warn_slowpath_common+0x4c/0x64) from [<c0179b84>
] (warn_slowpath_fmt+0x2c/0x3c)
<4>[ 37.277674] [<c0179b84>] (warn_slowpath_fmt+0x2c/0x3c) from [<c011ba54>] (
ptm_trace_enable+0x3b8/0x450)
<4>[ 37.277826] [<c011ba54>] (ptm_trace_enable+0x3b8/0x450) from [<c011bdb8>]
(ptm_write+0x180/0x418)
<4>[ 37.277887] [<c011bdb8>] (ptm_write+0x180/0x418) from [<c021dbb4>] (vfs_wr
ite+0xac/0x134)
<4>[ 37.278040] [<c021dbb4>] (vfs_write+0xac/0x134) from [<c021dce8>] (sys_wri
te+0x3c/0x68)
<4>[ 37.278162] [<c021dce8>] (sys_write+0x3c/0x68) from [<c0105e60>] (ret_fast
_syscall+0x0/0x30)
<4>[ 37.278284] ---[ end trace 3e69383386a66a84 ]---
<4>[ 37.278528] ------------[ cut here ]------------
<4>[ 37.278620] WARNING: at /home/aa/Project/Evita_ATT_WWE_ICS_CRC_Stable_2549
31/kernel/arch/arm/mach-msm/qdss-ptm.c:250 ptm_trace_enable+0x3b8/0x450()
<4>[ 37.278773] timeout while clearing prog bit
<4>[ 37.278834] Modules linked in: prima_wlan(P)
<4>[ 37.279047] [<c010c744>] (unwind_backtrace+0x0/0x12c) from [<c0179aec>] (w
arn_slowpath_common+0x4c/0x64)
<4>[ 37.279261] [<c0179aec>] (warn_slowpath_common+0x4c/0x64) from [<c0179b84>
] (warn_slowpath_fmt+0x2c/0x3c)
<4>[ 37.279383] [<c0179b84>] (warn_slowpath_fmt+0x2c/0x3c) from [<c011ba54>] (
ptm_trace_enable+0x3b8/0x450)
<4>[ 37.279505] [<c011ba54>] (ptm_trace_enable+0x3b8/0x450) from [<c011bdb8>]
(ptm_write+0x180/0x418)
<4>[ 37.279627] [<c011bdb8>] (ptm_write+0x180/0x418) from [<c021dbb4>] (vfs_wr
ite+0xac/0x134)
<4>[ 37.279719] [<c021dbb4>] (vfs_write+0xac/0x134) from [<c021dce8>] (sys_wri
te+0x3c/0x68)
<4>[ 37.279841] [<c021dce8>] (sys_write+0x3c/0x68) from [<c0105e60>] (ret_fast
_syscall+0x0/0x30)
<4>[ 37.279963] ---[ end trace 3e69383386a66a85 ]---
<6>[ 37.280054] msm_ptm msm_ptm.0: tracing enabled
<6>[ 37.291255] msm_etb msm_etb.0: etb dumped
<6>[ 37.291316] msm_etb msm_etb.0: etb disabled
<6>[ 37.295406] msm_funnel msm_funnel.0: funnel port mask 0x3 disabled
<6>[ 37.298489] msm_ptm msm_ptm.0: tracing disabled
<6>[ 37.341614] [PM] CPU1: msm_pm_power_collapse: change clock rate (old rate
= 0)
<6>[ 37.343293] mdp4_overlay_req2pipe: pipe=c0c81828 ndx=2 num=1 zorder=4 mixe
r 0 format = 9
<3>[ 37.707187] l2cap_sock_connect: failed -115
<6>[ 38.011353] [WLAN] Set country code: US
<6>[ 38.071356] mdp4_overlay_pipe_free: pipe=c0c81a40 ndx=3 stage 2 mixer 0
<6>[ 38.071600] mdp4_overlay_pipe_free: pipe=c0c81c58 ndx=4 stage 3 mixer 0
<6>[ 38.071753] mdp4_overlay_pipe_free: pipe=c0c81828 ndx=2 stage 4 mixer 0
<4>[ 38.072028] mdp4_overlay_update_layers: unstaging pipe ndx=3
<4>[ 38.072028] mdp4_overlay_update_layers: unstaging pipe ndx=4
<4>[ 38.072028] mdp4_overlay_update_layers: unstaging pipe ndx=2
<4>[ 38.072058] mdp4_overlay_update_layers: mask=0000F0FF new layermixer_cfg=0
0000100
<6>[ 38.873920] mdp4_overlay_req2pipe: pipe=c0c81a40 ndx=3 num=2 zorder=2 mixe
r 0 format = 9
<6>[ 38.885609] mdp4_overlay_req2pipe: pipe=c0c81c58 ndx=4 num=3 zorder=3 mixe
r 0 format = 9
<6>[ 38.888600] mdp4_overlay_req2pipe: pipe=c0c81828 ndx=2 num=1 zorder=4 mixe
r 0 format = 9
<3>[ 39.689516] qtaguid: iface_stat: stat_update() rmnet0 not found
<3>[ 39.693148] qtaguid: iface_stat: stat_update() rmnet0 not found
<6>[ 41.600793] call alarm, type 2, func alarm_triggered+0x0/0xa0, 41568000000
(s 41568000000)
<7>[ 42.714695] wlan0: no IPv6 routers present
<6>[ 43.281794] call alarm, type 2, func alarm_triggered+0x0/0xa0, 43249000000
(s 43249000000)
<3>[ 43.849412] l2cap_sock_connect: failed -115
<3>[ 49.018159] l2cap_sock_connect: failed -115
<6>[ 49.228933] call alarm, type 3, func alarm_triggered+0x0/0xa0, 0 (s 0)
[email protected]:/ $
---------- Post added at 06:47 PM ---------- Previous post was at 06:46 PM ----------
BTW.....Thanks for all the hard work
Didn't work on my Rogers XL unfortunately. I noticed my directory structure is a little different than in the instructions. Your adb instructions say:
Code:
echo 0 > /sys/devices/system/cpu/cpu1/cpufreq/online
Following that path with a file explorer I discovered my device has no cpufreq directory. The file "online" is in the cpu1 folder itself.
SetCPU shows 1809 MHz as selectable but does not show any changes in clock speed when selected as both min and max. Can't see any difference in speed.
Dmesg log is attached. Help would be appreciated! Thanks!
Oh ya, love this guy. Had this same type of thing for the 3d. Thanks op.
Sent from my SPH-D710 using Xparent ICS Blue Tapatalk 2
MatinatorX said:
Didn't work on my Rogers XL unfortunately. I noticed my directory structure is a little different than in the instructions. Your adb instructions say:
Code:
echo 0 > /sys/devices/system/cpu/cpu1/cpufreq/online
Following that path with a file explorer I discovered my device has no cpufreq directory. The file "online" is in the cpu1 folder itself.
SetCPU shows 1809 MHz as selectable but does not show any changes in clock speed when selected as both min and max. Can't see any difference in speed.
Dmesg log is attached. Help would be appreciated! Thanks!
Click to expand...
Click to collapse
Yeah, I made a mistake in regards to the directory structure. My mistake - I edited the post to reflect the correct directory that online is in.
Your attached log seems to be taken too late in the boot up process. You have to take it immediately after boot up or else it won't catch the crucial line solidus175 too. The line should look similar to:
[ACPU] select_freq_plan: ACPU PVS: Nominal
Where Nominal can be Nominal, Fast, or Slow.
EDIT: You know what, I can just change all three tables. That shouldn't hurt anything. Will release an updated version of the module.
coolbho3000 said:
Yeah, I made a mistake in regards to the directory structure. My mistake - I edited the post to reflect the correct directory that online is in.
Your attached log seems to be taken too late in the boot up process. You have to take it immediately after boot up or else it won't catch the crucial line solidus175 too. The line should look similar to:
[ACPU] select_freq_plan: ACPU PVS: Nominal
Where Nominal can be Nominal, Fast, or Slow.
EDIT: You know what, I can just change all three tables. That shouldn't hurt anything. Will release an updated version of the module.
Click to expand...
Click to collapse
Cool....Will wait for update. THANKS!
solidus175 said:
Cool....Will wait for update. THANKS!
Click to expand...
Click to collapse
Released a new version of the kernel in the topic post: http://www.setcpu.com/files/krait_oc_v2.zip. Let me know how it works out. If it doesn't, this version now has more debug logging, so a dmesg log right after you load the module is very helpful.
coolbho3000 said:
Released a new version of the kernel in the topic post: http://www.setcpu.com/files/krait_oc_v2.zip. Let me know how it works out. If it doesn't, this version now has more debug logging, so a dmesg log right after you load the module is very helpful.
Click to expand...
Click to collapse
Worked like a charm! Many THANKS!
Worked awesome! Thank you very much. I created a script for ScriptManager with a homescreen shortcut to make things easier each boot. Overclocking does indeed feel significant, noticing a healthy boost in N64oid.
Edit: After about a half hour of gaming my XL is pretty toasty. Hoping the casing doesn't take on a different hue
Is there anyway to have the module load automatically when the device boots? Like a modules.conf
Sent from my HTC One X using XDA
MatinatorX said:
Worked awesome! Thank you very much. I created a script for ScriptManager with a homescreen shortcut to make things easier each boot. Overclocking does indeed feel significant, noticing a healthy boost in N64oid.
Edit: After about a half hour of gaming my XL is pretty toasty. Hoping the casing doesn't take on a different hue
Click to expand...
Click to collapse
What was the temp?
Sent from my HTC One X using XDA
blacklistedcard said:
Is there anyway to have the module load automatically when the device boots? Like a modules.conf
Click to expand...
Click to collapse
You can write a script and set it to run on boot with scriptmanager.
I'll do another test when I get home from work to verify the temperature. Not enough battery left right now.
Do u have to use the perflock disabler because setcpu shows 1.8 but CPU spy only shows up to 1.5.
Sent from my HTC One X using Xparent ICS Blue Tapatalk 2
Hi guys,
alright, so this should be a pretty "standard" question,
but I'm still having issues to solve it:
I'm getting errors like the following:
<4>[ 8.899871] ecryptfs: Unknown symbol wake_up_process (err -22)
<6>[ 10.418523] subsys-pil-tz fe200000.qcom,lpass: adsp: Power/Clock ready interrupt received
<6>[ 10.456267] subsys-pil-tz fe200000.qcom,lpass: Subsystem error monitoring/handling services are up
<6>[ 10.462157] platform fe034000.sound: Driver msm8994-asoc-snd requests probe deferral
<4>[ 10.480352] wlan: Unknown symbol sched_setscheduler (err -22)
<4>[ 10.480426] wlan: Unknown symbol wake_up_process (err -22)
<4>[ 10.915183] texfat: Unknown symbol wake_up_process (err -22)
...
<4>[ 54.177317] core_ctl: Unknown symbol core_ctl_get_policy (err -22)
<4>[ 54.177351] core_ctl: Unknown symbol set_user_nice (err -22)
<4>[ 54.177375] core_ctl: Unknown symbol wake_up_process (err -22)
<4>[ 54.177490] core_ctl: Unknown symbol core_ctl_put_policy (err -22)
Click to expand...
Click to collapse
The thing is:
I've removed the exfat driver from the kernel source !
So how and why is it still being loaded - where is it stored above all ?
And how to force update it ?
This is sort of like a Gentoo user (which I am) figuring out why the modules that are included in a packaged up blob are re-occuring
Hope you guys can help me out with this one since this is massively hindering kernel development and evaluation what commits work best for our device (performance, stability, battery runtime, etc.)
Thanks !
take a look at the following branch:
https://github.com/zachariasmaladro.../commits/32.0.A.6.200_AP_Sun-Kernel_v6-stable
the 5 last comments before the newest (or only the sched/fair, scheduler related) commits had to be reverted before WIFI and other components started to work again !
The Kernel and its driver are built from friggin' source !
How is that possible ?
is the ROM using proprietary kernel modules (including WIFI, I thought bcmdhd was supposed to get opensourced meanwhile) and those depend on certain symbols ?
Blasted ! :/