I have a HTC Polaris and I installed yesterday Android.
I used Incubus26Jc's Super FroYo RLS10.5 Themed with polaimg-panel3-320-froyo-15-07-10.
When I try to open the camera, after a few seconds I get the error in the picture.
Radio version is 1.59.46.12
I got the same problom
My model and radio are the same to you,
and the problom is the same....
I just tried the latest Radio for Polaris and the same problem occurs.
zeoos said:
I have a HTC Polaris and I installed yesterday Android.
I used Incubus26Jc's Super FroYo RLS10.5 Themed with polaimg-panel3-320-froyo-15-07-10.
When I try to open the camera, after a few seconds I get the error in the picture.
Radio version is 1.59.46.12
Click to expand...
Click to collapse
i have the same problem
but my radio version is 1.65.38.14, i'm using Super FroYo 2.2[RLS10] and panel1(24-05-10)
humm, you can help me to find polaimg-panel3-320-froyo-15-07-10?
thanks!
Another with the same problem, any solution?
I used Incubus26Jc's Super FroYo RLS11 Themed with polaimg-panel3-320-froyo-15-07-10.
rfsaidel, the link polaimg http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
The camera works perfectly with the program layar, but keeps giving error when I want to take a picture. What is happening?
I use Android with Haret.
When is start my camera it says: Please insert an SD card before using the camera... but there is a SD card in the phone.
Reformat sdcard and try again
I have the same problem. Formatting (fat32) doesn't helped.
Device: pola100
Kernel: l1q1d (POLAIMG-PANEL1-320-FROYO.NBH)
Radio: 1.59.46.12 (Previous: 1.59.42.15 from Original HTC WWE 3.13.405.0)
OS: androidhtc.sourceforge.net (system-froyo-02-09-10_17.tgz)
System: NAND
Data: NAND
When i insert the sdcard dmesg gives me:
Code:
[ 535.350453] mmc1: Slot status change detected (0 -> 1)
[ 536.590495] set sdcc vdd to 17
[ 536.642967] clk_set_rate 21:144000
[ 536.645007] set sd clock - 0 20001
[ 536.753135] mmc1: Command timeout
[ 536.759012] mmc1: Command timeout
[ 536.760389] mmc1: Command timeout
[ 536.760389] mmc1: Command timeout
[ 536.760389] SD Init
[ 536.767470] set sdcc vdd to 15
[ 536.959049] mmc_sd_init_card: Delay 250 ms
[ 537.220389] clk_set_rate 21:32000000
[ 537.220389] set sd clock - 0 20001
[ 537.314612] mmc1: host does not support reading read-only switch. assuming write-enable.
[ 537.314687] SD Init Retry
[ 537.314730] mmc1: new high speed SDHC card at address b368
[ 537.318229] mmcblk1: mmc1:b368 USD 3931136KiB
[ 537.318765] mmcblk1: unknown partition table
Reformat the sd using a partition manager
Got rid of the sdcard error using:
adb shell
fdisk /dev/block/mmcblk1 (created one primary partition)
mkdosfs /dev/block/mmcblk1p1
umount /sdcard
<ejected and inserted sdcard>
But now there is another known error:
Starting WLAN, it immediately shows "Error".
I tried to use an hint from another thread:
running "Fix File Persmissions" from the bootmenu
without success.
Did you install the correlated wlan module for the choosen kernel/nbh?
You are going OT
I've hooked my new G2x up to windows, installed LG drivers, and get two separate drives to access Internal memory and external SD card.
However, when I hook it up to my Gentoo box, It only seems to recognize internal memory.
Looking at dmesg, here is what seems to be the relevant output:
Code:
usb 2-1.5: new high speed USB device number 3 using ehci_hcd
usb 2-1.5: config 1 interface 3 altsetting 0 has 3 endpoint descriptors, different from the interface descriptor's value: 2
scsi6 : usb-storage 2-1.5:1.4
scsi 6:0:0:0: Direct-Access LGE P999DW 0000 PQ: 0 ANSI: 2
sd 6:0:0:0: Attached scsi generic sg3 type 0
sd 6:0:0:0: [sdc] Attached SCSI removable disk
sd 6:0:0:0: [sdc] 10942464 512-byte logical blocks: (5.60 GB/5.21 GiB)
sd 6:0:0:0: [sdc] No Caching mode page present
sd 6:0:0:0: [sdc] Assuming drive cache: write through
sd 6:0:0:0: [sdc] No Caching mode page present
sd 6:0:0:0: [sdc] Assuming drive cache: write through
sdc:
sdc: detected capacity change from 5602541568 to 0
I assuming I'm at least missing a kernel module. Any ideas as to which it would be?
(Kernel 3.0, udev+udisks)
This is just a guess but do you have "ntfs-3g" installed on your box?
Yes, I do have two partitions mounted with ntfs-3g.
Is this an issue/conflict?
I have TF700 Infinity with Cromi-X 4.6.9 installed, running hundsbuah's 3.0.6 kernel with Data2SD enabled. I use SanDisk 32GB Mobile Ultra Micro SDHC card, formatted using gparted on Parted Magic linux. Fsync is enabled.
I noticed that my experience with Data2SD is deteriorating. Fresh after formatting Micro SD it works perfectly fine, but after week or two some random freezes start to occur (most often when running app's but sometimes even at lockscreen) forcing me to reboot. With more number of reboots freezes get more often after I'm desperate enough to format Micro SD again and reinstall. I've been trying with _that kernel, but it was no difference. Is that a problem of my SD Card or with Infinity? How can I fix it?
Here is the part of content of last_kmsg
Code:
[ 1789.970823] Switched to NOHz mode on CPU #1
[ 1792.498820] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 1792.971434] cpu_down(3)+
[ 1792.973679] CPU3: shutdown
[ 1792.975627] edp_update_limit: Limiting cpu speed from 1500000 to 1500000 during boot!
[ 1792.976218] cpu_down(3)-
[ 1794.117317] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 1794.841849] cpu ext_temperature=37
[ 1795.971717] cpu_down(2)+
[ 1795.975049] CPU2: shutdown
[ 1795.977786] edp_update_limit: Limiting cpu speed from 1500000 to 1500000 during boot!
[ 1795.978965] cpu_down(2)-
[ 1797.990758] mmcblk1: error -110 transferring data, sector 36657736, nr 344, cmd response 0x900, card status 0xb00
[ 1797.991805] mmcblk1: retrying using single block read
[ 1798.981523] cpu_down(1)+
[ 1798.982526] CPU1: shutdown
[ 1798.983655] edp_update_limit: Limiting cpu speed from 1600000 to 1500000 during boot!
[ 1798.984118] cpu_down(1)-
[ 1799.638992] mmcblk1: error -110 transferring data, sector 36657736, nr 344, cmd response 0x900, card status 0x0
[ 1799.639284] [mmc]:mmc_blk_issue_rw_rq:1101 SD freq. down to UHS_SDR12_MAX_DTR
[ 1799.642246] mmcblk1: timed out sending r/w cmd command, card status 0x400b00
[ 1799.642518] mmcblk1: command error, retrying timeout
[ 1800.322357] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 1802.446926] mmcblk1: error -110 transferring data, sector 36657737, nr 343, cmd response 0x900, card status 0xb00
[ 1802.449065] mmcblk1: retrying using single block read
[ 1804.863463] cpu ext_temperature=34
[ 1805.248817] mmcblk1: error -110 transferring data, sector 36657737, nr 343, cmd response 0x900, card status 0x0
[ 1805.251672] mmcblk1: timed out sending r/w cmd command, card status 0x400b00
[ 1805.251929] mmcblk1: command error, retrying timeout
[ 1808.053001] mmcblk1: error -110 transferring data, sector 36657738, nr 342, cmd response 0x900, card status 0xb00
[ 1808.053064] mmcblk1: retrying using single block read
[ 1810.851446] mmcblk1: error -110 transferring data, sector 36657738, nr 342, cmd response 0x900, card status 0x0
[ 1810.853818] mmcblk1: timed out sending r/w cmd command, card status 0x400b00
[ 1810.853875] mmcblk1: command error, retrying timeout
[ 1813.657813] mmcblk1: error -110 transferring data, sector 36657739, nr 341, cmd response 0x900, card status 0xb00
[ 1813.659954] mmcblk1: retrying using single block read
[ 1814.883548] cpu ext_temperature=32
[ 1816.459651] mmcblk1: error -110 transferring data, sector 36657739, nr 341, cmd response 0x900, card status 0x0
[ 1816.462061] mmcblk1: timed out sending r/w cmd command, card status 0x400b00
[ 1816.462161] mmcblk1: command error, retrying timeout
[ 1818.411499] gpio_keys: Pressed KEY_POWER
[ 1819.262896] mmcblk1: error -110 transferring data, sector 36657740, nr 340, cmd response 0x900, card status 0xb00
[ 1819.263004] mmcblk1: retrying using single block read
[ 1822.059974] mmcblk1: error -110 transferring data, sector 36657740, nr 340, cmd response 0x900, card status 0x0
[ 1822.067079] mmcblk1: timed out sending r/w cmd command, card status 0x400b00
[ 1822.069317] mmcblk1: command error, retrying timeout
[ 1824.877483] mmcblk1: error -110 transferring data, sector 36657741, nr 339, cmd response 0x900, card status 0xb00
[ 1824.879788] mmcblk1: retrying using single block read
[ 1824.902545] cpu ext_temperature=31
13422 Corrected bytes, 16 unrecoverable blocks
Also after last reinstall I noticed that I can't access ext4 partition of my sdcard. In /storage I see emulated, sdcard0 and sdcard1. Emulated and sdcard0 lead to data that are on my internal sdcard, sdcard1 is empty. However, data2SD is working, because i tested with androbench and the random write speed is 0.3-0.4Mbps and when I removed the Micro SD card from a slot the system booted with all my apps gone, so it made me sure, that my regular installation is on external sd.
"error -110 transferring data" and "timed out sending r/w cmd" indicates problems with your card. The TF700 is known to have troubles with fast microSD cards - some work reliably, some don't.
_that said:
"error -110 transferring data" and "timed out sending r/w cmd" indicates problems with your card. The TF700 is known to have troubles with fast microSD cards - some work reliably, some don't.
Click to expand...
Click to collapse
Well, the card is SanDisk Mobile Ultra, which worked nice for many people from what I've read. Anyway, I think I managed to solve the problem. I've read in one of threads that formatting to ext2 instead of ext4 might work better, so I tried it and so far so good.
Just if someone has simmilar problem - try ext2.
Arquiteto said:
Well, the card is SanDisk Mobile Ultra, which worked nice for many people from what I've read. Anyway, I think I managed to solve the problem. I've read in one of threads that formatting to ext2 instead of ext4 might work better, so I tried it and so far so good.
Just if someone has simmilar problem - try ext2.
Click to expand...
Click to collapse
I had a similar problem with crashing and freezing using Data2SD but I think it was because of a defective card. Since then, I tried using the CROMI-X without data2sd and I was surprised I was still satisfied with the response and speed of the tablet. Data2SD still might be a little bit faster but in my opinion the differences are not that noticeable anymore.
lasallegreen said:
I had a similar problem with crashing and freezing using Data2SD but I think it was because of a defective card. Since then, I tried using the CROMI-X without data2sd and I was surprised I was still satisfied with the response and speed of the tablet. Data2SD still might be a little bit faster but in my opinion the differences are not that noticeable anymore.
Click to expand...
Click to collapse
I think that all the advances made in kernel development and rom tweaks that data2sd is not as beneficial as it used to be
Arquiteto said:
Just if someone has simmilar problem - try ext2.
Click to expand...
Click to collapse
Thanks for the advice. Could you do us all a favor and report back in a week or so? This seems like a useful thing to document.
B00T_Sp0rk said:
Thanks for the advice. Could you do us all a favor and report back in a week or so? This seems like a useful thing to document.
Click to expand...
Click to collapse
Reporting back:
It looked like the problem was solved, as it worked fine... for a few days. And then it was all over again, so I guess the problem is the MicroSD Card after all. However it was a little better with ext2 the freezes returned so I dumped data2sd. My Infinity is now a bit slower, but at least it's stable. I got the freeze one more time without data2sd (checked the last_kmsg it was -110 error) but I'm using it for few days and it was the only time it happened.
You think that I might get a replacement MicroSD from SanDisk if I sent it back?
Arquiteto said:
Reporting back:
It looked like the problem was solved, as it worked fine... for a few days. And then it was all over again, so I guess the problem is the MicroSD Card after all. However it was a little better with ext2 the freezes returned so I dumped data2sd. My Infinity is now a bit slower, but at least it's stable. I got the freeze one more time without data2sd (checked the last_kmsg it was -110 error) but I'm using it for few days and it was the only time it happened.
You think that I might get a replacement MicroSD from SanDisk if I sent it back?
Click to expand...
Click to collapse
You may have a system problem rather than the external SD. Without data2sd, your system still caused the same problem. If you don't have any other solution, you may want to format your internal SD and start out fresh. I use 64G Samsung class 10 and it works fine with data2sd. Good luck.
LetMeKnow said:
You may have a system problem rather than the external SD. Without data2sd, your system still caused the same problem. If you don't have any other solution, you may want to format your internal SD and start out fresh. I use 64G Samsung class 10 and it works fine with data2sd. Good luck.
Click to expand...
Click to collapse
The problem looked the same, as it was -110, but might have been for different reason. And it havn't occured ever again so far, while with data2sd I had it few times a day after a while, so I guess it is the external SD fault after all.
I wonder why the manufacturers and users doesn't bother about the speed of internal memory. OFC most people look at the CPU, GPU and resolution when they buy tablets, but the speed of memory is also important parameter, especially in high-end devices.
Arquiteto said:
The problem looked the same, as it was -110, but might have been for different reason. And it havn't occured ever again so far, while with data2sd I had it few times a day after a while, so I guess it is the external SD fault after all.
I wonder why the manufacturers and users doesn't bother about the speed of internal memory. OFC most people look at the CPU, GPU and resolution when they buy tablets, but the speed of memory is also important parameter, especially in high-end devices.
Click to expand...
Click to collapse
I thought that you still have the same problem without the data2sd but it only happened once then you probably right about the defected external sd. I totally agree with you about the overall design of this tablet if it is intended for a high performance device but one year ago the technical specification was very impressive comparing with other product lines on the market. So to answer your question, I use it for an entertainment when I travel to kill time at the airport and check my personal email at the hotel. I don't expect much out of it and so far it does what it is supposed to do except for the slow internet. I found a solution with a custom rom...:good: I don't know what other users use it for and why manufacturer came up with that designed concept. I am guessing that they want more profit out of this product maybe.
Hi everyone
I'm working on a custom embedbed android version with printing support. I'm having some troubles when connecting the printer do the board (EM210 Android 4.0)
This is the log from dmsg when I connect the usb printer (1.1 USB) the board is compliant with USB 2.0.
[ 3867.524022] usb 1-1.3: new full speed USB device number 14 using s5p-ehci
[ 3867.614000] usb 1-1.3: device descriptor read/64, error -32
[ 3867.804011] usb 1-1.3: device descriptor read/64, error -32
[ 3867.994175] usb 1-1.3: new full speed USB device number 15 using s5p-ehci
[ 3868.084009] usb 1-1.3: device descriptor read/64, error -32
[ 3868.274402] usb 1-1.3: device descriptor read/64, error -32
[ 3868.469008] usb 1-1.3: new full speed USB device number 16 using s5p-ehci
[ 3868.883827] usb 1-1.3: device not accepting address 16, error -32
[ 3868.904184] hub 1-1:1.0: unable to enumerate USB device on port 3
[ 3869.114141] usb 1-1.3: new full speed USB device number 18 using s5p-ehci
I used USB Device INFO app and in Linux tab I can see that the printer was correctly mounted on /sys/bus/usb/devices/1-1.3/ but In Android there is no device detected.
Any idea on how can I try to make this work?
Thanks for any help