I need a straight answer as it's possibly the one thing I can't figure out.
For eclair, NCommander fixed camera, but camcorder and video were broken from a straight build from AOSP.
CM later fixed these, but I never quite figured out how. Then everybody else started getting the camera fixed on their roms (by pulling a couple libs, I assume), but I myself couldn't figure out how the heck it was done, where an alternate source was available, or even an explanation of exactly what was broken/how it was fixed, etc. Same went for video playback/hw acceleration.
Now, on froyo, camera is broken again and NCommander's camera won't work either. It's been fixed by other people, but when I ask around, there seems to get a reluctance and I never really get an answer (and don't give me the "you're not asking the right question" line, I'm being pretty straightforward).
I need somebody here who has some knowledge as to why/how camera/hw is not working and how to fix it. I don't need libs. I need to know how to get the thing built from AOSP, why it breaks, and what I should look out for in the future, should it break again.
As far as I can tell, the problem is that the qcomm proprietary parts are outdated (for dream, last were 1.6 and eclair/froyo break compatibility with those libraries). Those libraries have to be linked-to at compile time of other hardware-libs and without the correct library, it won't build right.
What I don't get is: 1. which parts are missing, 2. where are people getting them from, 3. how do you add them to AOSP (other than PRODUCT_COPY_FILES) to get camera and all hw working right (including 3d acceleration).
Or maybe the project aurora community is better able/willing to help...
Bump. Totally interested. If OP already got an answer, please share.
Jubeh sorry I can't help you out I'm not a dev or a chef so I can't really give you any help. But I am interested in how your progress is going with this rom?
I found two sources for hardware files for the msm7k on our phones, including the camera and hw3d driver for dream. Also, building camera for AOSP seems to be fixed now. I'm just waiting from my battery to get here so that I can test. ebay parts from hong kong take forever.
Related
http://techcrunch.com/2011/06/30/skype-for-android-now-support-video-calls-works-over-wifi-and-3g/
Not working on the transformer or the gtablet yet. But hopefully we'll get a working app soon either from microsoft or from the dev community.
I tried a patched version that took out the restriction. It force closes when trying to accept a call and enable video, but the settings and buttons show up...
gtab
Can some one upload the APK when they get the new video skype so we can try this on the gtablet.
Here's the issue, I think...
The support for video chat requires Gingerbread. If I understand correctly, this is because GB finally introduced a standard API to access the front camera.
Until Gingerbread did this, all apps that accessed the camera needed their own drivers to do so (there was no standard camera driver to access back then, which is why apps needed to have built in support for specific devices).
Skype is using this to their advantage by releasing an app that doesn't require much code change to support device almost any device (why they are only supporting specific devices at a time is mostly political AFAIK).
But here's the problem- There is no official Gingerbread for our hardware! All the GB roms we have are hacked together with peices of code with missing native hardware drivers since they don't exist! That means, I would guess, the new Gingerbread camera API is USELESS BECAUSE GINGERBREAD LACKS THE NATIVE HARDWARE SUPPORT!
Yes, this is awfully depressing. But without a real Official Gingerbread rom, unless Skype starts offering Froyo camera support (unlikely since they would go back to the old problem of suporting each camera hardware individually), this is just not going to happen.
Maybe if the rumors of official Honeycomb drivers turn out to be true, and Skype eventually supports video with HC (another *IF*), then maybe. But that's a long way off.
Very depressing- I was very excited about this working until I came to this realization.
Wrong thread.
How's that? Looks like the correct thread to me.
Dishe said:
How's that? Looks like the correct thread to me.
Click to expand...
Click to collapse
I meant myself. I put a post here and then realized it was meant for elsewhere. Multiple windows openned.
Here's the apk for the new released skype vid app.
Since at lease back in the 4.4 days of AOSP, the nexus 5 (and probably others) has had an issue with the camera when in video mode. There's a nasty green line that appears on the side of the video during playback.
It's an easy fix; just replace the file /system/lib/libmmcamera_interface.so with the one from the factory nexus image.
I have poured over the source code for this library, but I can't find out what it is that causes this anomaly nor why it is fixed in google's image, but not in the AOSP source. How can this have been an issue for so long? Am I the only one who runs self-compiled AOSP on my N5?
Anyway, does anybody have any idea what the cause is, or how to fix it in the source?
Hello!
I started searching to fix that issue this morning and i ran in to your post. Ive been building a while from aosp sources with minimal editing only, and i think this hasnt happened with 5.0.2 for me. Now that ive merged 5.1 into the source, i saw it happening again.
I checked few trusted developers vendors, blobs, etc. And i managed to make this:
https://github.com/sicknemesis/android_vendor_lge/commit/de6831773e3e083cef8d53f344f0a03f6a604268
As i write, im flashing and bootin a rom build with this commit and it seems its working correctly now.
All credits to original authors as seen in original commit! Hope this was the thing we are looking for and i see not lot of people check this Developer Discussion forum . I DO!
Gene Poole said:
Since at lease back in the 4.4 days of AOSP, the nexus 5 (and probably others) has had an issue with the camera when in video mode. There's a nasty green line that appears on the side of the video during playback.
It's an easy fix; just replace the file /system/lib/libmmcamera_interface.so with the one from the factory nexus image.
I have poured over the source code for this library, but I can't find out what it is that causes this anomaly nor why it is fixed in google's image, but not in the AOSP source. How can this have been an issue for so long? Am I the only one who runs self-compiled AOSP on my N5?
Anyway, does anybody have any idea what the cause is, or how to fix it in the source?
Click to expand...
Click to collapse
Wow, so the N5 was never intended to use the AOSP version of that library. I never checked the qcom binaries nor noticed that it was included there.
Thanks for this!
The Boot2Gecko people have a source fix for it:
https://bugzilla.mozilla.org/show_bug.cgi?id=1117662
https://github.com/mozilla-b2g/device-hammerhead/commit/c37663f828891cf7a49451a04f3f1ce7f7e5c054
Thanks. It appears that the same lack of patch exists in the M source. I'll try it when I get a chance.
I have used Chroma in the past with minimal issues, but prefer the pure stock over a rom - so my question is; is there any way to use the Chroma Rom Dialer on the stock 5.1.1? (since I know there's several telephony, dialer, phonesky apps/files) I am not sure how I would go about doing that, or what all I would need to change in order to pull it off - if this is even possible at all?
Reason for my question, I like that it has BUILT IN native call blocking ability that the stock dialer doesn't, other than THAT feature it's identical to the stock dialer. I don't care if it's the Chroma dialer, or another rom dialer, I just want the STOCK dialer (or stock-like) to have this ability.
I know there's 3rd party apps for this type of thing, and I've used many of them, but I very much so prefer NOT to have to use a 3rd party app for something that (IMO) should have been built in to begin with.
If you wish to know why this is important to me, read the spoiler:
So, I get ~3-6 calls every day that's just the same BS; Scam calls saying I can lower my CC interest rates and to press 1 to speak to a representative. They always call from a different number, so blocking them individually doesn't work since it's never the same twice (typically - you'll understand after reading below). If you DO press 1 you get a rude person who will cuss at you, call you names, or laugh at you if you ask to be removed from their calling list. Doing that will only make it worse. I've recorded dozens of calls where they say really effed up things to me. Beyond harassment, it's straight up abuse.
I have been getting them for years, I DO NOT own a credit card, never have owned one, and have never even applied for one - plus there's THOUSANDS of pages on Google about these type of calls being a major problem. Even the FCC has a $50,000 bounty for anyone who can legally or illegally stop them - no questions asked (how badass is that!?) - THAT should tell you how hard they are to catch, find, or stop.
After more than 2 years of filing formal complaints/reports with the FCC, Local PD, FBI (as told to by the FCC), USCC, and have seeked legal advice from my lawyer as to getting this stopped via getting a subpoena so uscc has to release the real call origin trace, I'm on the Do Not Call list... - I've been met with ONE solution that has been common on all counts; change my number. That's not really an option, I've had this number since 1997, I'm not about to change it for obvious reasons.
Now, I've tried many apps to get this stopped, ranging from free to paid, and have not found one that ACTUALLY works toward getting it stopped, many are difficult to use or require WAY too much effort and personal information in order to do anything but ask you to donate.
So far I have logged (through Google Voice VM) a growing total of 566 *different* numbers they have called me from - from all over the US and some that are unused anywhere on earth.
In conclusion, Ive logged 566 different numbers that have called me a total of 11,925 times since 2008.
If that isn't justification for this request, then IDK what is. Shy of ditching my phone altogether, I'm out of ideas.
Bumping - I'd really appreciate any help, gents.
iRub1Out said:
Bumping - I'd really appreciate any help, gents.
Click to expand...
Click to collapse
Have no idea. If dialer would work would need boh contacts and dialer apk. Have no idea where the code for that mod is and if ASOP dialer will even work on stock. Then you have odex vs deodex to work through.
If it CANT work on stock (which, honestly, I didn't expect it to) given, as you said, the differences are small on the surface but in the actual build they're very different. I understand that, and those are things I considered leading me to wonder.
Can anyone MAKE the stock dialer with that mod added in, or a otherwise stock rom with that?
It seems like a lot to request, I know, but I've been looking for this for months, I've even set up a bounty in a thread on TUSCC, its something that I've really hoped would become a mod thru xposed or "Pure Shamu" rom with it. However, it seems that others don't experience this ridiculous problem, leading to it not being as popular as I wish it was.
Trying to stop an ex from calling is one thing, but trying to stop every call that isn't a contact, I realize that's quite another. Thus is my case, its crazy how many spoofed numbers they use. I'm more amazed that the carrier hasn't done something than I am that it's not a mod. There's tens of thousands of people with this problem and the one solution that requires no effort on the end user isn't available to cell phone users.
I don't know - I'm just at my wits end with these calls. I'd be happy to do it myself if a dev is willing to give me some direction, or ideas to try out.
As a side note, I've recorded several where I just screw with them for as long as I can - then put it on YT after they realize they've been trolled and blow up. It's a small, yet, satisfying "middle finger" I can do.
iRub1Out said:
If it CANT work on stock (which, honestly, I didn't expect it to) given, as you said, the differences are small on the surface but in the actual build they're very different. I understand that, and those are things I considered leading me to wonder.
Can anyone MAKE the stock dialer with that mod added in, or a otherwise stock rom with that?
It seems like a lot to request, I know, but I've been looking for this for months, I've even set up a bounty in a thread on TUSCC, its something that I've really hoped would become a mod thru xposed or "Pure Shamu" rom with it. However, it seems that others don't experience this ridiculous problem, leading to it not being as popular as I wish it was.
Trying to stop an ex from calling is one thing, but trying to stop every call that isn't a contact, I realize that's quite another. Thus is my case, its crazy how many spoofed numbers they use. I'm more amazed that the carrier hasn't done something than I am that it's not a mod. There's tens of thousands of people with this problem and the one solution that requires no effort on the end user isn't available to cell phone users.
I don't know - I'm just at my wits end with these calls. I'd be happy to do it myself if a dev is willing to give me some direction, or ideas to try out.
Click to expand...
Click to collapse
If I knew what the mod is it would be possible to port to stock. My guess it is in smali which cannot access on stock odex. Stock Would have to be deodexed to access smali which is also possible in rom form. Nobody I know of is deodexing stock 5.1.1 We have done it and got it working but don't post as we still don't know if everything works. Lollipop is still hard to make fully working rom from stock image. M is even going to be harder. Would still need the code required to enable the mod.
prdog1 said:
If I knew what the mod is it would be possible to port to stock. My guess it is in smali which cannot access on stock odex. Stock Would have to be deodexed to access smali which is also possible in rom form. Nobody I know of is deodexing stock 5.1.1 We have done it and got it working but don't post as we still don't know if everything works. Lollipop is still hard to make fully working rom from stock image. M is even going to be harder. Would still need the code required to enable the mod.
Click to expand...
Click to collapse
I concurr, your talking about taking apk's not meant for a certain rom and adding them in to pray it works. Did you look in the market t.o see if there was a KB you liked there? You can't just switch around apk's like that because you could easily get force closes. If you want to try just copy and paste it into a rom. you wont brick doing that, it may work
I know it isn't as easy as swapping apks - I had *hoped* it would be similarly easy, but figured there was no way.
Idk what the mod is, or how Chroma did it - but the dialer looks stock other than the addition of that option under the advanced menu in the dialer settings.
I've looked in the market, used many of them, Mr. Number was my go to for a long time but it is iffy on 5.1 as *sometimes* a call will get through for a couple rings then gets blocked. It would also block known contacts on a rare occasion, I would go a couple days without knowing I had missed a call from a family member because it didn't show up in Mr. Number or the stock dialer - somehow it blocked it and had no record of the call even coming in.
That's why I was hoping to find a way to get this option in the stock dialer - without porting anything or swapping apks, that way it's a native feature to the dialer and I wouldn't have to depend on 3rd party apps to do it.
I've asked Google, but their solution was to add them to one contact and send the calls to VM - while that essentially works, that means I'd have to add all 500+ numbers to a single contact, and they OFTEN call from spoofed numbers I've never seen before - so that really doesn't solve anything.
And no, it isn't having issues paying the "guy" back.
Attempt at humor?
I am having difficulties with Google's (should we be saying Alphabet's?) My Tracks. It is correctly, as far as I can tell, showing altitude. It's just the speed is going hay-wire. I know to find an solution to this I should look through google specific forums.
Although, I would like to take this time, to learn how to do a proper bug report from one of the best communities I have come across. I want to make who ever's job it is easier to understand the issue at hand and be more willing to look into it. Solving it I can always be patient with.
With that in mind, my issue is speed related. As far as I know I need a computer to open a terminal to log what the device is doing. Being on the move makes that impossible. How can I record the information necessary to be used in a thorough bug report.
Then once all the data is collected, what do I look for? Finally, is there a certain format or list of criteria that a bug report should be in that is somewhat universal?
Thank you for your time.
PS: I am rooted, with Pure Nexus.
Many people complain about this and seems like few know about the issue. I should say that I'm not a dev, I just figured it out and tired of writing it after each complaint, which is why I write it as a new thread.
So, in short, there are ways in which gcam speaks with the camera. With RN8(t), we need the app use raw10 rather than raw_sensor for us to be able to have photos. This means that you need a version which either shoots with raw10 by default, or lets you switch from raw_sensor to raw10.
Sadly(?) there are not many that allows this, and almost all are version 6.x ones except Nikita's. The modders I found that allow switch or use raw10 are Nikita, overwhelmer, fu24, wyroczen, and trCam of tigr. There can be others, these are just those that I found. and I did not try each and every one of them. So if you are suffering from this problem, go for these modders' versions.
I may add that I like to use Parrot043's mod, as its output is practically what I want, yet unfortunately it is not usable without raw_sensor. Like his/hers, Arnova8G2's, BSG's, and many others' mods don't (didnt?) work. Yet as they are making new builds every now and then, maybe they will include a switch later on.
I should note that neither of those that I tried can do (good) astrophoto - or it was the case for me. Also none of these managed to produce good shadows (shadows in both Photoshop sense, shadows as shadows, and the transitive area between blacks and whites). On the other hand, it can be a problem with my device as I have seen people shooting pretty fine photos with these - including, interestingly, astrophotos. I just try and wrote my experience. Do NOT rely solely on my experience. Go and try for yourselves. This is just a starting point for those of you that have the problem, not an ultimate guide.
About auxiliary cameras, I cannot say much as I had them working at some point (with a fix from PA devs, I forgot the name of the dev and the patch sadly, and with fu24's version), yet now again they are broken. Funny part is that Paranoid Android claims to have them all working from the start, and other than me, I saw no one complaining that wide and macro don't work. Probably something is broken with my mobile, which is why I cannot say much on the issue.
Of the custom ROMs, I have found only Paranoid Android allowing shooting with raw_sensor. It might be the case with some other ROMs, so you better go check it out for yourselves as well. I can confirm that Pixel Experience and LineageOS did not allow shooting with raw_sensor, but it can change as well. Everything, as we know, comes down to the devs. This is just my experience, and I do not test each and every ROM every other day.
I hope that this will be useful for you, and there won't be complaints about pink/purple lines. This is because of GCam, not ROM builders as such. You can, surely, "force" the ROM builders to include raw_sensor shooting, yet it's up/down to them to do it or not.
So, I hope that this will help you to have a better idea about the problem, and you can solve it easily/easier.