yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] nokiabolt:
Your ROM works amazing! My old Inc is almost as snappy as my Maxx! Plus faster than my Droid 3 with official cm10.1! Great work! I wish I stuck this phone out another year! I still flash your new builds to it, plus great having FM radio! This phone is brand new now! The latest build fixed the camera artifacts too! Sorry I'm just excited

Sent from my DROID RAZR MAXX HD
[Droid Incredible Android Development] kramer56:
I had to go back to 4/16, I couldn't stand when I needed to use laptop or tethering I had to reboot phone to get it to work. It just kept saying it was turning on but never would until i rebooted so i reverted back one.
[Droid Incredible Android Development] NYC Coyote:
I'm about to try this out again after a long time on using Pons 7.2 as a daily driver (I keep reading this is ready for that) because of starting a new job and the idea of having Google Now giving me up to date traffic to get to the job is just too appealing....

Is there one build that is more stable than another right now (I keep reading something about a kernel issue.. as well as some reverting back to 4/16)
[Droid Incredible Android Development] kramer56:
Tether was my only issue and I mean only. I been using this rom as daily driver for along time. I say do it, you won't be disappointed
[Droid Incredible Android Development] tydiamond11:
Just plain WiFi not turning on too! It does the same thing.
[Droid Incredible Android Development] kramer56:
4/16 is pretty much flawless for me for what I use regularly. Some games lag a little but I like the rom
[Droid Incredible Android Development] zachf714:
I still don't see how you guys are having wpa_supplicant problems I dont on my rom or this ( I have this on my second testing inc )
[Droid Incredible Android Development] tydiamond11:
Why do I not send a log file, I will do it today latter "
[Droid Incredible Android Development] Flagmax:
I also had a problem with Wifi not turning on. After rebooting it worked so I did not get the logcat.

Another issue I got is with adb not finding my phone.

E/UsbDebuggingManager( 354): java.io.IOException: No such file or directory
E/UsbDebuggingManager( 354):	at android.net.LocalSocketImpl.connectLocal(Native Method)
E/UsbDebuggingManager( 354):	at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
E/UsbDebuggingManager( 354):	at android.net.LocalSocket.connect(LocalSocket.java:108)
E/UsbDebuggingManager( 354):	at com.android.server.usb.UsbDebuggingManager.listenToSocket(UsbDebuggingManager.java:79)
E/UsbDebuggingManager( 354):	at com.android.server.usb.UsbDebuggingManager.run(UsbDebuggingManager.java:115)
E/UsbDebuggingManager( 354):	at java.lang.Thread.run(Thread.java:856)
E/UsbDebuggingManager( 354): Communication error:
E/UsbDebuggingManager( 354): java.io.IOException: No such file or directory
E/UsbDebuggingManager( 354):	at android.net.LocalSocketImpl.connectLocal(Native Method)
E/UsbDebuggingManager( 354):	at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
E/UsbDebuggingManager( 354):	at android.net.LocalSocket.connect(LocalSocket.java:108)
E/UsbDebuggingManager( 354):	at com.android.server.usb.UsbDebuggingManager.listenToSocket(UsbDebuggingManager.java:79)
E/UsbDebuggingManager( 354):	at com.android.server.usb.UsbDebuggingManager.run(UsbDebuggingManager.java:115)
E/UsbDebuggingManager( 354):	at java.lang.Thread.run(Thread.java:856)
[Droid Incredible Android Development] mh0520:
Here's a logcat on the WiFi issue. Seems something is unable to start running that needs to. I'm far from an expert on any of this though. Hopefully this is helpful.
[Droid Incredible Android Development] NYC Coyote:
So if I NEED WiFi tether and hell.. WiFi in general.. I should use 4/16? Was the graphical glitches fixed in that?
[Droid Incredible Android Development] mh0520:
WiFi works in the 5/4 build. It's just really slow to turn back on if you turn it off. I'm guessing it took 8 to ten minutes before it came back on mine after that logcat I just posted but I wasn't really paying attention. It's back on now.

I can't speak to the tethering issue as I rarely use tether.

The graphical glitches are mostly limited to the 5/2 build. I see them on the adobe reader app when looking at pdfs but other than that I haven't noticed them on 5/4. 5/2 introduced the new adreno drivers if I'm not mistaken and 5/4 cleaned a few errors associated with that. Anyone that knows better than I please correct me, if I'm incorrect.

4/16 should be good as far as the graphical glitches except that the recent apps screen would blur if you use a live wallpaper. This doesn't happen on builds with the new drivers but the live wallpaper also goes black on this screen. Live wallpaper works fine on the newest build otherwise but on recent apps it's just a black background.

---------- Post added at 11:31 PM ---------- Previous post was at 11:26 PM ----------

On another note, I was having lag in this ROM for a few days now but I did a clean install with a full data wipe today and restored everything back with titanium backup. I'm now getting much faster smoother performance once everything settles out after a boot.

Great ROM and it's letting me hold onto my inc until either a black htc one for Verizon or something new from Motorola worthwhile. More likely than not the HTC one. I might have to make the jump to AT&T for that though, which, if I can't keep my unlimited data from Verizon, wouldn't be that bad anyways. Paying full price to keep unlimited data is really appealing....
[Droid Incredible Android Development] NYC Coyote:
So since I don't use live wallpaper.. and I use ProCapture for a camera... everything should work on it without an issue? (beyond the video camera.. and yes.. I know.. videocam illusion)
[Droid Incredible Android Development] mh0520:
As far as I know but don't quote me....Do a nandroid backup and try it out. It's definitely got a lot of neat features up from CM7.2.
[Droid Incredible Android Development] tiny4579:
The black background on recents is normal with LWP. That's from AOSP itself. I don't call that a bug.

I wonder if the WiFi and tethering changes are related to the changes to a module for WiFi vs builtin from before. I'll have to do some digging and check out your logcat if/when I get time. At least I can look at the logcat later.
[Droid Incredible Android Development] mh0520:
Fair enough if that's normal behavior. I'd much rather that than the way it was behaving on the old builds. Looks nice and smooth now.

Regarding the WiFi, if you get to it that's great but you've moved on to bigger and better things (I'm looking forward to those days soon). So, if you don't get to it I'm just thankful for all the work that's been done by you and all the other devs in getting the inc this far along. Thanks!
[Droid Incredible Android Development] tydiamond11:
Thank you for posting the log I was just getting ready to upload it lol thanks
[Droid Incredible Android Development] tiny4579:
That log is spammed with the usbdebugmanager debug messages. It's hard to read.
[Droid Incredible Android Development] mh0520:
I was afraid that was the case. I just searched for WiFi. Some stuff popped up.

Will disabling USB debugging stop those other messages?
[Droid Incredible Android Development] tiny4579:
It most likely will. But I found this in the logcat:

05-13 17:50:54.217 84 353 W CommandListener: Failed to retrieve HW addr for wlan0 (No such device)
05-13 17:50:54.227 84 353 D CommandListener: Setting iface cfg
05-13 17:50:54.227 354 417 E WifiStateMachine: Unable to change interface settings: java.lang.IllegalStateException: command '45 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 45 Failed to set address (No such device)'
05-13 17:50:54.237 354 4368 E WifiHW : Unable to open connection to supplicant on "wlan0": No such file or directory
05-13 17:50:54.247 4369 4369 I wpa_supplicant: Successfully initialized wpa_supplicant
05-13 17:50:54.637 4369 4369 E wpa_supplicant: nl80211: Could not configure driver to use managed mode
05-13 17:50:54.637 4369 4369 E wpa_supplicant: Could not read interface wlan0 flags: No such device

Most likely related to wifi being loaded as a module and not being able to reload properly. Or it could be a wifi crash.

You can try reloading the module with insmod /system/lib/modules/bcmdhd.ko from terminal emulator.

ADB issues can be worked around by enabling adb over network in dev options. Though I hope that logcat can give me clues to the adb issue as well.
[Droid Incredible Android Development] mh0520:
Sorry, I don't know what I'm doing with logcats. I'm learning as I go. Hopefully this one is a little more readable, even though it seems like it's a little too late anyways.

I tried reloading the module using the terminal command you suggested. It didn't seem to help but I'll let you know if that changes after a reboot.
[Droid Incredible Android Development] mh0520:
Now that the phone has rebooted it seems that the insmod command worked. Thanks!
[Droid Incredible Android Development] NYC Coyote:
And I am now guessing there will be a new build soon.. that I should wait for :)
[Droid Incredible Android Development] tiny4579:
It shouldn't as the OS should load the driver on boot so it can't load the module twice

I didn't promise that. I don't know if this is the cause but it's just a guess at this point. To revert it would require more cherry picks to the evervolv change and a custom kernel with WiFi built in.
[Droid Incredible Android Development] mh0520:
It said something to the effect of file already exists or something like that. It then rebooted on its own.

Now I'm not having the WiFi issue. I'll let you know if it pops up again.

If this sticks it's an easy enough fix for now. I don't see a need for a new build just to fix this.
[Droid Incredible Android Development] tydiamond11:
E/WifiHW ( 355): Supplicant not running, cannot connect

E/WifiStateMachine( 355): Failed to setup control channel, restart supplicant

I/dalvikvm(17820): Turning on JNI app bug workarounds for target SDK version 11...

E/Trace (17820): error opening trace file: No such file or directory (2)

E/Trace (17828): error opening trace file: No such file or directory (2)

D/dalvikvm( 4163): GC_CONCURRENT freed 411K, 65% free 2657K/7588K, paused 55ms+2ms, total 235ms

This is the log area with what I am seeing .
[Droid Incredible Android Development] mh0520:
So much for that. It's back to not working.

Oh well, leaving it on works well enough for me.

Great otherwise, thanks Tiny!
[Droid Incredible Android Development] tydiamond11:
Yah just leaving it on works lol
[Droid Incredible Android Development] Kaepernick:
Odd. I didn't have any wifi issues with this build.
[Droid Incredible Android Development] cmlusco:
Seems to be random. Sometimes you can turn wifi off and it will come back on just fine. Other times it will not, and require a power off. Not just a reboot but a power off.
[Droid Incredible Android Development] mh0520:
Yup, although a reboot seems to do the trick for me. Now you've given me something to look forward to. :)
[Droid Incredible Android Development] tiny4579:
For the Wi-Fi issue I'm going to try building the kernel with a more stable toolchain. It might help with stability.

I'm going to do a build tonight hopefully.
[Droid Incredible Android Development] kramer56:
does this wifi issue you guys are having have anything to do with the tethering issue I was having before I went back to 4/16
[Droid Incredible Android Development] tiny4579:
I built today's build with the AOSP GCC 4.6 toolchain for the kernel and Linaro GCC 4.7 for the ROM. Hopefully the more standard toolchain helps with WiFi. If not, I might switch back to the builtin WiFi from before 5/2.
[Droid Incredible Android Development] plexiglas81:
WiFi toggle on 5/15 seems solid compared to 5/4. Verified WiFi tethering works on 5/15 as well. Many thanks!
[Droid Incredible Android Development] dm47:
Hey guys my friend just gave me his incredible I just flashed the 5/4 build. This might be an easy question... but is there any way to disable the hardware key backlight?

many thanks to tiny, 5/4 build is much smoother than the ICS rom I came from

also I haven't run into any of the wifi issues on the 5/4 build yet
[Droid Incredible Android Development] zimlokks:
yes there is it should be, give me a second.

---------- Post added at 07:48 PM ---------- Previous post was at 07:45 PM ----------

http://dinc.does-it.net/Mods/SoftkeyLedsOFF.sh i suggest removing the .sh and set it in the /etc/init.d/...
[Droid Incredible Android Development] GnatGoSplat:
Is it possible to do the opposite? I always use the phone in the dark and I would like the hardware keys to be lit if the screen is lit.
[Droid Incredible Android Development] zimlokks:
ahh then don't put it in the init.d folder, use a app that does it on boot or do it manually when u want, that way a reboot will do just fine.
[Droid Incredible Android Development] tydiamond11:
Wi-Fi is working for me off and on yahoo ! Thank you so much tiny!
[Droid Incredible Android Development] zombolt:
Anything drastic besides the wifi fix? I backed down to 4/16 hoping things level out.
[Droid Incredible Android Development] tiny4579:
Nope. Just a blind sync. I suspect this will help tethering.
[Droid Incredible Android Development] tiny4579:
Sounds good so far. Let me know if you have any Wi-Fi issues guys. I want to look at adb next while waiting to see if Wi-Fi is better.
[Droid Incredible Android Development] jacobsensei:
Turning on WiFi is hit or miss with widgets or quick settings.

End up having to go into main settings.

Also getting unsupported kernel warnings, widget will not work.

Thanks for your work Tiny.

On VZ, waiting on the "One".

Probably a few months away.

4/16 Rom works fine.

Sent from my ADR6300
[Droid Incredible Android Development] nyonya:
Still having issues with Wi-Fi - the strange thing is, it was working fine on the 5/4 build for a week or so, then all of a sudden started behaving this way. Toggling on Wi-Fi causes my phone to reboot 2-3 minutes after I toggle it, once it reboots Wi-Fi is on and works fine.

Thanks for all you work on this Tiny! Any chance the graphical glitches in games can be fixed? Disabling hardware overlays works, but from what I've read here that's not really a good long-term solution.
[Droid Incredible Android Development] tiny4579:
I might just switch Wi-Fi back to built in. not sure about games. I fixed it in the ui and I don't really game and probably won't on the inc.
[Droid Incredible Android Development] tydiamond11:
Yah my phone worked when u turn it off and back on but not when it has been off for a little bit and then turn it back on
[Droid Incredible Android Development] plexiglas81:
I did have the WiFi toggle problem pop up just a bit earlier. No problem, though, since it works if you just leave it on. I just need to resist the urge to toggle when I'm not at work or home until the next build! :laugh:

EDIT: If it matters... WiFi was off for about an hour and I use the power control widget to toggle.
[Droid Incredible Android Development] zachf714:
[MENTION=3500210]tiny4579[/MENTION] try this toolchain. Its the one I use and I don't get wlan0 or WPA_supplicant problems https://github.com/VigorCM9/linaro
[Droid Incredible Android Development] tiny4579:
Did you try what others were saying and turn wifi off for a while and leave it and see if it fails to come on?
[Droid Incredible Android Development] zachf714:
[MENTION=3500210]tiny4579[/MENTION] yes I use tasker so it gets turned off when I leave my house
[Droid Incredible Android Development] tiny4579:
Can someone dump a dmesg output? I want to see if the wifi module gets killed or whatever happens on the kernel when this happens. I need it after the crash issue but before a reboot.

dmesg > /sdcard/dmesg.txt and upload it please next time you get this issue. i turned off wifi for a little while and it came on fine.

What network security types are you guys with this issue using? Just wondering if there's any correlation. I'm on WPA.
[Droid Incredible Android Development] zachf714:
[MENTION=3500210]tiny4579[/MENTION] newest build and the one before I had no problems but I use wpa2
[Droid Incredible Android Development] plexiglas81:
When I had the issue earlier today (phone turned off as a result... weird) I was not near any access points when I toggled off > 1 hour > toggled on.

Just toggled at home with 5 minute wait (WPA2-PSK) and it took ~3 minutes to turn back on. Only clicked power widget once to toggle off and once to try to turn back on. Maybe something useful in this... http://pastebin.com/jqkUdMjj
[Droid Incredible Android Development] tiny4579:
It may just be:

<3>[ 2604.217376] CFG80211-ERROR) wl_setup_wiphy : Couldn not allocate wiphy device
<4>[ 2604.217651] wl_cfg80211_attach failed
<4>[ 2604.319824] dhdsdio_probe: dhd_attach failed
<4>[ 2604.319976] dhd_osl_detach: MEMORY LEAK 1004 bytes

To see if it's hardware related, can someone with this issue try 4/16 again and try to reproduce it?
[Droid Incredible Android Development] zombolt:
Perhaps other conditions might exist that could affect your wifi experience? Who knows how many computers on your network, along with all those on other wifi networks. All sharing the same frequency band. Is it sunny out or is it rainy out?
[Droid Incredible Android Development] tydiamond11:
My network is wpa and I am now having all the same issues when I turn it off for say 10 mins and than turn it back on it will not turn on thanks!
[Droid Incredible Android Development] cmlusco:
Is there a setting i'm missing, or another way to make the screen stay on when charging? It's the only thing that bugs me about this rom.
[Droid Incredible Android Development] zimlokks:
it should be in settings>Developer Options>Stay Awake
[Droid Incredible Android Development] BoKnows?:
Is this what you want? I have encountered the WiFi issue on every ROM after 4/16. I am on 5/15 presently. I opened aLogcat and searched by Wifi, saved and renamed the file. I hope this helps point to the source.

Thanks for all you do.
[Droid Incredible Android Development] cmlusco:
There is no developer options menu, and i dont see it in any other settings menu.
[Droid Incredible Android Development] tiny4579:
In about phone you need to tap on the build number 7 times to enable it.
[Droid Incredible Android Development] tiny4579:
Can you guys try the 5/16 build I just uploaded? It should replicate properly on goo shortly. I switched back to built in wifi as an experiment. Let me know if wifi dies on you still please.
[Droid Incredible Android Development] mh0520:
Tiny, I think that might be a galaxy nexus build that was uploaded. It says toro and it's much bigger than typical inc builds so far.
[Droid Incredible Android Development] BoKnows?:
Failed for me in TWRP 2.5.0.0 to install. Goo didn't see it, so I downloaded from my PC, even checked MD5 before copy/paste. I reverted to 4/16 as I need my phone shortly. I'll check back later. Thanks anyway.
[Droid Incredible Android Development] tiny4579:
Read above. I pushed a Toro build by mistake.

There's a reason goo didn't see it as it shouldn't have.
[Droid Incredible Android Development] tiny4579:
Proper build posted. Sorry for the incovenience.
[Droid Incredible Android Development] jacobsensei:
OK, WiFi seems back to normal, working.

Still getting unsupported kernel warnings, widgets seem to be working though.

Everything else seems normal, except for some graphical glitches.

Sent from my ADR6300
[Droid Incredible Android Development] tydiamond11:
Downloading now will let us know if it is working right
[Droid Incredible Android Development] tiny4579:
I think your unsupported kernel warnings are from Chad's fast charge widget if you have that installed. The ROM currently uses evervolv which doesn't support fast charge. Are you sure that widget is actually working? I'd have to say no on evervolv's kernel.

Specifically where are these graphical glitches? I didn't notice any in the UI.
[Droid Incredible Android Development] jacobsensei:
Sorry Tiny, should have been more specific - graphic glitches seem to be in Antutu benchmarks only.

Also, you're right about Fast charge widget, removed.

Thanks.

Sent from my ADR6300
[Droid Incredible Android Development] tydiamond11:
I have tested the turning off of Wi-Fi and than back on about is working far thank you!
[Droid Incredible Android Development] cmlusco:
+1
[Droid Incredible Android Development] zombolt:
Ok I have a question about WiFi but not necessarily a ROM related bug issue. The apartment building I live in has shared a WiFi access point. I live in a densely populated part of the city. Particularly on my phone vs laptop it periodically disconnects, switches to 3g then will reconnect again. Before the latest calamities starting with 5/4 build, I just assumed it had to do with the router reaching it's maximum # of connections and environmental issues, coupled with perhaps a weak WiFi radio on the dinc and getting booted for that reason. So my question is: is my assumption a reasonable hunch? If yes, might it be possible to force the dinc wifi radio to tell the router to remain connected? If it sounds like the same bug, I am using 4/16..
[Droid Incredible Android Development] tiny4579:
The Wi-Fi was dying and nothing else. That should be fixed by using Wi-Fi built in instead of the one as a separate module. I won't know if it works for you until you try. what do you mean calamities? It only affected some not all.
[Droid Incredible Android Development] plexiglas81:
5/16 is noticeably smoother than (probably) anything I've tried on this phone that wasn't Gingerbread. Were any other under-the-hood changes made?
[Droid Incredible Android Development] zombolt:
It was an overstatement and a bit of theater, but the battery life changing was difficult to get used to for a guy like me because of personal problems. My seideo 3500 got jacked when I was mugged on Halloween night. For some reason the thieves tossed my dinc on the ground and left us both for dead. Couple months after that, she done quit charging on her own, so I gotta keep track of 3 mediocre batteries. I'll keep using this phone till death do us part. Blessed be!
[Droid Incredible Android Development] BoKnows?:
I installed the 5/16 ROM today and all I can say is, Wow! The smoothest and quickest yet. Battery life is great and the WiFi is spot on. Thanks.
[Droid Incredible Android Development] rlewis19:
I just moved to this ROM from the stock+ gingerbreak ROM. It's tremendous!

I was wondering how I can watch video's that were recorded from the original HTC video recorder. As for right now, the gallery is unable to display a preview for them and selecting one of the files gives 'Cant play this video' error.
[Droid Incredible Android Development] zombolt:
Happy I pulled my head out and quit being a baby about moving on from incredikernel. Wifi is working so much better now. Thanks tiny
[Droid Incredible Android Development] WildZontar:
I don't know why but all of the latest ROMs are giving me spontaenous reboots, both complete reboots and ones that go to the CyanogenMod screen. Could the ext4 mod have anything to do with this?
[Droid Incredible Android Development] tiny4579:
Last_kmsg please.
[Droid Incredible Android Development] zombolt:
After switching to the latest build today, I too have had at least 2 soft reboots.
[Droid Incredible Android Development] tiny4579:
Logs or it didn't happen. I don't have the time to try to reproduce bugs on ny inc.
[Droid Incredible Android Development] tydiamond11:
I am having no reboots this is the t Rom yet ! Thanks tiny
[Droid Incredible Android Development] NYC Coyote:
Ok.... so finally installed for the first time... still putting on apps (so not even done yet).. and I'll concur....

MANY MANY REBOOTS simply while trying to set it up.
[Droid Incredible Android Development] tiny4579:
Three reports of reboots. Absolutely 0 logs provided thus far. I shouldn't have to ask for this.
[Droid Incredible Android Development] tiny4579:
Coming from what ROM? Installed for the first time sounds like a different ROM.
[Droid Incredible Android Development] Kaepernick:
You guys do know how to get these logs, right?