yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] musical_chairs:
No you're not the only person - I would use my phone as a camcorder a lot more if it worked properly, but I've gotten hooked on enough of Jelly Bean features that I just can't handle GB any more.

Hardware video acceleration (at least for video playback) does work, at least mostly, in apps like YouTube and MX Player. I believe we mostly have the correct drivers for the display (not ported forward to the 3.0 kernel of course); hardware accelerated video recording is what is completely missing. Given enough of time and talent it could be fixed, but the likelyhood of anybody investing that kind of time and energy into a legacy phone is pretty low (what do you call those numbers that are infinitely close to zero but not actually zero? That kind of low).
[Droid Incredible Android Development] lukkypuggy:
What can we do to help get camcorder working?
[Droid Incredible Android Development] tiny4579:
Is it really worth it on a 3 year old device? Probably nothing. The hardware is not meant for ICS or greater. Use a software encoding based camcorder and see if it's better or upgrade to a new phone :). If Google had supported the Nexus One then things would be different here.

Ask Evervolv, I'm not sure if they're doing anything for camcorder on qsd8k. When did it last work properly? ICS or JB 4.1 or GB?
[Droid Incredible Android Development] lukkypuggy:
It worked in one of Pons' builds toward the end of October, and for me I can't get a new phone right now so it was just a hope.
[Droid Incredible Android Development] tiny4579:
So 4.1 works. Fully? No choppy camcorder? What if you pull the gallery2.apk from cm10?
[Droid Incredible Android Development] plexiglas81:
I'm using the Gallery2 from the last CM10 build with this ROM. It records but it's very, very choppy... like 1 frame/sec.

(just reporting, I don't use the recording option)
[Droid Incredible Android Development] tekweezle:
I think maybe it works on the CM 7.2/GB 2.3.x based roms but not anything higher.

I don;t think it ever worked on 4.x.x roms but then of those, I only tried yours. 4.1.2 and 4.2.2 varieties
[Droid Incredible Android Development] Kaepernick:
Camcorder worked fine on 7.2. Never tried ICS so I can't say.
[Droid Incredible Android Development] zombolt:
Have you tried any 3rd party camcorder apps?
[Droid Incredible Android Development] Kaepernick:
Camcorder apps are sadly lacking in the store. Most are just shortcuts to the stock app. Camera ICS uses its own camcorder but that one stutters too.

Is there a software encoding camcorder? I looked in the play store and couldn't find anything of note.

For the heck of it, I tried the camera and gallery from CM7.2. I froze the gallery/cam from 4.2. The gallery works. I tried it and it's the old Gallery that I don't like that much. The camera just force closes though. I can't get it to work. I didn't try to install it into system or anything, so maybe that's why. Or it simply doesn't work on 4.2.
[Droid Incredible Android Development] musical_chairs:
The camcorder hasn't ever worked correctly on JB. It was working for a while on ICS but as I recall it had a nasty memory leak and would only record about 30 seconds. (That may have been fixed later on, I don't remember). The best we've got on JB 4.1 or 4.2 is a choppy 640x480 camcorder or a software encoded camcorder. Apps like Camera ICS, DoubleShot, and lgcamera use system video encoding so they all act the same as the 'legacy' ICS/JB camera. VideoCam Illusions is the only software encoding camcorder I know of, and it does work, but you have to set the quality pretty low or it's choppy too.
[Droid Incredible Android Development] zimlokks:
just my two cents but i prefer a low resolution video than no video at all, anyways to have jellybean up and running on the dinc is simply amazing i believe a fix will come but not anytime soon its a trade off but ill take it anyday :), i suggest using tha app mentioned above(i forgot the name) if u really need a camcorder...

Flowed Away From My Samsung GS2 E4GT
[Droid Incredible Android Development] tiny4579:
If you absolutely need working camcorder and for it to work well use gingerbread. If you need 720p video recording, use a sense ROM or CM6.1 (CM 6.1 I found really boring).

Quick Edit:

I uploaded a new build of this ROM.
[Droid Incredible Android Development] tydiamond11:
What would be new in the new build?
[Droid Incredible Android Development] ph1nn:
Just did a full wipe and installed the new 3-22 build... don't know whats changes but I have no Ringtone or Notification sounds.

update: nevermind i rebooted and there they are.
[Droid Incredible Android Development] kramer56:
Just installed the build also, what are the changes tiny?

Also I forgot if we had to install gapps with every build even if we dirty flash or will they be erased when we update. I do it buy do I really need to?
[Droid Incredible Android Development] Pons:
This sounds like a job for the OP.
[Droid Incredible Android Development] kramer56:
Lol thanks pons.

---------- Post added at 09:29 AM ---------- Previous post was at 09:26 AM ----------

There are over 135 pages, I have read all at some point by following these builds but I can't remember much lol. No biggy not like it takes long wasn't sure if it was necessary that all.
[Droid Incredible Android Development] Pons:
Let me rephrase what I said, and give you a hint since I think you missed it:

Read the original post (OP) by tiny. It has both of your questions answered in two separate links on this mystical OP.
[Droid Incredible Android Development] kramer56:
Yeah had I clicked on q&a link like I just did I had my answer less than 30 seconds. Thanks pons. Guess I forgot that link was created by tiny, it's why you guys are so amazing
[Droid Incredible Android Development] Kaepernick:
Notification bar froze last night. Couldn't expand it or anything. Grabbed a logcat before I rebooted.

http://db.tt/XWVoxDHc

Still on 3/09, btw.
[Droid Incredible Android Development] musical_chairs:
I looked through your logcat quickly and didn't see anything that looked too ominous (not that I know what I'm looking for). I had had the status bar freezes a bunch last week and never found anything worthwhile in my logcats either. The problem was obviously related to SystemUI.apk (the status bar is part of that), and killing SystemUI either by applying a different theme or by using terminal commands would get things working again without needing to reboot. Eventually, I cleared data for SystemUI using Titanium Backup (free) and the problem went away.

I also flash the latest builds about as quickly as possible, so if the problem persists after clearing data for SystemUI, try flashing the latest build and clearing data for SystemUI again. Note: it does not work to kill SystemUI or clear its data from Settings/Manage Apps, you have to do it with a third-party app like Titanium.
[Droid Incredible Android Development] Kaepernick:
I'll give it a shot. It just happened again. I'll wait until my download finishes before I mess with it. This time, it happened during a long download and after the screen turned off.

How did you kill SystemUI from the terminal?
[Droid Incredible Android Development] musical_chairs:
Enter these commands in the terminal emulator. It's easier to read in landscape mode.

top

This shows running services, com.android.systemui was at the top of the list using about 25% cpu when the taskbar was frozen. Hit Ctrl-c to quit top - that's vol.down-c for those of you who don't use Hacker's Keyboard. Scroll up and make a note of the PID of com.android.systemui - mine is currently 471. Then, do:

su

...to become root, and finally,

kill 471

...or whatever the PID was of com.android.systemui. It will immediately respawn with a different PID.

This works to kill offending processes not only on Android but on any Linux system.
[Droid Incredible Android Development] tiny4579:
Or another way to kill systemui

kill `pidof com.android.systemui`

So you don't have to lookup the process. Above is a back tick and not a quote. Or use os monitor for task manager like interface and enable root mode.
[Droid Incredible Android Development] Osiris19:
I'm probably totally wrong on this, but do you think cm10.1 on the n7 pulls from the same merges as for your build? Just wondering cause I might put cm10.1 back on my n7.
[Droid Incredible Android Development] zachf714:
Except for his few cherry picks yes
[Droid Incredible Android Development] Osiris19:
Okay. Would it be worth using it as a troubleshoot tool?
[Droid Incredible Android Development] Kaepernick:
Used Titanium to wipe and kill systemui. Nadda. So, I just rebooted. I realized afterward that Watchdog can kill it too.I updated to 3/22 and wiped systemui data. Haven't had the issue yet so far.

Is there a way to remap the Search hardware button to something else? I tried it using system settings and that didn't do anything. Tried editing some keylayout files. Nothing. Tried Button Remapper. Didn't work. Want it to launch my camera (camera zoom fx, not default) since I never use it to search or for anything else, really.

EDIT: Nevermind. Button Remapper worked. Seems I have to long press the button for it to work. Had to set CZFX as default as well.
[Droid Incredible Android Development] hapablap:
Anyone else having an issue with not being able to swipe down for notifications in the latest build? I don't really have time to do a reset right now (I've been dirty flashing the last several nightlies) so I'll just deal with it for the moment unless others are having similar problem.
[Droid Incredible Android Development] tiny4579:
Read the post above you for a possible fix. Also dirty flashing should be fine on cm usually. I didn't see an issue with that either.
[Droid Incredible Android Development] Osiris19:
I don't have a single issue with the newest build.
[Droid Incredible Android Development] Cellulah:
Problem with most recent build. Says it's finding the update package, opening the update package, but then just goes back to recovery - I don't think it ever installs. :confused:
[Droid Incredible Android Development] Pons:
Try comparing the md5.
[Droid Incredible Android Development] Cellulah:
Checked before and just double checked. They are the same.
[Droid Incredible Android Development] kirkers:
Offline voice searching & typing -- how to get it to work?

[

Is this still necessary to make voice search work offline? Or has Tiny tweaked later versions of the ROM so that you can just install the offline voice files he has available in his developer download area?

I just install Tiny's ROM, Tiny's gapps, and Tiny's offline voice file zip files in that order.

Everything is great, EXCEPT whenever I am offline, Google Search or any other programme with voice search or typing capability (including the system keyboard) fails to work. I get "Can't reach Google at the moment". :(

Am I missing something, or is musical_chairs' approach the way it must be done? :confused:
[Droid Incredible Android Development] tiny4579:
You can just flash them but you have to make space before flashing the offline zip . so a reboot into the ROM to free space is needed prior to installing offline files.
[Droid Incredible Android Development] GrimeSyndicate:
Well, does the flash-able keyboard on the OP install to system as well or is that its purpose so that you can flash it after deleting the keyboard in the system folder and thereby still have the native keyboard but now have it installed outside the system folder?
[Droid Incredible Android Development] tiny4579:
The gapps package includes the keyboard. No need to flash it again. If gesture typing works you're good.
[Droid Incredible Android Development] Kaepernick:
Are we able to install it as a regular app? So we can have the stock keyboard and not have it fill up system space?
[Droid Incredible Android Development] tiny4579:
That one isn't installable in /data but you can try this one which took me a few minutes to find:

http://d-h.st/XuS

Here for the full thread:

http://xdaforums.com/showthread.php?t=1964663
[Droid Incredible Android Development] Kaepernick:
Thanks. It seems to work quite well. The swipe part works well too. This is a perfect replacement. We can delete the stock keyboard from system and use this to free up space. If you were to delete the stock keyboard in your next build and add this, would there be any problems?
[Droid Incredible Android Development] tiny4579:
I'm not going to delete the stock keyboard as there'd be no keyboard then but if everyone wants to use this one, I can stick with the AOSP one that doesn't have gesture typing which is also smaller.
[Droid Incredible Android Development] Kaepernick:
So, you can't/won't add it as a data app and get rid of the stock keyboard in system? I don't know if it would work on a fresh install, but I currently have the stock keyboard un installed and am using SwiftKey with no problems. The data/app stock keyboard works well too.

Not a big issue since anyone can uninstall it with Titanium if they want, I suppose. I doubt anyone would mind having the smaller AOSP one and installing the gesture one afterward.

Btw, I just checked out another logcat app, Logcat Extreme. It seems to be quite a bit better than the other apps to me. It saves the logcats into a much easier to read format.

https://play.google.com/store/apps/details?id=scd.lcex
[Droid Incredible Android Development] tekweezle:
i think you need a stock keyboard in case you are trying to resetup your phone after a factory reset. its just impossible to navigate the menus without being able to input. tried to do it without a keyboard in an earlier release and it did not work out too well.

it;s easy enough to remove anything you don;t need afterwards using titanium backup.

if you want to save space, maybe some of the stuff that could be a candidates would be DSP Manager, Google Talk, Gmail, Email, Exchange Services, Picassa uploader, CM File Manager and themes, Talkback(i haven;t figured out what it does) plus live wallpapers if you don;t use any of that stuff. These are just my opinion based on what I have replacements for. whatever works for you is fine. Some people get rid of Trebuchet Launcher right away but I use it.

other than that, I am on 3-22 on one of my Dincs and nothing bad to report.
[Droid Incredible Android Development] tiny4579:
This looks like a possible fix for the status bar issue some are seeing. An FYI, it's not related specifically to this version of CM.

http://review.cyanogenmod.org/#/c/34568/

I'll build tomorrow and hopefully it will be gone for good.
[Droid Incredible Android Development] lukkypuggy:
Finally got an upgrade to RAZR M, now I can let my little bro use this phone. Thanks for the help guys, great work!
[Droid Incredible Android Development] musical_chairs:
It certainly sounds promising:

That's exactly what was happening. It's crazy though that I was seeing this several times a day, and since applying my 'fix', it has happened exactly zero times.

3/22 build has been running great, by the way.
[Droid Incredible Android Development] tiny4579:
Yeah, I couldn't reproduce that issue ever on my phone. I tried to swipe on the status bar up and down repeatedly and it didn't seem to get stuck like it was suggesting may happen.

What's the general consensus on the keyboard? I'm wondering if I should push the AOSP keyboard and make the gesture keyboard optional or stick with what I have now. Gesture typing is a key Android 4.2 feature. Regular CM10.1 on my nexus doesn't need a special keyboard apk in the gapps for gesture typing. Not sure why it's not working out on the incredible.

Also, how do PIE controls sound for the next build? They will be part of the build but it will be off by default. See below.

Edit: It seems CM doesn't see the point of PIE or expanded desktop status bar visible options on devices with hardware keys. That can be overridden here by enabling the navbar and disabling the hardware keys which can only be done through an XML edit which I won't have by default. I kind of understand CM's stance on that as hardware keys and PIE will get messy together being both on on some devices.

Either way, the change mentioned above that should fix the status bar issue should be worth the upgrade alone.
[Droid Incredible Android Development] omniatic:
Since installing the 3/22 build, I haven't had a status bar freeze-up. A couple on 3/09 and once on 3/15, but none yet. As for the keyboard, which ever takes up less space would be fine with me. I have Swype installed, and don't use gesture typing, so it makes no difference to me.

Guess I don't know enough about the PIE launcher to throw out an opinion on that one. Don't know if I'm missing something, but it sounds like more trouble than it's worth. Should look into it and see.

At this point, 3/22 is running fine for me, no issues to gripe about. No reboots, no Bluetooth trouble, no lockups.

So...you decide what stays and what doesn't. I'm fine with that. If something is broken I'll let you know.

Thanks,

From my Incredible
[Droid Incredible Android Development] tiny4579:
OK then. For now I won't try to add PIE in. It should be a matter of disabling hardware keys and enabling the nav bar which should not be default in my opinion on the Incredible. I am planning to try to get the AOSP keyboard working with gesture typing (before the gapps one was the non-AOSP keyboard without those extra long press shortcuts on the keys. This one is slightly smaller which is good. If someone needs to reclaim space badly for the offline voice they can install another keyboard to /data and delete the stock one.
[Droid Incredible Android Development] tiny4579:
Use the built in one, incredikernel.
[Droid Incredible Android Development] jlvlawrence:
Bluetooth is working for me. Pairs nicely with my Sony stereo in my car.
[Droid Incredible Android Development] nathansnyder:
This update takes care of the widgets issue and is faster than ever! Thanks Tiny!
[Droid Incredible Android Development] jacobsensei:
Thanks for the updates, Tiny.

Running Great.

Merry Christmas to you and yours.

Happy Holidays everyone.

And To All A Good Night.

Sent from my Transformer
[Droid Incredible Android Development] kramer56:
Anyone using Chrome on the pc? If so can they get on the xda site? Mine keeps saying it's malicious spyware and wont let me on that site
[Droid Incredible Android Development] ffuser1:
works fine in both firefox and latest chrome
[Droid Incredible Android Development] Sir Lancelot:
Must be doing something wrong with GAPPS

Trying to transition from cm10 to cm10.1

Flashing ROM and Ext4 mod go just fine as a dirty install w/o wiping cache or anything. Boot into 10.1 and all is speedy and nice but now I need to load GAPPS

Flashing the GApps and the Start Up Wizard FC loops so I can't get any further.:silly:

Do I need to delete the start up wizard apk from the zip? Or is this indicitive of other GApps issues I'll run into once past with wizard?
[Droid Incredible Android Development] nathansnyder:
Are you using the Gapps from this thread, or an old one? That may be the issue.
[Droid Incredible Android Development] Sir Lancelot:
Yep. This thread.
[Droid Incredible Android Development] qrko:
Solved, to delete.
[Droid Incredible Android Development] musical_chairs:
That is how it will act if flashing gapps from 4.1 on a 4.2 ROM, I've never seen it when using the correct gapps. Make sure your gapps has 42 in the title (the current one for this ROM is gapps-jb42-20121212-signed-inc.zip) .

But the setup wizard shouldn't have to run at all if you're dirty flashing; the phone is already set up. You could try deleting the setup wizard apk from the gapps zip, or you coud delete it from /system/app/ after flashing using the file manager in TWRP (you have to mount system first to do that). Or, if by chance something changed on the latest build of the ROM that makes this more difficult, you could try restoring a nandroid of CM10, flashing one of the older CM10.1 build with gapps, and then, if that gets past the setup wizard, flash the latest ROM build.
[Droid Incredible Android Development] tiny4579:
Hey all,

This was posted by Vernox in the Evervolv thread. Can someone test this out on this ROM?

Hey Tiny seems looks like something is wrong with the phone.apk. When in a phone call if the call ends without hanging up the process com.android.phone pops up.If you end the call then everything is O.K. So bluetooth works fine. Only thing that hangs or causes an error is the other party hanging up or letting the phone call end without pressing the disconnect button.
[Droid Incredible Android Development] zimlokks:
guys format system before flashing anything remember gapps has a backup script so format manually

Sent from my rooted GameBoy Color
[Droid Incredible Android Development] musical_chairs:
No it works fine here. I called myself several times from my landline and hung up on myself, (what a jerk!) and my dinc said "call ended" and returned me to call history, no toasts or FC's, all behaved properly. I tried it with screen off (phone to my ear) and screen on. No problems here.
[Droid Incredible Android Development] tiny4579:
Cool, thanks for the feedback!
[Droid Incredible Android Development] Vernox701:
Same here just finished testing. Phone.apk behaves properly. Bluetooth works music plays pauses for phone calls and resumes without any hiccups
[Droid Incredible Android Development] Sir Lancelot:
I checked again and sure enough -- gaols I was using was 4.1. Now on 4.2 with no problems.

Thanks a heap!
[Droid Incredible Android Development] neotericpiguy:
Does anyone use Airdroid with this 10.1 build? I granted airdroid root permission to grab screenshots, but when sending an SMS from the web client they fail. Airdroid asks for the appropriate permissions to send SMS via airdroid, but I never had to do that in TINY's CM10. I've looked around and I can't find anything about this being a specific 4.2.1 issue but I really missed the ability to respond to my text from my computer.
[Droid Incredible Android Development] zimlokks:
thia is to every single person who spends time build/fuxing/improving our Inc's nd everyone who has collaborated/used/thanked/helped i wish you all happy holidays(im very much late)

Sent from my rooted GameBoy Color
[Droid Incredible Android Development] 123421342:
Thanks for your hard work tiny! Im going to backup nandroid and try this tonight. Will doing a batch restore with titanium cause any problems?
[Droid Incredible Android Development] Kaepernick:
I haven't had a notification bar freeze up since updating to 3/22 so far. Glad there's a possible fix, though.

As for PIE, is it just a software replacement for the hardware keys (home, menu, etc.)? I don't really see why we would need it, unless something disables the hardware keys.
[Droid Incredible Android Development] tiny4579:
Yeah, PIE is just gesture/swipe style nav keys. It is nice because you can swipe from the sides or top/bottom but I've had issues toggling them and it seems to be a bit picky. They're great for one handed operation on my Galaxy Nexus. I don't see a point on the Inc.

Anyone have adb broken on the 3/22 build? I'm hoping it's just me. Nothing changed on my end to cause it.
[Droid Incredible Android Development] GnatGoSplat:
Yep, ADB is still broken for me on the 3/22 build, but it was broken for me on 3/15 as well. I'm the guy with the f'd up NAND chip so /data and /cache are on SDCARD so maybe things are different for me.

Any possibility you could incorporate trackball wake? Albinoman's 4.2 ROM had that and I thought it was pretty cool.
[Droid Incredible Android Development] zachf714:
Let me find the pac commit for pie they enabled it in cm frameworks so you should just be able to pick it
[Droid Incredible Android Development] tiny4579:
Its already merged. What do you mean?
[Droid Incredible Android Development] tiny4579:
Are you sure? I've never heard anyone mention it and the old edit methods of changing the keylayout files don't seem to work after gingerbread.