NeoInfo, a tool for the Galaxy S3 Neo
AboutNeoInfo is a tool for the Samsung Galaxy S3 Neo which aim to figure out the bootloader, modem and camera sensor of the device. Those information are the most important prerequisites for modern Custom ROMs. Additionally it displays some more or less important information such as the current CSC, front cam type and more.
Features
Works without root access
Very obvious but yes, it displays your bootloader and modem versions
Get the best possible accurate information about the camera
Capable to detect the current battery/charger driver
Dark mode
Requirements
At least Android 4.4
A Galaxy S3 Neo (Duos)
Download/InstallationYou can get the latest APK from here. Install the App as normal APK.
Changelog
Code:
v1.0:
- initial release
Camera PermissionNeoInfo needs on Android 4.4 access to the Camera to get two specific rear camera characteristics in order to check if the rear camera does actually work. On Android 5.0 or newer this permission is not required nor asked.
Sourcehttps://github.com/prototype74/NeoInfo
F.A.Q.
Q: Does it need Root?
A: No, didn't I mention it in first post?
Q: The color of my Booloader/Modem version is orange. What does that mean?
A: Your Booloader/Modem is from 2015 release and might be outdated. If you face RIL issues or any other issue that might be related to your Booloader/Modem, consider upgrading if possible.
Q: The color of my Booloader/Modem version is red. That's not good right?
A: Yes, you have one of the oldest Booloader/Modem (from 2014) which will definitely cause RIL issues or bootloops at setup screen in modern Custom ROMs. You should upgrade to the latest Booloader/Modem if possible.
Q: What does SLSI_S5K4H5YB/SONY_IMX175 mean?
A: SLSI_S5K4H5YB = Samsung camera sensor | SONY_IMX175 = Sony camera sensor
Q: In camera section, all my camera types are okay but the camera status shows "Not working". What should I do?
A: That means you either have a different camera sensor or (if you're sure its the correct sensor) your camera hardware might be broken. If the first one is the case, flash a different Firmware/ROM that supports your sensor. For example, if your camera types show "SLSI_S5K4H5YB", flash a Sony firmware.
Q: The back camera type note shows "Your back camera kernel type does not match the others but it should not affect the camera functionality". Should I be worried?
A: No, as it says in the text "..but it should not affect the camera functionality", because it actually doesn't affect the camera functionality at all.
Q: The back camera type note shows "Your back camera firmware type does not match the vendor type" but my camera works?
A: If you camera works then good for you! This case however is unusual but happens if you flashed a stock firmware before which was meant for a different camera sensor. So the text in Vendor back camera type is your true camera sensor in this case.
Q: The back camera type note shows "Your back camera firmware type does not match the vendor type" and the camera status shows "Not working"! Help!
A: If your camera is actually not working then you need to research how the ROM you flashed does manage that:
Does the ROM offer a camera patch? If so, flash it to fix the camera.
Does the ROM offer an option to select the camera sensor (e.g. SEPerience-ROM)? Then you selected the wrong sensor. Reflashing the ROM and selecting the other sensor should fix it.
Does the ROM offer different builds (e.g. LineageOS)? Then you flashed the wrong build. Flash the correct build to fix the camera.
Tip: check what the Firmware back camera type does show. For example, if it shows "SLSI_S5K4H5YB" but your Vendor back camera type shows "SONY_IMX175" then you have a Samsung sensor.
Q: The Vendor camera type shows "SLSI_S5K4H5YB && SONY_IMX175", does that mean I got both sensors!?
A: No, but there are two reasons why that could happen:
You flashed a camera patch fix that didn't remove the unused camera blobs
Or, the ROM developer does include both camera blobs in their builds
In this case it's not easy to figure out which camera sensor you actually have. Thus, Back camera status will also display "Unable to check your back camera type".
Q: Can I install the App on a different Android device than S3 Neo?
A: Yes, you can install the App on any Android device but the features the App offers will be limited as it was desinged for the Galaxy S3 Neo.
Related
This concerns kernel devs and people with touchscreen problems.
As I saw android 4.4 updates didn't fix the touchscreen for some. In addition it made things worse, like in my case.
So I tried to force firmware updating the touchscreen module and try many different firmwares.
To ease that process I modified the already existing code of the drivers (ektf3k.c) to enable firmware update by demand and using a filepath.
In the package below you will find the modified driver source file for custom kernel developing, all firmware updates until now and a help file for how to flash them.
All fw were modified to a version number of 99, to lock them in place and not let future auto updates (unlock fw included).
Kernel driver source + Firmware files
EDIT: Added patch, check below
EDIT2: Corrected the typo in patch. Thanks @Tk-Glitch
After creating the custom kernel, you can use terminal or adb or a text editor to echo or edit /sys/devices/i2c-3/3-0010/update_fw and write the fw filepath. You can also check fw version by checking /sys/devices/i2c-3/3-0010/vendor (the last numbers are your fw version).
Check readme for more
To all kernel devs:
The modified drivers do not break anything. They just create a special sysfs file. The code is activated only by writing a path in that sysfs file.
To all others with touchscreen problems:
This needs a custom kernel with this modified driver. Otherwise you can't use the firmware files
Kernels with touchscreen force update patch:
Glitch
SaberMod franco.Kernel
X-Flo
If you incorporated the patch into your kernel please inform me to update the list.
Changelog of touchscreen firmwares:
Code:
A011:
A011 is the lastest touch firmware and used for factory image.
firmware update history:
A009:
Update boot-code Ver: 60.47 (Do not turn off WDT in IAP process).
Add Self Check Mechanism to enter suspend mode.
Modification Algorithm, and Digital Parameters for ER Module.
a. Improve "double fat finger (22 phi copper)" performance.
b. Improve "fast drawing straight line" performance.
c. Improve "multi-finger in co-axis (8 phi copper)" performance.
d. Improve "under table lamp" performance.
A010:
Modify Calibration Mechanism.
A011:
Modify Open/Short Calibration Mechanism for ESD problem.
Improve Stylus Performance
=================================================================
A012:
1.Fix the Sensitivity Problem That Suspend and Wake up When Charging.
2.Modification for Algorithm, and Digital Parameters for ER Module.
a.Improve "double fat finger (22 phi copper)" performance when charging.
=================================================================
A021 (A015):
Fix:
8717455: Holding touch panel edge by one finger,the touch action will be affected.
8768005: Holding Flo along the left edge of the device reveals false touch problems.
8840158: Pinch zoom in and out on chrome and maps doesnt seem as accurate / responsive as on nakasi.
8798827: Touch can not be correct clicked.
customer report: pin unlock will lose touch report.
Modification for AC De-noise Mechanism.
=================================================================
A025:
Based on A023 and remove the grip information.
1.[Issue 8840158] [FLO] pinch zoom doesnt seem as responsive / reliable as on nakasi.
2.[Issue 8858019] [FLO] Poor touch resolution.
Need calibration to fix these two issue with ER1/ER2 device:
3.[Issue 9052815] [FLO] Dead "Bands" on the touch screen.
4.[Issue 8930391] Spurious touchscreen taps.
=================================================================
A028:
Improve hovering like Nakasi
=================================================================
A029:
Need calibration for below Issue:
[Issue 9261425] New touch firmware is needed to apply the new parameters.
=================================================================
A031:
Fix following issues:
1.Latency on resume
2.Edge swipes lost (notification panel)
3.[Issue 9284036][FLO]ABS_MT_TOUCH_MAJOR values change
base on number of pointers down
=================================================================
A032:
1.firmware to A032.
2.modify driver to update power source when use slim port to hdmi.
A032 fix issue:
9471817:Hover touches.
9366206:Device show multiple-ghost touch after connect HDMI and tilt device to 40~65 degree.
9471956:Unclean lift offs.
9471962:Edge swipes causing hooks or missing touch points.
Noise problem.
Add ESD Protection Mechanism.
=================================================================
A033:
Fix issue:
1.Seeing lost touches.
2.Magic disappearing square.
3.Need to clean up small pointer dancing.
4.Pointer splitting.
5.Jumps between two large touches.
6.9521124:Poor performace in handwritten input method.
Bug: 9472154
Bug: 9471828
Bug: 9521124
Bug: 9471817
=================================================================
A034:
improvement:
9323363:Scrolling not smooth.
=================================================================
A036:
Fix issue:
962875:Need a new touch firmware to pass ESD test.
=================================================================
A038:
Fix/Improve issue:
1.[Issue 9692415] Touch screen on flo is broken for games
2.[Issue 9323363] [FLO/DEB] [Touch] Scrolling not smooth
3.[Issue 9471817] [FLO/DEB] [Touch] Hover touches
=================================================================
A040:
Fix/Improve issue:
1.[Issue 9692415] Touch screen on flo is broken for games.
2.Broken line.
3.Two Fingers Tapping Easy Connectivity.
4.co-axis problem with two finger.
=================================================================
A042:
Fix/Improve issue:
1.ghost touch probelm that caused by lcm slef-noise.
2.broken line in particular area.
=================================================================
A043:
Bug: 10388772
Bug: 10391124
Bug: 10541253
=================================================================
A044:
Fix issue:
1. Improve stability of two finger co-axis.
2. Ghost point problem of two fingers.
I've never had a touch screen problem
I have had touch issues. Not so much with 4.4.4
Sent from my Nexus 7 2013 using Tapatalk
CTCaer said:
This concerns kernel devs and people with touchscreen problems.
As I saw android 4.4 updates didn't fix the touchscreen for some. In addition it made things worse, like in my case.
So I tried to force firmware updating the touchscreen module and try many different firmwares.
To ease that process I modified the already existing code of the drivers (ektf3k.c) to enable firmware update by demand and using a filepath.
In the package below you will find the modified driver source file for custom kernel developing, all firmware updates until now and a help file for how to flash them.
All fw were modified to a version number of 99, to lock them in place and not let future auto updates (unlock fw included).
Kernel driver source + Firmware files
EDIT: Added patch, check below
After creating the custom kernel, you can use terminal or adb or a text editor to echo or edit /sys/devices/i2c-3/3-0010/update_fw and write the fw filepath. You can also check fw version by checking /sys/devices/i2c-3/3-0010/vendor (the last numbers are your fw version).
Check readme for more
To all kernel devs:
The modified drivers do not break anything. They just create a special sysfs file. The code is activated only by writing a path in that sysfs file.
To all others with touchscreen problems:
This needs a custom kernel with this modified driver. Otherwise you can't use the firmware files
Changelog of touchscreen firmwares:
Code:
A011:
A011 is the lastest touch firmware and used for factory image.
firmware update history:
A009:
Update boot-code Ver: 60.47 (Do not turn off WDT in IAP process).
Add Self Check Mechanism to enter suspend mode.
Modification Algorithm, and Digital Parameters for ER Module.
a. Improve "double fat finger (22 phi copper)" performance.
b. Improve "fast drawing straight line" performance.
c. Improve "multi-finger in co-axis (8 phi copper)" performance.
d. Improve "under table lamp" performance.
A010:
Modify Calibration Mechanism.
A011:
Modify Open/Short Calibration Mechanism for ESD problem.
Improve Stylus Performance
=================================================================
A012:
1.Fix the Sensitivity Problem That Suspend and Wake up When Charging.
2.Modification for Algorithm, and Digital Parameters for ER Module.
a.Improve "double fat finger (22 phi copper)" performance when charging.
=================================================================
A021 (A015):
Fix:
8717455: Holding touch panel edge by one finger,the touch action will be affected.
8768005: Holding Flo along the left edge of the device reveals false touch problems.
8840158: Pinch zoom in and out on chrome and maps doesnt seem as accurate / responsive as on nakasi.
8798827: Touch can not be correct clicked.
customer report: pin unlock will lose touch report.
Modification for AC De-noise Mechanism.
=================================================================
A025:
Based on A023 and remove the grip information.
1.[Issue 8840158] [FLO] pinch zoom doesnt seem as responsive / reliable as on nakasi.
2.[Issue 8858019] [FLO] Poor touch resolution.
Need calibration to fix these two issue with ER1/ER2 device:
3.[Issue 9052815] [FLO] Dead "Bands" on the touch screen.
4.[Issue 8930391] Spurious touchscreen taps.
=================================================================
A028:
Improve hovering like Nakasi
=================================================================
A029:
Need calibration for below Issue:
[Issue 9261425] New touch firmware is needed to apply the new parameters.
=================================================================
A031:
Fix following issues:
1.Latency on resume
2.Edge swipes lost (notification panel)
3.[Issue 9284036][FLO]ABS_MT_TOUCH_MAJOR values change
base on number of pointers down
=================================================================
A032:
1.firmware to A032.
2.modify driver to update power source when use slim port to hdmi.
A032 fix issue:
9471817:Hover touches.
9366206:Device show multiple-ghost touch after connect HDMI and tilt device to 40~65 degree.
9471956:Unclean lift offs.
9471962:Edge swipes causing hooks or missing touch points.
Noise problem.
Add ESD Protection Mechanism.
=================================================================
A033:
Fix issue:
1.Seeing lost touches.
2.Magic disappearing square.
3.Need to clean up small pointer dancing.
4.Pointer splitting.
5.Jumps between two large touches.
6.9521124:Poor performace in handwritten input method.
Bug: 9472154
Bug: 9471828
Bug: 9521124
Bug: 9471817
=================================================================
A034:
improvement:
9323363:Scrolling not smooth.
=================================================================
A036:
Fix issue:
962875:Need a new touch firmware to pass ESD test.
=================================================================
A038:
Fix/Improve issue:
1.[Issue 9692415] Touch screen on flo is broken for games
2.[Issue 9323363] [FLO/DEB] [Touch] Scrolling not smooth
3.[Issue 9471817] [FLO/DEB] [Touch] Hover touches
=================================================================
A040:
Fix/Improve issue:
1.[Issue 9692415] Touch screen on flo is broken for games.
2.Broken line.
3.Two Fingers Tapping Easy Connectivity.
4.co-axis problem with two finger.
=================================================================
A042:
Fix/Improve issue:
1.ghost touch probelm that caused by lcm slef-noise.
2.broken line in particular area.
=================================================================
A043:
Bug: 10388772
Bug: 10391124
Bug: 10541253
=================================================================
A044:
Fix issue:
1. Improve stability of two finger co-axis.
2. Ghost point problem of two fingers.
Click to expand...
Click to collapse
Been looking for something like this that embeds all the firmware variants in one package. Guess it's not usable unless integrated in some custom kernel... Will have to wait for aroma installer then. But thanks.
Well many have problems and were forced to flash custom kernels with different firmwares.
This can ease up a lot the process and help many people that are using custom kernels to test different fw.
For example many fixed their issues with A011 (aka ts10). Because like in my case, the problem comes from the LCD's electromagnetic interference on ELANtech's touch panel(tested with Nexus 7 Nexus 7 II Tester).
Well it's up to kernel dev's to incorporate the driver mod if they want.
I may make a stock based custom kernel, touch fw tester edition, when I get back home and refix my ubuntu vm.
So 1 flash, try firmwares, find the personal best, reflash previous kernel.
Hello, thanks for the patch, i'm using Glitch Kernel which implemented your patch and i'm going to try and fix my touchscreen but i want to know which version of the driver is the latest, is it the A011 or the A044?
And another question, i've just tested A011 and A044 but at vendor both show ELAN_KTF3K_xa064, are they both supposed to show the same version?
Trevomader said:
Hello, thanks for the patch, i'm using Glitch Kernel which implemented your patch and i'm going to try and fix my touchscreen but i want to know which version of the driver is the latest, is it the A011 or the A044?
And another question, i've just tested A011 and A044 but at vendor both show ELAN_KTF3K_xa064, are they both supposed to show the same version?
Click to expand...
Click to collapse
Yeah both of them show the same version to avoid updating to new one.
I may release an archive with incremental (bigger than a044) sometime.
The latest is A044 since months.
Also thank you for testing this mod.
Good luck mitigating the problem.
EDIT: Checked @Tk-Glitch kernel commits and corrected the typo to the above patch. Thanks
For the longest time I had crazy touch problems especially when I set the device down on the bed, etc, not unlike many others..but a week ago I pulled my screen protector off and all problems have completely vanished, put another one on, problems return immediately, can anyone explain this? And also is there a screen protector that I can use i.e, tempered glass, for anyone that found the same problem
trident76 said:
For the longest time I had crazy touch problems especially when I set the device down on the bed, etc, not unlike many others..but a week ago I pulled my screen protector off and all problems have completely vanished, put another one on, problems return immediately, can anyone explain this? And also is there a screen protector that I can use i.e, tempered glass, for anyone that found the same problem
Click to expand...
Click to collapse
Some have reported the same problem with screen protectors. I had similar issue with 2012 Nexus 7 when the screen got dirty with finger prints. I now use Nova screen. Lag almost unnoticeable. Matter of fact, it's mostly grounding issue. Too bad there still isn't a way to flash the OP batch, though, according to other threads, the multi-touch fix isn't for that. YAMTT records no problem, but if I leave it flat on a table, some areas don't register touches at all. I've used EMI tape as much as I can see and yet, no improvements. I guess it's between the LCD and the touchscreen. That being the case, no cure.
Hi @CTCaer,
I have touchscreen problems on my N7 Flo :crying:. Can you say me how I can test this patch? Or which kernel I must flash? It's there one, which have your patch already intergrated?
Thanks! :victory:
raXoN91 said:
....Can you say me how I can test this patch? Or which kernel I must flash? It's there one, which have your patch already intergrated? ....
Click to expand...
Click to collapse
Hey, check 1st post.
I added a list that I'll try to maintain
CTCaer said:
Yeah both of them show the same version to avoid updating to new one.
I may release an archive with incremental (bigger than a044) sometime.
The latest is A044 since months.
Also thank you for testing this mod.
Good luck mitigating the problem.
EDIT: Checked @Tk-Glitch kernel commits and corrected the typo to the above patch. Thanks
Click to expand...
Click to collapse
Do you know if there was a change from android 4.4 to 4.4.2 in the driver? From memory 4.4 seemed to be perfect and around 4.4.2 I started getting problems again (ghost touches)
CTCaer said:
Hey, check 1st post.
I added a list that I'll try to maintain
Click to expand...
Click to collapse
Hey, I fashed the Glitch kernel r151 and the issue is not fully fixed. It's Vetter! But ff the tablet get hot, the issue come again. Is there a special Version with the patch? Thanks :victory:
godutch said:
Do you know if there was a change from android 4.4 to 4.4.2 in the driver? ..
Click to expand...
Click to collapse
No it's A044. But when I updated 4.4.3->4.4.4, I checked logs and the touchscreen driver wrote something with calibration (can't remember exactly).
raXoN91 said:
Hey, I fashed the Glitch kernel r151 and the issue is not fully fixed. It's Vetter! But ff the tablet get hot, the issue come again. Is there a special Version with the patch? Thanks :victory:
Click to expand...
Click to collapse
The firmwares can't completely fix the problem, only can make the situation better. The device getting hot means that it uses a lot of power and thus more EMI for the touchscreen panel.
You have to test different fw because almost every fw has different internal calibration methods.
Also I learned that the correct way to use the forced calibration (as I mentioned in the other touchscreen problems thread, echo "FF" > /proc/ektf_dbg), is to put the device on an insulated surface, away from power sources, chargers and do it by using terminal emulator and not adb with wifi or cable. And also in flight mode.
CTCaer said:
No it's A044. But when I updated 4.4.3->4.4.4, I checked logs and the touchscreen driver wrote something with calibration (can't remember exactly).
The firmwares can't completely fix the problem, only can make the situation better. The device getting hot means that it uses a lot of power and thus more EMI for the touchscreen panel.
You have to test different fw because almost every fw has different internal calibration methods.
Also I learned that the correct way to use the forced calibration (as I mentioned in the other touchscreen problems thread, echo "FF" > /proc/ektf_dbg), is to put the device on an insulated surface, away from power sources, chargers and do it by using terminal emulator and not adb with wifi or cable. And also in flight mode.
Click to expand...
Click to collapse
I've noticed that Franco's kernel with embedded firmware comes in 2 versions: AOSP and CM. Should I switch between the two, would it be necessary to unlock the patch and reflash it again with the version that corresponds with the new rom? Thank you.
graphdarnell said:
I've noticed that Franco's kernel with embedded firmware comes in 2 versions: AOSP and CM. Should I switch between the two, would it be necessary to unlock the patch and reflash it again with the version that corresponds with the new rom? Thank you.
Click to expand...
Click to collapse
AOSP and CM are only the versions that are supposed to match with your rom. AOSP are the majority of the roms you'll probably use. (Stock, PA) CM are roms mostly derived from CM (basically CM, PAC)
In that case you only need to flash the rom if not already done. Then you need to flash the corresponding kernel version and you can use the said patch.
Envoyé de mon Nexus 7 en utilisant Tapatalk
zaclimon said:
AOSP and CM are only the versions that are supposed to match with your rom. AOSP are the majority of the roms you'll probably use. (Stock, PA) CM are roms mostly derived from CM (basically CM, PAC)
In that case you only need to flash the rom if not already done. Then you need to flash the corresponding kernel version and you can use the said patch.
Envoyé de mon Nexus 7 en utilisant Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. Guess I wasn't very clear. I'm now on CM-derived rom. So I flashed CM-based patched kernel. But if I decide to switch to an AOSP-based rom, do I need to unlock the CM firmware and flash the AOSP firmware instead? Or is it the case that once you flash it, it would stick until you unlock again, no matter what rom you install in between?
It locks it. Doesn't matter the kernel. It will only update it if the touchscreen goes into recovery mode.
To unlock it, use A044-unlock.b. This is untouched, so it will show _xA044 in the vendor sysfs and not _xA064.
Hello again, yesterday i've tried to "unlock" the firmware, but even after applying A044-unlock.b multiple times it's still showing version 100 (x64) on vendor.
I'm still on glitch kernel, so i don't know if the patch is working correctly on this kernel.
Try the attached file. It's stock A011.
If it succeeds and you reboot the driver should then flash the kernel's stock which is A044 (it should show _xa044).
Some days ago I installed a Resurrection Remix Rom (I actually don't know which one, sorry. I just know that it's got Lollipop) and when i went to the camera it said: <<Can't connect to camera>>
I still had warranty, so I installed the stock rom (I checked the camera and it still didn't work) and I sent the phone to the company. IMPORTANT NOTE: In the warranty ticket it said <<SOFTWARE ERROR>>
The only camera I can use is the "selfies" one
When I received it, the error was fixed, so I tried to install another ROM, so I installed CM12. But... I got the error AGAIN and I haven't got warranty anymore
That's what I tried
-Install Reset Camera and Camera (CMFix) (Camera CMFix didn't open and I had Restart Camera Installed :v)
-Checking if an app is having troubles with the camera
-Rebooting in safe mode
-Holding down the volume/power/back
-Clearing Data and Cache of the camera
-Removing my SD card
-Renaming the DCIM folder
- youtube. com/ watch?v=Fa9qggQJ990 (I can't even access to that menu ._.)
-Find “Use NuPlayer” and uncheck it & restart
-Using other camera apps
-Disabling the Google Camera and using the default one
-EDIT: I installed the Stock Rom with odin and did a factory reset. I even did a "system reset" with odin. AND IT STILL DIDN'T WORK OMFG. Then I tried to update the camera firmware (youtube. com/ watch?v=Fa9qggQJ990) because I've got KK now, but the "Phone/CAM FW Ver Check" is disabled. I googled my camera Cam FW Ver and it's not old
Thank you, I'ts a really annoying error. My S3 is giving me too many troubles, I'm starting to hate it... But I can't buy a new one :crying:
OHMYGOD I CAN'T FIND A WAY TO FIX THAT ERROR HELP PLEASE
//reposting because nobody answered :v
LOGCAT:
shri b. com/S3fzYuWo9IrOo9K?v=nc That's the logcat of the KitKat Camera
shri b. com/Csq5Quc33VXUdC3?v=nc That's the logcat of the Google Camera
(Sorry for the spaces, but I'm a new user and I can't put URLS
If you're confident that its not a software issue, then go ahead and unroot your phone and show it once (sometimes the problem maybe that the camera slot just got loose). But 'can't connect to camera' is common from cm12 onwards. Maybe its a kernel problem. The fact that stock firmware also failed is something abnormal. Even in a few Touchwiz roms, kernel changes led to cameras not working.
Anyway, If you're still on stock rom do to the dialer and enter
*#7353# quick test
*#*#4636#*#* for test and information
*#34971539# for Camera Firmware Update and
*#7412365# Camera Firmware Menu
sashankps said:
If you're confident that its not a software issue, then go ahead and unroot your phone and show it once (sometimes the problem maybe that the camera slot just got loose). But 'can't connect to camera' is common from cm12 onwards. Maybe its a kernel problem. The fact that stock firmware also failed is something abnormal. Even in a few Touchwiz roms, kernel changes led to cameras not working.
Anyway, If you're still on stock rom do to the dialer and enter
*#7353# quick test
*#*#4636#*#* for test and information
*#34971539# for Camera Firmware Update and
*#7412365# Camera Firmware Menu
Click to expand...
Click to collapse
I did *#7353# and tested the camera and it told me Can't connect to camera again, I can't choose "Phone to CAM FW Write (Main)" in *#34971539# and *#7412365# and *#*#4636#*#* didn't work
I guess It's a kernel problem
Thank you so much!
Hello partners!!!
Here we share the functional rom last for our MaX2!
At the request of many colleagues, I created this CM13 based on 29 September.
And adding the entire S19 firmware to have it fully updated and upgraded.
Fully functional quick and steady myself I was surprised with the performance tests ... 143,000 AnTuTu with hot enough to test mobile Cold believe can draw record numbers ...
To say that I still have problems with slow motion ....
I'm starting to not know where mistakes can be ....
Libs I managed to trace the entire structure of the official EUI and still does not work ....
Permits revised from top to bottom ...
Libs mother and CM13 ... zilch ...
Perhaps there may be something in the kernel (boot) but there are limited ...
As I change anything to do directly test the ROM does not start or comes into infinite loops ....
So ... I leave the rom completely finished but with 2 bugs.
And each user knows what he wants or what you need.
But the ROM is fully functional for day to day and is really fast and stable.
BUGS:
1 Slowmotion nonfunctional. The rest of the camera is fully functional with 21mpxl.
2nd nonfunctional IRDA. (With this ... if not roms stocks moment ... little we can do ...)
The first!!!! IMPORTANT
We do not force anyone has use or install the rom.
We do not make yourself responsible for possible errors or brik the terminal.
We simply share our work for all so that we can have the terminal in our language.
RoM CM13
CM13 based official of the day 29/09/2016
s19 official firmware with all its libs + kernel.
Rom eliminated completely stock only apks that created conflict with our terminal.
Doze functional.
Sound perfect.
wiffi
BT
Integrated Pico gapps
Some improvements in the build.prop
Installation Method
We have created a zip FULL.
ROM contains firmware s19 + recovery + 5.8 everything necessary for you to come firmware do not have problems to come and stay all properly installed and running smoothly or silly scares.
* Download rom.
* Enter the zip rom on your terminal.
* Restart recovery.
* Since the recovery to the wipes.
* Once the wipes, select the zip and install.
* Once installation is complete, restart System.
* Wait for the rom you first start, it takes a few minutes not alarmed.
downloads TeaMSpaiN
CM13 ROM S19: https://mega.nz/#!SwIHSB7C!rFQJsQxx-J-RI121GWsaC6DAhDkLHzJdDPvdVabZRRY
Your comments on this rom.
And if you find any bug report to try to fix them.
Greetings comrades!
DONATE PAYPAL: https://www.paypal.me/ParasiteYgaseOso
thanks for sharing this
Sent from my Le X821 using XDA-Developers mobile app
Thank you! I will try this rom.
Changing action of the left hardware button doesnt work, it just keeps working as "menu" button.
ArctiX said:
Changing action of the left hardware button doesnt work, it just keeps working as "menu" button.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=68885350&postcount=235
meangreenie said:
http://forum.xda-developers.com/showpost.php?p=68885350&postcount=235
Click to expand...
Click to collapse
Thanks, that worked
Thanks for your work! Does Camera API 2 work this time?
I flashed this rom today. Everything works well for me!
wiped system and dirty flashed from previous cm13 and it seems to be running very well
Nice, smooth, we will see battery performance compared to Mokee.
- Camera2 api doesnt work
- Slowmotion doesnt work
- IR doesnt work
- For me, missing Aegis app from Mokee is a big step back
Sent from my Le X820 using Tapatalk
@ParasiTe_RemiX Did you build this from source or port from another device?
Beautiful ROM, but for me in Japan for some reason LTE is not working, I can get only HSPA. This is strange because in the stock eui I can use LTE no problem.
Also the hardware buttons light up when you touch the screen, on Eui they only lit up when you touched the buttons, not the screen.
Oh, and after checking now, the AudioFX doesn't work system wide, only in the cm music app, in e.g. YouTube or Tidal, it doesn't make any change in sound.
Notification light is blinking when charging, is there any way to make it always on and not blinking?
ArctiX said:
Also the hardware buttons light up when you touch the screen, on Eui they only lit up when you touched the buttons, not the screen.
Oh, and after checking now, the AudioFX doesn't work system wide, only in the cm music app, in e.g. YouTube or Tidal, it doesn't make any change in sound.
Notification light is blinking when charging, is there any way to make it always on and not blinking?
Click to expand...
Click to collapse
For the hardware buttons backlight, you can turn them off in settings/buttons or you can turn the brightness of them right down, via editing the max_brightness file.(can't remember the path name atm, but can easily google)
For the charging light, you can turn the charging light off in settings/display. The options for them don't seem to work unfortunately.
When I plugged my phone to the computer I noticed a blank file with no name and hard disk icon on my sd card, when I tried to delete it, it wiped my whole sd card! don't delete that file if you see it.
Hello, This ROM is also compatible with the version Le Max 2 Pro?
pickmod said:
Hello, This ROM is also compatible with the version Le Max 2 Pro?
Click to expand...
Click to collapse
No, you can't flash it for X620!
bahuy2003 said:
No, you can't flash it for X620!
Click to expand...
Click to collapse
I have Le Max 2 Pro X820... it is compatible?
Thank you, looks really production quality
This is extremely close to what I wanted from this device: Straighforward CM13 (ok, I'll want CM14 next), no bloat, functional and fast.
Also rooted, which means I control my device, not some vendor who wanted my money but fails to cede the control over what he sold.
And most importantly: No longer any of these Chinese apps, which refused to get uninstalled while they claimed about any privilege Android can provide.
I sure hope security patches will be coming for years as the device looks powerful enough to last a long time.
Only bug I've found so far is apps like Hangouts and Duo can't access the Camera for video calls. Apart from that, flawless so far.
Hello.
After installing XperiFix, my camera is still not working. I am uploading the logs below. I noticed that the Magick 17.1 version from XperiFix doesn't work, and when I try to update or upload from a new one, I see a black screen after booting the phone, but when I press and hold power button I see a window to a turn off device and sometimes top bar appears (time, battery, etc.). I tried to install Magisk v25.2.
I also tried to upload the stock camera (https://gitlab.com/xperiance/camera/-/releases) but without the higher version of Magick I can't do it.
I have FW .205, before that I tried .270 but it didn't work, bootloop when starting the phone.
In the morning I will install the update from OTA to .235 and try to upload XperiFix or install the .145 version and see what happens next.
I tried Open Camera and made logs, but they didn't save, but the camera still doesn't work ;/
EDIT: I flashed FW .145 but didn't help.
I flashed Android 9 FW 47.2.A.11.228 to test, but I cant flashed XperiFix, because in TWRP write "read-only partition detected" and I see that I flashed Magisk nothing happens, it's as if it didn't install, I don't know why but I didn't have a problem with it before... In TWRP this options "read-only" is unchecked.
Translated with www.DeepL.com/Translator (free version)
Is it possible to fix this somehow, anyone know anything? I've read a lot of forum posts about it but nothing works, I'll just add that after installing some AOSP(probably Android 11) the front camera works but very poorly and after taking a picture you can see green artifacts on it.
Hey, do you know how to fix camera app on sony xperia xz1 not capturin?
My xperia xz1 is android 8, so I decided to flash an android 9 firmware using newflasher. After flashing the firmware, my camera has a problem that can't capture. Anyone can tell how to fix this issue? Plz help me. Sorry for bad English
Your browser is not able to display this video.
This is what happen on my xperia xz1. Camera is not capturing and not save a picture, recording also object tracking not working. This is happen after flash from android 8 version to android 9. Anybody know to fix this? Please help me. before flash the new android version, i didn't do any backup and my xperia is locked bootader. I'm using newflasher to flash the android 9 firmware.
Device comes with Android 9.0.
I've unlocked it, flashed Android 8.0, put TWRP recovery and gained root.
But during testing i've discovered the fact that camera lost it's autofocus ability in stock application.
Tried OpenCamera with Camera API 1/2 with the same result.
Any ideas?
so you didn't read about what happens when you unlock bootloader?