28-05-2015
Hi all, i have update mu l90-d405n to lollipop 5.0.2, lg have complicated the infrared, i has thinking that they may put google native code to control infrared, no luck, google function consumerIRmanager return false, the 5.0.2 version cames with quicksetSDK version 1.73 they alter the way the service is implemented, had a hard time to test a way send the raw codes, the lg sample sdk does not work with quickset version 1.73.
To send raw codes with android 5.0.2 must be root, delete the directory /system/app/QuicksetSDK, then install QuicksetSDK version 1.69, reboot and the lg sample sdk works, use qremote to create a remote, then install my app and send raw ir works.
Sucess, its possible to send raw ir codes with L90.
Hi, i am trying to send a raw ir hex code from my phone, but until now no sucess.
The lg suport toll me that que hardware wasnt compatible with that, so i'm trying to find a solution.
Hipotese 1: use learn funtion of qremote sdk
Hipotese 2: use function send raw ir of qremote sdk
Hipotese 3: add a new raw ir code to the database of lg qremote
Hipotese 1, does not work
the learn function return false, the lg L90 does not have ir led receiver or the learn function is not implemented in kernel
Hipotese 2, does not work, the funtion return sucessfull but nothing is send by the ir, the funtion works on the g3, so maybe that function is not implemented in the kernel of L90
Hipotese 3, i have take a look inside the the app lgqremote and quicksetsdk but can find a database
Question: how or where is the qremote app from lg getting the codes to send to the ir ?
I have take a look at the qremote sdk and inside it, in the setup function it looks for the existence of quicksetsdk, so where is the qremote app getting the codes to send to ir ?
to be continue....................
Hi, tested the ConsumerIrManager API 19, the result was emiter not found, i test it in stock rom android 4.4.2, can any one with stock lollipop, maybe lg implemented that funtion in the new version.
to be continue............
Hi all, did a few more test, i copy the g3 qremote.apk and quicksetsdk.apk to L90, the infrared does not get detected, then try with the g2 version, the infrared get detected but qremote cant get the list of the remotes.
Can anyone with L90 d410 with stock lollipop put here the files:
- LGQremote.apk
- QuicksetSDK.apk
I like to test it to see what i can learn from it.
Can anyone anser the this question, does qremote lollipop version of L90 bring the same number os remote manufactures ?
Thanks.
Guys, check the LG G Pad 7 forum. They got the IR working on cm12 and maybe they can help with the IR on L90.
Edit:
The g pad 7 forum is inside the g pad 10.1 forum if you cannot find it. Maybe you can ask for help from invisiblek.
Sent from my LG-D415 using XDA Premium App
Thanks, going to see that.
hal_2000 said:
Hi all, did a few more test, i copy the g3 qremote.apk and quicksetsdk.apk to L90, the infrared does not get detected, then try with the g2 version, the infrared get detected but qremote cant get the list of the remotes.
Can anyone with L90 d410 with stock lollipop put here the files:
- LGQremote.apk
- QuicksetSDK.apk
I like to test it to see what i can learn from it.
Can anyone anser the this question, does qremote lollipop version of L90 bring the same number os remote manufactures ?
Thanks.
Click to expand...
Click to collapse
I can't find those files, there are however :
QuickRemote 4.40.14
Quickset SDK Lite 0.1.69
Hi gorankx, those are the files, i didnt put the version, those files are on stock lollipop of L90 ?
Can you put then here so i can make test it ?
Thanks.
Here it is
Hi gorankx, thanks for the files, going to test them.
One question, is lollipop on L90 fast ? and the batery last the same time ?
Hi, i have found the database file of qremote, is in /data/data/com.lge.qremote/databases/qremotesettings.db the db only has the info of the devices that you configure in a room of the qremote app, and it does not give the full info of the device, only gives device id, function id code, manufacture, it does not contain the data of the pulse and duration that is send to the infrared...... :crying:
On the other hand, there is a file devices.xml is not a realy a xml file, look like a binary file, that also gets update when we add a device in qremote app, that file is big, 30k to 40k in size is added to that file when we add a device, maybe that file contain the data pulse, the raw command codes
going to do more tests..........
To be continue................
hal_2000 said:
Hi gorankx, thanks for the files, going to test them.
One question, is lollipop on L90 fast ? and the batery last the same time ?
Click to expand...
Click to collapse
Good luck, LP is pretty good and battery life is also good but thats after hard reset, which i had to do
SUCESS, it works !!!
Hi, thanks to gorankx files it worked, the lgqremote.apk file is currupt it doesnt get recognize, but that doesnt matter because that is just a frontend with buttons, the real magic is on quicksetsdk.apk, that file has the info about the ir brands and codes, and its responsavel for the comunication with ir hardware, the lollipop version compare to kitkat has one more file "librctransport.so" , i think that lib is responsivel for sending raw codes.
When i tested the new quicksetsdk with qremote sdk it WORKED, we can now send raw ir codes from the L90, there is a small bug, with syncrony, dont know it is a problem with the lib, the file provably was compile for android 5 not 4.4, or if is bad implementation of sendirpattern function of qremote sdk, so the way i found to work must of the times is click 3 times on the power button of qremote apk and then click on raw ir button and the raw code gets transmited, i managed to turn on my tv (the lg app does not have my tv brand).
So thanks again to gorankx user, and lg for compile a new version quicksetsdk that works, it was ridiculous having a phone with infrared and dont be able to send ir raw codes.
Going to write a app to control my tv, this project is close successfully.
Thanks.
Is it possible to install on CM12 ROM? I am not able to install it...
hal_2000 said:
SUCESS, it works !!!
Hi, thanks to gorankx files it worked, the lgqremote.apk file is currupt it doesnt get recognize, but that doesnt matter because that is just a frontend with buttons, the real magic is on quicksetsdk.apk, that file has the info about the ir brands and codes, and its responsavel for the comunication with ir hardware, the lollipop version compare to kitkat has one more file "librctransport.so" , i think that lib is responsivel for sending raw codes.
When i tested the new quicksetsdk with qremote sdk it WORKED, we can now send raw ir codes from the L90, there is a small bug, with syncrony, dont know it is a problem with the lib, the file provably was compile for android 5 not 4.4, or if is bad implementation of sendirpattern function of qremote sdk, so the way i found to work must of the times is click 3 times on the power button of qremote apk and then click on raw ir button and the raw code gets transmited, i managed to turn on my tv (the lg app does not have my tv brand).
So thanks again to gorankx user, and lg for compile a new version quicksetsdk that works, it was ridiculous having a phone with infrared and dont be able to send ir raw codes.
Going to write a app to control my tv, this project is close successfully.
Thanks.
Click to expand...
Click to collapse
Will you develop and publish with us the app? My bedroom TV is a blaupunkt and the LG app doesn't have it either. Thanks in advance.
Sent from my LG-D405n using XDA Free mobile app
I'm glad i could help, could you explain us bit more, how that works, about raw codes?
Hi,
wizzardsk
it should be possible to install on cm12, must be root, quicksetsdk runs a service and i think it needs root to run it.
Disrupthorblaupunkt
I dont have a blaupunkt tv, you need the raw ir codes for that command.
i am thinking in making a very simple app, just to control my tv, but i can put a spinner that reads a file with raw codes in it, and then you add raw codes to that file and it should work with your tv, i havent start it yet, may take some time.
gorankx
Hi, thanks again, your file saved me a lot of work, i was trying to figure the format that lg puts in the device.xml so i could add more devices.
Your question, are you asking what is a ir raw code ?
R: infrared information is transmited in pulses, it based on a diod that is on/off, a raw code as information on frequency of transmition and duration of time of on state and off state, all remotes, all the keys function can be express with a raw code, one raw code for a key.
example lg power on, frequency = 38000 hz
// An example to send raw IR data, from qremote sdk
private void sendLgTvPower()
{
// test sendIRPattern()
int[] LGTVPower = {9000, 4500, 578, 552, 578, 552, 578, 1684, 578, 552, 578, 552, 578, 552,
578, 552, 578, 552, 578, 1684, 578, 1684, 578, 552, 578, 1684, 578, 1684, 578,
1684, 578, 1684, 578, 1684, 578, 552, 578, 552, 578, 552, 578, 1684, 578, 552, 578,
552, 578, 552, 578, 552, 578, 1684, 578, 1684, 578, 1684, 578, 552, 578, 1684, 578,
1684, 578, 1684, 578, 1684, 578, 39342, 9000, 2236, 578, 96184, 9000, 2236, 578,
96184};
mIR.sendIRPattern(38000, LGTVPower);
}
the numbers in the array represent the time in miliseconds that the diod in on, then off, then on.......etc
remote central has lots of raw ir codes for many devices, they are express in hex pronto codes, lg function need decimal numbers.
hope that helps.
So basically we can control any IR device by setting raw codes, btw where we can find raw codes, is there some kind web site or something like that with raw codes for different devices?
And i hope you can make app that makes process of adding new models easily. Well, wish you best!!!
hal_2000 said:
Hi,
wizzardsk
it should be possible to install on cm12, must be root, quicksetsdk runs a service and i think it needs root to run it.
Click to expand...
Click to collapse
Well, it does not work. I am root, of course, I installed quicksetsdk and I could not install the other app anyway (after installing: the app was not installed.)
Quick Remote for CISCO Set Top Box
How can I use LG L90 Quick Remote with CISCO z260 Set Top Box?
wizzardsk said:
Well, it does not work. I am root, of course, I installed quicksetsdk and I could not install the other app anyway (after installing: the app was not installed.)
Click to expand...
Click to collapse
Hi, quicksetsdk.apk installs a service to comunicate with ir hardware, it does not show anything to user, qremote.apk is a frontend with buttons, on that app when you click on a button it send a message to the service of quicksetsdk, and then the service sends the code to ir hardware.
On lg phone you need quicksetsdk to install the service, and qremote.apk or qremote sdk sample to be the frontend to be able to work with ir.
Related
any developer can port HTC one max camera ?
darkidz555 said:
any developer can port HTC one max camera ?
Click to expand...
Click to collapse
Why? They are esentially the same AFAIK
Because HTC one max can capture picture with with ourself in it like Samsung s4 can use back camera capture picture while using front camera to include us inside
Sent from my HTC One using xda app-developers app
darkidz555 said:
Because HTC one max can capture picture with with ourself in it like Samsung s4 can use back camera capture picture while using front camera to include us inside
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Have you tried simply installing it yet? I'm thinking Sense 5.5 framework is Sense 5.5 framework... If you haven't, here is a flashable of the One Max camera. It may need some libs to go along with it...but try it and let me know. If you get any crashes, get me a log during the crash and if it's missing libs I can pull them too..
homeslice976 said:
Have you tried simply installing it yet? I'm thinking Sense 5.5 framework is Sense 5.5 framework... If you haven't, here is a flashable of the One Max camera. I've renamed the apk to Camera2 so ut won't overwrite the current camera. It may need some libs to go along with it...but try it and let me know. If you get any crashes, get me a log during the crash and if it's missing libs I can pull them too..
Click to expand...
Click to collapse
I`ve just checkt it... I replaced it with the original .apk because the installation is not working this way... so there is no extra camera app in app drawer. Anyway... as I said, I replaced the original file and the camera starts. But there is no difference... means I cant find an option for the portrait/main camera effect. Should there be an extra icon or a option in camera settings?
BanBoo said:
I`ve just checkt it... I replaced it with the original .apk because the installation is not working this way... so there is no extra camera app in app drawer. Anyway... as I said, I replaced the original file and the camera starts. But there is no difference... means I cant find an option for the portrait/main camera effect. Should there be an extra icon or a option in camera settings?
Click to expand...
Click to collapse
i have no idea. I'm not running sense at the moment and I don't have a max. That's the camera apk pulled from a One Max stock/rooted ROM. I would have assumed it would be a camera mode.. if i get a minute to flash a sense rom this afternoon i'll look at it.
Edit: Dual mode didn't show up for me either. After tearing apart out sense 5.5 camera and the one max 5.5 camera, both contain the code for dual camera mode, so it must be getting activated by a flag somewhere else? I'll keep looking.
Edit 2: @BanBoo I managed to get it enabled (screenshot) but the picture doesn't actually take/save, and the second camera preview is black. Still playing
Edit3: Any suggestions from the pros?
Code:
W/CameraDeviceManager( 6014): openCamera(Front)
W/CameraController( 6014): openCamera(Front)
E/QualcommCamera( 255): ERR!! camera is opened and cameraId didn't match! now 0 new 1
E/CameraClient( 255): Could not open camera 1: -1
E/CameraClient( 255): initialize: Camera 1: unable to initialize device: Operation not permitted (-1)
W/CameraBase( 6014): An error occurred while connecting to camera: 1
W/HTCCamera( 6014): onPreviewStarted() - Invalid handle
E/CameraDeviceManager( 6014): openCamera() - Fail to open camera
E/CameraDeviceManager( 6014): java.lang.RuntimeException: Fail to connect to camera service
E/CameraDeviceManager( 6014): at android.hardware.Camera.native_setup(Native Method)
E/CameraDeviceManager( 6014): at android.hardware.Camera.<init>(Camera.java)
E/CameraDeviceManager( 6014): at android.hardware.Camera.open(Camera.java)
E/CameraDeviceManager( 6014): at com.android.camera.CameraController.openCamera(CameraController.java:400)
E/CameraDeviceManager( 6014): at com.android.camera.CameraController.<init>(CameraController.java:229)
E/CameraDeviceManager( 6014): at com.android.camera.component.CameraDeviceManager.openCamera(CameraDeviceManager.java:323)
E/CameraDeviceManager( 6014): at com.android.camera.dualcamera.DualCameraController.openSecondaryCamera(DualCameraController.java:1339)
E/CameraDeviceManager( 6014): at com.android.camera.dualcamera.DualCameraController.startSecondaryPreview(DualCameraController.java:1704)
E/CameraDeviceManager( 6014): at com.android.camera.dualcamera.DualCameraController.onPreviewAdapterCreated(DualCameraController.java:1082)
E/CameraDeviceManager( 6014): at com.android.camera.dualcamera.DualCameraController.handleMessage(DualCameraController.java:724)
E/CameraDeviceManager( 6014): at com.android.camera.component.Component$MessageHandler.handleMessage(Component.java:70)
E/CameraDeviceManager( 6014): at android.os.Handler.dispatchMessage(Handler.java)
E/CameraDeviceManager( 6014): at android.os.Looper.loop(Looper.java)
E/CameraDeviceManager( 6014): at com.android.camera.CameraThread.run(CameraThread.java:2811)
E/DualCameraController( 6014): openSecondaryCamera() - Fail to open camera : Unknown
Maybe the Camera.apk checks your build.prob to see if its a One or a One Max and enable the feature? What if you change your model ID to match the Model ID of the One Max
solracarevir said:
Maybe the Camera.apk checks your build.prob to see if its a One or a One Max and enable the feature? What if you change your model ID to match the Model ID of the One Max
Click to expand...
Click to collapse
Good suggestion but no-go. I'd imagine a check like that would just be to enable the feature,which I managed to do a little differently.. according to the log it looks like it's not identifying the cameras properly once in dual capture mode.. but I don't yet know where/when they're identified
Sent from my HTC6600LVW using Tapatalk 4
How did you get the other options to show up in the camera, or can you link a copy of what you did
it seems that is working, tried it on 4.4.2, but no OAD support..
to enable it add the following line to android/system/device/motorola/omap4-common/common.mk
frameworks/native/data/etc/android.hardware.bluetooth_le.xml:system/etc/permissions/android.hardware.bluetooth_le.xml
next to
frameworks/native/data/etc/android.hardware.usb.host.xml:system/etc/permissions/android.hardware.usb.host.xml \
and (device specific) system/device/motorola/maserati/bluetooth/bdroid_buildcfg.h
#define BTA_DM_COD {0x1A, 0x01, 0x14}
#define BTIF_HF_SERVICES (BTA_HSP_SERVICE_MASK)
#define BTIF_HF_SERVICE_NAMES { BTIF_HSAG_SERVICE_NAME }
#define PAN_NAP_DISABLED TRUE
#define BLE_INCLUDED TRUE
#define BTA_GATT_INCLUDED TRUE
#define SMP_INCLUDED TRUE
after
#define BTM_DEF_LOCAL_NAME "Motorola Droid 4"
tried with new bluetooth firmware from https://github.com/TI-ECS/bt-firmware, is working but is not stable.
the default firmware is working well with the sensor tags
lucize said:
it seems that is working, tried it on 4.4.2, but no OAD support..
Click to expand...
Click to collapse
Great
I've just pushed your changes to my repositories, so they will be included in tomorrows nightly.
Merry Christmas,
Michael
Merry Christmas to everyone !
All devices that have the TIInit_10.6.15.bts firmware should work so maybe this would be of help for someone else, maybe you can talk with Hashcode or David to enable it on every device. 4.3 should work too !
Regards
lucize said:
All devices that have the TIInit_10.6.15.bts firmware should work so maybe this would be of help for someone else, maybe you can talk with Hashcode or David to enable it on every device. 4.3 should work too !
Click to expand...
Click to collapse
Ok, short gerrit crash-course
Configure your local git to commit with the name and email-address you want to be visible in public repositories
Create an account on http://review.cyanogenmod.org/
Upload an ssh public key there
Clone the repository you want to change with something like:
Code:
git clone ssh://[email protected]:29418/CyanogenMod/android_device_motorola_omap4-common
(This is not necessary if you are working on a direct CM clone and have no other changes in your repository)
Make your changes, commit them
Push your changes to gerrit:
Code:
git push ssh://[email protected]:29418/CyanogenMod/android_device_motorola_omap4-common HEAD:refs/for/cm-11.0
This will tell you an URL where your change is visible.
Go to that URL and add reviewers to your change. For example: Hashcode, David Hacker and probably me (Michael Gernoth)
If your change is acceptable, it will get merged into the CM repository
That's all, no great magic
For more info, have a look at: http://review.cyanogenmod.org/Documentation/user-upload.html
Best regards & thanks for your work,
Michael
lucize said:
Merry Christmas to everyone !
All devices that have the TIInit_10.6.15.bts firmware should work so maybe this would be of help for someone else, maybe you can talk with Hashcode or David to enable it on every device. 4.3 should work too !
Regards
Click to expand...
Click to collapse
Is that firmware part of CM11 or something that I'd have to install manually onto my Droid 4? If so, how does one upgrade the Bluetooth firmware?
bofis said:
Is that firmware part of CM11 or something that I'd have to install manually onto my Droid 4? If so, how does one upgrade the Bluetooth firmware?
Click to expand...
Click to collapse
is part of cm11, you can find it in /etc/firmware/
you can find it here
https://github.com/TI-ECS/bt-firmware/commits/master this is the history page where you can find various versions, but the last version from December won't load and the rest will not work with the headset (no sound)
htc one x has the same bluetooth chip and has a newer version of firmware, but the sound on headset will not work either, everything else seems to work
you can see the version at the beginning of the file, motorola has TI_P6_15.56
to update, turn bluetooth off, simply overwrite the file and the turn it on again.
I noticed that this eventually made it to CM11 for all of Moto OMAP cousins, except for the Bionic (Targa). Any reason that the Targa was left out? A lack of hardware support, or was it just never tested?
guyincog said:
I noticed that this eventually made it to CM11 for all of Moto OMAP cousins, except for the Bionic (Targa). Any reason that the Targa was left out? A lack of hardware support, or was it just never tested?
Click to expand...
Click to collapse
I don't know if it has the proper chip but the firmware is correct so it should be possible. I don't have one to test.
Regards
lucize said:
I don't know if it has the proper chip but the firmware is correct so it should be possible. I don't have one to test.
Regards
Click to expand...
Click to collapse
Thanks for the reply. I've got one, maybe I'll see if I can talk one of the builders for the Bionic will make a test build with the necessary common.mk change.
I apprciate the work on this, and the kernel update you've got in progress. Any extra features we can add to these old devices is a huge bonus.
This might be the wrong place to ask this, but does CM11 or CM11 on our phone support the APTX codec via Bluetooth?
bofis said:
This might be the wrong place to ask this, but does CM11 or CM11 on our phone support the APTX codec via Bluetooth?
Click to expand...
Click to collapse
it has the hardware support
http://www.aptx.com/product/motorola-razr-maxx-smartphone
but don't know about the rest of the things
This app has been heavily inspired by SabrWolfs [APP][ROOT] Touch screen fixer.
The app is supposed to at least temporarily improve the touch on the Oneplus one, making the device usable. I can't guarantee that it works for you, but it makes a big difference for me.
The app requires root, and executes the shell command cat /sys/class/input/input0/baseline_test every time the screen is turned on. It is not based on Tasker, but implemented as an ordinary app. The difference compared to Touch screen fixer, and the reason I made this app, is that the vibration is configurable. I initially implemented this app to be able to deactivate the vibration entirely, but since it actually takes a second or two to run the command and get touch working again, I found that I actually prefer a very brief vibration as feedback that the device is ready for use.
As usual with root apps, don’t forget to grant the app root access the first time it is started, otherwise it won’t work.
And as always, I can't take any responsibility if this app makes your house to burn down, your car to explode or your phone to overheat
Edit:
Here is the complete code:
https://github.com/jaqob/OnePlusTouchFix
It was not really intended to be shared, so be gentle
Allot of users have been helped by flashing a different ROM, so it's kind of ROM related I guess.
Therefor it might be best to tell people which ROM you are using.
Gamm86 said:
Allot of users have been helped by flashing a different ROM, so it's kind of ROM related I guess.
Therefor it might be best to tell people which ROM you are using.
Click to expand...
Click to collapse
I'm using stock 12.0-YNG1TAS2I3, the latest offical CyanogenMod release. But, the same problem existed before as well, so it is not directly related to a specific ROM.
102 downloads and not a single reply or thank you..
I can't give any feedback,i never had any problems with my touchscreen.
But Thanx for posting your work and apparently your app works as intended or there would have been a S...storm.
zodiaxe66 said:
102 downloads and not a single reply or thank you..
I can't give any feedback,i never had any problems with my touchscreen.
But Thanx for posting your work and apparently your app works as intended or there would have been a S...storm.
Click to expand...
Click to collapse
Yes, this must be the first bug free app ever
let me try and giv u a result
As the result, i do feel different in touch screen. Much more sensitive
Thanks will try it
Could anybody explain why cat-ting a file (i.e. just read a file content) can fix some issue?
May I see the source code of this apk?
Am using oxygen os from day 1 and never had suck issue.
Though i had some problem in cyanogenmod nightlies so reverted back to stock oxygenated n os
Sent from my A0001 using XDA Free mobile app
dxxvi said:
Could anybody explain why cat-ting a file (i.e. just read a file content) can fix some issue?
May I see the source code of this apk?
Click to expand...
Click to collapse
The relevant part really just looks like this
Code:
public static int runTouchFixCommand()
{
int result = -1;
try {
Process p = Runtime.getRuntime().exec(new String[]{"su","-c","cat /sys/class/input/input0/baseline_test"});
result = p.waitFor();
} catch (IOException | InterruptedException e) {
e.printStackTrace();
}
return result;
}
The key here is that it is the /sys folder. It is not an ordinary filesystem but a virtual one used to communicate with different attached devices, in this case the synaptic touch driver.
See wikipedia for some further details: https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard#FHS_compliance
If I understand things correctly, reading baseline_test will run this code:
https://github.com/CyanogenMod/andr...s/input/touchscreen/synaptics_dsx_i2c.c#L1780
Which near the end does this "//step 5:reset touchpanel and reconfig the device".
Or it may just be magic
Edit:
Here is the complete code:
https://github.com/jaqob/OnePlusTouchFix
It was not really intended to be shared, so be gentle
Definitely works very well. I was using SabrWolf fix before this, thanks for the additional vibration duration option.
Unfortunately this app seems to be needed for CM12.1 as well. Fortunately it still works
Is it possible to make updates or make new version for CAF build rom?
This apps work well on Slimsaber but didn't work on sultanxda Caf build...when I use it on I got this popup "fail to excute command, is you phone rooted?"....both rom is rooted btw...
Sent from my A0001 using Tapatalk
nice app i think
since i didnt encounter any touch issue in my OPO since day 1
cant say any, but its a good job
u should try to implement it in xposed and caf
iPusak Gaoq™ said:
Is it possible to make updates or make new version for CAF build rom?
This apps work well on Slimsaber but didn't work on sultanxda Caf build...when I use it on I got this popup "fail to excute command, is you phone rooted?"....both rom is rooted btw...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I haven't tested any CAF build (perhaps I should), but in the sultanxda case, I would guess this line in the description is to blame "Rewrote half of the Synaptics touchscreen driver (over 2500 lines of code modified; your touchscreen might work better)". The function my small app relies on (synaptics_rmi4_baseline_data in synaptics_dsx_i2c.c) is removed. So I'm afraid I can't get it to work there.
wrinkletit said:
nice app i think
since i didnt encounter any touch issue in my OPO since day 1
cant say any, but its a good job
u should try to implement it in xposed and caf
Click to expand...
Click to collapse
I have worked a bit with xposed, but I don't really see any gain to use it for this purpose..?
iPusak Gaoq™ said:
Is it possible to make updates or make new version for CAF build rom?
This apps work well on Slimsaber but didn't work on sultanxda Caf build...when I use it on I got this popup "fail to excute command, is you phone rooted?"....both rom is rooted btw...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I have tried Sultans CM12 version, with the CAF kernel now, and my phone is working better then it ever have. No problem with the touch, so no need for this app, at least not for me.
Hey all,
the problme is that the international version has another cam module (13mp) than the chinese version (18mp).
Therefore the custom roms , which are always based on the chinese version and cant use the camera.
Now I need some help on how to implement the driver from the original firmware:
http://rom.download.nubia.com/Germany/Z9mini/NX511J-update.zip
Into this custom rom from mokee:
http://download.mokeedev.com/?device=nx511j
My phone is already rooted and has a custom reovery. I already tried to "zip-edit" the mokee rom and copied/replaced files from the stock rom into the mokee rom , base on this info from here and here e.g.:
Libcamalgo.so
Libcameracustom.so
Libcameraclient.so
Libcameraservice.so
Libcamerametadata.so
and
system/lib/ libcamdrv.so
system/lib/libcamalgo.so
system/lib/libcameracustom.so
system/lib/libdpframework.so
system\etc\permissions\android.hardware.camera.xml
and then rezipped the rom and signed the zip with the autosign tool.
This "custom" rom than could even be successfuly installed with twrp without an problem, but then didnt
get beyond the mokee boot logo.
Now my question is:
Can this be due to the fact that the stock rom is 5.02 and the custom rom/mokee is 6.01 and the drivers simply cant work due to another android version?
Am I thinking way to easy with this simple "copy/paste zip editing" and something more complex like editing the kernel has to be done?
Any tip for what to do is very appreciated, as I think I have to solve it by myself due to a lack of mass-interest in this device.
Does it support Indian version?
Sent from my NX511J using XDA-Developers mobile app
Sorry for my late reply, I've been on vacation.
I dont know if it supports the indian version. My device is the EU version I guess...
It has a different camera module whith only 13mp-
Hi!
Just replacing those files can't work. The drivers for the t4k37 camera sensor aren't built in in the mokee release.
When it boots, it only polls those Sony IMX sensors. Furthermore the librarys for the t4k37 sensor arent't in the rom.
I'vre tried to build my own mokee rom, but with no luck, got only to boot animation. The device isn't supported officialy by
Mokee any longer. As I didn't build android before, my knowledge is obviously too little for this kind of task... perhaps some
more experienced guys could help...
Also it's hard to understand what is the exact difference in the chinese, indian , international an german modells of the phone, there are little informations.
Just flashed Mokee MK51.1-nx511j-160420-HISTORY.zip and moved the appropriate libraries to the flash, it seems, that the t4k37 sensor initializes and works. Sadly there's no camera app preinstalled.
Tested with Open Camera App from Playstore. I'll now try to get the original camera app.
Libraries where taken from germans stock rom in vendor folder.
kai4065 said:
Just flashed Mokee MK51.1-nx511j-160420-HISTORY.zip and moved the appropriate libraries to the flash, it seems, that the t4k37 sensor initializes and works. Sadly there's no camera app preinstalled.
Tested with Open Camera App from Playstore. I'll now try to get the original camera app.
Libraries where taken from germans stock rom in vendor folder.
Click to expand...
Click to collapse
Hi kai4065!
Can you give me more info please. Which file list I need to replace. I need to create patch for one of localized firmware. Also may be you know where I can get last de firmware? My device was flashed with NX511J_DECommon_V1.01 now but buyed with 1.02.
Thx for any help.
falkolab said:
Hi kai4065!
Can you give me more info please. Which file list I need to replace. I need to create patch for one of localized firmware. Also may be you know where I can get last de firmware? My device was flashed with NX511J_DECommon_V1.01 now but buyed with 1.02.
Thx for any help.
Click to expand...
Click to collapse
Here's the list:
# Camera
etc/firmware/cpp_firmware_v1_4_0.fw
etc/firmware/cpp_firmware_v1_2_0.fw
etc/firmware/cpp_firmware_v1_1_6.fw
etc/firmware/cpp_firmware_v1_1_1.fw
-lib/libmm-qcamera.so
-lib/libmorpho_jpeg_io.so
-lib/libmmjpeg_interface.so
-lib/libqomx_core.so
-lib/libmorpho_memory_allocator.so
-lib/libmmcamera_interface.so
-lib/libmorpho_strobe_photo_jni.so
-lib/libmorpho_image_converter.so
-lib64/libmorpho_jpeg_io.so
-lib64/libmorpho_memory_allocator.so
-lib64/libmorpho_image_converter.so
lib/hw/camera.msm8916.so
bin/mm-qcamera-daemon
bin/mm-qcamera-app
vendor/lib/libmmcamera_faceproc.so
vendor/lib/libchromatix_ov5648_p5v18g_common.so
vendor/lib/libchromatix_skuf_ov5648_p5v23c_snapshot.so
vendor/lib/libactuator_rohm_bu64297gwz.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_preview.so
vendor/lib/libmmcamera_t4k35.so
vendor/lib/libmmcamera2_stats_modules.so
vendor/lib/libactuator_bu64291gwz.so
vendor/lib/libmmcamera2_stats_algorithm.so
vendor/lib/libjpegdhw.so
vendor/lib/libmmcamera_t4k37_qtech_f4k37ab.so
vendor/lib/libmmcamera2_c2d_module.so
vendor/lib/libmmcamera2_cpp_module.so
vendor/lib/libmmcamera2_vpe_module.so
vendor/lib/libmmcamera_ov2720.so
vendor/lib/libmmcamera_S5K4E1_13P1BA.so
vendor/lib/libchromatix_t4k35_nightmode_1.so
vendor/lib/libmmipl.so
vendor/lib/libchromatix_t4k35_common.so
vendor/lib/libchromatix_ov2720_preview.so
vendor/lib/libmmcamera_sunny_q5v22e_eeprom.so
vendor/lib/libjpegehw.so
vendor/lib/libmmcamera2_sensor_modules.so
vendor/lib/libchromatix_ov5648_q5v22e_zsl.so
vendor/lib/libchromatix_ov5648_oty5f03_common.so
vendor/lib/libmmcamera_sp1628.so
vendor/lib/libmmcamera_skuf_ov5648_p5v23c.so
vendor/lib/libmmQSM.so
vendor/lib/libactuator_bu64291gwz_t4k35.so
vendor/lib/libmmcamera_wavelet_lib.so
vendor/lib/libchromatix_t4k35_preview.so
vendor/lib/libchromatix_t4k35_hfr_120.so
vendor/lib/libmmcamera2_pproc_modules.so
vendor/lib/libmmcamera_imx132.so
vendor/lib/libmmjpeg.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_snapshot.so
vendor/lib/libchromatix_ov5648_oty5f03_default_video.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_nightmode.so
vendor/lib/libactuator_bu64291gwz_camcorder.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_common.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_default_video.so
vendor/lib/libmmcamera_tintless_algo.so
vendor/lib/libmmcamera_ov5648_oty5f03.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_video_hd.so
vendor/lib/libactuator_bu64291gwz_camera.so
vendor/lib/libchromatix_t4k35_default_video.so
vendor/lib/libmmcamera2_wnr_module.so
vendor/lib/liboemcamera.so
vendor/lib/libactuator_bu64291gwz_t4k35_camcorder.so
vendor/lib/libchromatix_ov5648_preview.so
vendor/lib/libmmcamera_ov5648.so
vendor/lib/libmmcamera_ov5648_p5v18g.so
vendor/lib/libchromatix_ov5648_q5v22e_preview.so
vendor/lib/libchromatix_t4k35_snapshot.so
vendor/lib/libchromatix_ov5648_p5v18g_preview.so
vendor/lib/libmmcamera2_isp_modules.so
vendor/lib/libchromatix_ov5648_q5v22e_snapshot.so
vendor/lib/libmm-qdcm.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_hfr_120.so
vendor/lib/libchromatix_t4k35_nightmode.so
vendor/lib/libmmqjpeg_codec.so
vendor/lib/libchromatix_ov5648_q5v22e_common.so
vendor/lib/libmmcamera2_imglib_modules.so
vendor/lib/libmmcamera_tintless_bg_pca_algo.so
vendor/lib/libchromatix_ov5648_p5v18g_default_video.so
vendor/lib/libchromatix_ov5648_q5v22e_default_video_hd.so
vendor/lib/libchromatix_ov5648_common.so
vendor/lib/libchromatix_ov5648_oty5f03_snapshot.so
vendor/lib/libmmcamera_imglib.so
vendor/lib/libmmcamera_hdr_gb_lib.so
vendor/lib/libchromatix_ov5648_p5v18g_default_video_hd.so
vendor/lib/libmmcamera2_frame_algorithm.so
vendor/lib/libmmcamera_hi256.so
vendor/lib/libmmcamera2_iface_modules.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_liveshot.so
vendor/lib/libchromatix_skuf_ov5648_p5v23c_common.so
vendor/lib/libchromatix_ov5648_default_video.so
vendor/lib/libchromatix_skuf_ov5648_p5v23c_default_video.so
vendor/lib/libchromatix_ov5648_p5v18g_zsl.so
vendor/lib/libqomx_jpegdec.so
vendor/lib/libchromatix_ov5648_snapshot.so
vendor/lib/libchromatix_ov5648_oty5f03_preview.so
vendor/lib/libmmcamera_hdr_lib.so
vendor/lib/libmmcamera_ov5648_q5v22e.so
vendor/lib/libactuator_bu64291gwz_t4k35_camera.so
vendor/lib/libchromatix_ov5648_oty5f03_zsl.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_pre4zsl.so
vendor/lib/libchromatix_ov5648_zsl.so
vendor/lib/libqomx_jpegenc.so
vendor/lib/libchromatix_ov5648_q5v22e_default_video.so
vendor/lib/libmmcamera_ov5645.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_nightmode_1.so
vendor/lib/libmmcamera2_is.so
vendor/lib64/libmmcamera2_stats_algorithm.so
vendor/lib64/libchromatix_imx214_hfr_60fps.so
vendor/lib64/libchromatix_imx219_q8n13a_common.so
vendor/lib64/libactuator_rohm_bu64297gwz_camcorder.so
vendor/lib64/libchromatix_imx214_default_video_4k.so
vendor/lib64/libchromatix_imx214_nightmode_1.so
vendor/lib64/libchromatix_imx219_q8n13a_default_video.so
vendor/lib64/libchromatix_imx219_q8n13a_liveshot.so
vendor/lib64/libchromatix_ov8858_q8v19w_common.so
vendor/lib64/libchromatix_imx234_liveshot.so
vendor/lib64/libchromatix_imx219_q8n13a_snapshot.so
vendor/lib64/libchromatix_imx234_hfr_120.so
vendor/lib64/libchromatix_ov16825_common.so
vendor/lib64/libchromatix_imx214_snapshot.so
vendor/lib64/libchromatix_imx234_snapshot_nightmode_1.so
vendor/lib64/libchromatix_imx214_liveshot.so
vendor/lib64/libchromatix_ov8858_snapshot.so
vendor/lib64/libchromatix_imx234_snapshot_nightmode.so
vendor/lib64/libchromatix_ov8858_liveshot.so
vendor/lib64/libchromatix_imx179_preview.so
vendor/lib64/libchromatix_ov8858_hfr_60fps.so
vendor/lib64/libchromatix_imx234_common.so
vendor/lib64/libchromatix_ov8858_q8v19w_snapshot.so
vendor/lib64/libchromatix_ov13850_default_video.so
vendor/lib64/libchromatix_imx219_q8n13a_preview.so
vendor/lib64/libchromatix_imx234_default_video.so
vendor/lib64/libmmcamera2_frame_algorithm.so
Probably not all files are necessary, but i was too lazy to test it out one by one. I just replaced all of them. The libs for the imx sensor probably aren't needed.
Latest german rom is V1.01, as far as I know. Never ever seen a german localized V1.02. Files above were taken from 1.01.
Just works for 5.1, as in Mokee 60.1 there's some sort of timeout when it tries to initialize the driver. Some patching would be needed, but trying to build Mokee myself
didn't resume a working ROM.
kai4065 said:
Here's the list
Click to expand...
Click to collapse
Thank you! I'll try. :good:
Just wanted to let you know,that I was sick of copying the files in every new release, so I just swapped the main camera sensor with the Sony sensor found in the Chinese model. Works like a charm.
Video Link -- https://www.youtube.com/watch?v=qgq4hdTtpDE
Look at the video.i don't think it's fake.and the uploader is saying that he is running an android 7 emulator.so is that possible to do that on 540(8.1 devices) without secureboot unlock.??because as i know those device can't be unlock for now actually.
@feherneoh thats not my question ..i m just asking that without bootlocker unlock is it really possible to run an android emulator.???
wow..it will be awesome ...then i need some research about this bcz i m a noob..btw thanks bro @feherneoh
@feherneoh got nothing ..can u suggest me something to run andro emulator in lumia..
Lumia 540 android convert korbo kivabe