Android/Linux for CDMA Touch Pro 2 - Page 149

slow4g63 · #**1481** (**permalink**) 03-17-2010, 11:19 PM

did I add the line correctly??

jeep447 · #**1482** (**permalink**) 03-17-2010, 11:21 PM

Sorry man just saw your post...yeah thats how I have it

jeep447 · #**1483** (**permalink**) 03-17-2010, 11:27 PM

Quote:

Originally Posted by cflynt

Not crazy, that is something that works, but the mic doesn't so not really usable, but is progress in the least!

Ok scratch that man...I'm sorry my wife is a tool...she said she could here me but I just tried to double check...nothing comin from my end...I hope I didnt stir up a bunch of crap...My bad!!! Soooorrrrryyyy!

**JDM_SOHC** · #**1484** (**permalink**) 03-17-2010, 11:38 PM

This development was movin fast those first couple days, teasin us huh... =)

**cflynt** · #**1485** (**permalink**) 03-17-2010, 11:51 PM

As far as where to put the switches, you can put them anywhere in your cmdline as long as it ISN'T the last switch. The switch "physkeyboard=" has to be your last switch. I added this to the FAQ.

And ya, unfortunately the MIC for speakerphone is not currently working!

Boominsvx · #**1486** (**permalink**) 03-18-2010, 12:47 AM

Quote:

Originally Posted by icevapor

Hey all, I noticed this on another forum and didn't see it here. If you plug in your phone (via wall or usb) before running booting to android, your phone will charge.

I started with 6 bars power (in settings-power) and played w/ my phone for like 1.5hrs and when I came back to wm I still had six bars. So yeah..... try it.

I dont know if you can unplug it after your in android and plug it back in later... try that too.

I am going to not mess w/ it and leave it, see if it gains bars. I know that a "green bar" isn't a really good unit of measurement, but who cares if I get more bars :P..

Quote:

Originally Posted by icevapor

So charging does work if you have the charger plugged in before you boot up android. I gained in bars.in wm after letting it charge in android.

I don't know if you can unplug and replug to charge... someone test it out.

Quote:

Originally Posted by newedeh

The newest Kernel seems to work with charging.

Quote:

Originally Posted by jeep447

Ok i might be crazy but I just added the command line switch for speakerphone and with this kernal my speakerphone works!!! I can hear the person on the other line and she could hear me all through the speaker! Anyone else got this or did i miss something? thanks

The chargering seems to be selective phones. Some people can, others can not. I pointed this out maybe 15 or 20 pages back now, and even tried to ask the irc chat room why mine charges when they all report "Not charging". If you got one that does, your a lucky one. They say it's just something of a form of trickle charge due to the power wattage in the usb cable.
The speakerphone works with the switch placed further back in the command line (Before the keyboard command), but neither of the microphones will trigger when speaker is toggled on. For these two reasons, sound and charging are NOT working... atleast not for everyone. Hope that clears up some of the confusion.

Sound only works in latest kernel. Charging has been working for many kernels now. I noticed it with mine about 4 or 5 kernels ago.

**cflynt** · #**1487** (**permalink**) 03-18-2010, 02:15 AM

For those that have been waiting on the final commit for the Touchscreen Double Tap issue, it has finally been posted, thanks MrPippy for posting it. Here is a link to the package:

http://zimages.googlecode.com/svn/au...318_061343.tar

Just delete your zImage and modules from your storage card and put the new ones in place. If you were running the test build, this probably won't give you anything more, but at least it is in the autobuild now.

Boominsvx · #**1488** (**permalink**) 03-18-2010, 03:03 AM

Tested and commented. At least with this package I can finally get back to the being able to download. Works flawlessly. Still charging for me.

mrrogers1 · #**1489** (**permalink**) 03-18-2010, 05:48 AM

Quote:

Originally Posted by cflynt

For those that have been waiting on the final commit for the Touchscreen Double Tap issue, it has finally been posted, thanks MrPippy for posting it. Here is a link to the package:

http://zimages.googlecode.com/svn/au...318_061343.tar

Just delete your zImage and modules from your storage card and put the new ones in place. If you were running the test build, this probably won't give you anything more, but at least it is in the autobuild now.

Thanks for posting this, I just happened to pop in to see if there were any updates in the first post. Do you know, is MrPippy going to be updating at least the first thread when a fix or update like this is made? I think we are used to see the actual thread title updated when there is one but I know that hasn't been done since this great ride began.

Boominsvx · #**1490** (**permalink**) 03-18-2010, 06:01 AM

It's not JUST him that's posting the kernels. Mr. Pippy is working on the specific rootfs that we use for cdma, but this update does not change anything in that file. No changes have been made to the rootfs since this thread was made. It's all in the kernel. If you follow the long directions in the first post, you'll have this version with the fix inside it. If you download "all in one" cabs, you'll have to wait until they are updated with it. If you want to update them manually, download the latest zimage from HERE, extract it to your desktop and change the name of the zimage to file so it's just called "zimage" without the quotes. Leaving that folder open, plug i your phone and go to your storage card. When you find the file that conatins a "zimage" and a "modules.wholebunchofnumbershere", delete both of those off the card and replace them with the ones you extract and renamed. Hope that helps people understand the upgrade process a little better.