Database Info

Alcatel OT-995 development

This thread is meant for (technical) discussion of OT-995, notably ICS-based (e.g. CM9 and AOKP) OS and kernel development.
Any non-technical questions/discussion belong in the general OT-995 thread.
Status quo
There's an ongoing effort bring CM9 and AOKP to the OT-995. Although neither is anywhere near complete, basic functionality (graphics/audio/gsm (non-data)/wifi/sensors) is present.
Both iuss and fonix232 currently maintain Android repositories related to OT-995. A common kernel is maintained by iuss, based on the 2.6.35.11 release by Alcatel.
Updates will likely be posted in this thread, but this topic start may not be fully up-to-date.
Source repositories
kernel: https://github.com/ius/tct_cocktail_kernel
android/bootable/recovery: https://github.com/ius/android_bootable_recovery
android/device/tct/cocktail: https://github.com/ius/android_device_tct_cocktail
(on top of the CM 'ics' branch)
android/device/alcatel/cocktail: https://github.com/fonix232/android_device_alcatel_cocktail
android/vendor/alcatel/cocktail: https://github.com/fonix232/android_vendor_alcatel_cocktail
Flashable releases
fonix232 has provided flashable builds of CM9 and AOKP: http://goo.im/devs/fonix232/OT995/ICS
(Be aware that these might not always be up to date with the repositories listed above)
Other bits of interest
iuss' slightly outdated README for his repositories.

fonix232 said:
Possibly, couldn't really boot yours though :\
Also, some more info about liblights. The tempfix works (keyboard lights up with screen), but apparently when the keyboard file is set in liblights, it won't call the keyboard function. If I set it to e.g. the notification LED, it is called, but bails out with error 13 (no access to notification LED control).
Click to expand...
Click to collapse
I just found some spare minutes and had a look at it as well (had to run & was working on writing the topic start for this thread, so I didn't get to posting about it).
It suddenly struck me that there's both a buttons and keyboard light; our virtual keys are buttons, I suppose keyboard is reserved for the backlight of a hardware keyboard.
Alcatel/TCT labeled the buttons backlight 'keyboard-backlight' in kernel, which it isn't.. I've fixed this; now the backlight works as expected. The notification light doesn't work with the CAF/AOSP liblights (different device paths), for now the stock (binary) liblights should work - it probably requires a chmod of the sysfs files in init.rc.

iuss said:
I just found some spare minutes and had a look at it as well (had to run & was working on writing the topic start for this thread, so I didn't get to posting about it).
It suddenly struck me that there's both a buttons and keyboard light; our virtual keys are buttons, I suppose keyboard is reserved for the backlight of a hardware keyboard.
Alcatel/TCT labeled the buttons backlight 'keyboard-backlight' in kernel, which it isn't.. I've fixed this; now the backlight works as expected. The notification light doesn't work with the CAF/AOSP liblights (different device paths), for now the stock (binary) liblights should work - it probably requires a chmod of the sysfs files in init.rc.
Click to expand...
Click to collapse
That makes sense - however, if you check my files, I've clearly made it so even if it there's a keyboard or buttons device, both calls the keyboard code - what never happens. I've logged it, every device open, every call of write_int, every device light setting, everything, and keyboard only showed up when:
a, Not the proper keyboard brightness path was given (in my case, it was the notification LED)
b, Moved the keyboard control to the lcd-backlight controller function - as it is currently.
And apparently yes, I've forgot to chown the whole LED folder's content to system
Also, our biggest problem is: this LED acts like as a battery/attention/notification LED, while keeping the modes of a trackball - slow pulse, fast pulse, constant on, constant off, and breathe. What would be the best way to approach?
(Just a sidenote: setting the notification LED's brightness to 0 will lead to the crash and reboot of the phone)

handy tool for making logs...
This app runs the following commands:
dmesg
logcat -v time -d
logcat -v time -b radio -d
getprop
uname -a
ps
Click to expand...
Click to collapse
Download : dl.dropbox.com/u/2889810/apps/getlogs_v1.1.apk
Thread : http://forum.xda-developers.com/showthread.php?t=1123129

I do it by hand, but thanks ;D

maby its a good thing to copy the apk to system/app
there will be a lot of people installing the build and then complain here that some stuff dont work (also bugs u didnt even realize they where there cuz u cannot test alone)
and when u ask them for logs some of them dont even know how to do it..

fonix232 said:
That makes sense - however, if you check my files, I've clearly made it so even if it there's a keyboard or buttons device, both calls the keyboard code - what never happens.
Click to expand...
Click to collapse
If I interpreted things right, you mean neither was ever called? If you had wired buttons-to-keyboard it should've worked, the reason why set_keyboard_light was never called is because TCT hacked the Java framework (by making the turn-on-screen-backlight-and-buttons event turn on the keyboard light as well).
Also, our biggest problem is: this LED acts like as a battery/attention/notification LED, while keeping the modes of a trackball - slow pulse, fast pulse, constant on, constant off, and breathe. What would be the best way to approach?
Click to expand...
Click to collapse
The monkey approach - I checked out the code for Nexus; it doesn't provide a battery light at all (which is probably only useful if you have a green/red led); attention and notification are routed to the same led.
The stock liblights seems to work quite well, e.g. notification (sms/mail) causes a blink, attention (USB inserted) a constant light.
Let's just copy stock liblights for now, we can rewrite/reverse it later.
(Just a sidenote: setting the notification LED's brightness to 0 will lead to the crash and reboot of the phone)
Click to expand...
Click to collapse
Good catch. Fixed in my kernel tree (no-op instead of a null fptr call)

iuss, I understand your concerns, and most probably will stick to it, but I've already began writing liblights Actually, it's like, around the fifth revision, fifth try, and still no worky. Just finished up my test-package (ultimate AOKP-CM9 with GApps installer, will post it separately), will test that and check back.
EDIT:
Tried your new kernel, but somehow, wifi fails to connect. DHCP timeouts, etcetera.

Works fine here (and I didn't touch anything related). For reference, a built zImage.

iuss said:
Works fine here (and I didn't touch anything related). For reference, a built zImage.
Click to expand...
Click to collapse
Egh, turns out it was my fault, something frikked up with my installer. Still working on the small quirks tho
Also an idea about BT - why not use the same module that the Galaxy Tab P4 series used? They are all BCM4330, so theoretically it should work!

question is it possible to make 3 point multitouch? (or more?)

The controller appears to be able to detect > 2 fingers, but doesn't return data for more than two.
In other news, I pushed a fix to make the ts driver once again support 2 fingers.

iuss said:
The controller appears to be able to detect > 2 fingers, but doesn't return data for more than two.
In other news, I pushed a fix to make the ts driver once again support 2 fingers.
Click to expand...
Click to collapse
The 5306 can detect up to 5 distinct touches, but apparently either the chip was locked down to two (or via baseband, and might be unlocked in ICS), or just the communication signal is processed in a wrong way.
But nice addition with the multitouch support!
EDIT:
First drawback of the stock liblights: the buttons light won't come alive after unlocking the screen, but needs to set the brightness manually. Does not occur if brightness is set to auto.

fonix232 said:
EDIT:
First drawback of the stock liblights: the buttons light won't come alive after unlocking the screen, but needs to set the brightness manually. Does not occur if brightness is set to auto.
Click to expand...
Click to collapse
Odd. Works just fine for me. I don't see how it's related to brightness either.. (what brightness? screen? I didn't touch it, nor have I any auto-brightness-control related overlay, if that's relevant).

iuss said:
Odd. Works just fine for me. I don't see how it's related to brightness either.. (what brightness? screen? I didn't touch it, nor have I any auto-brightness-control related overlay, if that's relevant).
Click to expand...
Click to collapse
I don't see either, but when brightness is on manual, I have to modify the value for the keyboard lights to show up.

Performance issue
I know, my question is maybe premature.
But what about the performance. Do you feel it could be faster than the stock rom?
Maybe some quadrant test would give us some idea?

it feels amazing

I think I might know a way to have 5-point touch, but it won't be easy...
Looking at the source code of the ft5306, you can see that in the firmware upgrade part, it points to a header file: FTS0094P430_CockTail_V1d_20111123_app.h
This header is nothing else, but an actual FT5306 firmware file, dissected into bytes. Basically, they took the hexa code of a binary firmware, and pasted it into a text file byte by byte! Sounds stupid, but actually a good way to integrate a firmware into the kernel.
However, the function can be overwritten so instead it reads bytes from an actual binary firmware file, located on the filesystem. Doing that, plus acquiring a 800*480 FT5306 firmware image (so far I've only found an 1024*600 one) would result in unlocking the whole capacity of the panel!
Also gave a try at the camera HAL. I can't make it work sadly :\

What happens if you write bogus firmware to ft5306, though? :x

The panel will most probably won't work, although the firmwares are pretty similar in all the ft5x06 series.
Aaaalthough, if you reflash a proper firmware, it should work again

Mi4C "backlight flickering"

Hi guys,
First sorry for my english, im french..xD
I have some "backlight flickering" problem on my MI4C.
There is quick varitions of backlight intensity at random times.
I had this problem with MIUI so i flashed cm-12.1-20151016, and more problems.
But i updated to CM12.1 cm-12.1-20151112-UNOFFICIAL-libra and the problem is back.
Do you have a solution ??
Thanks.

I noticed that suddenly the screen will get very bright, quite annoying.

ermacwins said:
I noticed that suddenly the screen will get very bright, quite annoying.
Click to expand...
Click to collapse
Ty for you answer, but it's not just the brightness who change but more the backlight doing like flashes.
I found a youtube video with similar problem.
But i cant post link.
You can find it on youtube typing :Sony Xperia Z1 backlight flickering.

semtex37 said:
Ty for you answer, but it's not just the brightness who change but more the backlight doing like flashes.
I found a youtube video with similar problem.
But i cant post link.
You can find it on youtube typing :Sony Xperia Z1 backlight flickering.
Click to expand...
Click to collapse
I watched the Video, but i have never seen this in my Mi4c.
https://youtu.be/uaGPgP_mmcQ

In miui the problem should be already fixed in 5.11.5, at least this is in the changelog.

Wow it is weird. I don't have that either (nor miui nor cm)

Yes i saw this for miui but i didnt tried, i changed for CM12.1 just before.
But i didn't saw the problem on the first CM build.
It's strange.

It happened to me twice. 5.11.5 the problem still continues. Now I use 5.11.12 not yet any flickering:fingers-crossed:

What if you change the level of adaptive display ? It is like you are on the edge between two different states and the phone doesn't know which one to choose.

bibihub said:
What if you change the level of adaptive display ? It is like you are on the edge between two different states and the phone doesn't know which one to choose.
Click to expand...
Click to collapse
I tried with low or high level of brightness and with adaptativ display on and off.
Same.

Hi everybody,
It happened again today so i tried differents things:
-Disabled Double Tap 2 Wake (1 of the new feature of the cm update): useless
-Turn ON the option to Disable HW Overlays (I saw on internet that can solve some screen flickering problems): wait and see
there is a risk ??
-I enabled performance mod on battery settings:
Is it good or not ?
Is it useless if im already using kernel adiutor set in on demand ??
Thanks.

I had a similiar problem with my Mi4 and managed to solve the problem by flashing this kernel after flashing CM: https://www.androidfilehost.com/?fid=24686681827314188
Little downside is; the kernel has a double-tap-to-wake-feature, which gives me some random unlocks in my pocket.

CM13 Z5P E6853 Beta -- Updated NegaSpork

This is a no-frills thread.
Okay here it is.
cm_satsuki-Nega_Spork.zip
For dsds testing: cm_satsuki_dsds_test_boot.img Note: you will see the Sony Bootanimation instead of CM13, this is intentional. Also detection may take a minute or two. Provide clear reports.
For dsds model owners, flash rom clean, then in recovery reboot to bootloader and flash this test boot.img with fastboot
Code:
fastboot flash boot cm_satsuki_dsds_test_boot.img
fastboot reboot
NegaSpork
Working:
Sim [single]
Storage
NFC
Audio record fixed
The rest is the same.
What doesn't work:
Since the camera is still not "fixed" we will just say it doesn't work, deal with it.
Next on my todo list is fmradio
DSDS support is still being worked out by the project members. [see test boot image above]
NOTE: OpenGapps may bug out quickpanel/pulldown menu. This may be related to version used.
I experienced this with pico and nano. [see note below]
Click to expand...
Click to collapse
Thanks @KbaB.BroS for testing :good:
Everything from before works, cell, mobile data, nfc, etc.
Internet speeds are good.
It feels snappier than before, so smooth
The pulldown bar works, I can interact with the toggles without any force closes. If somebody complains about their devices, let them know to use OpenGAPPS. I use the mini version
Click to expand...
Click to collapse
Cyanogenmod Source
Thanks to/for
@CTXz Sources and convincing me to get a Z5P instead of another Sammy device.
Sony Kitakami Platform Developer Organization
@zacharias.maladroit For answering questions, many questions. :silly: [ still have more... xD ]
Those of you without a sense of humor, go away.
Okay current features i'm working on and stuff that works/doesn't work
UVC support enabled in kernel. probably need to build rom-side support still. libuvc avutils etc.
- This is for plugging in camera devices in conjuction with apps like LegitDashcam.
USB Gadget functionality as per pelya's work ,
- pelya/android-keyboard-gadget Use in conjuction with the include USB Keyboard app to utilize your phone as a keyboard/mousepad.
I am working my kernel source here toward net-huntery goodness.
The rest you tell me, and you tell me properly. Messages like
"waahhh my whatchamhoozit is all floompy"
are not acceptable.
This is not a random discussion thread either. Idle chatter belongs in general.
This is also NOT a discussion thread for Xposed,Viper, etc..
Thank you.
m

Notes and Updates
NOTE
I have been running this build for two days now and so far , meh it's alright.
Audio [mic] and Camera issues are definitely annoying.
SELinux is COMPLETELY disabled on this build. If You want security go back to stock.
SELinux enforcing is the goal though.
I strongly recommend using a "traditional" root os SuperSU over systemless-root.
Reasons:
Opengapps requires a factory-reset or fresh install to set up correctly!
Privacy Guard based root sucks. It forgets alot of permissions granted.
Use BETA-SuperSU-v2.52 , I wil attach below as it seems hard to find by conventional means.
Would have posted earlier but needed a smoke break *>cough<* :silly:

Updates and Notes
Reserved

Attached UPDATE-SuperSU-v2.46.zip for another option ,
since that worked the best for me in the past.

Thanks for the input. I get error: 7 to install the .zip file
any solution?

Rubensss said:
Thanks for the input. I get error: 7 to install the .zip file
any solution?
Click to expand...
Click to collapse
You need to use the recovery @moonbutt74 compiled from his other thread.
Sent from my Z5 Premium using XDA Labs

KbaB.BroS said:
You need to use the recovery @moonbutt74 compiled from his other thread.
Sent from my Z5 Premium using XDA Labs
Click to expand...
Click to collapse
Thanks , I have already installed.

@moonbutt74
Would be easier to keep the ROM as daily and test if it supported the dual sim version phones too
Apart from that, some of my observations during a small period of usage :
Pardon me if these are already mentioned.
Screen brightness doesn't reach full capacity
Speaker volume is low I think
For me, I felt the display had some slight glitches. Enabled GPU rendering in developer settings and felt it got better , can't guarantee on this though
Had to revert to stock based since sim functionality for me wasn't available ( I have a dual sim phone)

Ashray_Vk
Okay good deal, umm let me try compiling a seperate kernel package.
Yep brightness is currently HORRIBLE
I didn't notice any glitches display-wise, do you actually mean lag in some screen transitions?
I only tested with radioball and raging thunder.
The build i just tested out had full WOW, HOW THE HELL DO I TURN THIS DOWN BRIGHTNESS. :silly:
So either atm i get crappy brightness as max level which is like 75% of stock.
Or i get the nice stock brightness but the slider breaks/doesn't work.
The speaker volume is limited to where it actually should be. Use a mediaplayer that has an option for software decoding, that is a 100% [double] boost. It's not the idea to bomb out the speakers by default, each user can find their own tweak.
m
On the "daily build" thing, my upload time is horrible, so i will not be pushing out excessive/pointless builds. when i have something else fixed, then i will upload another build. Currently i'm boxing with the brightness issue and getting the mic working for audio recording.

moonbutt74 said:
Ashray_Vk
Okay good deal, umm let me try compiling a seperate kernel package.
Yep brightness is currently HORRIBLE
I didn't notice any glitches display-wise, do you actually mean lag in some screen transitions?
I only tested with radioball and raging thunder.
The build i just tested out had full WOW, HOW THE HELL DO I TURN THIS DOWN BRIGHTNESS. :silly:
So either atm i get crappy brightness as max level which is like 75% of stock.
Or i get the nice stock brightness but the slider breaks/doesn't work.
The speaker volume is limited to where it actually should be. Use a mediaplayer that has an option for software decoding, that is a 100% [double] boost. It's not the idea to bomb out the speakers by default, each user can find their own tweak.
m
On the "daily build" thing, my upload time is horrible, so i will not be pushing out excessive/pointless builds. when i have something else fixed, then i will upload another build. Currently i'm boxing with the brightness issue and getting the mic working for audio recording.
Click to expand...
Click to collapse
By screen glitches, I meant that I saw a few glitches when I scrolled down menus ( like even settings app).
Might be just my sleepy eyes too, lol. And in the beginning, everything was feeling laggy, till I enabled those GPU options in the developer settings and turned the screen off and turned it back on.
Don't rely on this data though, I hope someone else verifies this thing before you take it up as an issue .
-Ash

Ashray_Vk said:
By screen glitches, I meant that I saw a few glitches when I scrolled down menus ( like even settings app).
Might be just my sleepy eyes too, lol. And in the beginning, everything was feeling laggy, till I enabled those GPU options in the developer settings and turned the screen off and turned it back on.
Don't rely on this data though, I hope someone else verifies this thing before you take it up as an issue .
-Ash
Click to expand...
Click to collapse
No problem I'm just looking for clarification, are you talking about lag or screen tearing?

moonbutt74 said:
No problem I'm just looking for clarification, are you talking about lag or screen tearing?
Click to expand...
Click to collapse
There was lag in the beginning, no doubt. Lag was there since the boot animation itself.
Yes! Screen tearing is the term i was searching for. I felt like I saw minor issues of screen tearing along with the lag. ( especially when I scrolled down the settings )
I'm so sorry if I am not able to make things clear.

Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app

Killastyle said:
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Click to expand...
Click to collapse
K,
right now we are working on an Alpha build, self evident in thread title. Xposed being superfluous/unecessary is not being discussed in this thread. Of course later on in the release/beta level thread it will most likely be covered.
@KbaB.BroS
On the good side got brightness and auto brightness sorted.
@Ashray_Vk , give me a bit on the dsds kernel, from what I'm understanding SS an DS were supposed to have been combined, so I am running a fresh build after resync, which on my comp will take a day :silly: adn probably not as long as the actual upload
:laugh:
m

moonbutt74 said:
K,
right now we are working on an Alpha build, self evident in thread title. Xposed being superfluous/unecessary is not being discussed in this thread. Of course later on in the release/beta level thread it will most likely be covered.
@KbaB.BroS
On the good side got brightness and auto brightness sorted.
@Ashray_Vk , give me a bit on the dsds kernel, from what I'm understanding SS an DS were supposed to have been combined, so I am running a fresh build after resync, which on my comp will take a day :silly: adn probably not as long as the actual upload
:laugh:
m
Click to expand...
Click to collapse
Normally, if I'd flash a stock based ROM which was meant for single sim, one sim would work in the dual sim models but the memory card would be not detected . sadly, that wasn't the case with cm though. Not even a single sim gets detected.

Ashray_Vk said:
Normally, if I'd flash a stock based ROM which was meant for single sim, one sim would work in the dual sim models but the memory card would be not detected . sadly, that wasn't the case with cm though. Not even a single sim gets detected.
Click to expand...
Click to collapse
you tried enabling only single SIM mode in Sony's (or other) "Stock" ROM and then flashing this ROM ?
Then at least one SIM might work - unless of course the Z5 devices handle things entirely differently

zacharias.maladroit said:
you tried enabling only single SIM mode in Sony's (or other) "Stock" ROM and then flashing this ROM ?
Then at least one SIM might work - unless of course the Z5 devices handle things entirely differently
Click to expand...
Click to collapse
Um, actually, was running rom aur and then had disabled one sim ( just because i didnt want to use that sim) and then had flashed this.
Unfortunately, not even a single sim worked in this.

Killastyle said:
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Click to expand...
Click to collapse
No problem with XPosed for some time here

Updated Build
CM13 Z5P E6853 Somehwere in Alpha -- Updated DragonLady
see OP , OH! and READ IT. grrrrrrr
Please verify communications are functioning, sim detection, in-call mic working etc.
Is your model SS or DS? Please state model number.
Brightnes and auto brightness should be fixed.
External storage fixed
Re-introduced kcal support in kernel
Included system apps [free, and free versions] - as we are testing , some creature comforts.
Adaway.apk
HKB.apk <--- hacker's keyboard
HKNDCTRU.apk <--- hacker's keyboard cyrillic/russian support
KernelAuditor.apk
NetworkDiscovery.apk <--- fairly useful network discovery app, find it on fdroid
NovaLauncher.apk
OpenCamera.apk
PicuriRam.apk
Quickpic.apk
Rebooter.apk
Superuser.apk <--- enable developer options and root access via that way first, then run supersu and update.
Terminal.apk < jackpal terminal
TotalCommander.apk
USB-Keyboard.apk
USBKB.apk < this one and the one above are the same app, i dun goofed.
Wifitoggle.apk
i am working a vanilla cm13 as well as my own custom build in the same turn, the custom utility in sbin is ccrypt, if you want to know how to use it, pm me and i'll give you a break down. do not use it to encrypt a block device !! single files only, and do not use a generated key, use a memorizable alpha-numeric password, else leave it alone.
m
@zacharias.maladroit WHAT HAPPENED TO PERRY !?!?!?!? :crying:

@moonbutt74
I'm sort of wiping the slate clean in several areas of my life - and that (unfortunately) was part of it :angel:

How to increase brightness of the LED flash?

Hi,
It's been a while since I've been trying to increase the brightness of the LED, which unfortunately in our XZP is very low. I tried increasing the value of the file "flashed_calc_parameters.cfg" as in the picture, but I did not get any results. :crying:
Does anyone know how to help me?:victory:
Thanks.

I had the same thought last weekend and I tinkered around a little - without success...
In my Z5 Prem, this file was much more complex and I searched for any comparable values but found nothing.

the_brad said:
I had the same thought last weekend and I tinkered around a little - without success...
In my Z5 Prem, this file was much more complex and I searched for any comparable values but found nothing.
Click to expand...
Click to collapse
I do not understand why sony decided to lower the brightness in the top of the range. I had z5compact and had the same problem, while on m4 aqua the flash was perfectly in line with the other phones.

Nothing?

I mean the brightness of the torch...
Nobody can help me?

Maybe you have to mod kernel to increase current:
https://github.com/AndroPlus-org/an...ot/dts/qcom/msm8998-yoshino-common.dtsi#L3637
I'l try when I have time.
[EDIT]
Tried and didn't work...

AndroPlus said:
Maybe you have to mod kernel to increase current:
https://github.com/AndroPlus-org/an...ot/dts/qcom/msm8998-yoshino-common.dtsi#L3637
I'l try when I have time.
[EDIT]
Tried and didn't work...
Click to expand...
Click to collapse
Editing the file flashed_calc_parameters, I realized that this increases the brightness of the flash fording the photos ...

Now you got my curiosity again...
I tried several things and the most important one seems: The device even boots and the torch stays the same low brightness with an empty flashed_calc_parameters.cfg
I modded it using magisk and it's automount magic.
I also tried the old modded version of my Z5 Premium, which was modded the same way like your Z2 but again nothing.

the_brad said:
Now you got my curiosity again...
I tried several things and the most important one seems: The device even boots and the torch stays the same low brightness with an empty flashed_calc_parameters.cfg
I modded it using magisk and it's automount magic.
I also tried the old modded version of my Z5 Premium, which was modded the same way like your Z2 but again nothing.
Click to expand...
Click to collapse
I edit the file flashed_calc_parameters with "X-plore", granted permission writing, and now I entered the parameters as well as you can view. I think they are too high ... anyway I haven't noticed no difference, if not that of the brightness when shoot a picture with flash, in this case the intensity of the light is definitely increased. the problem is that to me interested only a flashlight ...

I can't find any solution please help me....

I'm still looking for...
Help ?

the torch is utterly pish. if you put a white page up on the screen and ramp up the screen brightness, you get a better flashlight then the one on the back. doesn't help for photos but it might help someone

dazza9075 said:
the torch is utterly pish. if you put a white page up on the screen and ramp up the screen brightness, you get a better flashlight then the one on the back. doesn't help for photos but it might help someone
Click to expand...
Click to collapse
I do not care about the photos, anyway Editing the file you'll have more brightness using flash for photos not for torch, But I often use the flashlight ... The problem is that this sony is really useless for the amount of light ...

AndroPlus said:
Maybe you have to mod kernel to increase current:
https://github.com/AndroPlus-org/an...ot/dts/qcom/msm8998-yoshino-common.dtsi#L3637
I'l try when I have time.
[EDIT]
Tried and didn't work...
Click to expand...
Click to collapse
Is this getting called as well?
https://github.com/AndroPlus-org/an...m/msm/camera_v2/sensor/flash/msm_flash.c#L335

pbarrette said:
Is this getting called as well?
https://github.com/AndroPlus-org/an...m/msm/camera_v2/sensor/flash/msm_flash.c#L335
Click to expand...
Click to collapse
I changed it to LED_FULL but it seems nothing changed...
https://drive.google.com/file/d/1f8BJYYh-srujpLPD8meIDpgol5MgVY_B/view?usp=sharing

AndroPlus said:
I changed it to LED_FULL but it seems nothing changed...
https://drive.google.com/file/d/1f8BJYYh-srujpLPD8meIDpgol5MgVY_B/view?usp=sharing
Click to expand...
Click to collapse
Note that I'm looking at the XZ1c files, because that's what I've got downloaded and extracted, but..
The problem appears to be in libcameralight.so itself.
The flashlight is calling on the function chip_vr_torch_turnon(), which takes no parameters and simply makes a call to chip_torch_set_current(25000).
The camera is instead setting the current first, then calling chip_torch_turnon() which uses the existing, hopefully pre-set, current value.
You can see there difference between the camera flash and the torch from logcat logs:
PHP:
adb logcat -b all | grep libcameralight
Camera Flash:
03-12 20:49:47.430 928 30064 D libcameralight: msm_flash_v2.cpp chip_torch_set_current: current 125000
03-12 20:49:47.430 928 30064 D libcameralight: msm_flash_v2.cpp chip_torch_turnon: start
Torch:
03-12 21:45:29.302 928 1524 D libcameralight: msm_flash_v2.cpp chip_vr_torch_turnon: start
03-12 21:45:29.302 928 1524 D libcameralight: msm_flash_v2.cpp chip_torch_set_current: current 25000
So the camera flash is pushing 125mA (125,000uA) to the LED, while the torch is only pushing 25mA.
Someone would have to shim the chip_vr_torch_turnon() function to read a parameter from a file or setting.
You could probably also hexedit the libcameralight.so files (lib and lib64), but that would have to be a static, non-user-configurable value.
Either would likely still require the mod in msm8998-yoshino-common.dtsi because it also appears to be doing sanity checks against the max brightness values configured in the kernel.
EDIT:
Now that I actually think about it a bit, those values of 125mA and 25mA have got to be wrong.
That's what logcat is reporting, but they have to be much higher than that because there's no way the flash LED is efficient enough to be putting out that much light at 25mA.
So there must be some additional mapping going on beyond what the function calls for to get to what the hardware is actually delivering to the LED.
Still, that mapping is irrelevant to the issue. Shimming the function or modding the libraries is still the only real way forward.

pbarrette said:
EDIT:
Now that I actually think about it a bit, those values of 125mA and 25mA have got to be wrong.
That's what logcat is reporting, but they have to be much higher than that because there's no way the flash LED is efficient enough to be putting out that much light at 25mA.
So there must be some additional mapping going on beyond what the function calls for to get to what the hardware is actually delivering to the LED.
Still, that mapping is irrelevant to the issue. Shimming the function or modding the libraries is still the only real way forward.
Click to expand...
Click to collapse
Nah, that looks about right. The LED is not that bright in Torch mode, you can get better brightness from those cheap button cell torches.
LEDs nowadays are pretty darn efficient.
Looks like you are on the right track for this!

Ok,
So here's a hex-edited mod for the vendor/lib/libcameralight.so and vendor/lib64/libcameralight.so files that changes the call to the chip_torch_set_current() function from chip_torch_set_current(25000) to chip_torch_set_current(65535).
That's the highest value I can do without a shim (or better knowledge of ARM assembly) because the x32 version of the library is using a MOV function to stuff a register with a 16-bit value (0xFFFF).
Standard disclaimer applies: This could literally, physically break your phone.

pbarrette said:
Ok,
So here's a hex-edited mod for the vendor/lib/libcameralight.so and vendor/lib64/libcameralight.so files that changes the call to the chip_torch_set_current() function from chip_torch_set_current(25000) to chip_torch_set_current(65535).
That's the highest value I can do without a shim (or better knowledge of ARM assembly) because the x32 version of the library is using a MOV function to stuff a register with a 16-bit value (0xFFFF).
Standard disclaimer applies: This could literally, physically break your phone.
Click to expand...
Click to collapse
ok pbarrette
i will try it @night
hope it works
edit: working. torch is better led light is brighter now

pbarrette said:
Ok,
So here's a hex-edited mod for the vendor/lib/libcameralight.so and vendor/lib64/libcameralight.so files that changes the call to the chip_torch_set_current() function from chip_torch_set_current(25000) to chip_torch_set_current(65535).
That's the highest value I can do without a shim (or better knowledge of ARM assembly) because the x32 version of the library is using a MOV function to stuff a register with a 16-bit value (0xFFFF).
Standard disclaimer applies: This could literally, physically break your phone.
Click to expand...
Click to collapse
Wow that's really cool ?. It works great... You're super.
Thanks.

POCO F1 Screen Retention/Ghosting Image on custom ROM/Kernel [FIX]

Issue:
1.Some users (like me) must have faced issue of screen ghosting or retention in which if the device is used at max brightness, they see a ghosted image on sides of their phone. (Especially visible when switching from a light theme to dark, for eg, going in chrome incognito mode you will see it)
2.Usually it happens after flashing a custom ROM or kernel.
Fix:
Method 1:
1. In case if its a custom ROM, go to Settings > Display > LiveDisplay
2. Set the Color Profile to ‘Standard'.
3. Go to color calibration setting and set the following values:
Red at 90%
Green at 90%
Blue at 90%.
4. Keep the display screen of for some time (15 min) and boom! Issue solved.
[Note: Max brightness may feel a little less than before but its still better, you will get used to it]
Method 2:
1.In case you have a custom kernel, you can refer to other threads or manually set the values of Red, Green and Blue by yourself by using a ‘Kernel Manager App'.
Just keep it at minimum than its original values.
Conclusion:
This issue is NOT a hardware issue, its a software issue that can be fixed by implementation of any following methods.
Source:
I got through some other threads of Redmi having same issue. Just the difference is in the settings I used, you can customize it as per your own will BUT make sure that the ghosting does not appear by use of that setting. If successful, you may replay

What are you talking about??
This issue is not available in Pixel exp plus pie, is this a Stock rom issue??
but i didn't experience it for whatever hours i was on stock Miui.

It is not software issue, but the low hardware quality I presume

Ravindrasan said:
What are you talking about??
This issue is not available in Pixel exp plus pie, is this a Stock rom issue??
but i didn't experience it for whatever hours i was on stock Miui.
Click to expand...
Click to collapse
It is not the case that every user will face it. In case if it occurs, you may make use of these procedures.
Mostly, if you use max brightness and switch suddenly to dark grey, you can notice it (in custom ROMs / custom kernel ).
Sent from my POCO F1 using XDA Labs

OdinDxD said:
It is not software issue, but the low hardware quality I presume
Click to expand...
Click to collapse
No it is a software issue. I am not talking about the yellow spot issue (that is hardware issue)
This one is ghosting or temporary burn in caused due to change in the default color calibration.
I faced it before but after trying the above settings, even at max brightness, the ghosting did not appear again. So it actually works.
Ghosting does not remain forever in LCD. So its not harmful to hardware in any way. (Just buggy)
Sent from my POCO F1 using XDA Labs

Devlik said:
It is not the case that every user will face it. In case if it occurs, you use make use of these procedures.
Mostly, if you use max brightness and switch suddenly to dark grey, you can notice it (in custom ROMs / custom kernel )
Sent from my POCO F1 using XDA Labs
Click to expand...
Click to collapse
What exactly will i notice, i want to know what happens??

I agree. Screen Retention or Ghosting is mostly present on other devices (I'm not talking about the Pocophone alone but on every other devices) and can be fixed via software implementations or updates. Changing color profile and/or color settings can be a solution too.

Ravindrasan said:
What exactly will i notice, i want to know what happens??
Click to expand...
Click to collapse
Umm. You can google it. For example, look at this picture: (From search result, it just occurred in dark backgrounds in my case)
Sent from my POCO F1 using XDA Labs

Devlik said:
Umm. You can google it. For example, look at this picture: (From search result, it just occurred in dark backgrounds in my case)
Sent from my POCO F1 using XDA Labs
Click to expand...
Click to collapse
Can't it be issue related to bottom bar of chrome (u said when switching to incognito mode)?

Ravindrasan said:
Can't it be issue related to bottom bar of chrome (u said when switching to incognito mode)?
Click to expand...
Click to collapse
Well it appears on every side of the screen and not just bottom. Even when I boot to twrp after being on a bright screen for long time, the status bar, some text and navigation bar appears. ... It fades away tho, not permanent as in amoled. LoL
Sent from my POCO F1 using XDA Labs

Devlik said:
Issue:
1.Some users (like me) must have faced issue of screen ghosting or retention in which if the device is used at max brightness, they see a ghosted image on sides of their phone. (Especially visible when switching from a light theme to dark, for eg, going in chrome incognito mode you will see it)
2.Usually it happens after flashing a custom ROM or kernel.
Fix:
Method 1:
1. In case if its a custom ROM, go to Settings > Display > LiveDisplay
2. Set the Color Profile to ‘Standard'.
3. Go to color calibration setting and set the following values:
Red at 90%
Green at 90%
Blue at 90%.
4. Keep the display screen of for some time (15 min) and boom! Issue solved.
[Note: Max brightness may feel a little less than before but its still better, you will get used to it]
Method 2:
1.In case you have a custom kernel, you can refer to other threads or manually set the values of Red, Green and Blue by yourself by using a ‘Kernel Manager App'.
Just keep it at minimum than its original values.
Conclusion:
This issue is NOT a hardware issue, its a software issue that can be fixed by implementation of any following methods.
Source:
I got through some other threads of Redmi having same issue. Just the difference is in the settings I used, you can customize it as per your own will BUT make sure that the ghosting does not appear by use of that setting. If successful, you may replay
Click to expand...
Click to collapse
I am neither using a custom ROM nor have done anything to change device performance.
---------- Post added at 10:04 AM ---------- Previous post was at 09:54 AM ----------
Devlik said:
Issue:
1.Some users (like me) must have faced issue of screen ghosting or retention in which if the device is used at max brightness, they see a ghosted image on sides of their phone. (Especially visible when switching from a light theme to dark, for eg, going in chrome incognito mode you will see it)
2.Usually it happens after flashing a custom ROM or kernel.
Fix:
Method 1:
1. In case if its a custom ROM, go to Settings > Display > LiveDisplay
2. Set the Color Profile to ‘Standard'.
3. Go to color calibration setting and set the following values:
Red at 90%
Green at 90%
Blue at 90%.
4. Keep the display screen of for some time (15 min) and boom! Issue solved.
[Note: Max brightness may feel a little less than before but its still better, you will get used to it]
Method 2:
1.In case you have a custom kernel, you can refer to other threads or manually set the values of Red, Green and Blue by yourself by using a ‘Kernel Manager App'.
Just keep it at minimum than its original values.
Conclusion:
This issue is NOT a hardware issue, its a software issue that can be fixed by implementation of any following methods.
Source:
I got through some other threads of Redmi having same issue. Just the difference is in the settings I used, you can customize it as per your own will BUT make sure that the ghosting does not appear by use of that setting. If successful, you may replay
Click to expand...
Click to collapse
I am neither using a custom ROM nor have done anything in past which can have these after effects. I am facing these issue or may be noticeable after the rollout of the MIUI11 ROM. So i contacted other who owns pocof1 , but their device don't have these issues. Then i contacted the service center and they reinstalled the MIUI11 but the problem persists.
So then i thinking of a screen replacement since i m on a warranty period so should i do that to solve this issue?.
Also u gave the settings to resolve the issue for a stock/CustomUI but wht for the MIUI , pls give the setting for them too.
pls answer all my queries!

Kakipa said:
I am neither using a custom ROM nor have done anything to change device performance.
---------- Post added at 10:04 AM ---------- Previous post was at 09:54 AM ----------
I am neither using a custom ROM nor have done anything in past which can have these after effects. I am facing these issue or may be noticeable after the rollout of the MIUI11 ROM. So i contacted other who owns pocof1 , but their device don't have these issues. Then i contacted the service center and they reinstalled the MIUI11 but the problem persists.
So then i thinking of a screen replacement since i m on a warranty period so should i do that to solve this issue?.
Also u gave the settings to resolve the issue for a stock/CustomUI but wht for the MIUI , pls give the setting for them too.
pls answer all my queries!
Click to expand...
Click to collapse
This reply is pretty late, sorry for that.
1.You need to be rooted.
2.Download ColorChanger app from PlayStore.
3.Give root privileges.
4.Decrease the color in Custom1/Custom2/Custom3 by long tapping to these values:
R:240
G:240
B:240
S:1.00.
5.Save it (top left corner)
Con: You need to apply this every time you boot into your device.
You can upgrade to pro and enable “Activate on boot" from app setting to make this happen automatically.

I did it but it doesn't work, I'll consider change the hole panel

Can you take a look at the attached screenshot and confirm if these values are okay. Apart from RGB values, do I need to tweak anything else? Thanks in advance.

Oh I see, I got this problem, and realize I set livedisplay profile to dynamic. I thought my screen was wore out

Devlik said:
This reply is pretty late, sorry for that.
1.You need to be rooted.
2.Download ColorChanger app from PlayStore.
3.Give root privileges.
4.Decrease the color in Custom1/Custom2/Custom3 by long tapping to these values:
R:240
G:240
B:240
S:1.00.
5.Save it (top left corner)
Con: You need to apply this every time you boot into your device.
You can upgrade to pro and enable “Activate on boot" from app setting to make this happen automatically.
Click to expand...
Click to collapse
Is it a s/w or h/w issue and if i install custom ROM(pixel experience) will that help

Kakipa said:
Is it a s/w or h/w issue and if i install custom ROM(pixel experience) will that help
Click to expand...
Click to collapse
This is a hardware problem, i tried everything and failed so i got original lcd folder replaced from the service center and now no screen retention.

I am from India itself, do you know which service center to go to? Since poco split from mi, am i in trouble or i should head to the mi service center. And my is under a warranty of 6 months and i'm in the 3rd month now....is it free or you got to pay money for the service?
Thanks in Advance.

Deleted

I solve this problem on miui oficial without root, Just applying standard contrast on screen settings.