Database Info

Trouble with Touch screen, multi touch

I have cyanogens latest rom installed. I tried all the previous versions as well and I keep
having the same problem.
My Touch screen on my MyTouch3g keeps, for lack of a better description, going to sleep. I can still use the multi touch zoom function in the browser,but I cannot screen flick or get the icons to respond. I can hold the bottom of the screen and turn off and on and sometimes this will repair the problem. It seems to recur randomly. Is there any place to look in the log file to see what is causing this? I'm at a total loss after 6 or so roms and still no go. I tried the stripped down rom labeled TMO-OTA-US-DRC83-Rooted_update and also the expansion pack to no avail. I can't really believe this is hardware related since it's random and fixes with a power cycle most times. I'm just finding it annoying as hell, and I hope someone might be able to point me in the right direction.
I've done the bootloader flash/delete data and re-installed each time.
Latest rom from Cyanogen isCyanogen mod 4.2.4
Kernel version is 2.6.29.6-cm42 (does this matter? I include because I'm not sure)
Thanks
Mike

Maybe this will help
look for a post on how to install cyanogen rom on your MTY3 and dowlaod the rooted rom there.
secondly,
see this thread and the last post from me.
http://forum.xda-developers.com/showthread.php?t=583683

I've done multiple re-installs. The same problem keeps resurfacing within minutes.
I can use the touch screen and then it craps out. Oddly it will many times still allow pinch and zoom multi-touch in the browser. But single touch, such as in typing web addresses etc. , does not work.
Does anyone have an idea as to why this might be happening? Is there a particular file that is escaping the wipe/ reboot and reload process that is still not being replaced.
I'm curious if the Kernel has anything to do with this.
Any ideas?
Mike.

try redownloading the rom and the htc image like redownloading from the source wipe the ext erior partition as well pretty much completely restart the process except keep root lol... if that doesnt work then you need to unroot and reroot the bad boy all a learning experiance

Wipe the exterior partition? Doesn't this occur when I do a wipe/data? I have never partitioned the sd card. It has been the same since I received it. Will this affect the screen behavior?
Thanks for the input
Mike

oh well I figured you would be running apps2sd which requires a exterior partition or ext2/3/4 as some may call it... most roms require a wipe of that as some storage will transfer to there and cause problems ona seperate rom for some but if yours is a fresh sdcard then the only thing I can suggest is get a redownload of the cyan rom

CM 4.2.11.1 Camera and Home Screen issues

Firstly I'd like to thank PSYCHO13OI on the #cyanogenmod IRC channel for spending quite a bit of his time helping me out. I thought I might just throw my problem out there.
I received my new HTC Magic a few days ago, but spent quite a few days prior researching different ROMs.
I've got a 32A that came from 3 Australia.
Firstly, a summary of what I originally did.
After receiving my phone and playing around with the original ROM;
1) I fastbooted into: recovery-RA-sapphire-v1.5.2H.img.
2) I wiped data, and wiped a non-existant ext partition.
3) I partitioned the SD card using 32MB swap-size and a 256MB ext partition. Further I used ext2 -> ext3.
4) Loaded and flashed the following in order:
- DRC83_base_defanged
- update-cm-4.2.11.1-signed
5) Rebooted.
After 30 minutes of the original boot splash screen, I took the battery out (I couldn't, and still can't, figure out how to hard power off) and re-fastbooted into the recovery image.
6) I reperformed steps 1-4, this time actually flashing the kernel port: bc-4.2.11.1-ebi1-signed. I also repartitioned the SD card using a swap size of 256MB and ext partition of 1024MB and went from ext2 -> ext3 -> ext4.
7) Rebooted again.
8) When I get to the "Touch the android to begin." screen, I got this error message:
Sorry!
The process com.android.
phone has stopped unexpectedly. Please try again.
My only option is to force close which still allows me to touch the android and proceed as normal. Otherwise, everything seemed fine and dandy.
A few days later I decided to try using the Camera and Camcorder apps. This caused a reboot. This did not happen on the original ROM.
After the reboot I noticed that the home screen hung after trying to swipe my home screen. This eventually lead to the error message (after 10 seconds or so):
Sorry!
Activity Home(in process
android.process.acore) is not
responding.
I was prompted with the option to either force close or wait. Choosing either will restore complete functionality in 20-30 seconds.
Now this happens after every reboot (and I'm uncertain whether or not it is related to the Camera issue).
Trying to fix both issues, I repeated the flashing process, this time wiping the dalvik-cache as well.
Still no go. I've made the logcats of the first boot after reflashing CM 4.2.11.1 as well as a reboot. I have also linked my last_kmsg after rebooting due to the Camera app crash.
1st Boot: http://pastebin.com/m356cf97e
Reboot: http://pastebin.com/m69a15127
last_kmsg: http://pastebin.com/m76c42ee6
This camera issue is touched on here: http://code.google.com/p/cyanogenmod/issues/detail?id=792
As for the Camera issue, similar to the OP in the above thread, I only have issues when on battery power. However, I do not have any issues in other apps that utilize the camera such as barcode readers.
Things I have not tried:
- Another CM version.
- Wiping battery information or anything else other than data/ext partition/dalvik-cache.
- Reflashing an original ROM (which I did not backup - my friend's Magic is coming in the next week or so, so I'll grab his image).
Hopefully I've documented everything important (and perhaps trivial). I'm open to any suggestions.
EDIT: Some things I forgot to mention.
- 8GB Class 4 SD card
- Added details to my original post about partition sizes/types.

It seems I was wrong about rebooting only in the default Camera and Camcorder apps as I just recently experienced a reboot on the Barcode Scanner app.

Perhaps try an older version of cm. I had more stability on some of the older releases

What would be one of the more stable versions?

i always find CM has better themes and mods "BUT" the rom is laggy. in fact, amon's rom is fast and clean but not much of any theming. wasted.

scyzerd said:
What would be one of the more stable versions?
Click to expand...
Click to collapse
i'm back to 4.2.9.1 atm because it's a little less buggy. something like that or 4.2.8.1 or 7.1 maybe? go for the .1 versions because they will contain bug fixes for any known issues in the first release at that number...

I have that problem too... but I don't get it as often now. maybe once in a blue moon.....
there is two things I notice that when the reboot happens in the camera mode.
1) there are too much tasks running (you can notice it because the phone runs a little laggy, or if you check Taskskiller and the memory running low)
2) the audible selection is turn on
so now I watch taskskiller before I used the camera and reboot deson't happen that often, specially with the audible selection turn off.
let me know if you guy discover some other fix....

I wonder why in the world did you make such a big swap partition, since you have a 32A model you don't need any swap to run the CM ROM. To be honest CM works flawlesly without the SWAP partition on my phone which is also 32A. I have no problems with the homescreen nor the camera. Please try to repartition the SD card so it doesn't use the SWAP partition, you can also ditch the ext partition as the 32A model has more than enough space for applications installation (about 295MB space). Wipe and reinstall from scratch. Enjoy a working CM 4.2.11.1 build, you can even try 4.2.12.2
EDIT: ehhh, and if you encounter an alarm clock bug where the screen doesn't turn on when the alarm goes off, replace the existing alarm application (AlarmClock.apk) with the one provided in release 4.2.9. You lose some functions in the alarm clock but it works

Same problem different ROM
I'm having the same problem on a Rogers Magic 32A using AmonRa's Donut ROM.
The phone reboots after the 1st or 2nd restart of the camera. Plugged in to a charger, I can restart the camera at least 10 times. This isn't surprising since I did a wipe and reinstall the ROM and the problem still occurred with no other apps installed. Very strange.

I have the same problem...No not so much after I start using an other cam app, however the phone still reboots itself.

Jelly Bean Issues

Hello!
After updating from ICS to JB 2 months ago I constantly facing with different problems with. I was enjoying ICS and expected best experience from JB.
First of all I missed all of my media files from SD. I searched xda for answer and discovered same issues. All answers was, like, "delete .nomedia and/or wipe your device". I didn't have ANY .nomedia file on my SD. So, I forced to wipe all of my data, app settings, etc. and recover it again. F*ck, why I must format my phone to make it work properly? Sometimes I have known bug with stock launcher when it doesn't show any icons or render one icon to whole screen. Sometimes my device freezes and I only can reset it by ejecting battery. Very poor battery life. Several days ago my battery suddenly dropped to 0% from 60%! Look at pic in attachment.
But main problem with JB is performance. With ICS I hadn't any lags in simple games such as Cut the Rope, but in JB I often facing small freezes and lags that highly annoying. Sometimes one game running OK, but next time it very sluggish. I can't understand why. I constantly have ram issues. In ICS I saw stock launcher crash very rarely. But in JB after every Internet surfing or gaming I must wait to stock launcher load. More frequent is widget issues. When I press Home button I see that stock calendar widget blinking. That seems like it loading or reloading.
So, the main question is: what can I do with this? Is there any custom rom that hasn't this issues? Can I cut some JB features to increase it performance? Is there anyone that have same problems?

schroding3rscat said:
First of all I missed all of my media files from SD. I searched xda for answer and discovered same issues. All answers was, like, "delete .nomedia and/or wipe your device". I didn't have ANY .nomedia file on my SD.
Click to expand...
Click to collapse
look here http://forum.xda-developers.com/showthread.php?t=1913629
by the way I have no lag at all and a very good experience with JB

lostman.it said:
look here http://forum.xda-developers.com/showthread.php?t=1913629
by the way I have no lag at all and a very good experience with JB
Click to expand...
Click to collapse
I'd already solve this problem with wiping, but I didn't touch any of my media files. I don't think this was caused by corrupted file.

Wipe is necessary when you flash a brand new rom. I've experienced the same issue upgrading to jb from ics, solved by doing a full wipe!

Crucio32000 said:
Wipe is necessary when you flash a brand new rom. I've experienced the same issue upgrading to jb from ics, solved by doing a full wipe!
Click to expand...
Click to collapse
Of course I did this.
Also, sometimes I stuck with (bug?) android.server process consuming all CPU. Only phone restart helps.

I don't have a lot of complaints, and haven't had the same performance issues, though I don't do a lot of gaming. That's what the Nexus 7 is for.
The media scanner in Android sucks in my opinion, so if your files aren't showing up you may want to try running something like SDRescan. My music files (in Music directory on SD card) will show up as soon as I re-open Play Music.
You could try turning off Google Now if you haven't already. I did that and the battery seems to be a little better.

OP, I used to have the same problem and I could never find the .nomedia file. I had to delete ROM manager and its folder. After a full wipe and many tries, I got it to work. As for the launcher crashes, you might want to download an alternative from the play store. One that keeps it "in memory", that way it hardly crashes. I have Nova launcher and it happens frequently to where I switched to Apex haha.
This helped me and hoping it helps you. Good luck!
Sent from my Nexus S using xda premium

Poor Performance ,Even on CM11

Ever since I got the TF300T, I felt it was a little sluggish at times. I assumed it was because of all the bloatware and/or the Asus ROM.
I've dealt with it ever since I got it, which is pretty much the day it came out, and I'm tired of that.
I really hoped Jelly Bean or KitKat would help so I unlocked the bootloader, flashed TWRP and flashed a CM11 nightly. (From the 18th I think.)
Its been running for a few hours now, and I feel like its just as slow as before.
I'm aware I could buy a newer device (like a Nexus 7 or 10) but that's not an option right now.
I'm also aware that I could try another ROM like OMNI or Cromi but
(a) I choose CM because I've used their ROMs in the past and I trust them, and
(b) I'm not really in excited about trying 2, 3 or 5 different ROMs
Is this the sort of performance I should expect from this device?
Is this as good as it gets?
Sent from my TF300T using xda app-developers app

You should see a significant performance improvement from stock to CM11. For example starting or switching applications is much faster.
Can you describe in more detail, what you are doing, and where you consider it to be slow?
Sent from my TF300T using Tapatalk

Did you wipe /data, /system, /cache, & dalvik cache before you flashed CM11?

what he said
like ebildude said make sure to do proper wipes before installing rom. i've personally only used cromix and it works great, even though it's stock based - theres lots of tweaks. also look into getting a fast microsd and take a look at rom2sd ,data2sd and cache2sd tweaks in the cromi thread-may boost performance a little. hope you get it working to your satisfaction, this is really a good little machine when it works right, can even dual boot linux, look at the xubuntu thread.

Phylum said:
Ever since I got the TF300T, I felt it was a little sluggish at times. I assumed it was because of all the bloatware and/or the Asus ROM.
I've dealt with it ever since I got it, which is pretty much the day it came out, and I'm tired of that.
I really hoped Jelly Bean or KitKat would help so I unlocked the bootloader, flashed TWRP and flashed a CM11 nightly. (From the 18th I think.)
Its been running for a few hours now, and I feel like its just as slow as before.
I'm aware I could buy a newer device (like a Nexus 7 or 10) but that's not an option right now.
I'm also aware that I could try another ROM like OMNI or Cromi but
(a) I choose CM because I've used their ROMs in the past and I trust them, and
(b) I'm not really in excited about trying 2, 3 or 5 different ROMs
Is this the sort of performance I should expect from this device?
Is this as good as it gets?
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Try installing a kernel, like GEASS or GRIM. Then use overclock and a new scheduler.

Thanks for the replies!
f69m said:
You should see a significant performance improvement from stock to CM11. For example starting or switching applications is much faster.
Can you describe in more detail, what you are doing, and where you consider it to be slow?
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
I flashed it yesterday afternoon around 3pm and didn't do much with it other than
add my Google account
create a new user account and link that to Google
I haven't loaded it down with apps, yet.
In general, moving about the device seems choppy (not smooth) and its not responsive whether I'm
Opening and closing the app drawer
Scrolling the app drawer or home screen
Accessing menus in settings.
When turning on the screen it takes 5-7 seconds before the screen actually turns on.
Launching applications or games aren't any faster and there's some stuttering when watching media. (Like HBOGO)
ebildude123 said:
Did you wipe /data, /system, /cache, & dalvik cache before you flashed CM11?
Click to expand...
Click to collapse
I did a factory reset, installed ROM then wiped cache. I'll look at the TWRP menu when I get home.
brewmeister said:
like ebildude said make sure to do proper wipes before installing rom. i've personally only used cromix and it works great, even though it's stock based - theres lots of tweaks. also look into getting a fast microsd and take a look at rom2sd ,data2sd and cache2sd tweaks in the cromi thread-may boost performance a little. hope you get it working to your satisfaction, this is really a good little machine when it works right, can even dual boot linux, look at the xubuntu thread.
Click to expand...
Click to collapse
I really like this device for a variety of reasons, and I'd love to dual boot Linux! (I'm a huge FreeBSD and Gentoo fan!) Despite how sluggish its been, I've gotten a lot of work done on this device. Well via things like Citrix and LogMeIn. When traveling we use it to watch TV and do things that would otherwise be too difficult to do on a phone.
I have a 32GB Class 10 microsd in the tablet and 16GB Class 10 SD card in the battery/keyboard portion.

Something just occurred to me: Could it be that the system is scanning the SD cards? One is mostly empty (twrp backup, files for flashing) but the other is packed with data. (Maps for OsmAnd, TitaniumBackup backups, music, photos and other stuff etc.)

ebildude123 said:
Did you wipe /data, /system, /cache, & dalvik cache before you flashed CM11?
Click to expand...
Click to collapse
The TWRP Factory reset wipes data, cache and dalvik not including internal storage.
The advanced wipe let's you choose the option to wipe everything, but I only did cache and dalvik.
Also after flashing a ROM TWRP has a convenient 'Wipe Cache/Dalvik' button on the screen, which I did.
So to be sure, I just did a factory reset again , followed by an advanced wipe wiping everything except my memory cards (Data, dalvik, system, cache). I reflashed CM11, wiped cache and dalvik then flashed the gapps.
That sufficient?

cmendonc2 said:
Try installing a kernel, like GEASS or GRIM. Then use overclock and a new scheduler.
Click to expand...
Click to collapse
I'll read into this a bit more and maybe give it a go. Does one seem to work better for the TF300T than the other?

Phylum said:
The TWRP Factory reset wipes data, cache and dalvik not including internal storage.
The advanced wipe let's you choose the option to wipe everything, but I only did cache and dalvik.
Also after flashing a ROM TWRP has a convenient 'Wipe Cache/Dalvik' button on the screen, which I did.
So to be sure, I just did a factory reset again , followed by an advanced wipe wiping everything except my memory cards (Data, dalvik, system, cache). I reflashed CM11, wiped cache and dalvik then flashed the gapps.
That sufficient?
Click to expand...
Click to collapse
Yup, looks good to me.

Phylum said:
I'll read into this a bit more and maybe give it a go. Does one seem to work better for the TF300T than the other?
Click to expand...
Click to collapse
Well by my testing, GEASS seemed more stable, but Grim had more raw power. It will depend on what apps you have installed and use.

Phylum said:
In general, moving about the device seems choppy (not smooth) and its not responsive whether I'm
Opening and closing the app drawer
Scrolling the app drawer or home screen
Accessing menus in settings.
Click to expand...
Click to collapse
Opening recent apps can sometimes take 2-3 seconds, especially if there are a lot of recent apps and it has not been used in a while. But usually it is less than 1 sec. Everything else you list should be very snappy, less than 1 sec, usually far less.
When turning on the screen it takes 5-7 seconds before the screen actually turns on.
Click to expand...
Click to collapse
That is much too long! I get the lock screen in less than a second.
Did you see any improvements after the full wipe including data?
Phylum said:
Something just occurred to me: Could it be that the system is scanning the SD cards? One is mostly empty (twrp backup, files for flashing) but the other is packed with data. (Maps for OsmAnd, TitaniumBackup backups, music, photos and other stuff etc.)
Click to expand...
Click to collapse
That is indeed possible; maybe it is waiting for the device to settle, especially during the long screen-on time.
Any improvement, if you remove the sdcards?
Sent from my TF300T using Tapatalk

Ok its been about a few hours since I wiped + reflashed and I have a bittersweet update.
The Good:
I'm noticing an immediate improvement this time around!
+ The CPU is now at a more reasonable 0.1x-0.2x versus a constant 3.xx - 5.xx!
+ When waking up from sleep (pressing the power button) the screen is on almost immediately versus 5-7 seconds.
+ Opening the app drawer, moving between screens is not only faster (more responsive) but its not as choppy. (maybe completely lagless)
+ In general its noticeably faster.
+ I installed Netflix, HBO GO etc and playback is smooth.
The Bad:
- There's still the occasional slowness in general, although not as frequent, but its especially slow when downloading & installing apps. (like it hangs)
- It was running nicely *until* I added a second user. Immediately after creating the account, there was a significant decrase in performance. I noticed this in the stock Asus ROM even after wiping and not installing anything. Not sure if this is an Android thing or unique to this device. (Also, it just rebooted right in the middle of creating the account; fluke I suppose as it didn't happen a second time.)
- CPU is now hanging around 0.3x - 0.5x after adding the new user. I assume its caused by whatever background processes associated with the new account but the 'presence' of the new account is being felt.
While I'm not excited about the cons, its considerably better than what it used to be.
I'll test without the microSD & SD card tomorrow and let the system 'rest' and 'settle' for tonight.
Your input has been invaluable and I'll keep pressing on!
Sent from my TF300T using xda app-developers app

Is there a [CM] utility that allows you to easily update to the most recent nightly?
Or do we just download the zip and flash in recovery?
Sent from my TF300T using xda app-developers app

Phylum said:
There's still the occasional slowness in general, although not as frequent, but its especially slow when downloading & installing apps. (like it hangs)
Click to expand...
Click to collapse
Try the ROW I/O scheduler, that should perform much better with background writing.
Phylum said:
Is there a [CM] utility that allows you to easily update to the most recent nightly?
Or do we just download the zip and flash in recovery?
Click to expand...
Click to collapse
There is a CM updater in the system "about" settings.
Sent from my TF300T using Tapatalk

Phylum said:
Ok its been about a few hours since I wiped + reflashed and I have a bittersweet update.
The Good:
I'm noticing an immediate improvement this time around!
+ The CPU is now at a more reasonable 0.1x-0.2x versus a constant 3.xx - 5.xx!
+ When waking up from sleep (pressing the power button) the screen is on almost immediately versus 5-7 seconds.
+ Opening the app drawer, moving between screens is not only faster (more responsive) but its not as choppy. (maybe completely lagless)
+ In general its noticeably faster.
+ I installed Netflix, HBO GO etc and playback is smooth.
The Bad:
- There's still the occasional slowness in general, although not as frequent, but its especially slow when downloading & installing apps. (like it hangs)
- It was running nicely *until* I added a second user. Immediately after creating the account, there was a significant decrase in performance. I noticed this in the stock Asus ROM even after wiping and not installing anything. Not sure if this is an Android thing or unique to this device. (Also, it just rebooted right in the middle of creating the account; fluke I suppose as it didn't happen a second time.)
- CPU is now hanging around 0.3x - 0.5x after adding the new user. I assume its caused by whatever background processes associated with the new account but the 'presence' of the new account is being felt.
While I'm not excited about the cons, its considerably better than what it used to be.
I'll test without the microSD & SD card tomorrow and let the system 'rest' and 'settle' for tonight.
Your input has been invaluable and I'll keep pressing on!
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Most ROMs lag when updating from the store etc. Just turn off auto updating and do them manually and don't use the tab for 5 mins whilst it is updating.
As for multi user - it's bawked - never seen it work well on any device. I'd forget it for now as the performance hit is not worth it.

Phylum said:
Is there a [CM] utility that allows you to easily update to the most recent nightly?
Or do we just download the zip and flash in recovery?
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
You can use the CM updater found in your settings.

[Q] screen goes black after app launch

My phone learned a new trick last week: launch an app, and the screen turns dead black after the app's splash loading screen.
It doesn't happen with every app or every time certain apps are launched, but if it is going to happen, it is always just after an app loading screen and before the app itself would be displayed. It never happens on a system or preference screen, or in an app without a splash animation.
Button back-lighting, volume control, and haptic seem to remain active and respond as normal, but the app seems to be locked into the foreground with a black screen, and can't seem to do anything to stop it but reboot the phone via power button hold.
I'm running CM 12.1 nightlies on a Verizon S3. I've been updating the CM nightlies, well, nightly since last week in hopes a fix would be included in one of them, but I'm not sure this is a ROM issue. I've also wiped Dalvik/Cache several times, with and without a ROM update. I saw black screens on some phones were caused by theme window animations, so I've disabled these in CM, but hasn't made a difference.

Just a guess on my part, but if the nightlies do not fix this you may end up needing to do a clean flash. Hopefully you do not have to go as far as formatting /system.

dawgdoc said:
Just a guess on my part, but if the nightlies do not fix this you may end up needing to do a clean flash. Hopefully you do not have to go as far as formatting /system.
Click to expand...
Click to collapse
Thanks, but wouldn't a "clean flash" require wiping `system`?
I'm wondering whether this is possibly a hardware problem too: this phone's been pretty beaten up, not sure how to determine that though.

deesto-xda said:
Thanks, but wouldn't a "clean flash" require wiping `system`?
I'm wondering whether this is possibly a hardware problem too: this phone's been pretty beaten up, not sure how to determine that though.
Click to expand...
Click to collapse
I'd wipe everything, including system and your internal SD card, then you'll know for sure if it's hardware related or not.

deesto-xda said:
Thanks, but wouldn't a "clean flash" require wiping `system`?
I'm wondering whether this is possibly a hardware problem too: this phone's been pretty beaten up, not sure how to determine that though.
Click to expand...
Click to collapse
Yeah, I was thinking internal sdcard, like @BadUsername said.