yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] zachf714:
use git reset --hard

and that text box is nano, use ctrl O and ctrl X to get past it

edit- with that you should be able to build and have screen, if it does not build I will look at cm source again

edit2- that revert should not cause the problem that you are having, I think you have a merge error or something along those lines ( like this <<<HEAD )
[Droid Incredible Android Development] Vernox701:
just for reference just a noob when it comes to linux . So I have followed the build instructions on tiny's github page after setting up a dual boot box on my laptop. My local files are that which are downloaded using the repo sync. So whatever I think is an error I look it up before I post. So for example when I first setup my build environment and I do not apply any revert/cherrypicks the build goes through and gives me both an ota.zip package and a regular zip with the md5numbers and such in the out directory. However if I attempt any cherrypick/revert then the build errors show up. I understand if I am having make** errors then I look and remove that roomservice.xml from the .repo/local_manifests folder but whats happening lately is when I apply the display revert the HWC_Blit causes error in /hardware/libhardware/lightservices****xml. saying that things are not defined and the build breaks ....same if I only add the dalvik changes. So do I 'git reset --hard' after applying these changes or only to correct the changes.

a) I know the problem is the display revert I just think I am not typing the command correctly

b) or my local tree files whatever you call it repo is missing files.

c) I know its not that difficult to build from source but I never learrned spanish in High School so I think thats whats holding me back
[Droid Incredible Android Development] zachf714:
I would do repo sync -d first

then for the display commit, git revert , it uses nano so use the on screen controls which is pretty easy, hit control O then hit enter then hit control x then enter

that reverts the commit, which is the problem. You are checking out back to before the LED light commit which you dont want to do, which is why I am saying to git revert
[Droid Incredible Android Development] Vernox701:
Hopefully this looks correct after a repo sync then After applying the 'revert'

the build just finished but display still didnt work so I'm attempting again.....Thanks for all your help

Fetching projects: 100% (362/362), done.
Syncing work tree: 100% (362/362), done.

hardware/libhardware/: discarding 1 commits
vern@vern-Satellite-A665:~/android/cm10$ cd ~/android/cm10/hardware/libhardware
vern@vern-Satellite-A665:~/android/cm10/hardware/libhardware$ git revert 5b70e9b2
[detached HEAD 31e1eb6] Revert "Revert "hwcomposer: Add HWC_BLIT compositiontype value""
1 file changed, 3 insertions(+)
[Droid Incredible Android Development] zachf714:
Sounds like there is still something going on, I can fork the proprietary blobs tomorrow and set then back to before we moved up to the ion heap from pmem then you can use incredikernel to build which may fix display
[Droid Incredible Android Development] Vernox701:
Pons 10.1 github uses different commits for display and I may have not done something correctly. The build take two hours plus so I've already started it hopefully I got it correct this time.
[Droid Incredible Android Development] tiny4579:
Display actually works if you wait for it to fully boot. There are issues and I think it has something to do with one of the display or native commits.
[Droid Incredible Android Development] Vernox701:
Well youre right Display works...No bootanimation ,but after the room boots up the Display shows but all the screens bleed though if that makes sense and rom is unusuable.Maybe the correct term is overlay. I can't get into settings to change anything. But once I reflash your 7/08/ version everthing is fine again.

knowing correct terms woiuld make it easier to explain, So I figured you knew the display issue was the screen bleed through effect where everything just renders and is shaky
[Droid Incredible Android Development] zachf714:
It is from the ion heap, it happened on carbon as well. You resorted last I remember to setting the ro prop for disable hw overlays
[Droid Incredible Android Development] tiny4579:
The hw overlays disable fixed basic corruption, I'm not sure if it fixed the more major issues that vernox and I are seeing now.

I can't remember if I broke it down the line but the revert at the top should have fixed the display issues. It needs a bit more poking around to see if there is something missing.

Ahh, I think I remember

debug.composition.type=cpu

in build.prop.

Evervolv worked fine without removing ion.

We're also missing this commit, but it's performance based and won't fix the corruption.

https://github.com/Evervolv/android...mmit/f114431147e81f71f243d4c7852d422299ed6464
[Droid Incredible Android Development] tiny4579:
To use CPU composition, either:

1. In build.prop change debug.composition.type=mdp to debug.composition.type=cpu and reboot

2. To fix it for builds, edit device/htc/qsd8k-common/qsd8k.mk and change debug.composition.type=mdp to debug.composition.type=cpu there

For number two, this is what you'd edit

https://github.com/Evervolv/android_device_htc_qsd8k-common/blob/jellybean/qsd8k.mk#L78

hw overlays is something different though they may be effectually the same.
[Droid Incredible Android Development] zachf714:
The log is showing lots of copybit and surfaceflinger errors. To me that either means adreno blobs or something that complies with frameworks/native
[Droid Incredible Android Development] tiny4579:
Adreno is only for 3d. Copybit may be a problem. It's not an issue on cm10.2 but then 10.2 has that adb issue. 11 has neither issue.

It's hard to dedicate to much time to an old device especially when newer software doesn't have a particular issue.
[Droid Incredible Android Development] Vernox701:
Thanks changing the debug composition type to cpu helped and was my original problem four days ago.The process was good to learn something new. Thank you.
[Droid Incredible Android Development] zachf714:
revert this commit in vendor/htc e8c96d82ad6f61715cd5e919c3c0a087ed45257d

and switch the kernel from evervolv to incredikernel which requires you changing the local_manifest and the BoardConfig

You can either fork the device tree, make the changes locally, or use my device tree (same exact tree other than defconfig and kernel dir) but option 3 is currently out of order because go figure github is only half working
[Droid Incredible Android Development] Vernox701:
OK I'll try those changes later on this evening......

Do I also include the debug composition change
[Droid Incredible Android Development] zachf714:
option 3 is good now, I will update my manifest then you can just make the changes to yours to reflect mine

edit- commit 1 https://github.com/zachf714/android_device_htc_inc/commit/c4999f6de6cad434c26fc75936528d4fdc3a736b

commit 2 https://github.com/zachf714/android_device_htc_inc/commit/2c35817b91e43c00b0ef7a1778bb1de109058229
[Droid Incredible Android Development] tiny4579:
I don't believe you need the debug composition change if you disable ion. Since I haven't actually tried it in a while without ion, I don't know if it's needed.
[Droid Incredible Android Development] zachf714:
nope, not needed without ion. when I build carbon without ion it was fine
[Droid Incredible Android Development] Vernox701:
/android/cm10/vendor/htc$ git revert e8c96d82ad6f61715cd5e919c3c0a087ed45257d

error: Your local changes would be overwritten by revert.

hint: Commit your changes or stash them to proceed.

fatal: revert failed
[Droid Incredible Android Development] zachf714:
git status to see your local changes

also [MENTION=3500210]tiny4579[/MENTION] I have a feeling this is a BAD idea https://github.com/zachf714/android_kernel_common/commit/3190d29d5a75fbda25141d737bf1775201898329
[Droid Incredible Android Development] Vernox701:
o k fixed revert issue just to make sure do I still use git revert 5b70e9b2 for Display or is that included in the commits and local tree that I just synced
[Droid Incredible Android Development] zachf714:
you need that revert as well
[Droid Incredible Android Development] Vernox701:
ok about to build

---------- Post added at 05:17 PM ---------- Previous post was at 04:26 PM ----------

/android/cm10/vendor/htc$ git revert e8c96d82ad6f61715cd5e919c3c0a087ed45257d
[detached HEAD e69233a] Revert "qsd8k: use mako egl libs"
9 files changed, 1 deletion(-)
rewrite qsd8k-common/proprietary/eglsubAndroid.so (97%)
rewrite qsd8k-common/proprietary/libEGL_adreno200.so (81%)
delete mode 100644 qsd8k-common/proprietary/libGLESv2S3D_adreno200.so
rewrite qsd8k-common/proprietary/libGLESv2_adreno200.so (68%)
rewrite qsd8k-common/proprietary/libgsl.so (85%)
rewrite qsd8k-common/proprietary/libq3dtools_adreno200.so (76%)

is this okay seems like the percentage should be 100%

anyways first build didnt boot.. where do I look to see if the kernel has changed to incredikernal before the build starts
[Droid Incredible Android Development] zachf714:
didnt boot? make sure the kernel repo is in kernel/htc/incredikernel
[Droid Incredible Android Development] Pons:
I don't know who's tree you're using, but look for TARGET_KERNEL_SOURCE as well as TARGET_KERNEL_CONFIG under BoardConfig.mk

https://github.com/PonsAsinorem/android_device_htc_inc/blob/cm-10.1/BoardConfig.mk#L34

https://github.com/PonsAsinorem/android_device_htc_inc/blob/cm-10.1/BoardConfig.mk#L79
[Droid Incredible Android Development] Vernox701:
So I git cloned to pull in your device tree,I have a new folder android_device_htc_1

inside of that folder is the Manifest folder ... Well the local_manifest was for cm_11 so I think that was the issue.

My question is how or what would be the best way to create a second device tree since the one I am trying is different then what I already have. and kernel how to do this kernel repo
[Droid Incredible Android Development] zachf714:
Modify your current local_manifest to instead of pointing to tinys github, point to mine so instead of tiny4579/android_device_HTC_inc it should be

zachf714/android_device_htc_inc
[Droid Incredible Android Development] Vernox701:
Got it ....then ....repo sync -d
[Droid Incredible Android Development] zachf714:
-d just resets your local changes
[Droid Incredible Android Development] tiny4579:
Or just pull the local_manifest from his repo and cherry-pick the kernel commit as well as the one zach mentioned earlier.

My honest advice, read up on Linux and git as it sounds like it could help you and minimize your questions and issues.
[Droid Incredible Android Development] Vernox701:
Ok thats what I need to do ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[Droid Incredible Android Development] Vernox701:
Heres a logcat after building...
[Droid Incredible Android Development] zachf714:
you NEED to revert this change, (https://github.com/Evervolv/android_vendor_htc/commit/e8c96d82ad6f61715cd5e919c3c0a087ed45257d) which I posted earlier as well, or surfaceflinger and hwc die. That is why tiny stopped incredikernel on 4.2 because we could not find what drewis had done differently in the evervolv kernel that made ion work correctly. From that log, you are still using those mako egl blobs there for still using ion

edit - you are going to want to revert this as well in device/htc/qsd8k-common https://github.com/Evervolv/android...mmit/104fda59bf73a5046f5209ef45618ad0954b94ad

my bad, I did not realize they removed the pmem header files
[Droid Incredible Android Development] tiny4579:
Actually, incredikernel wouldn't even boot on 4.2 so I couldn't get as far as a logcat. Ion would crash the kernel at the beginning causing a reboot.
[Droid Incredible Android Development] zachf714:
I was reverting all the ion changes
[Droid Incredible Android Development] Vernox701:
Not that I know anything but I think the problem is Tiny uses this for display on cm 10.1 and changing the debug composition type

#Fix display issue
cd ~/android/cm10/hardware/libhardware
git revert 5b70e9b2

while other forks are using these reverts/cherrypicks for display

#Fix breakage due to CM revert part 1
#http://review.cyanogenmod.org/#/c/33305
cd ~/android/cm10/frameworks/native
git fetch http://review.cyanogenmod.org/CyanogenMod/android_frameworks_native refs/changes/05/33305/1 && git cherry-pick FETCH_HEAD

#Fix breakage due to CM revert part 2
cd ~/android/cm10/hardware/qcom/display-legacy
git revert b4331823c
[Droid Incredible Android Development] tiny4579:
I'm pretty sure both of them were mine.

EDIT: Hey, it's worth a shot. I'm going to not set the build.prop to CPU and try that commit and revert using Evervolv's frameworks/native and see how that goes.

EDIT2: Nope, the same graphical gltiches exist and CPU composition is still needed.
[Droid Incredible Android Development] Vernox701:
were you able to get display using incredikernal.....
[Droid Incredible Android Development] tiny4579:
Didn't try yet. The 4.4 Incredikernel should work with ion. You should just be able to revert ion and you should be able to use my Incredikernel for 4.2.2. This is based on what Zach says.
[Droid Incredible Android Development] Vernox701:
I couldnt get it to work thats why I asked....I was thinking I'll play around with this week to see what happens
[Droid Incredible Android Development] zachf714:
I reverted the ion commits when I built carbon because it caused the display problems that now are on 10.1 but I am not sure if I had given him all the commits. And yes the 4.4 incredikernel on my git should work with 4.2.2 unless there was a major change in the ion headers for 4.4
[Droid Incredible Android Development] fillyo:
I have my old incredible running Carbon ROM, which was installed a half year ago. A friend needs to use this for a while, is this ROM stable for basic phone use and internet, etc?
[Droid Incredible Android Development] Neo:
Yes
[Droid Incredible Android Development] lazycrazyboi:
Is the camera still broken on this ROM? I need to start using my dinc as a daily driver again.... And camera, WiFi, phone, browser, fb, gmail are what I'm looking for...
[Droid Incredible Android Development] ryanguy426:
The camera works, but the photo mode runs at around 5 fps (guess) with screen tearing. Video mode runs at around 2fps, making it barely able to record. The camera takes decent pictures though if you hold it still enough... panoramas are a no go because they become pretty blurry. Other than that, I've found no real problems with this ROM.
[Droid Incredible Android Development] tekweezle:
Download a 3rd party camera app like CameraZoom Fx. Due to the software being better and the shutter speed faster, pictures come out better.

Sent from a Freedompop HTC Evo 4G
[Droid Incredible Android Development] lazycrazyboi:
One more question which of the uploads should I install on my phone? The 10.2 would boot to tell me the setup app wasn't working and nothing further. The one right after that was released after a 10.1 was so laggy and glitch I could nearly get out of the home screen...
[Droid Incredible Android Development] ryanguy426:
It's not very clear which one you should flash or download... Tiny might want to update the OP :P

Anyway, take a look at the image below I created. I had the same issue as you at first... just gotta download the right zip :cyclops:

Hope this helps you, and anyone else wanting to flash this in the future :laugh:
[Droid Incredible Android Development] tiny4579:
Well, goo has changed a lot since I've used them and the replication of files could have had an issue. The 9/05 zip was incomplete (one of them was about 10MB).

Also, I'm not sure how the CM-10.2 zip got there. That may have been part of the problem. Did you read the file name?

I'm reuploading the most recent CM10.1 zips and creating a CM10.2 for my 10.2 builds.

The inc is hardly a current device so I have to dust it off (figuratively) to re-test the ROMs. I wouldn't have uploaded them without testing so they all should work. So it looks like the 10.2 zip was bad. No reason the latest 10.1 zip should have failed. If the latest have the same problem again I'll remove them (I don't have any current time to test them). How does that sound?
[Droid Incredible Android Development] darkharbinger81:
I can honestly say that most of your roms that I've ran have worked the thing is if it fails to flash maybe switch recovery. I've had an issue with twrp recovery not flashing certain things but after switching AmOn Ra or can 5.0.2 it would flash but I'm also unlocked with s-on too
[Droid Incredible Android Development] lazycrazyboi:
Thanks for your feedback. I'll test it out. Nice to know tiny still checks this page. I'll also Change my recovery mode see if that makes any difference.
[Droid Incredible Android Development] darkharbinger81:
Hope that helps its just something I've ran across and thought I might mention
[Droid Incredible Android Development] tiny4579:
Recovery shouldn't matter. If it fails it likely is something to do with the zip or not wiping if switching ROM versions.

Rather than just switch recoveries if a different recovery works, it'd be good to know why the recovery fails.
[Droid Incredible Android Development] lj1722:
Download

Long story short I have an HTC Incredible that I use for a few odd jobs and Id like to put your CM10.1 build on it. The problem is that goo.im seems to have been shut down. You dont by chance have it uploaded to anywhere that it could be downloaded do you? If not I totally understand but I thought it might be worth a try.
[Droid Incredible Android Development] tiny4579:
Actually, I do if you don't mind dev-host.

http://d-h.st/users/tiny4579/?fld_id=15482

I guess I uploaded there when goo was either down or having major issues.
[Droid Incredible Android Development] ClubSpade12:
I'm in boot forever? Why?
[Droid Incredible Android Development] Uzephi:
Please explain how you flashed so we can see what went wrong and what version you flashed.

Did you wipe system/data/cache before flashing? What firmware are you on? What radio? These are the things you need to add to your post so we can assist troubleshooting
[Droid Incredible Android Development] ClubSpade12:
It's alright I figured it out, just reformatted it all, then flashed again. I believe the problem was an incompatible Gapps package. All good now though.
[Droid Incredible Android Development] swofra:
New to android as I am using the DINC after losing a newer phone.

Hope this forum still gets some traffic...I've never used that site before, but when I try to download either zip there it just takes me to an ad for another site. Am I doing something wrong?

One more question: I have rooted my phone, have busybox/superuser loaded, have S-on, and am running GB stock 2.3.4 load 4.08.6.19 710RD . Can i just simply erase the caches and dalvik and then install this ROM fresh or do I need to something more extensive?
[Droid Incredible Android Development] taosk8r:
Can someone post a working mirror/new version for this? I hear its the best for dinc (Need something really stable).
[Droid Incredible Android Development] Arthemist Arora:
Hi can someone plz upload this ROM ? Would really appreciate it!
[Droid Incredible Android Development] tiny4579:
I figured there'd be questions about this. No, I'm not seeing double widgets and I didn't wipe anything, not even cache or dalvik. The issues probably didn't come from an upgrade. There are two digital clock widgets (chronus and digital clock). To use the new lockscreen clock you have to add it to the lockscreen, you can probably remove the old one. Also, the weather and calendar won't show on the lockscreen due to how android minimizes the widget by default and only showing a 2x2 grid which you'd have to maximize if you wanted to see weather and/or lockscreen.

You don't have duplicate calendar or clock apps under the app drawer do you?
[Droid Incredible Android Development] nyonya:
So, how does this latest build perform compared to the latest CM10 nightly? Is it time to move over?
[Droid Incredible Android Development] pRuben:
- no I don't. They are in the widget drawer. No biggie.

- thanks for the tip to add / remove the clock. The lockscreens widgets are new to me. It works great now, however I am still having issues on how to permanently re-size the 2x2 grid to something bigger on the main lock screen. It seems that the rotary slider takes too much space, and there isn't a way to re-size the chronos to show all the other info permanently.
[Droid Incredible Android Development] tiny4579:
There isn't a way to do that right now. It's the same issue on my Galaxy Nexus. For tablets it shows the max size but not phones.

It does seem to make it feel minimally useful for now.
[Droid Incredible Android Development] zimlokks:
I think ghost touches are quite the problem for me but that's on my part. Sometimes I yawn(pulling all nighers) straight into my phone and boom ghost touches lol just turn the screen off and completely wiping it(the screen) usually solves the problem. :) if not the reboot is necessary

Sent from my rooted GameBoy Color
[Droid Incredible Android Development] tiny4579:
Check the OJ as well for dust.
[Droid Incredible Android Development] zimlokks:
Mine is kinda broken. It's sunk in and well gives me problems.

Sent from my rooted GameBoy Color
[Droid Incredible Android Development] CyanoLou:
Tiny: Working very nicely, Thanks. Lockscreen changes, swipe keyboard, google now, widgets and messaging all work. I noticed a " Basic Sleep Mode" sleep system app listed in TB. this seems new.

Using: Beautiful Widgets for clock/weather and lockscreen app. Apex as my launcher, Camera360 for pictures, Dolphin Browser, Titanium Backup, Rom Toolbox for SD boost; Quickpic for my gallery. Running interactive governor at 245/960. Battery Life is and has been good. I delete unwanted system apps and have about 48 MB free.

Currently only issue is with app store. It runs, loads and searches apps fine, but will not download and gets stuck on "Downloading....." and no progress occurs. I cancel after awhile. This happened on the 1227 Rom. I will give this a further look and flash the prior gapps. Anyone else have this happen?
[Droid Incredible Android Development] zimlokks:
Clear Google Play Store data :) should work i guess it thinks its downloading something else

Sent from my rooted GameBoy Color

---------- Post added at 10:57 PM ---------- Previous post was at 10:56 PM ----------

Btw can we add any other widgets to our lockscreen or only those(clock, google ears) ?

Sent from my rooted GameBoy Color
[Droid Incredible Android Development] Shano56:
Chronus fcs when trying to edit weather settings in system settings, anyone else get this? I can get a logcat when I'm on a computer. Maybe I'll try clearing chronus data
[Droid Incredible Android Development] Cellulah:
Anyone tried this with the latest build?

http://xdaforums.com/showthread.php?t=1987032

Its gotten a lot of hype as of late and I'm wondering if it could help out with performance... If I were a more experienced user I'd give it a go myself.
[Droid Incredible Android Development] BarackMitzvah:
I'm using it on CM7 and am noticing improvements, give it a go!
[Droid Incredible Android Development] Cellulah:
Great to hear, thank you! Did you flash the zip or merely install apk? Lastly, do you know if it's possible to revert the changes it makes? Whole thing is rather vague which causes some concerns for me..
[Droid Incredible Android Development] BarackMitzvah:
I used the apk and its just a simple on off switch with an option to use on boot.
[Droid Incredible Android Development] saltcreep1:
How do you get google now to work?

EDIT - never mind a little more searching and I think I found the answer. Sorry!!!
[Droid Incredible Android Development] Cellulah:
Well, thanks again! Figure I'll give it a go and hopefully notice some improvement.
[Droid Incredible Android Development] tiny4579:
The app has to support the API for that to work. There's a hack floating around that allows any widget on the lockscreen but I don't think it's supported by CM.

No problems here.

How are your partitions looking? Can you post the output of df from terminal?