yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] tydiamond11:
I will be testing the 09 build dirty flashing should I not?
[Droid Incredible Android Development] tiny4579:
You can try but the poster right above you was getting fc. I'd say try a clean wipe if anything.
[Droid Incredible Android Development] tydiamond11:
I will try and if I get it I will do a clean wipe
[Droid Incredible Android Development] nokiabolt:
Let me know how it goes...if data works, I'll do a clean flash.
[Droid Incredible Android Development] tydiamond11:
No the 09 build does the fc even with clean wipe I am going back to 07 it worked perfect besides the data part.

---------- Post added at 05:15 PM ---------- Previous post was at 05:15 PM ----------

Idk about the 08 build any one know?

---------- Post added at 05:32 PM ---------- Previous post was at 05:15 PM ----------

Does any one have the 11-07 build still downloaded I deleted it and now i need it back. lol or if the 11-08 build works let me know i can't download ether. Pons there is a very big issue with the 09 build you can't boot.
[Droid Incredible Android Development] Pons:
Odd. I'm currently not making changes (no time to debug), and am just compiling. The 11/07 build should still be on goo.im. I've also started it uploading to dev-host.

When I get home, I'll add a warning of "use at your own risk" or similar.
[Droid Incredible Android Development] tydiamond11:
Thanks
[Droid Incredible Android Development] nokiabolt:
11/07 is a great version to use if your inc is on WiFi or don't mind no data (like me). Performance is excellent.

---------- Post added at 12:31 AM ---------- Previous post was at 12:30 AM ----------
[Droid Incredible Android Development] nokiabolt:
Build 20131110 works. No issues thus far. Data not working as of yet, I tried flashing this build over tiny 10.1 20130708 hoping data would carry over. Not case but that's okay
[Droid Incredible Android Development] norm883:
Nook HD+ 4.3.1

I am not sure I am in the right spot or forum but I am running this on a Nook HD+ and all is running beautiful but at times the entire device locks up. This happens on the lock screen and when swiped you just see a flash of the home page then right back to lock screen. Will not allow entry. Happens when the device sits even for only a few minutes. Need to reboot to get back in. Then works fine, let it go to lock screen (will not allow entry). anyone else having the problem? Right now I have the lock screen turned off and appears to be running fine. Happened with original install and now two of the nightlies.

norm883
[Droid Incredible Android Development] nathansnyder:
This is running really smooth!

One question: Is anyone having issues with Android Contact Sync? It won't sync Google contacts, or even show my Google account in the People app. It's a little thing, but I've tried reinstalling, wiping data, etc., and no results.

Thanks Pons!

Nathan
[Droid Incredible Android Development] tony442:
You need to flash the latest gapps.
[Droid Incredible Android Development] tydiamond11:
What has changed with the 11-10-2013 build?

---------- Post added at 10:02 PM ---------- Previous post was at 10:01 PM ----------

Sorry the 11-13-2013 build lol
[Droid Incredible Android Development] Pons:
If this was not a mispost and you actually wanted to post here....this ROM is for the HTC Incredible, not Nook HD+. So you should probably find another ROM.

This one is pretty user friendly to view: http://changelog.bbqdroid.org/ You could also check my device tree on github for inc specific changes (nothing there between the dates), and the various Evervolv github repos I use (qsd8k-common and kernel, and their htc vendor)

Edit: I might have fixed data. Stay tuned for next build.

Edit edit: uploading the 11/14 build to both Goo and dev-host (but looking at the site, I think Goo is now working). ETA is about 12 minutes for Goo, but I gotta run to work and don't have time to test. If someone runs this build, let me know if About phone is picking up the network type, and what's going on with data.
[Droid Incredible Android Development] Vernox701:
11/14/2013 build

Mobile Network Type

unknown

Mobile network State

disconnected

when I go to voice dialer and open APN there is nothing set
[Droid Incredible Android Development] tydiamond11:
Have you tried putting in the apns manually? My Inc is not on service so I can't test
[Droid Incredible Android Development] Vernox701:
Yes but they don't stick , I have pulled the ones from tiny's evervolv 4.3 rom (etc folder and framework)as well swapped wpa_supplicant in the system bin

even changed some of the libs , modified the build prop but it seems as if the 3g is diabled and only wifi works.... not a developer so I try different things that I think may work.im pretty sure sure its somethig simple in the init.rc or updater script somewhere along those lines the 3g option is not defined or declared.
[Droid Incredible Android Development] GnatGoSplat:
My NAND is bad, so my emmc is unusable and therefore /sdcard is unusable too. I'm using inc_mount_sdcard.zip that Tiny made to mount /data and /sdcard to my physical sdcard (except now my sdcard partition is /emmc).

Is there any way to switch /sdcard back? 4.3 doesn't seem to have a vold.fstab file to edit. I tried editing /fstab.inc, but it keeps changing back when I reboot.
[Droid Incredible Android Development] tiny4579:
You can change fstab.inc but its part of the ramdisk in the boot.img. It needs to be unpacked, edited, repacked, then flashed for changes to take effect. Otherwise you're just editing a file in memory.
[Droid Incredible Android Development] GnatGoSplat:
Thanks, I managed to get it to work by modifying the INC_mount_sdcard.zip that you made. I added these lines to sdmount.sh before "#build new ramdisk":

#edit fstab.inc
sed -i '/\/devices\/platform\/msm_sdcc.3\/mmc_host\/mmc2 \/storage\/sdcard0 auto defaults voldmanaged=sdcard:3/c /devices/platform/msm_sdcc.3/mmc_host/mmc2 /storage/sdcard1 auto defaults voldmanaged=sdcard:3' fstab.inc
sed -i '/\/devices\/platform\/msm_sdcc.2\/mmc_host\/mmc1 \/storage\/sdcard1 auto defaults voldmanaged=external_sd:1/c /devices/platform/msm_sdcc.2/mmc_host/mmc1 /storage/sdcard0 auto defaults voldmanaged=external_sd:1' fstab.inc

By some miracle, that worked! Pretty cool since I really had no idea what I was doing. I just copied what you had for the other files and modified accordingly.
[Droid Incredible Android Development] Vernox701:
Pons can you update default.prop

#

# ADDITIONAL_DEFAULT_PROPERTIES

#

persist.sys.usb.config=mass_storage,adb

persist.sys.strictmode.disable=true

ro.secure=0

ro.allow.mock.location=1

ro.debuggable=1

right now its trying to mount as a mtp

#

# ADDITIONAL_DEFAULT_PROPERTIES

#

ro.debuggable=1

persist.sys.usb.config=mtp,adb,adb

persist.service.adb.enable=1

ro.adb.secure=0

ro.secure=0

ro.allow.mock.location=0
[Droid Incredible Android Development] Pons:
That's not the problem. The problem is the ril isn't even recognizing the network type. It must recognize the network, before it request a data connection.

Done. It'll be in next build.
[Droid Incredible Android Development] GnatGoSplat:
After playing with this ROM for a day, I am really impressed with the performance. Virtually no lag whatsoever! Before, I had tons of lag, enough I was thinking it was time to retire the old DInc. General UI smoothness is now equivalent in feel to my much newer dual core devices. Here I was thinking the guy who said his DInc is now a "speed demon" was exaggerating, but it really is! Thanks, Pons!
[Droid Incredible Android Development] tydiamond11:
Yes thanks pons for the info
[Droid Incredible Android Development] BarackMitzvah:
Really? So the rom is up to standards as far as using it as a daily?
[Droid Incredible Android Development] GnatGoSplat:
Only if you don't need mobile data since I don't think it's working yet. I don't need it since I just use Wifi.
[Droid Incredible Android Development] srinia:
Very speedy rom with Wifi Issues

Pons,

Thank you for working on this new version of JB. I loaded this ROM yday(the latest that is in goo) and here is my quick feedback.

I could not get the 3g to work at all.

There are issues with Wifi also. Some times the Wifi toggle button in the setting gets disabled and a reboot enables it again.

The rom in general is fast.

I use Ultra Slim Gapps for CM10.2 JellyBean 4.3 Super Trimmed version
[Droid Incredible Android Development] Vernox701:
Pons,

Is it possible that in your git that the HTCqualcom ril is the problem its labeled as No Data Calls . Could it be operating as a wifi only script.
[Droid Incredible Android Development] zachf714:
That could very much be the issue
[Droid Incredible Android Development] Pons:
Yes, the wifi and telephony package is being looked at. Just I've been really busy. They have me teaching a class now, so instead of researching android and inc stuff, I'm researching my class to ensure I'm putting out the best knowledge I can.

I know what you mean by the ro.telephony.ril_class=HTCQualcommRIL, but I'm not sure what you mean by "its labeled as No Data Calls." That class is a data, voice, lte class designed for use by all HTC QC devices (excluding the M7). But I just woke up and haven't had my coffee, so maybe I'm missing something obvious. Please provide a link or more indepth explanation because everything is still foggy.
[Droid Incredible Android Development] Vernox701:
https://github.com/PonsAsinorem/and...mmit/71bb8485b40dad740194a73628084e8dbed305cb

This is not the exact page but evervolv uses a different setprop argument here in android 4.3 but the page I was viewing that day had notes on different changes. The setprop you are using is different from evervolv and guessing since you don't use data thats why you used a different ro.telophony.ril.....

ll keep looking for the page I saw ...thanks for checking it out
[Droid Incredible Android Development] Pons:
I know you said that's not the same page, but....

https://github.com/Evervolv/android_device_htc_inc/blob/jellybean-4.3/full_inc.mk#L38

Evervolv uses full_inc for some, and system.prop for others. In this case, both have the same

ro.telephony.ril.v3=skipdatareg,emptycallchanges

and I do use data (but not on these more recent builds), which is why this kinda irritates me. It used to work about 3-4 weeks ago, when I stopped doing builds (with the same HTCQC class and v3 props), then I started compiling again, and something broke it. Busy with work, so I haven't had a lot of time to sit down and find the issue.
[Droid Incredible Android Development] Vernox701:
okay I dont understand fully everything within the code but Im speaking about the

ro.telephony.ril_class=HTCQualcommRIL

Thats the only thing blaring out as different.

I misread and misunderstood the + and - as for what was removed and whats being added referring to your Oct 27 commit
[Droid Incredible Android Development] Pons:
As for that, I just specified that it uses the HTCQualcommRIL, because, well, it's a HTC device with Qualcomm hardware. Not sure why Evervolv doesn't use that, and they use the standard RIL instead. I might have to ask them one of these days.
[Droid Incredible Android Development] Vernox701:
No big deal Pons I just trying to learn and understand things more clearly . I was reading your device tree or whatever its called and for example board-info.txt says i failand didn't have a/home partition, so this is going to be huge

so I saw something pertaining to the ril and it had a comment about No calls No Data so I jumped all over it thinking that was the problem .
[Droid Incredible Android Development] mamarley:
I just installed this and everything seems to be working pretty well, except I can't use ADB over USB. I have the option enabled in the Developer Settings and there is "Android Debugging Enabled" in the notifications, but the computer can't see the device. Does anyone else have this problem?
[Droid Incredible Android Development] tiny4579:
Hey mamarley how's it going?

Try turning on adb network. There's a weird bug on cm on this device that doesn't properly enable adb without adb over network turned on.
[Droid Incredible Android Development] mamarley:
Yep, that works. Do you think this bug will get fixed? Because turning on ADB-over-TCP is something of a security risk.

Also, is there an Incredikernel or some other kernel that supports 128mHz CPU and USB Fast Charging for this? I checked the Incredikernel thread but it doesn't appear to be compatible with this ROM.
[Droid Incredible Android Development] tiny4579:
I made a 4.3 compatible incredikernel as proof of concept. I'd need to rebuild to make sure it has the latest changes from ev kernel but yeah it's doable.

Not sure about the adb issue. I don't know what broke it but I'd love to fix it but I've tried a few times without success.
[Droid Incredible Android Development] mamarley:
A 4.3 Incredikernel would be great! I am missing smartass, 128mHz, and USB Fast Charge. :)
[Droid Incredible Android Development] tiny4579:
Its bootlooping. Maybe a rebase off of evervolv kernel may be needed, especially since 4.4 brings ion back into play and that caused reboots on incredikernel.

I might be able to pull the last_kmsg from evervolv as it doesn't have the adb issue.
[Droid Incredible Android Development] tiny4579:
Must have been me as it's working fine now on both CM10.2 and Evervolv 3.3.

Edit: By the way, incredikernel has been updated.
[Droid Incredible Android Development] lesdense:
The one thing that's kept me off of CM9 and CM10 on my old INC is that Netflix and other streaming video services don't seem to work. My Incredible is an off-contract "media phone" these days so smooth streaming audio and video and Bluetooth audio are key to my uses. Has anyone tested streaming video and/or Bluetooth audio with this ROM?
[Droid Incredible Android Development] tiny4579:
There is an xposed module to get Netflix working. I'm not sure if it still works but it's worth a try.
[Droid Incredible Android Development] mamarley:
It might be a good idea to remove

service auditd /system/bin/auditd -k
class main

from the init.rc file because this service won't run without SELinux being enabled. Instead, it just spams

I/auditd (12739): Starting up
E/auditd (12739): Failed on audit_set_pid with error: Protocol not supported
I/auditd (12739): Exiting

to the log.
[Droid Incredible Android Development] zachf714:
I hate selinux, but maybe we should try and add support for it. I know Steve wants to set it to enforcing for 10.2 at some point and it's set to enforcing in kitkat by default
[Droid Incredible Android Development] Pons:
I've been debating on how best to do that for a good bit (granted, half-heartedly). Init.rc is located at android_system_core, and I'm trying not to fork more than needed. The only thing I currently have forked, is android_vendor_cm, and that's to chop down on the /system/apps.
[Droid Incredible Android Development] zachf714:
You could create an override in the inc tree for init.rc, could be talking out of my a** tho
[Droid Incredible Android Development] kozmo198:
How can i fix wifi not turning on issue? The wifi was working, but stopped after about 4 days. Now when i try turning it on, it either does not slide towards the On button in settings,sometimes showing only wifi turning on but stays lie that for a long time without turning on. or in power control widget, same thing happens, it stays showing its powering on, but does not. I had checked back on my phone after i woke up, and it started working again, but now the next day its doing the same thing not turning on. my htc incredible is flashed to this rom, with slim gapps package.

Another issue is i can not play youtube videos. they seem to buffer, but do not play. Can you guys help me fix these problems. Thank you. My htc incredible is flashed onto boost mobile, but I think they terminated my boost mobile account for inactiveness. I recently got this incredible working, and am trying to renew its life.
[Droid Incredible Android Development] zachf714:
you said about 3 or 4 weeks ago

these stand out

https://github.com/CyanogenMod/andr...mmit/65d20e35fe02861307d8ff1ecc73425701d3fd7d

https://github.com/CyanogenMod/andr...mmit/7d7eed6f2856fbccfa2b84977f2cba9cdab1aac1
[Droid Incredible Android Development] Vernox701:
Pons ....any updates...?
[Droid Incredible Android Development] zachf714:
He got an m7vzw =p
[Droid Incredible Android Development] Pons:
Sorry, been working on a few other projects, and I can no longer test data. So it's hard to tell if it's fixed satisfactorily or not. Also, that was the only real issue that I can think of off the top of my head, and no, I'm not going back to read my own OP. Way too much work.

I'll try to push out an updated build, but my device tree and vendor/cm should be up to date, if anyone wants to compile their own.

And this. ^^^^
[Droid Incredible Android Development] Vernox701:
Alrighty Thanks
[Droid Incredible Android Development] Pons:
Quick question to those that have used this ROM: does Goo Manager OTA work for this ROM? Just noticed I had a special character (a period to be exact) in ro.goo.rom, and supposedly it doesn't work with (all?) special characters. I know it doesn't work with hyphen/dash and/or underscore.

Edit: also compiling a new build.

Edit edit: new build up. Sorry for the lack of updates.
[Droid Incredible Android Development] tydiamond11:
The goo ota I'd good now that they fixed there servers the little dot just makes it where you have in the manager to click on Inc or somthing twice. What is new in the New build?
[Droid Incredible Android Development] Pons:
What, 1.5 months of merged CM changes isn't enough? :P
[Droid Incredible Android Development] tydiamond11:
Yeah that is great! Any ideas about if we will get cm11?
[Droid Incredible Android Development] Pons:
Shouldn't be too hard. The hardest part for me in doing these is the creation of a visually pleasing OP that doesn't look thrown together.
[Droid Incredible Android Development] tydiamond11:
Well you did a good job here just copy another roms form
[Droid Incredible Android Development] tiny4579:
There is the problem of space to deal with. Evervolv shrunk their ROM in kitkat for the Inc and it barely fits and CM is a slightly larger ROM to begin with. Still, it can probably be done.
[Droid Incredible Android Development] tydiamond11:
I understand but it is just amazing that this phone is still going lol
[Droid Incredible Android Development] zachf714:
I tried cm11, everything (literally everything) forced closed on boot and I could not for the life of me get a log out of it
[Droid Incredible Android Development] tydiamond11:
It just needs work I guess. Just like evervolv has lol
[Droid Incredible Android Development] ryukiri:
Hmm, maybe we could try implementing LVM like what Zaclimon did with the Galaxy Player here. They now have a decently sized /system partition.
[Droid Incredible Android Development] Vernox701:
Thanks for the update.....will the data fixes for kitkat work here... can telephony-common.jar be swapped
[Droid Incredible Android Development] musical_chairs:
They mostly should, though we are using a different patch for basic support for cdma data calls based on NV on kitkat than what is used on JB 4.3. The dinc-specific fixes are pretty much the same on both. Look for the stuff submitted to Evervolv by this guy, this should cover all the data patches for 4.3 except for the basic one, which CM has merged anyway:

http://review.evervolv.com/#/q/owner:ross.squires%40gmail.com+status:merged,n,z

Swapping out the .jar file? I have no idea what would happen...
[Droid Incredible Android Development] Vernox701:
That's my fault for asking halfway question...what i really wanted to know was is there a way to fix data with out building the rom from source...

I tried to setup a build envirement once but it was a train wreck
[Droid Incredible Android Development] musical_chairs:
...and my fault for forgetting that not everybody builds their own roms from source. Looking back over the thread it looks like data was working early on (before it was released) so my advice is not that helpful anyway.

---------- Post added at 08:44 PM ---------- Previous post was at 08:20 PM ----------

Pardon a potentially stupid question, but where are those v3 props in your source? I can't find them.
[Droid Incredible Android Development] tiny4579:
It's here:

https://github.com/PonsAsinorem/android_device_htc_inc/blob/cm-10.2/system.prop#L6

As long as it shows in the build.prop it's there. It's redundant to have it in both places.
[Droid Incredible Android Development] musical_chairs:
OK, thanks. (I was on the wrong branch... :o )
[Droid Incredible Android Development] Pons:
Due to other projects and the slowing down of cm-10.2, I will only being pushing out builds of this once a week (probably over the weekend).

If you see something that got merged and want a build sooner, it's ok to request me to update the build sooner. Just don't request every night. :P
[Droid Incredible Android Development] Mafworld:
Thanks for update PonsAsinorem :) wifi works much better now
[Droid Incredible Android Development] zachf714:
Trolololol
[Droid Incredible Android Development] Vernox701:
what a tease
[Droid Incredible Android Development] tpearsall:
Thanks for putting this together! One of my kids has been hell bent on iTouch and saving his money (costs $250!!), but with your CM10.2 build I was able to avoid an Apple product AND he saved $250 when I have him an old Inc without service that was laying around. He is loving it!

Thanks again!!
[Droid Incredible Android Development] kramer56:
Hey guys since my laptop crapped out I haven't been following the threads much at all. Right now I'm running cm7.2 stable but I miss the newer roms. Is there a jb rom that works good now? I need tether, data, phone, camera, really that's about all I worry about. I been reading a little about the kitkat but it seems like it's not there yet. You guys have any suggestions for me?
[Droid Incredible Android Development] Pons:
Honestly, I'd stay with CM7.2 if I were you. Most of the newer ROMs have issues with the camera, which you labeled as a must.
[Droid Incredible Android Development] kramer56:
Not really a must must but I do use it to send mms and things like that. We're building house so I take pics once in awhile to keep contractor informed of his mistakes lol

---------- Post added at 08:01 AM ---------- Previous post was at 07:42 AM ----------

OK so ev 3.3 is a jb rom and 4.0 kitkat? I'm so confused now lol. Was just on goo app and under tiny that it listed by not sure what they are
[Droid Incredible Android Development] tydiamond11:
Yes 3.3 is jb and 4 is Kitkat go with this rom here it was very good,!
[Droid Incredible Android Development] Pons:
Does anyone still use this ROM, or has everyone migrated to CM11 or other builds? If people don't use this, I'll close this project out and focus on other projects of mine. Probably Omni next.
[Droid Incredible Android Development] Vernox701:
I personally am waiting for a fix to mms then I was going to request an update.
[Droid Incredible Android Development] Pons:
That's going to be tricky for me to look into without data/service on my device.
[Droid Incredible Android Development] Vernox701:
Okay that makes sense Well its still a great rom that was really the only hold up as far as I am concerned.
[Droid Incredible Android Development] Vernox701:
MMS FIX? Maybe

So today I had some time to play around.

First I flashed cm10.1 no GAPPS and then I dirty flashed cm 10.2 (1/21/2014) and I was able to send and receive MMS(picture messages)

afterwards I started thinking and I remembered when we first moved to JB we needed to manually add Apns-conf to system/etc and also change the apns.xml inside of framework-res/xml. So I tried the first two and still nothing happened did a lot of reading of old forum threads and took a look at the eri.xml So I changed that one out as well and Now I can receive MMS pictures using cm10.2 I used the files from cm10.1
[Droid Incredible Android Development] zachf714:
Are you kidding ? I am going to do that on 11 and see if it works
[Droid Incredible Android Development] Vernox701:
Yes it definitely works...