Thanks for the great ROM; this in conjunction with Tiny's Beta 4 is nothing short of amazing!
I too am seeing that that particular option is disabled, however. I am on your fourth build posted last night.
[ROM][UNOFFICIAL] Pons CM10 Inc builds (NIGHTLY)
- Thread starter Pons
- Start date
-
- Tags
- cm10 cyanogenmod htc incredible kang
- Status
Thanks for the great ROM; this in conjunction with Tiny's Beta 4 is nothing short of amazing!
I too am seeing that that particular option is disabled, however. I am on your fourth build posted last night.
I can confirm test build 4 with Tiny' s kernel 4 shows torch greyed out in the toggle menu.
Also, can anyone else confirm video recording is working with the latest build? Can't get it working in my device.
Last edited:
Its shows its recording but won't save
Sent from my ADR6300 using xda app-developers app
I have the same: Grayed out torch and video working but not saving.
Clean install w/ test #4 and tiny's beta 4 (interactive / noop)
Yep same prob same setup.. my cam isn't flickering now after thismorning
Sent from my ADR6300 using xda app-developers app
Pons you need this to activate the torch overlay: https://github.com/busches/android_device_htc_inc/commit/2e511d386113138fe3aba74b0886e84ffb3410d2
Last edited:
I'll take a further look at it when I get home. Still at work for probably another 2 hours at least. It's just odd that I have it and so do a few others, yet others don't. I know I didn't do anything special for the build I'm running.
So the consensus is beta 1 and 4 still flicker on YouTube, but 2 and 3 reboot (as expected on those two, just checking). Flickering more, less or the same? And how's the camera, still got that wonkieness?
Not much wonkieness for me on the camera
Sent from my ADR6300 using xda app-developers app
Still some artifacts on the first use of a boot (clear and just fine after that), and when zooming in and out. Test Build #4 for me.
Back on 9/15 nightly, seems about the same as test4.
Camera still artifacts first try, especially in settings.
YouTube some flickering, not that bad, so close to working.
Torch toggle is grayed out in settings, but mine is checked and still working.
Sent from my ADR6300
Camera still artifacts first try, especially in settings.
YouTube some flickering, not that bad, so close to working.
Torch toggle is grayed out in settings, but mine is checked and still working.
Sent from my ADR6300
Alright, two more test builds. Again, focus is on camera and video playback. Torch toggle should be fixed (thanks Zim, I cherry-picked your commit), not sure why it worked for some and not others.One (or both) will probably soft reboot on video playback. Hopefully just one build does. For those who are wondering, I'm narrowing down the issue for the video playback. That way we can quit frankensteining CM10, and stick as close as possible to pure CM10 source.
Also, these have quite a few upstream commits, so you shouldn't hesitate to switch to them (hoping they're stable
). They should still function with Goo OTA, for when I put out the next build.
Test5: cm-10-20120918-PONS-inc.zip - 107.99 MB
Test6: cm-10-20120918-PONS-inc.zip - 107.99 MB
Edit: sorry about all these test builds. I could keep them strictly to myself, but that would slow things down a lot. I'm actively engaged at work for 12 hours with no time to test. So I let yall test for me while I sleep. After these two builds, test builds should slow down significantly while I zero in on the issue. If I get enough feedback on these two today, I'll resume nightlys tonight (20 hours for me) or the night after.
Also, these have quite a few upstream commits, so you shouldn't hesitate to switch to them (hoping they're stable
). They should still function with Goo OTA, for when I put out the next build.Test5: cm-10-20120918-PONS-inc.zip - 107.99 MB
Test6: cm-10-20120918-PONS-inc.zip - 107.99 MB
Edit: sorry about all these test builds. I could keep them strictly to myself, but that would slow things down a lot. I'm actively engaged at work for 12 hours with no time to test. So I let yall test for me while I sleep. After these two builds, test builds should slow down significantly while I zero in on the issue. If I get enough feedback on these two today, I'll resume nightlys tonight (20 hours for me) or the night after.
Last edited:
Thanks for doing it, been to busy myself to look into anything or even flash an update to test.
Flashed test build 6 just now and I see that the camera artifacts are fixed (zooming still causes it, but that's nothing, really) with the default kernel; Tiny's Beta 4 causes them to come back. Also, using Zimeron's commit for LED flashlight worked as well.
Great work!
// Update
On test build 6, both stock kernel and Tiny's, I can't get data working over 3G or WiFi. I have the connectivity icons, but they're both saying no Internet and I can't do anything data-reliant. Going back to build 4 as I need Internet for work..
Maybe I spoke too soon.. I'll do a clean install because after flashing back to Build 4, I still have no data whatsoever. Will report back when I've completed the install in a little bit.
Clean install seems to have taken care of data, but that's back to build 4. If I get a chance, I'll update it to 6 later and see what happens.
Last edited:
Alright, two more test builds. Again, focus is on camera and video playback. Torch toggle should be fixed (thanks Zim, I cherry-picked your commit), not sure why it worked for some and not others.One (or both) will probably soft reboot on video playback. Hopefully just one build does. For those who are wondering, I'm narrowing down the issue for the video playback. That way we can quit frankensteining CM10, and stick as close as possible to pure CM10 source.
Also, these have quite a few upstream commits, so you shouldn't hesitate to switch to them (hoping they're stable
Test5: cm-10-20120918-PONS-inc.zip - 107.99 MB
Test6: cm-10-20120918-PONS-inc.zip - 107.99 MB
Edit: sorry about all these test builds. I could keep them strictly to myself, but that would slow things down a lot. I'm actively engaged at work for 12 hours with no time to test. So I let yall test for me while I sleep. After these two builds, test builds should slow down significantly while I zero in on the issue. If I get enough feedback on these two today, I'll resume nightlys tonight (20 hours for me) or the night after.
Test 5 flickers a bit in YouTube but it does play the vid
Sent from my ADR6300 using xda app-developers app
I'm on the 9/16 build and torch is greyed out for me as well
Sent from my ADR6300 using xda app-developers app
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
46CM10 Pons
Goo.Im Download for Kangs
Dev-Host Mirror
(updated only on request)
MediaFire Mirror
(updated only on request)
Evervolv Gapps
(recommended due to their smaller size)
Goo.Im Gapps
Merged Commits for Jellybean
(aka Changelog)
What this ROM is:
- Stripped version of CM10 (to make it fit) using tiny's/chad's incredikernel synced and compiled from source
- Uses only CM10 source, and...
- missing components from Evervolv
- incredikernel source from tiny4579
- and my HTC Incredible device tree
- Now supports OTA updating via the Goo Manager app
Removed (with my suggested replacements, if any)
- CMUpdater (only shows official, CM7, builds for the Inc; use the included Goo Manager app)
- CMWallpapers
- Music
- MusicFX
- Nfc
- Protips
[*]ROM ManagerCM removed it themselves in favor of open sourced CMUpdater - SoundRecorder
- SpareParts
- Terminal Emulator
- VideoEditor
- Basic wallpaper
- Galaxy4 wallpaper
- HoloSpiral wallpaper
- MagicSmoke wallpaper
- MusicVisualization wallpaper
- NoiseField wallpaper
- PhaseBeam wallpaper
Known issues:
- Watching YouTube videos
causes the phone to rebootflickers occasionally - Camera preview is glitchy with stock app; use a 3rd party one instead
- Video camera has a very low fps (it stutters)
- Laggy at first, due to filled system space (let it settle, then delete any system apps you don't need)
- anymore, let me know
Source/Sauce (in case you missed it)
- CM10 (I use their manifest.xml)
- Evervolv (I use parts of their frameworks and other repoitories to fix qsd8k specific issues)
- My device tree for the Inc
- Incredikernel by tiny
- For a complete list of what's added/removed/replaced from CM10's manifest, check my local_manfiest.xml
FAQ:
[Q] Pons, why are you compiling your own? Why don't we get official CM10 goodness?
[A] Well, now, why don't you take a gander at this: CyanogenMod: CM 9+, N1 (and other S1 SoC)
[Q] Gee, Pons, this here looks fun. How do I compile it myself?
[A] Here ya go, lil guy. Just follow these instructions: How to Compile CM10 for the Inc (if you encounter any issues using this to compile, please report here so I can troubleshoot and update if need be)
Why a thread? I finally got my builds (and computer) roughly where I'm satisfied with, with no major issues, other than the usual for our phone. Now that I'm tweaking/troubleshooting the source, trying to fix the playback issue, (and CM's no longer supporting our device and pushing commits without regard for us), there's a lot of variables in the mix. I've also made my computer into a build bot with a nightly script to compile. All this might or might not break my compiles, and I'll get feedback a lot quicker if something breaks. Also, I'm tired of troubleshooting by myself; this way, I get a wider range of testers.
Credits/Thanks
All credit goes to Cyanogen and the rest of the CM team, and especially our HTC Incredible maintainers, as listed by the CyanogenMod site: jistone (aka CUViper/This Guy), slayher, and of course, koush. Of course, don't forget about the Evervolv team, who have given our outdated qsd8k device a lot of love, despite being dropped by CM.
In addition, I'd like to thank Albinoman for bringing AOSP JB to the Inc first, Zimeron for bringing CM10 to the Inc first, and tiny4579 for his incredikernel.
For some reason, I have received several requests to put a donation link in my profile. You can always donate to the CyanogenMod project or the Evervolv project, but if you feel you HAVE to donate to me, I've put a link in my profile, and all donations will go towards upgrading my computer, so I can stay on top of this for CM10/11/and beyond.9Anyone want to give this power.qsdk8k.so a whirl? I have a full ROM with this modded file but would like verification. Download the attached zip file and push it to /system/lib/hw in recovery and boot your phone.
If it works I'll push it to my fork of Pon's github and then share what I did.
Fixed bad upload. I think it didn't like the file name so I reuploaded as power.zip.8Unfortunately, I can no longer maintain this (or any) ROM.
My computer crashed due to a faulty BIOS. It looked like it updated correctly, but it froze for 30 seconds and powered itself off while I was inside the menus (after the update, not during; weird). Now whenever I power it on, LEDs (no screen, no beeps) turn on for 3 seconds and it shuts it self off. Tried everything short of a motherboard swap (remove coin-cell battery, blind flash BIOS from a thumb drive and floppy drive, etc). I need to get my warranty transferred (I forgot to do that). Once I transfer it to me, they send out a box, I ship it to them, they fix it and send it back. Grand total time of 2 weeks to 2 months. By the time it gets back, I'll either be gone or about to be gone.
Tiny has told me that he can take over compiling the ROM. But due to this not being his primary phone, and having more of a life than me, it will not get updates as frequently and definitely not nightly. More when he has time or when he sees a worthwhile change (I pushed out nightlies when there was any change, even if it was a very minor one). I probably shouldn't have; it spoiled yall.
I do plan on picking this back up, but it really depends on where I end up. Half the time I don't know till I get off the plane, and even then that's generally a temporary stop while I get pushed further in. As such, I don't know what the Internet, if any, will be like.7
So four against.
Do you mean it is working now, or was that a typo and you meant not working?
I never noticed it was gone. But I don't use it. I flash Evervolv gapps after this ROM, and there's always an update to the Google Search (and the Play Store). If I get some time (probably not soon), I'll update the gapps if Evervolv doesn't.
If I take out DSP Manager, I'll probably add Apollo in a couple of builds. No promises, though.
You're right, that is odd that it installs without errors. Or are we supposed to have this library in the first place? I'm going to do some looking into this when I get a chance.
Thanks for a ll the feedback, gents.
Edit: at mamarley's suggestion, I enabled alpha compositing for smoother transitions. Will be in the next build.6
I'll probably compile a build tonight with those two open commits to try it out. I'll throw it on dev-host first, in case it's broken so Goo OTA doesn't snag it and mess everyone up (though if it does, standard disclaimer of it's not my fault, you flashed it, not me).
