yashsingh1/xdaforums huggingface dataset:
[TouchPad Q&A, Help & Troubleshooting] mputtr:
flash the latest nightly.
[TouchPad Q&A, Help & Troubleshooting] Andysan:
screen unresponsive281]flash the latest nightly.[/QUOTE]

Thanks for the reply. I may consider doing that, guess that with a Android backup I don't have much to lose. Would like to avoid it if possible as not being as widespread they aren't as proven and I've ironed out all other issues in alpha 2 such as wifi etc ...

Thanks :-)
[TouchPad Q&A, Help & Troubleshooting] mputtr:
the latest nightly offers quite a few fixes.....

including vibration from sleep and tons of other stuff. not much can go wrong.
[TouchPad Q&A, Help & Troubleshooting] BIGSimon:
There has been loads of improvements in CM9 wifi has been fixed sound distortion when the screen off is fixed many speed fixes we now have themes working

Do a nandroid backup in CWM then copy that to your pc for safety then wipe system partition DO NOT FACTORY RESET OR WIPE DATA or you will lose you data, then flash latest nightly and latest gapps then wipe dalvik cache/cache partition's then in advanced fix permission's and reboot system
[TouchPad Q&A, Help & Troubleshooting] Andysan:
Well.... I dip my hat to you guys.

Went ahead and installed the latest nightly - even if it doesn't fix my issue, I was suprised by how polished it felt compared with Alpha 2. Typically with bleeding edge stuff I'd have expected to have more issues, but alls I had to do was reinstall YouTUbe and flash the gapps-fixer zip for my Calender sync, plus I see lots of lovely new settings to play with.

Will report back if the screen hangs again, here's hoping...
[TouchPad Q&A, Help & Troubleshooting] Andysan:
Frustratingly this issue has started happening for me again running 31 May nightly - touch screen has become unresponsive half a dozen times in the last ten minutes.
[TouchPad Q&A, Help & Troubleshooting] mputtr:
Maybe trying wiping it and doing a brand new flash from the latest nightly. (I know it sucks to reinstall stuff, but maybe there are some leftover codes that is causing trouble.. )
[TouchPad Q&A, Help & Troubleshooting] darkassain:
i agree either to wiping data or up your min cpu speed as it might the amount of apps you have installed that auto start/resume when turn on the screen..
[TouchPad Q&A, Help & Troubleshooting] lufc:
Please use the Q&A Forum for questions &

Read the Forum Rules Ref Posting

Thanks ✟

Moving to Q&A
[TouchPad Q&A, Help & Troubleshooting] b4silver:
I only had that problem once. Rebooted by holding home and power never had it again.
[TouchPad Q&A, Help & Troubleshooting] aqnd:
Had this issue yesterday for the first time since installing cm9 6(?) months ago.

Tried a nightly build as suggested, but given the rarity in the first place, can't be sure it's fixed ;)
[TouchPad Q&A, Help & Troubleshooting] trunzoc:
This happens to me all the time across all ROMs I have tested.

This happens in OaT's and turning the screen off/on, fixes it temporarily.

This happens in Butta, but turning the screen off/on does nothing. I have to reboot using power/home.

I have also been unable to find a specific app that causes it, but it does seem to occur more often in graphic intensive games.

I can go for days without it happening, then BAM, it stops responding to touch, from that point forward, no about of reboots or full shutdowns seems to fix it for several hours. I'll reboot and sometimes it'll be immediately, sometimes it will be 3-5 minutes, but it will happen again.

Then a few hours later it'll stop happening and I'm good for a few more days.

Do those of you using CM9 find that screen off/on fixes it, or do you need a full reboot?
[TouchPad Q&A, Help & Troubleshooting] Moshe5368:
I am running the night lies and have to say that the only time I experienced this was with the may nightlies. I have not experienced any issues with the 7/04 nightly.
[TouchPad Q&A, Help & Troubleshooting] Bharakrama:
Interestingly enough I think I found out what causes the screen to stop responding. When the TouchPad is locked in landscape and then I turn it portrait while its still locked, then the screen becomes unresponsive. Does that make sense?
[TouchPad Q&A, Help & Troubleshooting] Bharakrama:
I take it back. The screen became unresponsive even in landscape mode. There goes my well formed and thoroughly investigated theory.

---------- Post added at 07:54 PM ---------- Previous post was at 07:22 PM ----------

I've been using Nova Launcher ... I switched back to Trebuchet and it appears to be working normally. Of course I may be spouting this half-cocked like I did before. What launcher are you using?
[TouchPad Q&A, Help & Troubleshooting] Moshe5368:
I run SPB 3D launcher and do not experience any response issues with the latest nightlies. I use my touchpad constantly as a laptop replacement so mine gets a workout every day. To my knowledge, no one was ever able to find any one app that was responsable for this behaviour but it was noted in earlier builds.

,
[TouchPad Q&A, Help & Troubleshooting] Andysan:
I too still have this issue - as per others, fine for days, then it will occur consistently and I keep having to screen off/on and eventually it stops of its own accord. Am sure its a software issue, but someone here says they also had it in WebOS and HP provided a replacement.

http://rootzwiki.com/topic/20740-screen-unresponsive-in-cm9/

For me as simply flapping the screen on/off fixes it and I've never had the issue within WebOS, it has to be software - this started as soon as I first installled CM9.
[TouchPad Q&A, Help & Troubleshooting] Andysan:
Bump - still no fix identified for this by anyone with this issue please?
[TouchPad Q&A, Help & Troubleshooting] Andysan:
To anyone still following on, followed nevertells advise and completely started again from scratch and it happened after about twenty mins of using the stock browser. I think i've tried not using that app before so am just going to assume that this is either a software bug or a hardware issue that only manifests itaelf within Android
[T-Mobile Samsung Galaxy S II SGH-T989] rfail1988:
I have tried multiple ics roms - only tmo based - and have had low call volume on all of them. Is this ics specific or phone specific? I have done multiple dark side cache wipes and follow all standard installation instructions carefully with each new rom. Can I fix this and if so how? Thanks :-)
[T-Mobile Samsung Galaxy S II SGH-T989] ImARaptor:
This sounds phone specific, as all of my previous ROMs (I am currently using AOKP so this is a known-issue) had standard in-call volume. You can try Volume+ as I know that app has a way to change in-call volume that may or may not work. Hope this helps! :D
[T-Mobile Samsung Galaxy S II SGH-T989] Optimizer:
With most ICS based roms right now, they are usually ports or leaks from other carriers phones, meaning there are going to be some bugs with the phone.

With most of the ICS roms, it is also a known issue of the call volume being too low, and it is known to the developer.

You might just have to sit back and wait for more stable builds or wait for our great developers to find fixes to the problems! :D
[TouchPad General] adder101:
Does any of the rom's have a mic working?

I've just installed S-voice and want to test it.

Thanks
[TouchPad General] Izeltokatl:
No. It's a hardware/driver issue across the board.

Sent from my rezound
[TouchPad General] rkaede:
try use the webos :D
[TouchPad General] BIGSimon:
Some of the CM7 roms had limited success with the mic but CM9 isn't ready yet

And S-voice won't work in webos lol
[TouchPad General] x000x:
cm9 has been out for like 5 months now.. i dont have any faith the mic or cam will ever work in cm9.
[TouchPad General] adder101:
:D s-voice for ics only, even then it had to be modified as its exclusive for Samsung s3.

If it worked in gb even if it was not that good, surely it could be made to work in ics.

Though the installation of s-voice was without any problems.
[TouchPad General] BIGSimon:
Mic and camera are at the bottom of the pile of things to do, getting an OS that was never designed for the TouchPad is no easy thing, drivers and wrappers have to be written from scratch with no support from HP. So have faith in the developers, remember most of them are either at full time work or school/college and are offering you there work for free, maybe you could ask HP to fix the camera and mic I think they would abandon that idea faster than they abandoned the TouchPad itself.
[TouchPad General] jsgraphicart:
Exactly what BIGSimon said. CM9 is still ALPHA. Meaning some things will not work. Not everything that is released is perfect right away. Developing ROMs isn't always an easy task. What they have done in 5 months is pretty damn great.
[TouchPad General] x000x:
yeah i know that. but i seem to recall that it at least halfway worked with cm7. plus, in a short time android will have another os version, jellybean or something. and then what? will cm9 be abandoned and work start with that one? and once again, the camera and mic will be pushed back down to the bottom of the list in order to work on more essential things? seems like a endless cycle
[TouchPad General] BIGSimon:
There's a big difference between Android 2.3.7 gingerbread and Android 4.0.4 ice cream sandwich which meant everything had to be re-written to work Android 5 jelly bean is more of an evolution of ICS so drivers will carry over, all the work that's been done now will mean that when JB is released the touchpad will get it a lot faster with everything working
[TouchPad General] Unrealwolf:
JellyBean will be a minor update, it will have a version 4.1, it isn't as huge step as going from 2.3 to 4.0.

Anyway, sound is surely being worked on (developers (partially, maybe) have gotten rid of bad screen-off sound issue last week), and we will see some progress in a time. If you want a tablet with all features working out-of-the-box, i guess, you should buy another device.
[TouchPad General] BuffMcBigHuge:
The latest audiolibs seems to be working great. Too bad S-Voice is having connection problems. Anyone know how to resolve the server issues in S-Voice?
[TouchPad General] perlmeister11:
+ 1 ;-)
[TouchPad General] jsgraphicart:
Do you have your device spoofed to be a galaxy s3? I think you need to that for it to work
[TouchPad General] BuffMcBigHuge:
I was able to get it working by flashing this:

http://xdaforums.com/showthread.php?t=1667046

Works wonderfully with the new audiolib!
[TouchPad General] Izeltokatl:
Is there a flashable audiolib somewhere?

--update--

Found it

http://goo.im/devs/jcsullins/cmtouchpad/testing
[TouchPad General] Unrealwolf:
Nighlyy 0620 has everything mic needs already included.
[HTC Sensation] Tester30:
I know I was down this road before.

I upgraded my 4G to ICS one of the first ones...

Then using One-X toolKit successfully installed CWM and root the thingy...

Silly me.. Started Fooking with perfectly fine phone..... and screwed it up to the point that I lost Sense, contacts, music... Otherwise it booted and worked...

Now started at point 0 again. D/loaded GB RUU, flashed it with no probs...

Looked for T-mo ICS update, found it and installed. NOW....... Dummy me, can't install CWM.... Can't root. All my effort end up at white HTC screen with no response at all, until I pull the battery out and then restart it. Restarts fine, everything works, but with no root cannot use Titanium and do have some apps to install.

Please, if someone had the same situation would you give me some pointers....

Getting to the point to go insane..... Thanks!!
[HTC Sensation] flare4000:
Did you s-off or are you s-off? To check take the battery out of your phone put it back in and hold down the power plus the volume down rocker. If it says S-off then just follow this guide if not you see what hboot you are on, assuming its 1.2x then follow this guide if its 1.18 then just use this
[HTC Sensation] Tester30:
Thanks for the reply.

After 10 hour fighting with that thing, finally got it done...

Still have no idea of what happened but, what I've done last, I didn't let it to reboot... Clicked BOOT TO RECOVERY right away.. It might of done the trick and allow me toboot to CWM and install the Superuser..... Now everything is fine..

Thanks, all!!!!
[HTC Sensation] Tester30:
Done it so many times in almost a year... S-OFF.. Unlocked, 1.27.000

Just a brain F*rt, I guess.....LOL
[Samsung Galaxy Nexus] a5pe4:
I just ran into a problem when rooting. I unlocked the bootloader and flashed clockworkmod for GSM and then pulled the battery to reboot but it didn't wipe the phone so I'm not sure what to do. I have a 4.0.4 IMM761
[Samsung Galaxy Nexus] beekay201:
Why did you pull battery? Did you unlock and flash cwm manually?
[Samsung Galaxy Nexus] a5pe4:
The tutorial I'm watching said to. I am unlocking manually. So I figured out that once the phone reboots the recovery seems to be erased. I am able to flash the recovery and then immediately go into it but if I power off the recovery won't work and I end up with a dead android with a red triangle above it. I want to flash superuser also but I think I will still have this recovery issue if I am not mistaken?
[Samsung Galaxy Nexus] beekay201:
http://xdaforums.com/showthread.php?p=25902280#post25902280´

checkout this post from efrant for an updated su.zip: http://xdaforums.com/showthread.php?p=26356773#post26356773
[Samsung Galaxy Nexus] a5pe4:
I got impatient and ended up just flashing the recovery, superuser, and the AOKP ROM all in one go. Works for now! Hope my recovery is still there when I reboot tho...
[HTC One X] wrecked77:
so everytime i try to flash the cleanrom 2.0 or go into recovery i get this white htc screen that says something about this version being for development only??

i rooted my phone then i unlocked the boot loader... any suggestions?
[HTC One X] treebill:
Have you tried?

fastboot erase cache

fastboot reboot
[HTC One X] ckpv5:
Are you sure that you have the international HOX, not the AT&T HOX ?

They are two different device. CWM recovery for HOX will not work for AT&T HOX.
[HTC One X] theDroidfanatic:
Its usually caused when the kernel is different from the one supplied with the rom, or you lock your bootloader with a custom rom installed, try flashing the kernel that came with CleanRom. And hit the thanjs button :)

Sent from the world's most beautiful and fastest phone, the HTC One X. Nuff Said.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] pakalrtb:
Can someone explain me why a kernel does not perform optimally right away?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] brockyneo:
I don't know the fancy logic saying but its like installing a new operating system on a PC once installed ya it fine but it need to settle ie with your apps ,settings ect then it will be at its full potential :D
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] pakalrtb:
Thanks but I was hoping for a more technical answer :)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] baz77:
I dont understand either, are there code optimalisations running that change the system or kernel config? Bit odd.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] pakalrtb:
Any dev's answer ? :confused:

P_
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] SpoonerPS3:
This is a good question. I've been wondering too.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] baz77:
In ny experience an os becomes slower in due time...
[Kindle Fire Android Development] seishuku:
In case no one believes me, here's a console dump (typing blind of course, this was an early attempt with no LCD):

d.
.
Starting periodic command scheduler: crond.
FATAL: Could not load /lib/modules/3.0.21+/modules.dep: No such file or directory

Debian GNU/Linux 5.0 carrier tty1

carrier login: usb 1-1: new low speed USB device number 2 using musb-hdrc
usb 1-1: device v0b38 p0010 is not supported
input: HID 0b38:0010 as /devices/platform/omap/musb-omap2430/musb-hdrc/usb1/1-1/1-1:1.0/input/input4
generic-usb 0003:0B38:0010.0001: input: USB HID v1.10 Keyboard [HID 0b38:0010] on usb-musb-hdrc-1/input0
input: HID 0b38:0010 as /devices/platform/omap/musb-omap2430/musb-hdrc/usb1/1-1/1-1:1.1/input/input5
generic-usb 0003:0B38:0010.0002: input: USB HID v1.10 Device [HID 0b38:0010] on usb-musb-hdrc-1/input1
root
Password:
Last login: Sun May 27 21:55:28 UTC 2012 on tty1
Linux carrier 3.0.21+ #40 SMP PREEMPT Sun May 27 16:59:27 CDT 2012 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
carrier:~# echo skdjfhnsdkjfshdsummit_bat_notifier_call val=41
summit_smb347 4-0006: summit_fsm_stateTransform:state : suspend(0) -> suspend(0) ; event : EVENT_BATTERY_NTC_NORMAL
kfjshdkjfshdfkjshdfkjsdhfkjsdhfkjsdhfkjshksdjfhskjdhfskjdhfsdkjfhsdkjfh > /dev/fb0
carrier:~# echo skdjfhnsdkjfshdkfjshdkjfshdfkjshdfkjsdhfkjsdhfkjsdhfkjshksdjfhskjdhfskjdhfsdkjfhsdkjfh > /dev/fb1
-bash: echo: write error: No such device
carrier:~# omap-rproc omap-rproc.1: rproc_loader_cont: failed to load ducati-m3.bin
cat /dev/vcs1 > /dumpp.txt

I was trying to get something to come up on the framebuffer, to no avail of course.

The backlight comes on, and it seems like it want to work, but there's nothing.
[Kindle Fire Android Development] sthomas38:
Are you talking about a true Debian dual-boot on our tablet? That could be really awesome :).

Envoyé depuis mon Amazon Kindle Fire avec Tapatalk
[Kindle Fire Android Development] seishuku:
Actually, yes.

It's mostly a matter of having a proper framebuffer console and telling the kernel to use a root instead of using the initrd to setup android.

If we could get a scripted bootloader, one that would give a customizable boot menu, you could easily boot whatever you wanted.
[Kindle Fire Android Development] sthomas38:
And what about it : http://thomaspolasek.blogspot.fr/2012/04/arch-linux-lxde-w-xorg-mouse-keyboard_16.html?m=1 ? :)

Envoyé depuis mon Amazon Kindle Fire avec Tapatalk
[Kindle Fire Android Development] seishuku:
Well, I already got most of that working, chroot environment is easy.

I got the full Linux init going, no android at all... just no display.
[Kindle Fire Android Development] Hashcode:
Display might be tricky, as we are currently using the very latest graphics modules from TI. I'm not sure if you can use those in our current build.

That being said you could send a cat /proc/msg to a file during boot and that might contain your error.
[Kindle Fire Android Development] seishuku:
Well I already have a working fbcon in android, but it seems the display just isn't being enabled in Linux.

I've tried "echo 1 > /sys/devices/omapdss/display0/enabled" to force it on, but nothing.

The back light is already on though...
[Kindle Fire Android Development] BorrowADolla:
I thought EXT2 was for really old linux distros.
[Kindle Fire Android Development] seishuku:
Not really, its just more compatible.

I could have made pretty much anything...
[Kindle Fire Android Development] NiHaoMike:
I read somewhere that SSDs should use EXT4.
[Kindle Fire Android Development] masterchop:
i am really anxios to see this even though is only cmd line.

will the steps to get this going available even for SSH commands?
[Kindle Fire Android Development] seishuku:
I really should hack together a wifi script to get some kind of network connection, would make working on it a little (lot) easier.

The idea here though is to basically have a full linux, to operate exactly like it would on a PC.

With a working framebuffer console, an X.org config can be made and X should work just fine with the touch screen too.

The end result, with just keyboard, should be a full blown linux system.
[Kindle Fire Android Development] Hashcode:
The real question is how long it would take to compile android for.. itself.
[Kindle Fire Android Development] pbailey212:
They can start reproducing them selves, isn't this how terminator started?
[Kindle Fire Android Development] Sblood86:
This is really off topic but Hashcode's comment and pbaileys phone reminded me of a test project Drew (of Team Hydro) did where he chrooted ubuntu onto an LG-LS670 and compiled a kernel for it natively, took just under 3 hours.
[Kindle Fire Android Development] seishuku:
I'm at a bit of a loss here... if I disable surfaceflinger, so I keep my android fb console, then if I disable the display and reenable it, I lose the console.

Also, in my initrd, I can remove everything except ueventd and still keep the console... so something ueventd (init) is doing to enable the console.

In Linux I can play with enabling/disabling the display, but nothing seems to provoke Linux to give me an actual console.
[Kindle Fire Android Development] pbailey212:
On the vm670 legend has it, people have compliled whole roms in 30 minutes, with an optimus v, and Leslie Ann's build server

sent from my Nokia 5110
[Kindle Fire Android Development] seishuku:
Aha! Got it!

http://www.youtube.com/watch?v=PXhnVP3lWLU

For whatever reason sysfs wasn't taking my commands.

Now I can work out some bugs and get X working.

I also switched the USB gadget from android to an Ethernet CDC, so I can SSH via USB while I get wifi working.

Edit-

Sorry about the super blurry video, my phone's camera is having "issues".
[Kindle Fire Android Development] seishuku:
Ok, I've switched to the official Debian armel wheezy distro (basically just formatting my linux partition and untaring the distro), seems to have fixed a lot of problems... One being aptitude not working correctly (seen in the video).

I need to enable some kind of ip forwarding on my local linux install, so I can get a temp internet connection on the kindle via USB gadget ethernet cdc (ssh and http already works).
[Kindle Fire Android Development] anantshri:
looks cool can you provide package which we can also try.

i have been trying to start this work on kindle but looks like you have made good progress and your base could be used to leverage a lot more.

BTW did you had a look at Spark tablet KDE interface pacakge.

i suppose we can mix merge both projects to get a working linux tablet.
[Kindle Fire Android Development] seishuku:
Here's my kernel

http://www.mediafire.com/?sv83fjk213oi7ol

the minimal rootfs (seems to be more up-to-date than the wheezy distro I used)

http://rcn-ee.net/deb/rootfs/squeeze/debian-6.0.4-minimal-armel-2012-05-29.tar.xz

It contains another tar, unpack that tar.xz on your linux system, then adb the armel-rootfs tar to the kindle and untar that to your kindle's linux partition.

and the rc.local that sets up the fbcon and sets and ip addess to the usb cdc gadget

http://www.mediafire.com/?gx46xxb4813n5ob

Now, when you build your boot.img, you should only need to set the cmdline for the root, I have mine on partition 9, so my cmdline is "root=179:9" (9 being the partition).

And installation is basically just copying the rootfs above to the formatted partition, unpack it, and copy the rc.local to the etc directory (ungzipping it first, of course).

That's basically it.

Everything should be able to be done via ADB.

If you haven't repartitioned yet, I would recommend resizing media to be 1GB smaller, and put a new partition after it (partition 13). That way it doesn't disturb the android system much. Mine is pretty custom, so it's not likely to work for 99.99999% of users. :lol:

I have the usb gadget set to use 192.168.5.1, but you can edit rc.local to use whatever you want.

It's also somewhat buggy, it seems I have to force the usb to change modes first (plug in a usb device first, then plug in the pc) to get it to bring up the CDC ECM gadget, but after that you should be able to set an ip to the pc side (usb0) and ssh into the tablet.

Otherwise, you can just plug in a USB keyboard and run the console directly, but I would recommend ssh, since you'll have a network connection there and can set up a iptable nat to get internet access to the kindle... After that getting the wifi working shouldn't be too hard.
[Kindle Fire Android Development] seishuku:
Where's my easy button...

http://youtu.be/LL7yGFuNU0w

Touchscreen needs work though, it crashes X as soon as you touch the screen.