Sorry i provided wrong name. It should be panel_size. Yours is 0x80000740.Sorry, i searched but i dont know how to check panel_type
dmesg attached
Sorry i provided wrong name. It should be panel_size. Yours is 0x80000740.Sorry, i searched but i dont know how to check panel_type
dmesg attached
i had record a videoSorry i provided wrong name. It should be panel_size. Yours is 0x80000740.
Yes, i'm familiar with that issue. Now I just need some more users with that issue, to post their info about atrix (before i can start to work on fix).i had record a video
i cant post links youtube id:
uGJN8nCiw1U
It sounds weird and i dont know if its useful but if you let the phone sleep and it cold down the problem dissapear (for less than minute -until it go warm again-). You can force cold putting it in the fridge for 5 minutes and works like a charm. you will get a happiness minute to enjoy this great job.Yes, i'm familiar with that issue. Now I just need some more users with that issue, to post their info about atrix (before i can start to work on fix).
They definitely deserve it This is some piece of work. Bravoand do not forget to buy a beer to those fantastic developers!!!
I'm testing the last cm 10.1 version with the new kernel and I'm having reboots when screen is off.Anyone getting random reboots with the microSD card inserted?
So I guess the issue of cannot lockup in gmaps is common?just tested on my d00 tegrapart and running for half day..so far the issue i encounter is at OP such as unable to wake up screen after a period and front camera unusable..i give it more time to see whether it will reboot(using 16gb san disk sd card). i also file transfer using bluetooth, it work fine also..the only thing i cant do is get a lock in google maps but i guess that was on low priority
not sure..but i cant get lock in google maps..but i guess i can wait until they sort out other kernel issue only fix thisSo I guess the issue of cannot lockup in gmaps is common?
Gửi từ MB860 của tôi
This might sound odd but for me I couldn't get a lock on cm9 or cm10.1 with new kernel. I kept trying and clearing cache and data and force closing maps in app info. Then I would open navigation and put in a address for it to take me to. Eventually it locked on cm9 yesterday and cm10.1 today. Both times it took forever. After it finally worked no problem after. Quick lock after 1stnot sure..but i cant get lock in google maps..but i guess i can wait until they sort out other kernel issue only fix this![]()
The font? yes, but you need a third-party keyboard to install languages...Does It Support Multilingual Specially Arabic Language ?
Thats the same issue i have and have always had with the new kennel even when i compiled it.CM10.1: can not wake up the screen and judder
CM9: each time when waking up the screen jitter
same here. see my previous attach image/Thats the same issue i have and have always had with the new kennel even when i compiled it.
Im ATT as well but my other atrix also ATT that i replaced cause a section of digitizer went out has non of these issues just tested it so this is really annoying lol the phone thats unusable does not have this crippling issue. I just went and looked at your pic and yes its the exact same issue and before anyone says did you wipe... Yes i have been on android a long time and did full wipe of everything. It seems there is a cross section of phones that are ether way less common so they slipped by the devs or just have some other issue.same here. see my previous attach image/
i'm att and u guys??
agreed with ur ideas. i'm come from china and our forum (it's called gfan ,maybe u've heard of it) are discussing about this issue as well.Im ATT as well but my other atrix also ATT that i replaced cause a section of digitizer went out has non of these issues just tested it so this is really annoying lol the phone thats unusable does not have this crippling issue. I just went and looked at your pic and yes its the exact same issue and before anyone says did you wipe... Yes i have been on android a long time and did full wipe of everything. It seems there is a cross section of phones that are ether way less common so they slipped by the devs or just have some other issue.
It seems the same problem that me. Im ATT and you can check my previous post for more info. Provide more info about your phone [1]Im ATT as well but my other atrix also ATT that i replaced cause a section of digitizer went out has non of these issues just tested it so this is really annoying lol the phone thats unusable does not have this crippling issue. I just went and looked at your pic and yes its the exact same issue and before anyone says did you wipe... Yes i have been on android a long time and did full wipe of everything. It seems there is a cross section of phones that are ether way less common so they slipped by the devs or just have some other issue.