Database Info

[APP] TorchButton v2.3, using camera LED as flashlight [UPDATED Dec 8]

Continuing my quest of using the LED as flashlight for my new HD2, I updated TorchButton to support the HD2 as well.
Dropped your keys? Finding something behind the bench? Performing surgery on a computer and need to find that jumper on the mainboard?
This is a simple application built for some HTC devices that have a hardware LED, normally used to take pictures in the dark. However I found the LED to be perfect to be used as a handy pocket flashlight.
Usage
There is no GUI for this application. Just start TorchButton to enable the LED on the back of your device. Start TorchButton again to turn it off.
Check out the readme if you're an advanced user and wish to change some registry settings, i.e. to allow a longer maximum time the LED is enabled.
Known issues
- [Fixed] New icons are not working when TorchButton is installed to Storage Card
Todo
- Create an app to configure the registry settings
- See if support for Omnia Pro (B7610) is feasible (someone should send me the related dlls...)
- [Done] Add a seperate timeout for bright mode
- [Done] Add blink mode with bright led
- [Done] Use new icons provided by tnyynt
- [Done] Add support for Omnia (the one found here)
- [Impossible] See if it's possible to control leds seperately ('economic mode') Sorry, this is not possible. (Tech-talk: setting a single GPIO enables both LEDs. There doesn't seem to be a GPIO for each LED seperately.)
Wishful thinking
- Camera app to interpret the morse
History
Version 2.3
- Fix icons not showing in HTC Sense or WM 6.5 start menu when installed to Storage Card.
Version 2.2
- New icons for all TorchButton apps (thanks tnyynt!). These only work in WM6.5 and up. Older OS's will still see the old icons.
- Added registry setting to use bright setting in blink mode (see BlinkUsesBrightMode).
- Bright mode now has a seperate timeout, configurable in registry (see BrightModeTimeout).
- Added support for Samsung Omnia i9x0 devices (hopefully they all work). Thanks to raph/zemrwhite2/PaSSoA. Thanks to Chainfire for testing on his Omnia i900L.
- [edit] Shortcut names have changed. I found them nicer this way, no two-line icons. And the text is now also not cut-off when added as shortcut in the home screen.
- [edit] Improved handling of bright mode. It should stop immediately now when pressed again, instead of waiting for a 500ms interval. This makes BlinkUsesBrightMode possible combined with low intervals for blink mode.
- [edit] Soft-reset your phone after upgrading from an older version! Else the new icons will not show.
Version 2.1
- Bright mode is now support on the HTC HD2 (Leo).
- Added a one-time warning message when bright mode is used for the first time.
Version 2.0
- Initial version with support for the HTC HD2 (Leo) (bright mode is not supported on the Leo)
Version 1.x
- Support for the Touch Pro

Dont think about something. Untill i read your post. This could be handy sometimes. Thnx

Awesome man I was just thinking how I missed that
Btw what's missing for bright mode to work? If I'm not mistaken there is a brighter mode just before taking a pic.

Thanks! I was dissapointed that hTorch didn't work on the HD2 now I got this. Wonderful!

Great ! thanks
Have it on my Omnia and was hoping to have it for my future HD2 !

You're all welcome! Glad to hear you like it.
12aon said:
Awesome man I was just thinking how I missed that
Btw what's missing for bright mode to work? If I'm not mistaken there is a brighter mode just before taking a pic.
Click to expand...
Click to collapse
The mode is there, but it's not as easily called as it was on the Touch Pro. In fact I haven't found the API call at all yet. May need some hacking around the API to get that to work. The normal mode produces _quite_ the amount of light though, it's even more light than the bright mode of the Touch Pro thanks to the dual led.
Zero Masamune said:
Thanks! I was dissapointed that hTorch didn't work on the HD2 now I got this. Wonderful!
Click to expand...
Click to collapse
hTorch will work again once I update the C# wrapper to support the Leo, as hTorch makes use of my C# library. I'll do that somewhere in the upcoming week.

Great, works perfect ! Txs

Can anyone confirm this don't burn anything out? On the X1 the light modules weren't heatsinked properly and caused vibrator motor to screw up after 15secs use as a torch.
Thanks!

kinnyfaifai said:
Can anyone confirm this don't burn anything out? On the X1 the light modules weren't heatsinked properly and caused vibrator motor to screw up after 15secs use as a torch.
Thanks!
Click to expand...
Click to collapse
I can't confirm it won't ever burn out. However, realise that enabling the LED is actually the same as using your camera with the lights on in the dark. This _shoud_ be possible for prolonged times as well.
Were you using the 'bright' setting on the X1? (If that's possible there.) That might explain it better... otherwise you could just send in the device for repair, as it's normal use of the device. Especially if it's after only 15 seconds.

NetRipper said:
I can't confirm it won't ever burn out. However, realise that enabling the LED is actually the same as using your camera with the lights on in the dark. This _shoud_ be possible for prolonged times as well.
Were you using the 'bright' setting on the X1? (If that's possible there.) That might explain it better... otherwise you could just send in the device for repair, as it's normal use of the device. Especially if it's after only 15 seconds.
Click to expand...
Click to collapse
It was a known problem that the LEDs weren't heatsinked properly on the X1 and there was a huge warning on using hTorch. I've not installed hTorch and never used the LEDs on my X1 as a torch cos of this oversight by the manufacturer. I do miss being able to use the LEDs as a torch though, it's very handy.

Heej nice, i come from oud-Beijerland

nice app, but bright mode doesn`t work for me..

NetRipper said:
Continuing my quest of using the LED as flashlight for my new HD2, I updated TorchButton to support the HD2 as well.
Dropped your keys? Finding something behind the bench? Performing surgery on a computer and need to find that jumper on the mainboard?
This is a simple application built for some HTC devices that have a hardware LED, normally used to take pictures in the dark. However I found the LED to be perfect to be used as a handy pocket flashlight.
Usage
There is no GUI for this application. Just start TorchButton to enable the LED on the back of your device. Start TorchButton again to turn it off.
Check out the readme if you're an advanced user and wish to change some registry settings, i.e. to allow a longer maximum time the LED is enabled.
History
Version 2.0
- Initial version with support for the HTC HD2 (Leo) (bright mode is not supported on the Leo)
Version 1.x
- Support for the Touch Pro
Click to expand...
Click to collapse
20mihalko said:
nice app, but bright mode doesn`t work for me..
Click to expand...
Click to collapse
Isn't it clearly stated that brightmode doesn't work.......jeez....dude...read

ET said:
Isn't it clearly stated that brightmode doesn't work.......jeez....dude...read
Click to expand...
Click to collapse
sorry, my mistake

kinnyfaifai said:
It was a known problem that the LEDs weren't heatsinked properly on the X1 and there was a huge warning on using hTorch. I've not installed hTorch and never used the LEDs on my X1 as a torch cos of this oversight by the manufacturer. I do miss being able to use the LEDs as a torch though, it's very handy.
Click to expand...
Click to collapse
The vibrate function does not work at all on my X1 after installing and using hTorch. User beware..!
This is my next phone when O2 decide to put it on their shelves, and hopefully its built better than the X1.

Any chance of some source code?
I've been looking through the HD2 camera drivers, and have found a few things that should be the LED (can't test it as I have no device), but am wondering if it's the same method as yours!

l3v5y said:
Any chance of some source code?
I've been looking through the HD2 camera drivers, and have found a few things that should be the LED (can't test it as I have no device), but am wondering if it's the same method as yours!
Click to expand...
Click to collapse
Here are the important code snippets of the API that I'm using. The methods were pretty obvious (luckily).
typedef int (__stdcall *LEO_INIT)();
typedef int (__stdcall *LEO_SETCURRENT)(DWORD dw1);
...
LEO_INIT InitFlashLight;
LEO_SETCURRENT PMICFlashLED_SetCurrent;
...
hCamera=LoadLibrary(L"CameraPlatform.dll");
...
InitFlashLight = (LEO_INIT) GetProcAddress(hCamera, L"InitFlashLight");
PMICFlashLED_SetCurrent = (LEO_SETCURRENT) GetProcAddress(hCamera, L"PMICFlashLED_SetCurrent");
...
InitFlashLight(); // must be called before SetCurrent has any effect
...
PMICFlashLED_SetCurrent(0); // turns it off
PMICFlashLED_SetCurrent(1); // turns it on
There's also a PMICFlashLED_SetMode(x); but I haven't been able to figure out what it does. As far as I could see when disassembling it wants one parameter.
If you have any ideas on the bright mode, they'd be more than welcome. If you want the full source to make some modifications or to toy with it, let me know.

NetRipper said:
Here are the important code snippets of the API that I'm using. The methods were pretty obvious (luckily).
typedef int (__stdcall *LEO_INIT)();
typedef int (__stdcall *LEO_SETCURRENT)(DWORD dw1);
...
LEO_INIT InitFlashLight;
LEO_SETCURRENT PMICFlashLED_SetCurrent;
...
hCamera=LoadLibrary(L"CameraPlatform.dll");
...
InitFlashLight = (LEO_INIT) GetProcAddress(hCamera, L"InitFlashLight");
PMICFlashLED_SetCurrent = (LEO_SETCURRENT) GetProcAddress(hCamera, L"PMICFlashLED_SetCurrent");
...
InitFlashLight(); // must be called before SetCurrent has any effect
...
PMICFlashLED_SetCurrent(0); // turns it off
PMICFlashLED_SetCurrent(1); // turns it on
There's also a PMICFlashLED_SetMode(x); but I haven't been able to figure out what it does. As far as I could see when disassembling it wants one parameter.
If you have any ideas on the bright mode, they'd be more than welcome. If you want the full source to make some modifications or to toy with it, let me know.
Click to expand...
Click to collapse
That's what I'd come to as a conclusion, so glad that works!
Is there any need to un-init the flash light?
PMICFlashLED_SetMode will probably need some playing around, though might enable your "bright" mode. Will have a play with that when I get an HD2!

l3v5y said:
That's what I'd come to as a conclusion, so glad that works!
Is there any need to un-init the flash light?
PMICFlashLED_SetMode will probably need some playing around, though might enable your "bright" mode. Will have a play with that when I get an HD2!
Click to expand...
Click to collapse
There doesn't seem to be an un-init function. However, the debug console shows that it detects when the DLL is being attached to or detached from, so there's probably some cleanup code there.
I also haven't found any side-effects yet. TorchButton works fine even when the camera app is running. They don't interfere with eachother (other than toggling the LED to their own behalf). On the Touch Pro it wasn't possible to run TorchButton and the camera app at the same time. Not that I ever wanted to, but still.
In regard to that mode function. It must be for something. I tried using it in various ways already but it didn't matter. Maybe you'll have more luck

might be confused right now, but seems that when in camera mode, and battery is below 50% you cant use the flash - anybody know if this will affect the app?
haven't got my hd2 yet so cant help you out, but there's a thread under the Leo -- > Leo sub-forum
cheerios!

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

Ask any question thread

I was meaning to make this thread and forgot all the questions I had.
I'll start with one, does the CM rom have dual sim function?

I can't seem to find the data usage in settings unless miui removed it?

ermacwins said:
I can't seem to find the data usage in settings unless miui removed it?
Click to expand...
Click to collapse
In the security app

Does the screen type we have get screen burns?

ermacwins said:
Does the screen type we have get screen burns?
Click to expand...
Click to collapse
i think your battery is empty before that happens
Found this on ars technica site:
Actually it's physically impossible for an LCD to get screen burn - that refers to the phosphorous coating on old CRTs where the electron beam actually burnt away the coating... (which is technically reversible, however I doubt it would be economically feasible and requires specialist equipment)
LCDs suffer from a something similar - which is called image persistence, a static image causes a parasitic capacitance to build up which prevents the liquid crystal molecules from returning to their normal relaxed state. The good news is that it's reversible and can be performed by an end user.
It can usually be recovered by displaying a full white screen and depending on the severity of the persistent image it can be recovered in as little as an hour...
Also due to the nature of IPS panels they tend to suffer the image persistence problems sooner than other LCD panels. Modern laptops shouldn't suffer from image ghosting (not at a hardware level anyway) - on older panels is was caused by slow refresh rates and panel response times (The old cursor submarining on Apple PowerBook 140s spring to mind). Extremes in temperatures can cause ghosting or panel lethargy in older panels - most modern panels have impressive temperature ranges...
Source: http://arstechnica.com/civis/viewtopic.php?t=1206279

I guess I can install the nav bar mod without worrying about screen burns then

Yes

I did install soft buttons last week but it wasn't transparent where aosp based roms are and was worried about screen burns so removed it

ermacwins said:
I did install soft buttons last week but it wasn't transparent where aosp based roms are and was worried about screen burns so removed it
Click to expand...
Click to collapse
But on other phones they are often also not transparent

Example being the desktop, its transparent and some apps also have it transparent

ermacwins said:
Example being the desktop, its transparent and some apps also have it transparent
Click to expand...
Click to collapse
Yes, but before Android KitKat almost all nav bars were black

Yea I know that, just want it to mimic nexus method

Is there any app that can assign long press actions to Tue capacitive keys? I need long press menu/recents button launch last app. Sadly miui doesn't have this. I know cm rom has it but need it on miui rom.

ermacwins said:
I was meaning to make this thread and forgot all the questions I had.
I'll start with one, does the CM rom have dual sim function?
Click to expand...
Click to collapse
To answer original question, yes, dual sim works well. You assign which sim to use for outgoing calls or to ask you every time which sim to use. same with sms. For data you assign one sim.
The one sim that is primary can use 3g, lte, while the secondary uses 2g (from what i have observed).

Hello, are there any Mi4c users using CDMA/Evdo Rev. A networks? I'm using CDMA networks but the data connection not working at all neither through CDMA or Evdo Rev. A or even LTE, but the sms & voice working normal. Has anyone facing the same problem? Maybe has solution to it?
Thanks.

Anyone else have issues with the alarm not ringing in the morning, after the phone haven't been used for 6-8 hours during the night? I'm currently using Sleep as Android as my alarm app and I've set the alarm to ring every morning, but it never does. I assume this is because of MiUI's memory optimization, which causes it to shutdown the app during the night and therefore the alarm won't ring when I've set it to.
I've tried looking for an option to customize/turn off the memory optimization for certain apps, but I can't seem to find any option for this. Anyone experienced the same issues and have any solution to it, because the alarm is kinda necessary for me ^^

Well the default alarm works fine for me and I'm on build 5.11.5

Default alarm app works fine for me too

ermacwins said:
Well the default alarm works fine for me and I'm on build 5.11.5
Click to expand...
Click to collapse
rob rich said:
Default alarm app works fine for me too
Click to expand...
Click to collapse
Hm, alright.. maybe I should try to use the default alarm and see if it works. You don't have any ideas of why Sleep as Android isn't working? I have tried to set the alarm during the day when I'm constantly using the phone and then the alarm is working perfectly, so it seems like the phone is doing something during the night that turns off the app.
Thanks for your answers.

Is there any way of preventing the miui CD mounting when connecting to PC with USB?

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:

Screen brightness "flickering" on non stock ROMs

Hi, finally I have time to make a thread about this. The problem is present on every non stock ROM, no matter if it is lollipop, MM or Nougat based. At low brightness, it seems like the screen is uppering-lowering brightness really fast. I have made a video, because "maybe" I didn't explain it very well :silly:
https://drive.google.com/open?id=0B1r3IiDMSm40R3Y0NlhzQXowOGs
(the phone is placed in the dock but it is NOT charging, in case you wonder. Also there is a small line of pixels that look like "interferences", at the right of the screen, near navigation bar, but this only happened with a kernel provided by optimumpro in order to try fixing the flickering issue)
Here and here I attached logs with different ROMs. (these ones have already been reviewed in other previous posts, but maybe they are still useful)
Nailyk asked me if the problem is present in recovery too, but I can't tell you, since the screen background in recovery is black and the flickering is more easily noticeable in white backgrounds. Anyway, I'd say that there is no flickering in recovery but I'm not sure. I may need a white themed recovery with a vey low minimum brightness value.
Also, it seems like I'm the only one with this problem (AFAIK) so there's always the chance that it is a hardware issue with my phone, but it would be strange cause with stock ROMs the screen is perfect, and screen brightness can go very low without problems.
So I am here to ask for help, and to help helping anyone interested in fixing the issue. Thank you very much!
@nailyk @optimumpro @Myself5

i too face this issue... i think this issue is GPU related... i also have flickering on stock roms. but of i keep my device warm enough.. the flickering goes away...

Interesting. I will test it again in a warm environment. But I think that this starts to sound more like a hardware issue...
Sent from my D6603 using Tapatalk

Glad you opened the thread.
About recovery it will be interesting to know if it is only kernel or rom+kernel issue.
Also flashing a recovery is faster than a full rom for testing purpose.

nailyk said:
Glad you opened the thread.
About recovery it will be interesting to know if it is only kernel or rom+kernel issue.
Also flashing a recovery is faster than a full rom for testing purpose.
Click to expand...
Click to collapse
I've installed a white theme in twrp and I didn't notice any flickering.
News: the bug is also present in Concept rom. I've checked twice and it is. But I forgot to take any log, so if you need them just tell me.
Also, I've checked very carefully if there's any slight flickering on stock Sony rom (actually I'm on ExistenZ with EliteKernel) and there isn't. I even lowered brightness to the minimum via kernel settings, as EliteKernel allows you to tweak colors, and I still don't see any flickering.
Sent from my D6603 using Tapatalk

blackhawk_LA said:
I've installed a white theme in twrp and I didn't notice any flickering.
News: the bug is also present in Concept rom. I've checked twice and it is. But I forgot to take any log, so if you need them just tell me.
Also, I've checked very carefully if there's any slight flickering on stock Sony rom (actually I'm on ExistenZ with EliteKernel) and there isn't. I even lowered brightness to the minimum via kernel settings, as EliteKernel allows you to tweak colors, and I still don't see any flickering.
Click to expand...
Click to collapse
Interesting.
Right now I don't have lot of time. As this flickering doesn't produce into recovery it shouldn't be kernel related.
Here are some experiments you can do: Set a high value to screen timeout then on root:
Code:
[email protected]:/ # find /sys -iname "*bright*"
/sys/devices/leds-qpnp-23/leds/rgb/brightness
/sys/devices/leds-qpnp-23/leds/rgb/max_brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_green/brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_green/max_brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_blue/brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_blue/max_brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_red/brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_red/max_brightness
/sys/devices/leds-qpnp-24/leds/wled:backlight/brightness
/sys/devices/leds-qpnp-24/leds/wled:backlight/max_brightness
[B]/sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/brightness
/sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/max_brightness[/B]
/sys/devices/msm_sdcc.1/leds/mmc1::/brightness
/sys/devices/msm_sdcc.1/leds/mmc1::/max_brightness
/sys/devices/msm_sdcc.2/leds/mmc2::/brightness
/sys/devices/msm_sdcc.2/leds/mmc2::/max_brightness
The two interesting values are lcd-backlight/max_brightness & lcd-backlight/brightness. Your path will differ, depending on the kernel used, panel, etc...
Code:
[email protected]:/ # cat /sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/max_brightness
255
Here is my max value with a specific rom. Then I can set any value 1<x<255:
Code:
[email protected]:/ # echo 20 > /sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/brightness
and see the back-light changing.
Please make some experiments with this and collect data. Like working rom name, backlight_max_value, flickering start at 10, kernel version, and path of /brigthness.
If it is related to this value you should be able to reproduce into recovery.
P.S.: I just test on the CM-12.1 and notice something weird:
Code:
[email protected]:/ # cat /sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/max_brightness
4095
[email protected]:/ # cat /sys/devices/01-qcom,leds-d800/leds/wled:backlight/max_brightness
255
and only /sys/devices/01-qcom,leds-d800/leds/wled:backlight/brightness is affecting backlight.
Noticed flickering for 1 to 4 on my device.

Thanks for your time! I'm right now on Jaguar ROM (5.1.1)
/sys/devices/leds-qpnp-23/leds/rgb/brightness
/sys/devices/leds-qpnp-23/leds/rgb/max_brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_green/brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_green/max_brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_blue/brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_blue/max_brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_red/brightness
/sys/devices/leds-qpnp-23/leds/led:rgb_red/max_brightness
/sys/devices/leds-qpnp-24/leds/wled:backlight/brightness
/sys/devices/leds-qpnp-24/leds/wled:backlight/max_brightness
/sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/brightness
/sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/max_brightness
/sys/devices/msm_sdcc.1/leds/mmc1::/brightness
/sys/devices/msm_sdcc.1/leds/mmc1::/max_brightness
/sys/devices/msm_sdcc.2/leds/mmc2::/brightness
/sys/devices/msm_sdcc.2/leds/mmc2::/max_brightness
Click to expand...
Click to collapse
and I have been playing with
/sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/brightness
Click to expand...
Click to collapse
The flickering is present with values from 1 to 5, maybe 6.
Stock values on ROM were
/sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/brightness = 4095
/sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/max_brightness = 4095
Click to expand...
Click to collapse
but I have no /sys/devices/01-qcom,leds-d800/leds/wled:backlight/max_brightness directory, nor something similar.
Eit: Mmm I don't know what I've done, but right now changing the setting
/sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/brightness
Click to expand...
Click to collapse
does nothing. I'll try again to find what I've done different. I'm a bit disaster, I know. I don't know how I've changed birghtness with these commands :S

blackhawk_LA said:
Thanks for your time! I'm right now on Jaguar ROM (5.1.1) and I have been playing with
The flickering is present with values from 1 to 5, maybe 6.
but I have no /sys/devices/01-qcom,leds-d800/leds/wled:backlight/max_brightness directory, nor something similar.
Click to expand...
Click to collapse
Use a find command like:
Code:
find /sys -iname "*bright*"
Anyway I noticed a problem on the cm-12.1 related to this. Didn't find the exact bug right now. My workaround was: trigger max value (with the slide) then go back to the wanted value. Flickering disappear. Need to reproduce to fix.

i have the flickring and ghosting when my z3 is cold and the problem gone when it heats a bit
could this problem be from my rom (6.0.1 ExistenZ)!
---------- Post added at 01:55 PM ---------- Previous post was at 01:51 PM ----------
TechnoFreak750 said:
i too face this issue... i think this issue is GPU related... i also have flickering on stock roms. but of i keep my device warm enough.. the flickering goes away...
Click to expand...
Click to collapse
Same happens with me
i think its hardware issue

If it happens on stock rom it sounds like hardware related, but as for me it doesn't happen in stock roms, maybe it's a mix of hardware - software.
Could you take a dmesg (better if you do it just after booting) to see which model is your panel? If you don't know about adb, you can do it with this app https://play.google.com/store/apps/details?id=com.eolwral.osmonitor Go to settings, check root permissions, then go to messages -dmesg and export. @TechnoFreak750
Sent from my D6603 using Tapatalk

@nailyk @optimumpro
In stock Sony ROM there is the same 4095 for max brightness
[email protected]:/ # find /sys -iname "*bright*"
/sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/brightness
/sys/devices/mdp.0/qcom,mdss_fb_primary.168/leds/lcd-backlight/max_brightness
/sys/devices/leds-qpnp-ec948600/leds/rgb/brightness
/sys/devices/leds-qpnp-ec948600/leds/rgb/max_brightness
/sys/devices/leds-qpnp-ec948600/leds/led:rgb_green/brightness
/sys/devices/leds-qpnp-ec948600/leds/led:rgb_green/max_brightness
/sys/devices/leds-qpnp-ec948600/leds/led:rgb_blue/brightness
/sys/devices/leds-qpnp-ec948600/leds/led:rgb_blue/max_brightness
/sys/devices/leds-qpnp-ec948600/leds/led:rgb_red/brightness
/sys/devices/leds-qpnp-ec948600/leds/led:rgb_red/max_brightness
/sys/devices/leds-qpnp-ec948800/leds/wled:backlight/brightness
/sys/devices/leds-qpnp-ec948800/leds/wled:backlight/max_brightness
/sys/devices/msm_sdcc.1/leds/mmc1::/brightness
/sys/devices/msm_sdcc.1/leds/mmc1::/max_brightness
/sys/devices/msm_sdcc.2/leds/mmc2::/brightness
/sys/devices/msm_sdcc.2/leds/mmc2::/max_brightness
Click to expand...
Click to collapse
And the screen brightness is changed (at least) by the lines marked in bold. I haven't try the others as I don't know if they are screen related, notificacion LED or whatever.
Edited: One more thing. The minimum brightness in stock ROM is 29. If manually set to a low value, let's say 4, editing the file, the flickering appears on stock ROMs. Now I'm going to try Jaguar ROM again to see if "29" is as dark as stock (I will have to trust my eyes and memory), and if there's flickering with these value. Because I always felt that stock ROMs were at least as dark as AOSP when using minimum brightness in settings.
Edited 2: On Jaguar, with /sys/devices/leds-qpnp-24/leds/wled:backlight/brightness = 29 there's no flickering. It seems brighter than in stock but probably it's my perception, as I can't compare at the same time.
I think we can assume that it's somehow hardware related, but I don't know if there is any software solution or improvement, since the software and the "routes" are different in stock and AOSP.

blackhawk_LA said:
@nailyk @optimumpro
In stock Sony ROM there is the same 4095 for max brightness
And the screen brightness is changed (at least) by the lines marked in bold. I haven't try the others as I don't know if they are screen related, notificacion LED or whatever.
Edited: One more thing. The minimum brightness in stock ROM is 29. If manually set to a low value, let's say 4, editing the file, the flickering appears on stock ROMs. Now I'm going to try Jaguar ROM again to see if "29" is as dark as stock (I will have to trust my eyes and memory), and if there's flickering with these value. Because I always felt that stock ROMs were at least as dark as AOSP when using minimum brightness in settings.
Edited 2: On Jaguar, with /sys/devices/leds-qpnp-24/leds/wled:backlight/brightness = 29 there's no flickering. It seems brighter than in stock but probably it's my perception, as I can't compare at the same time.
I think we can assume that it's somehow hardware related, but I don't know if there is any software solution or improvement, since the software and the "routes" are different in stock and AOSP.
Click to expand...
Click to collapse
Great report.
Setting a 29 value will not provide the same result if max_brightness is 4095 or 255
Suppose 29 was set with max_brightness 4095 it will have a corresponding value of 2 for max_brightness 255. (cross multiplication: (255*29)/4095=1.2)
I remember reading in another thread that you are using cm-12.1 right now. Is it right?
P.S.: you can play with /sys/devices/leds-qpnp-ec948600/leds/led:rgb_*/brightness , it will bright up the notification led

nailyk said:
Great report.
Setting a 29 value will not provide the same result if max_brightness is 4095 or 255
Suppose 29 was set with max_brightness 4095 it will have a corresponding value of 2 for max_brightness 255. (cross multiplication: (255*29)/4095=1.2)
I remember reading in another thread that you are using cm-12.1 right now. Is it right?
P.S.: you can play with /sys/devices/leds-qpnp-ec948600/leds/led:rgb_*/brightness , it will bright up the notification led
Click to expand...
Click to collapse
Yes, I had some problems with Gmail on Jaguar and also I missed cm themes, so right now I'm on your latest cm12.1 A great daily driver!
Sent from my Xperia Z3 using Tapatalk

blackhawk_LA said:
If it happens on stock rom it sounds like hardware related, but as for me it doesn't happen in stock roms, maybe it's a mix of hardware - software.
Could you take a dmesg (better if you do it just after booting) to see which model is your panel? If you don't know about adb, you can do it with this app https://play.google.com/store/apps/details?id=com.eolwral.osmonitor Go to settings, check root permissions, then go to messages -dmesg and export. @TechnoFreak750
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
i have tried aosp, lineage os etc.. it always happens. finally the sulution is just keep your device warm enough.

TechnoFreak750 said:
i have tried aosp, lineage os etc.. it always happens. finally the sulution is just keep your device warm enough.
Click to expand...
Click to collapse
Can you tell us more details please? (step to reproduce)
Also do you have an original panel? If it is a replaced one read the thread to reproduce tests and giving us the panel name.
cc: @xkeita