Search results

In light of the latest news about Huawei, we need to develop more of our firmware.:) Sent from my HWPLK using XDA Labs

If you can write code for build libs, if you known how to call any class or function from other class, which located in other lib..You can be helpfull for me) Sent from my HWPLK using XDA Labs

Good result)..I need someone who known good C++..if i want go forward..Thats is my problem.. Sent from my HWPLK using XDA Labs

Run bench on you los14 and share result. Los14 is unusable because camera. Battery life is not big problem for me..It is like the same to los 13. If i have two Honors 7, i will continue work on los14.. Btw..I think stock EMUI battery service can be full implemented to los ...I will think about...

cskNalnw9ew Just info only. Sent from my HWPLK using XDA Labs

Yes, this is one of few reasons..I think biggest one. Sent from my HWPLK using XDA Labs

You have to wipe internal storage. Importante-you will lost all you data stored on this storage.

01-08 14:09:10.300 E/ImagingSystem(2959): virtual android::status_t hw::BnHwCamCfgSvr::onTransact(uint32_t, const android::Parcel&, android::Parcel*, uint32_t): Permission Denial: can't use the camera. I got new message..but i dont known how to undestand what is wrong... Ok, i undestood what is...

Are you kidding?

Main bug not solved in los 14 is camera, camera is not working at all. In los 13 camera is working, but not full properly..

Hi. Just for info..I stoped development of Los 13 and Los 14 for Honor 7. Game over..

Hi guys, look at this. https://pastebin.com/kubbxTtc I am back to los14 camera issue. And carefull this.. 11-04 11:33:08.079 E/Camera3DeviceImpl(3989): int hw::Camera3DeviceImpl::open():ioctl HWCAM_V4L2_IOCTL_MOUNT_BUF failed! ret=-1 11-04 11:33:08.079 E/Camera3Module(3989): static int...

I dont have it any more.

Why are you need it? Never did anythings with this..

It is too optimistic) I am not so optimistic .

Just import it from file.

Device tree have not much difference if compare to los13 device tree. It may say almost the SAME. Important is small things like sepolicy, sound configurations, media codecs and so on..I saw you device tree, vendor and didn't understood why I have bootloop because of audiopolicy...So, it was...

I don't use any patches from you for kernel, believe me. I use just sepolicy update patch for android N. That's all, I don't see any importate changes in kernel source by you. But.. ---------- Post added at 01:20 PM ---------- Previous post was at 01:18 PM ---------- It may be, because I use...

Yes, I have a progress related to camera and I hope soon I will have camera working at least on same level as I have on my los13 build. ---------- Post added at 07:37 AM ---------- Previous post was at 07:34 AM ---------- Yes, this is true. I am working on my closed source.

Maybe better Android P?)))

Big **** is that's camera stuff can not to be easy ported from other similar device, which have android 7.0...and similar IMG mechanism. basically it can be, but need really hard work on it..

No, kernel part is OK. P.S. It is really very disappointing, because all others features are working great, performance is more better as on los13, battery life too..Security also in enforcing mode by me..Only camera big, big splinter in the ass)

Well, if we will undestand why is hwcamcfgsvr crashing...Then we will get a working camera.. This is a crashlog, https://pastebin.com/Lak9J9rz, ...Any ideas will good) Btw this is full crashlog of camera https://pastebin.com/HZGKCdNS So, here is missing only crashed hwcamcfgsvr service...

A reason of update will be if camera will be fixed..In my opinion..All others features are working fine, at least I have.

Do you have blobs from nougat?:confused::eek: That's will be easier)

I think that's camera fix will take a lot time, maybe few month or more..Maybe it will be not fixed at all. I have a feel that's camera issue is inside of camera hal files, which have source not compatible to android 7. Because android 7 have many major changes related to camera..It is really...

Wrong way man..

How did you know that's camera is fixed?:confused:;) when you have a bootloop allways:)

Hwcamcfgsvr is needed by every camera app. You will not able to configure camera sensors without this hardware camera service.

Ok, sure you defined new domain. I am bad teacher too, because /system/bin/glgps47531 u:object_r:gpsd_exec:s0 must to be so defined.

***.. Is it hard to understand? If you have file in bin folder called glgps47531, you have to add domain called also glgps47531! Not gps47531, it was a example from me! Or you have to rename executable from glgps47531 to gps47531..

This is standart definitions of domain for android 7.x.x(here is in cause gpsdaemon) # gpsdaemon daemon type gpsdaemon, domain, domain_deprecated; type gpsdaemon_exec, exec_type, file_type; # Started by init init_daemon_domain(gpsdaemon) As next for gps47531 daemon # gps47531 daemon type...

It is really hard look for a black cat in a dark room, especially if it is not there. Any daemon will never started in android 7, if it is not defined in Selinux policy..And does not matter is it permissive mode Selinux..And look to the previous posts..

I have a feel this is gapps bug..

Hm..You was able access my bitbucket git for long time..Why you didnt useed it??? So, for full gps fix you have at least define gps47531 selinux domain and add few important rules to this domain..Look in logs for avc..

I don't know what you already fixed. GPS? IR sensor? WiFi hotspot? WiFi direct? Gyro sensor? HD video playback? Sdcard? Ussd code? Dualsim? Phone profiles? ..And more..

What is reason of OTA update? If most of main features are not working..

If you have 47531c1 chip..ofcause:silly: you can find correct info here

***** what i sad befor? If you have 47531 chip..you need only files related to 47531, all others you have delete, this is garbage! Look to screenshots

Ok, i hope you removed also not needed daemons from init.connectivity.gps.rc too.

You dont undestand what means official? It means for example camera source, sensors source and many more related to hardware..

It will be never official, because it can not to be official!

Then you have to undestand one small think first. Huawei make multiplatform(multidevice) firmware, this cause it content hal, binary, configs for many peripheral chips..(just garbage in our case) Lineageos is not multiplatform. Ofcause it possible to do it, but first you habe build a Rom for one...

Have you also 47531 GPS chip too?

I must to be helpfull. But i use other one, which is more time better in my opinion.. ---------- Post added at 02:11 PM ---------- Previous post was at 02:06 PM ---------- Is a device tree and vendor in you git actually? Because i need to undestand how you try to fix it by you build.

2.2

I dont think thats is helpfull for us. But anyway thks:)

You can usw carliv kitchen to repack Boot.

Ok, clear.. Because it used OMX.google.h264.encoder, not HW.