yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] tiny4579:
Only reason to change radio is better network stability. Sometimes you might see better signal. Sometimes people say it gets worse. However there are outside factors that affect signal strength.

Its my kernel with the ROMs. Also see cm 10 thread.
[Droid Incredible Android Development] drizzt5:
Hey,

I've uploaded the error for when I try to build. Do you know why this is happening?

Thanks
[Droid Incredible Android Development] mjliteman:
Happening for me too. I'll get a voicemail but the notification won't come on until a reboot and then won't go away after hearing the message until I force stop the phone app.

By the way, on an unrelated matter, with wake with volume rocker I was just curious if there was a way to separate waking with VOL Down and sleeping with VOL Up (or vice versa) or something like that. I think it would be incredibly convenient but was wondering if anyone else thought the same or if it was even possible.

Thanks again for all the support of these old Dincs!
[Droid Incredible Android Development] dacmcbibs:
aw man..... another RTFM moment. thanks for pointing me in a direction. Turns out that i accidentally flashed a non-Tiny gapps.

Oddly, reflashing just the gapps left the keyboard force closing like it was going out of style... so i reflashed the rom and the gapps and i'm back in business.. THANKS!
[Droid Incredible Android Development] tiny4579:
Yeah m cm reverted a change within the last two weeks and a companion change want reverted on the EV side. I haven't been publishing my cherry picks since most people don't build the ROM and until recently cherry picks weren't needed for 10.1.
[Droid Incredible Android Development] Kaepernick:
Well, I changed the number of columns on my home screen from 6 back to 4. Checked the live walls it wouldn't let me download before and it let me download and install. This one made me scratch my head a bit but at least they work now.
[Droid Incredible Android Development] drizzt5:
Could you merge the changes, please?
[Droid Incredible Android Development] tiny4579:
No. Its not my repo and I want to avoid another fork for one change. What I can do is add the cherry-pick list to the device repo similar to how the local manifest has a copy there. Or I can add it to the readme on the inc repo.
[Droid Incredible Android Development] ohredwood:
I just noticed that too, not sure when it started but the other day I had a call come in while I was sleeping, missed call, no big deal. So, that day, I rebooted my phone and when it came up, message indicator came up. I just had a call a few minutes ago, and was waiting for the message indicator to come up, nothing. So I rebooted the phone and sure enough, there is a message. Now that I've played it, indicator won't go away, unless I reboot phone, again.

Something I don't have setup correctly, I haven't done anything different than what I normally do for the last several Pons/Tiny's roms I've installed.
[Droid Incredible Android Development] zombolt:
My stock battery quit charging. Red Light would blink while turned off indefinitely so I bought 3x 1500 batteries with charger off ebay for $12. I cannot get past 62% with battery in phone. Any ideas?
[Droid Incredible Android Development] omniatic:
Did you fully charge them with a wall charger, or in the phone? Also, maybe your phone charger is bad.

...sorry...I was on the phone...
[Droid Incredible Android Development] zombolt:
Since the batteries charge in both the external wall charger and a DINC with a non functioning screen from water damage I can only assume something broke inside the phone itself. Hopefully other components in the device will not break.
[Droid Incredible Android Development] omniatic:
After 3 or 4 reboots a day, some soft, some hard, I noticed a pattern. They all happened after opening several apps in a short period of time. Always seemed to be low on free ram, too. I disabled zram and the free ram levels are much better, and no reboots.

So, does zram work? Seems to me it did the opposite of what it's supposed to. Don't know if anyone else reported any issues with it.

...sorry...I was on the phone...
[Droid Incredible Android Development] Kaepernick:
Anyone having trouble with Titanium Backup? I try to do a batch backup and part way through, it just black screens and restarts. Sometimes it causes the phone to reboot. I don't know if it's a superuser issue or what. I tried with the stock superuser and with Koush's from the store. Should I try SuperSU?
[Droid Incredible Android Development] musical_chairs:
I never used zram, I thought it sounded kind of experimental (and like more trouble than it would be worth.)

Titanium did the same thing for me too, I figured it was a flukey app in there somewhere that was making it crash, so I backed each app up individually and it was fine. I didn't look into it deeper.
[Droid Incredible Android Development] Osiris19:
I have to say, this is probably the most stable build of CM10.1 for the dinc. For everything I use it for, it works perfectly. I only get alight lag now and then, otherwise its pretty quick. Thanks tiny. Glad I can clutch onto this phone for another year or two.
[Droid Incredible Android Development] tiny4579:
I'm not chasing and can't chase down reboot issues without a last_kmsg. I remember issues before attributed to zram so it may be best to disable it if you have it on and have stability issues.
[Droid Incredible Android Development] rick311:
This is a great ROM. But is there anything I can do to improve battery life? It seems to drain super fast!

Note: this phone is not my daily driver and suits on my coffee table all day in airplane mode with WiFi turned on. This morning it was at 96% and now it's at 40%
[Droid Incredible Android Development] drizzt5:
If you could add the cherry picks to the local manifest that would be awesome.
[Droid Incredible Android Development] sweeds:
I get system FC's on reboot. Tried clearing cache/dalvik/fix permissions. Warning still appears. I can press 'Wait' and it doesn't seem to have a major effect, but still seems sketchy. Suggestions?
[Droid Incredible Android Development] tiny4579:
Just wait. Are you using a theme? And which build?
[Droid Incredible Android Development] Kaepernick:
I forget. How do we go about getting last_kmsg?
[Droid Incredible Android Development] zimlokks:
using adb: adb pull /proc/last_kmsg or manually with a root enabled file explorer :)

Flowed Away From My Samsung GS2 E4GT
[Droid Incredible Android Development] tekweezle:
Just my observations-

For me, I notice that my battery meter depletes faster when on 3g and out and about doing stuff. On wifi, seems to deplete at a slower pace. I think that's generally accepted that the 3g radio takes some power to run and is less efficient than the wifi.

On airplane mode, i usually get 2-3 days on stand by using 3500 mah batteries .

However lately I have noticed my phone depleting more quickly overnight since loading roms from February onward. I wonder if something changed with regards to how the wifi adapter handles sleep mode. I had always set it to wifi on always to sleep because I don't want to use 3g. Lately, i notice when I bring my phone out of sleep, it's disconnected from my router and on 3g and takes a few seconds to reconnect.

I never noticed before recently that there was a setting for wifi optimized when battery too. Is that a new feature or has it always been there?

Sent from a HTC Droid Incredible running CM 10.1

---------- Post added at 01:22 AM ---------- Previous post was at 01:14 AM ----------

The dinc does have a limited amount of RAM-I think it's 410mb. have you tried removing some of the system programs that you might not be using? Like Google Talk, Dsp Manager, Picassa uploaded, ect.... . For some reason random programs seem to get cached into memory. Considering Facebook and Amazon app store totals about 100mb by themselves, every little bit you can save could help.

Sent from a HTC Droid Incredible running CM 10.1
[Droid Incredible Android Development] zachf714:
The tasker betas from their websites help with battery on all Roms if you know how to set it up .. Like I have mine to disable WiFi if I not connected to my home network for 5min :) it really helps for those that get bad battery
[Droid Incredible Android Development] tiny4579:
I didn't do quite that but I updated the README.md in device/htc/inc so you can see the list.
[Droid Incredible Android Development] tiny4579:
In case anyone was wondering, here's a simple tutorial for tasker.

http://tasker.wikidot.com/turnonwifiathome
[Droid Incredible Android Development] Shano56:
If you have WiFi set to always on when screen off, either set it to turn off when screen is off, or just turn WiFi off when you are done.

A new battery might help too. Or you might have a wake lock keeping it up all night
[Droid Incredible Android Development] tiny4579:
New build is up!

No new cherry picks or changes I made to what's being built but the volume rocker wake setting is back.
[Droid Incredible Android Development] kramer56:
I just installed it with gapps still from 307 right?. Anyway how is the 4.2.2 going so far?
[Droid Incredible Android Development] omniatic:
Works for me.

Thanks Tiny.

...sorry...I was on the phone...
[Droid Incredible Android Development] musical_chairs:
The notification bar froze up on me again, this time I was on the system theme. (I didn't even have any other themes installed). I ended up downloading a theme from the Play Store and applying it, and, just like before, that caused the notification bar to stop and restart, which got it going again (without rebooting). I'm at 71 hours uptime (love seeing how long I can go without rebooting - and yes, this is not on the latest build but on 0309), and it has been running flawlessly except for this one glitch.

Admittedly, I have been doing some unconventional things with my phone desktop (as in, one completely empty homescreen and a unity-style side launcher bar thingy - whatever it's called), but the notification bar behavior is exactly like I've seen before (it started with Pons's build IIRC), and I had time to grab a logcat this time, sooo,.....

logcat.txt was grabbed when the notification bar was frozen. CPU usage seemed pretty high too, like something was chewing away at it and getting nothing done. logcat2.txt was grabbed a few minutes later, when I tried to force stop a few system processes in hopes of reviving the notification bar (this was unsuccessful). Finally, I downloaded a theme, applied it, (notification bar now working), then reapplied the system theme. The logs are long and boring, and I didn't see anything that stood out, but what do I know...
[Droid Incredible Android Development] zachf714:
Are you using TSF shell .. That may be the problem if so it seems to be s ram and CPU hog from my experiences
[Droid Incredible Android Development] musical_chairs:
No not TSF shell - Nova Launcher (one empty homescreen, no dock), Glovebox, and Device Info live wallpaper. Pretty cool, actually. I did try Unity Launcher too, but Glovebox is nicer IMO.
[Droid Incredible Android Development] musical_chairs:
I had the notification bar freeze again on the newest build. I still didn't see anything in my logcat, but being a Linux guy I opened the terminal and ran 'top'. It showed that com.android.systemui was consuming about 35% CPU. So (Linux guy, remember) I ran 'su' (to become root) then 'kill #####' (the PID number of com.android.systemui as reported by top) and bingo - notification bar dies, then restarts and all is well. I guess since systemui isn't actually dying or ceasing to respond, nothing shows in logcat until you kill it. At any rate, something is definitely amiss with systemui, that sometimes it spins or blocks or whatever.

It seems to have been triggered by either toggling wifi or clearing notifications. Now if I can just figure out how to reproduce it reliably, maybe that will actually be helpful information...
[Droid Incredible Android Development] jacobsensei:
Yeah, had this too, trying to clear notifications.

Everything still works, just no drop down.

Changing themes crashes the SysUI and resets it, then it works again.

Sent from my ADR6300
[Droid Incredible Android Development] zachf714:
Can you pull a copy of your system ui.apk ... A factory reset may help
[Droid Incredible Android Development] tiny4579:
How do you think that will help? Seems to be a weird random issue maybe on goggles side. See below example.

https://vzwsupport.jive-mobile.com/#jive-discussion?content=/api/core/v2/discussions/781299

A factory reset tends to only mask problem that existed unless the issue was caused by the user.
[Droid Incredible Android Development] kirkers:
Silencing the volume rocker

Thanks for that, Tiny! My power button is getting ominously wiggly-wobbly, so I want to minimise touching it.

With a screen off app, I can turn off the screen by touching the app icon on the home screen.

With your new 2013-03-15 ROM, I can get the screen back with the rocker volume, once I make the change in System Settings

(under Display --> Wakeup Options section --> Volume Rocker Wake)

Now, the last bit for me will be SILENCING the volume rocker, the sound of which I do not like on general principles and will tolerate only so long as the rocker is not used for other purposes, particularly turning the screen back on.

So far as I know, there is no System Setting for silencing the rocker, and no app that serves as a front end for the process.

I managed to do it manually in my old stock rooted Gingerbread ROM by physically changing the file names of all the volume audio files (volume-1.mp3, volume-2.mp3, etc) located in <root> /system/media/audio/ui/

In your ROM, I find at this location only two OGG files named "media_volume" and "VolumeIncremental". Neither of these performs the sound when the volume rocker is touched. A search of literally everything for files containing 'vol" in the name produced no useful results.

Would you kindly let me (and others reading this) know where to find the correct files so they can be turned off? :fingers-crossed:

Thanks again for your wonderful work on the old DINC! You definitely got me out of jail with my INCREDIBLY slow and misbehaving rooted stock GB ROM! :highfive:
[Droid Incredible Android Development] musical_chairs:
Maybe I'm crazy but I'd rather have it freeze every few minutes (and maybe figure out what is going on) than reset it and make it go away. And my systemui.apk should be the same one as comes with the ROM by default. It has happened on several builds now, which means systemui.apk has been wiped and replaced several times. Plus, now that I've found two different ways of working around it without even rebooting, I'm not too worried.

And now it will probably quit happening and I'll never know what was going on...

Another thought, I just wiped data for SystemUI (in Titanium, you can't wipe data for that in Manage Apps) and it reset my wallpaper to default. So it could be related to live wallpapers too I guess, I had been playing with those extensively. I'll see what happens with a static picture and freshly-wiped systemui data.

---------- Post added at 07:10 AM ---------- Previous post was at 07:06 AM ----------

I noticed that when I had the lockscren disabled, the volume rocker would often beep when waking the phone. It doesn't do it at the lockscreen.
[Droid Incredible Android Development] tiny4579:
Have you tried unchecking volume adjustment sound under sound settings?
[Droid Incredible Android Development] Shano56:
How widespread is this issue? Sure it may mask it but the thing is these builds are so hacky and not supported by the cm team, its only really supported by tiny right now, so if a wipe fixes it u should just go with it
[Droid Incredible Android Development] Kaepernick:
He's saying that a factory reset is just a temporary solution. It'll just keep happening. If the problem persists and it isn't caused by the user, he wants to find the root cause.
[Droid Incredible Android Development] tiny4579:
Both are good points. True that a wipe may help clear the issue but it's good to find the actual cause which wiping may fix without determining the root cause.

Considering I've heard about this issue rarely (after it was reported here first) on other devices, I'd say it's a very rare issue so it may just be best for musical_chairs to do a wipe.
[Droid Incredible Android Development] Osiris19:
Tiny, what did you do to this build? It's like you gave it crack. It's BLAZING fast. Animations are instant (.5x) and there's no lag right now. Hopefully it'll stay like this after it settles.
[Droid Incredible Android Development] GnatGoSplat:
This ROM is working wonderfully for me. All games work great and without lag. Doesn't the HD2 and Incredible share the same CPU+GPU? My HD2 with AOSP JB and CM10 both crashes on some games and is so laggy as to be unplayable on others - and these are the same games that work flawlessly on this ROM. Tiny, maybe you should help those guys out because this experience on the DInc is what the HD2 needs.

One issue I have, but haven't seen anyone else mention is with the 3/15 build, my notification sound volume is always at max even when the ringtone/notification slider shows otherwise. Changing it doesn't reduce the notification volume. If I check the box to unlink notification from ringtone, the individual notification volume control has no effect on the volume, it's always full blast (except in the mute position).

Trackball wake would also be nice.
[Droid Incredible Android Development] musical_chairs:
Well at first there were at least four of us reporting this issue, then suddenly it was just me, which I found rather odd... At any rate, it hasn't happened since I switched back to static wallpaper and wiped data for SystemUI in Titanium, and that was almost 48 hours ago. I'm gonna put live wallpaper back on and if it doesn't happen in another day or so, I'll figure that wiping data for SystemUI must have fixed it.
[Droid Incredible Android Development] ph1nn:
The 3-15 build is great, but anyone know what's up with the phone touchscreen being completely unresponsive when plugged into USB? As soon as I pull it out I can use it again.
[Droid Incredible Android Development] tiny4579:
Can you get a logcat and dmesg output if possible? Instead of sending dmesg output to a txt file you could copy /proc/kmsg to the sdcard and upload or post it.
[Droid Incredible Android Development] mhejek:
I got it too:D
[Droid Incredible Android Development] tiny4579:
Did you see my response? Me too only helps gauge how widespread an issue is and doesn't help diagnose the cause. Logs please.
[Droid Incredible Android Development] mjliteman:
I've been searching for a solution to this far and wide. There are tons of people having this problem (not all on this ROM) but just as many who are not and no one really seems to know why. I talked to VW tech support for an hour last night just to make sure it wasn't something on their end. They did everything they could, short of a hard reset, and even updated my voicemail on their end. The VW FAQ says there is an option in the carrier voicemail settings to turn the indicator on/off (call VM, hit 4, then option 1), but it doesn't even give me an option 1, just begins with option 2.

What's interesting is the tech would call and leave a VM (no indicator would show up), then would try to call the phone again, but it would go straight to VM as if the phone was still in use. So to test that, after the tech left a new VM, I force stopped the phone app and then the tech called back and was able to ring the phone normally. So they think it was something definitely on the phone's end. And it seems to make sense because when the phone is rebooted, the phone app would be closed down and started clean when the phone boots back up. It's just weird that it's only the VM indicator, all other indicators are working fine (missed calls, SMS).

It's as if the phone app is preventing the notification from coming through and preventing it from releasing after listening to the VM unless it's force closed or phone rebooted.

I really don't think it's something with the ROM but maybe the underlying CM/Jelly Bean sources, some people seem to think it might be a problem with 4.2. I may just revert to an older build to test it out because I don't remember having this issue on an older version. And I don't use GV or any other voicemail app, just the plain VW voicemail so it's my only way to know when there's a new VM. Still no solution that I've found unfortunately.
[Droid Incredible Android Development] tiny4579:
It could be the way jellybean has been ported to the dinc. My voicemail indicator works fine on my galaxy nexus. If its an issue on the inc its deeper than cm specific and probably device tree or framework related. Since an official evervolv maintainer doesn't have an xda thread the best way to reach them is probably preludedrew on twitter to see if they've heard of it. Or another thing you can do is test on evervolv to see if it happens first.
[Droid Incredible Android Development] tiny4579:
No issues here.
[Droid Incredible Android Development] GnatGoSplat:
Would either of you happen to be using aftermarket chargers? This is a pretty common problem with capacitive touchscreens and cheap aftermarket chargers.

No touch issues for me with the OEM charger.
[Droid Incredible Android Development] ph1nn:
It is an aftermarket cheepo microUSB cable yea... think that's it? I'll try and logcat. (i'll have to logcat from the computer via adb and debugging mode i think because the phone is unresponsive when it occurs)

It's not everytime, occasionally it does it though. It's happened with my dinc2 too on AOSP roms.
[Droid Incredible Android Development] lukkypuggy:
Is there gonna be anything new with the camera in the next month or two? Camcorder?

I'm torn between this ROM and stock, they both are smooth and very fast, but stock has everything working but cm10.1 has all the features!
[Droid Incredible Android Development] zombolt:
on my device, the stock roms are more unstable than the unofficial cm10's. riddled with force closes and acore errors. can't believe htc would release such shoddy software to tha masses. glad this device gets talented developers keeping it relevant!
[Droid Incredible Android Development] GnatGoSplat:
A cheap cable might do it too, but I was thinking of the charger that plugs into the wall. The touchscreen on most devices won't work when plugged into cheap chargers.
[Droid Incredible Android Development] kirkers:
Volume Rocker silencer -- Tiny to the rescue again!

Oh, I see it now. The explanation was truncated on my little DINC screen in portrait mode. In landscape, I get to read all the text and of course it is exactly what I want! If this is a special feature of your ROM, I thank you profusely for including it! :D
[Droid Incredible Android Development] tiny4579:
This is cm's feature and not mine.
[Droid Incredible Android Development] tekweezle:
for me Camera is still working fine using older version of Gallery version 40000(versus 40001). Camcorder doesn;t save files in that version though.

I am wondering if hardware video acceleration will ever make it into this ROM. i believe it;s not working. I realize that I may be the only person out there affected by this and the answer may never be available(hardware driver doesn;t exist or not ported).

other than that and the persistent voicemail indicator issue, everything works well.
[Droid Incredible Android Development] plexiglas81:
Is that the Gallery from the CM10 or CM9 ROM?
[Droid Incredible Android Development] tekweezle:
i believe it;s from CM 10.

if you want to try it, I have it as a Titanium Backup file. I had to give it a support extension to upload to this forum.

after downloading to your phone, get rid of the .7z extension so the extension is .TiBkp and import into Titanium Backup.
[Droid Incredible Android Development] plexiglas81:
Thanks. I ended up just ripping it out of the CM10 rom and sideloaded it since I don't use Titanium. I was disabling 10.1 Gallery because I didn't care for the lockscreen camera and was using CameraICS and QuickPic to replace Gallery functionality. File this under "why didn't I think of that?"