Develop Bugs

[RECOVERY] ClockworkMod TOUCH 5.5.0.4 v4.3 - (7/9/12)

This is gweedo767's touch recovery ported to the skyrocket/hercules. Because many people have been asking me what the difference between this one and the version that koush put out here is the difference:
This one is open source.
This one has swipe gestures (up,down,left,right)
This one has different UI settings
This one has soft keys on the bottom of the screen
This one has 2 different options of font
Here is a youtube video I made of how it works: ------> VIDEO
4 ways to use recovery:
volume rockers
soft keys on bottom of screen
capacitive buttons
swipe gestures (up/down = scroll && left = back && right = select)
HOW TO INSTALL:​
CWMR5504_INSTALL-4.3.zip (NEW ICS BACKGROUND): ---------> BLUE-FONT
CWMR5504_INSTALL-4.3.zip (NEW ICS BACKGROUND): ---------> ROBOTO-FONT
- Just flash in CWM
Click to expand...
Click to collapse
TERMINAL INSTALL:​
recovery.img: (NEW ICS BACKGROUND) ----------------> BLUE-FONT
recovery.img: (NEW ICS BACKGROUND) ----------------> ROBOTO-FONT
- download to sdcard
- open terminal emulator (or adb) type:
Code:
$ su
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22 bs=4096
Click to expand...
Click to collapse
Odin Install​
recovery.tar.md5 (NEW ICS BACKGROUND): ---------> BLUE-FONT
recovery.tar.md5 (NEW ICS BACKGROUND): ---------> ROBOTO-FONT
Click to expand...
Click to collapse
Test Drive:​
CWMRT5504_TEST-4.3.zip(NEW ICS BACKGROUND): -------------------> BLUE-FONT
CWMRT5504_TEST-4.3.zip(NEW ICS BACKGROUND): -------------------> ROBOTO-FONT
(This will not alter ANY files on your phone. It is just a test drive basically. You flash it through ClockworkMod that you have already installed and it runs over it showing you how it would be if you did install it. Once you reboot you will still have the same recovery that you had.)
Click to expand...
Click to collapse
v1:
Code:
- Initial release
v2:
Code:
- fixed "back button disabled/enabled" when scrolling past top to bottom
- 2 different font versions (roboto and normal)
-- roboto font is a little bigger
- complete fix of adb and usb mounting
v2.5:
Code:
- added a cool new ICS background! (thanks CyanmodICS for the idea)
- added green/red font versions
- cleaned up the code a bit
v3:
Code:
- in process of fixing hanging backup issue (need extensive list of apps people have installed when having issue)
- fixed ALOT of bugs
- added many more options for internal/external sdcard
- more....(i cant remember)
- i will add the other color options back in a few days
v3.5
Code:
- fixed recovery.fstab to mount internal sdcard as /sdcard to recognize .hidenandroidprogress file
- ascii art???
v4.0
Code:
- fixed the fix_permissions not working (thanks minotauri)
- fixed sd-ext and .android_secure errors in backup
v4.1
Code:
- re-arranged order of "install from internal/external sdcard" to put internal first
- added "Reboot Recovery" option to the bottom of the advanced menu
- a few code cleanups
v4.2
Code:
- fixed bug where background would reset to blank black after installing a zip/backing up/restoring
- added option to reboot into download mode in advanced>>reboot download mode
v4.3
Code:
- hopefully fixed the hanging backup bug once and for all
- merged all of CWM's latest code changes
Thanks to:
Code:
gweedo767
plastikman
utkanos
romracer

what is the difference between this one and the one that was posted a few weeks ago? I see this is 5.5.0.4 and the other is 5.8.1.3 so does that mean that this is older or is the other older? I am just a little confused sorry for the noob questions.

mojorisin7178 said:
what is the difference between this one and the one that was posted a few weeks ago? I see this is 5.5.0.4 and the other is 5.8.1.3 so does that mean that this is older or is the other older? I am just a little confused sorry for the noob questions.
Click to expand...
Click to collapse
np. are you talking about the one from koush? from rom manager? so that one is all 'tap' to select. and it seems all cluttered and hard to use for me. this one has swipe gestures and soft keys on the bottom and this one is actually open source (heaven forbid koush make his open source....) which means that if there are aspects that people want changed we can go in and change them freely, which has been done already. yes, this one is a lower version but there are no real changes in the 2 builds. try this one out and see for yourself the difference and let me know if you do or do not like it (hopefully you do ) and if you dont you can easily go back to the one you had before.

sk8erwitskil said:
np. are you talking about the one from koush? from rom manager? so that one is all 'tap' to select. and it seems all cluttered and hard to use for me. this one has swipe gestures and soft keys on the bottom and this one is actually open source (heaven forbid koush make his open source....) which means that if there are aspects that people want changed we can go in and change them freely, which has been done already. yes, this one is a lower version but there are no real changes in the 2 builds. try this one out and see for yourself the difference and let me know if you do or do not like it (hopefully you do ) and if you dont you can easily go back to the one you had before.
Click to expand...
Click to collapse
have backups/restores been tested to work pretty solidly? I only read that the interface navigation had been tested.

sk8erwitskil said:
np. are you talking about the one from koush? from rom manager? so that one is all 'tap' to select. and it seems all cluttered and hard to use for me. this one has swipe gestures and soft keys on the bottom and this one is actually open source (heaven forbid koush make his open source....) which means that if there are aspects that people want changed we can go in and change them freely, which has been done already. yes, this one is a lower version but there are no real changes in the 2 builds. try this one out and see for yourself the difference and let me know if you do or do not like it (hopefully you do ) and if you dont you can easily go back to the one you had before.
Click to expand...
Click to collapse
Just a little confused...did you use the original CWM Touch from Koush's or is this (yours?) a brand new development? Nonetheless I'll try it out and see which is better for me
Thanks for posting (and developing?)

miguel.b said:
have backups/restores been tested to work pretty solidly? I only read that the interface navigation had been tested.
Click to expand...
Click to collapse
they have the 2 times i tried. worked perfectly normal.

Joy2DaWurld said:
Just a little confused...did you use the original CWM Touch from Koush's or is this (yours?) a brand new development? Nonetheless I'll try it out and see which is better for me
Thanks for posting (and developing?)
Click to expand...
Click to collapse
so i used the source gweedo767 made but he made it for the galaxy nexus so i ported it to work with the skyrocket/hercules. it was alot of work.
anyone who does not want to install please try out the fakeflash zip file in the OP. there is absolutely no chance of anything happening to your phone by flashing this as it is just a test flash. it will let you experience how the real install is but will not change ANY files on your phone.

miguel.b said:
have backups/restores been tested to work pretty solidly? I only read that the interface navigation had been tested.
Click to expand...
Click to collapse
This recovery does indeed charge the phone's battery. Updates to the % are driven by updates to the screen it seems - scroll a bit to refresh the battery charge reading.

Nice... looks nice...

Works well, great job. Again the battery percentage is a great touch!

Two thumbs up for making it opensource.

i fixed adb and usb mounting in the fakeflash .zip but not in the tar.md5 yet....soon though

miguel.b said:
Safeguards in place, I installed via Odin as described, no issues. Was able to perform a backup and restore operation successfully and cleanly. What's more this recovery seems to support battery charging on my Telus T989. There's a battery % counter in the top right quadrant. I sat and watched it advance from %50 to %51. Truly a gem considering the amount of time we spend in there. Of course if I'm mistaken (it is after all 4am here) and this is just a readout of the current charge and not an indicator as to the ability to charge in recovery, please sound off. Scrolling feels accurate and sure.
One recommendation would be to perhaps better isolate the onscreen nav buttons (fantastic considering softkeys aren't illuminated in regular recovery) from the processing readouts or any text for that matter for clarity. Currently the nav buttons lie directly over top the CWM Touch Recovery version text at the bottom left of the screen. Almost superimposed. Onscreen logging also scrolls through the nav buttons, making it just mildly hard to read. Aesthetics for the most part really.
Excellent Go. This is my new recovery.
This recovery does indeed charge the phone's battery. Updates to the % are driven by updates to the screen it seems - scroll a bit to refresh the battery charge reading.
Click to expand...
Click to collapse
yah im actually working on getting the output to not go behind the soft keys. all versions of this CWM have that bug which is kinda annoying. i think gweedo767 is working on it as well.

Can i have a flashable zip of this? I dont want to go on the pc.
sent from the Dark §¡3€

Would it be possible to have a .img file that I could flash through terminal? Please and thank you
Sent from next year on my CM 10ed G-Mobile Galaxy Note 2

novanosis85 said:
Can i have a flashable zip of this? I dont want to go on the pc.
sent from the Dark §¡3€
Click to expand...
Click to collapse
markusf21 said:
Would it be possible to have a .img file that I could flash through terminal? Please and thank you
Sent from next year on my CM 10ed G-Mobile Galaxy Note 2
Click to expand...
Click to collapse
so i posted the recovery.img in the OP so all you gotta do is download it to sdcard and then run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22 bs=4096
hope that makes things easier

novanosis85 said:
Can i have a flashable zip of this? I dont want to go on the pc.
sent from the Dark §¡3€
Click to expand...
Click to collapse
i tried making a flashable zip that would install it but i didnt do it right apparently. this is what i put in the updater-script:
Code:
assert(package_extract_file("recovery.img", "/tmp/recovery.img"), write_raw_image("/tmp/recovery.img", "/dev/block/mmcblk0p22"), delete("/tmp/recovery.img"));
does anyone know how to properly write the updater-script to flash this?

sk8erwitskil said:
so i posted the recovery.img in the OP so all you gotta do is download it to sdcard and then run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22 bs=4096
hope that makes things easier
Click to expand...
Click to collapse
Wow that was a much faster response than expected. I will flash this after work tomorrow. Thank you
Sent from next year on my CM 10ed G-Mobile Galaxy Note 2

Great work, AUGUST BURNS ROCKS !!!!!!!!!!!!!

zoth said:
Great work, AUGUST BURNS ROCKS !!!!!!!!!!!!!
Click to expand...
Click to collapse
+1 ABR is awesome

OnePlus One DroidKit | by iTechy OPEN SOURCE! | No longer being maintained

Droidkit OnePlus One Windows
Hey guys iTechy21 here and I am glad to announce I have a NEW project I'm working on to make an open source toolkit made from c# to allow easy development for other devices. This project will aim to support as many devices as possible with different toolkits for different devices therefore unifying the experience between them.
This will also be 100% open source when fully complete and is released under the GPLV3 licence (apart from the stuff I did not develop e.g. Custom Recoveries, root.zip, adb / fastboot and stock software all rights go to their respective owners).
Features
Support for any android version and Rom
Full Backup and Restore of apps + data (Nandroid is in the works...)
Unlock / Lock your bootloader (removed locking due to possible issues)
Flash a custom recovery (all supported including stock)
Shows attached device(s) in status bar
Advanced CMD mode for power users - type any ADB Command you want!(Will be reimplemented!)
Booting the device into and out of fastboot with a button click
Flash back to stock (Lollipop!) and keeps your bootloader unlocked
To come
Flash 100% stock DONE!
Save backups with custom names DONE!
Install APK's through ADB DONE!
Flash zip via recovery commands DONE!
Improve UI to make it look cleaner...
Backup the EFS Partition (will be coming Soon) DONE!
Log screen to help amateurs with adb learn (and also output errors to be more verbose) Abandoned due to too many issues
Ability to change colour theme from light to dark and the colours (coming Soon™)
Improve OTA system (continuous)
I am accepting requests if they are not too obscure to find out (even better if you find a way to do it as it cuts down on my research time which I don't have a lot of )
Legal
This is an unofficial toolkit made by an independent developer who has no association with oneplus apart from the fact that he owns a 64gb Sandstone black phone. I cannot be held responsible for anything that may happen to your phone! Even if it is just exploding, catching fire or just voiding the warranty.
Changelog
Material 0.0.1.5 ) - Major Milestone! - Untested Oxygen OS flashing. Do-so at your own risk! (Might not work not fully tested)
Improved theming
Updates to internal .dll's
Stability improvements
UI Tweaks
More verbosity via dialogue messages
System requirements​To run this needs an x86 or x64 based system (Not supported on Windows RT)
And version 4.5 of the .NET framework (which is installed upon install if missing (needs testing!) and requires Windows 7 or Higher (sorry XP users )
Downloads​No Download as no longer maintained and buggy​QR for nerds
[QRCODE]http://repo.itechy21.com/toolkit.html[/QRCODE]
Known issues​You tell me...
XDA:DevDB Information
DroidKit | OnePlus One Windows *STABLE*, Tool/Utility for the OnePlus One
Contributors
itechy, All the helpful folks over at Stack Overflow
Source Code: https://github.com/Droidkit/OnePlus-One/tree/master
Version Information
Status: No Longer Updated
Current Stable Version: V0.0.1.5
Stable Release Date: 2015-09-17
Created 2015-03-16
Last Updated 2015-12-06​

FAQ
Q: How do I do X?
A: You click the button corresponding to the action
Q: How do I flash to stock and then unlock the bootloader?
A:
You put your device into fastboot mode.
Once done select your device model (16Gb or 64Gb) and then click flash to stock.
The Bootloader should stay unlocked after the flashing process...
Q: What Roms do this ToolKit support?
A: Any android based ROM with the ADB Debugging interface!
Q: Help it's not working!
A: Try 3 things.
Re-installing the toolkit to re-install the drivers
Enable ADB in the developer settings (tap on build number (in about phone) x times until you get a toast notification)
Update the ToolKit

I found a Bug!
Great and thanks for finding one! I can now hopefully track it down and fix it if you provide the following:
The Computer's OS
What you were doing
How you can reproduce this
Your device
The code from the message that appeared
This will help me track down and hopefully fix the error. And once open sourced these can be reported via GitHub!
Please be aware that messages that just say "HELP" or "IT CRASHED" will be ignored as they don't help...

GOOD JOB .....Bro

kishorparmar said:
GOOD JOB .....Bro
Click to expand...
Click to collapse
Thanks
I hope it isn't too buggy and it works for you

Anyone already try this tool? I want download, but size so damn high

zipperX said:
Anyone already try this tool? I want download, but size so damn high
Click to expand...
Click to collapse
I knew that would be an issue. That's due to the fact it includes all the stock files for CM11S. However I will make it possible by downloading it within the app unzipping it and then flashing the device. But I'm fairly novice at c# and I don't have a lot of time to develop at this moment in time...

Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up

timmaaa said:
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Click to expand...
Click to collapse
Thank you I'll finally get noticed for something XD

... It works great but the size is a big deal.
Also, i suggest that ... you show what version of recovery you will flash - TWRP ( is generic and the filename does not gives you clue, the same for the others )
Also, for the Stock firmware ( wich version is it ?! )
SuperSU is not updated ... you could improve and use the last stable from chainfire
all the other things looks great so far.

itechy said:
Hey guys iTechy21 here and I am glad to announce I have a toolkit I have made. This is my first toolkit and is currently still being developed (adding / tweaking features) to allow you to easily do basic adb stuff and more advanced things are coming when I have time to develop this :silly:
This will also be 100% open source when fully complete but is released under the GPLV3 licence (apart from the stuff I did not develop e.g. Custom Recoveries, root.zip, adb / fastboot and stock software all rights go to their respective owners).
Click to expand...
Click to collapse
Can we have more mirrors (faster ones)? Like MEGA? Google Drive is kind of slow :cyclops: Great work!:good:

ygor.almeida said:
... It works great but the size is a big deal.
Also, i suggest that ... you show what version of recovery you will flash - TWRP ( is generic and the filename does not gives you clue, the same for the others )
Also, for the Stock firmware ( wich version is it ?! )
SuperSU is not updated ... you could improve and use the last stable from chainfire
all the other things looks great so far.
Click to expand...
Click to collapse
Thanks for the feedback. I may improve that make to another form with information on the specific versions (along with a built in download tool). Along with updating the SuperSU.zip
The first thing I'll do is work on that once all the basic features are there. But generally its the latest version of TWRP that is stable along with the other recoveries...
As for the stock I think the one I included was 44s but it may be 5Q (ew). Ill be implementing a downloader for the stock images to download whatever the latest version is from cyanogen...
sabrefresco said:
Can we have more mirrors (faster ones)? Like MEGA? Google Drive is kind of slow :cyclops: Great work!:good:
Click to expand...
Click to collapse
I'll see what I can do but the size will be reduced in the next update as it will remove the stock zip and replace it with a downloader which will download the stock images and then flash them reducing the size massively... (but I use Gdrive as its easy to find the download link unlike with Dev-host...)

I can´t flash twrp with this toolikt any one have a clue?

Do you have the adb drivers installed? Or is it throwing an error?

Updated to fix issues, add ota support, install APK's and improve performance
Sent from my A0001 using Tapatalk

Is "fully complete" v1.0.0? I'd love to stretch my C# muscles a bit.
EDIT: I can't read. Sorry.

dont worry about it
we always have moments... Its almost ready but I don't have a lot of time to develop so it may take me a while to get everything in there....
Just improving the ota updater now as its throwing exceptions...

Download link is not working. Please re-up. Thanks

godzulu said:
Download link is not working. Please re-up. Thanks
Click to expand...
Click to collapse
+1

If anyone has this file, send it to me and I can host it on one of the servers I rent. If we use a Dropbox link, it's going to get so much traffic that the persons account will get suspended.

[KERNEL] Skin1980's Huawei Watch Kernel

Hi guys, here is my kernel for the Huawei Watch.
Features:
- SELinux permissive;
- Autoroot script;
- init.d support;
- busybox;
- unlocked all cores for better performance;
- added the mpdecision binary for the CPU hotplug (disabled by default)( thanks to @invisiblek that used it in his G Watch boot image);
- raised max cpu freq to 984Mhz for a good compromise between performance and battery life;
- added Smartmax governor and set it as default;
- various ramdisk changes;
- added intelli_plug from faux123 and set it in eco mode (enabled by default);
- added kppd from @savoca to control screen parameter ( RGB channel and other things ),
see HERE for more details
- added 3 script to simplify the use of kppd:
1- kppd-configure: to configure and try your settings;
2- kppd-on: make an init.d script to load you kppd settings at boot;
3- kppd-off: turn of auto boot of the script above.
Version 2.5 changelog:
- added powersuspend and somw hooks in the panel driver, this fix the intelli_plug screen off profile.
- added interactive governor and set as default;
- added an interface to control the voltage of the vibrator, you can play with it:
This will show the current value (stock):
Code:
cat /sys/module/drv2605/parameters/current_voltage
To change it you have to:
Code:
echo "your value" > /sys/module/drv2605/parameters/current_voltage
To use this kernel you have to unlock your bootloader. This mean that the device will be factory resetted.
To try the kernel ( will be resetted to stock after a reboot ):
Code:
adb reboot bootloader
fastboot boot sturgeon-skin1980-2.0.img
To flash the kernel:
Code:
adb reboot bootloader
fastboot flash boot sturgeon-skin1980-2.0.img
fastboot reboot
tnx to @invisiblek ( i took some ideas from his G Watch kernel ) @Chainfire and @savoca
Source: https://github.com/Skin1980/sturgeon
EDIT: removed for now.

I seem to be getting a much better battery life now. Thanks!

So let's say I want to modify my screen using KPPD, say, add more saturation. Would I just need to extract postproc.cond through adb, modify it, then adb push it back and reboot? Since the device obviously doesnt have a keyboard or support for most apps.

Sorry for the inane basic question, but how do you physically access the watch to do this? Through the charging pad connected by USB to the computer?

billku said:
Sorry for the inane basic question, but how do you physically access the watch to do this? Through the charging pad connected by USB to the computer?
Click to expand...
Click to collapse
Yup!

Any concern that we'll lose the ability for an OTA update?
Sent from my Nexus 6 using Tapatalk

Thank you the kernel, watch feels much snappier. Do you have or know where to get the stock kernel to reflash for updates?

Right here. It was right under your nose.
http://forum.xda-developers.com/showthread.php?t=3219596
Sent from my Nexus 7 using Tapatalk

bmg1001 said:
So let's say I want to modify my screen using KPPD, say, add more saturation. Would I just need to extract postproc.cond through adb, modify it, then adb push it back and reboot? Since the device obviously doesnt have a keyboard or support for most apps.
Click to expand...
Click to collapse
In a shell use
Code:
kppd-configure
Then if you want autostart on boot
Code:
kppd-on

Anybody try or have any luck dealing with the red tint issue by tweaking the colors?

tiny4579 said:
Right here. It was right under your nose.
http://forum.xda-developers.com/showthread.php?t=3219596
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Perfect, thank you!

renfrja said:
Anybody try or have any luck dealing with the red tint issue by tweaking the colors?
Click to expand...
Click to collapse
it can't be fixed, neither with red=0. That sh*t is always there.

Skin1980 said:
it can't be fixed, neither with red=0. That sh*t is always there.
Click to expand...
Click to collapse
Assumed that'd be the case but figured it was worth asking.
It's driving me irrationally crazy so not sure whether I'm keeping it.
Regardless, thanks for the work.

Does the watch have a flag bit set when you unlock that can't be reset? You know like phones do for warranty reasons... (Maybe OTA updates too?)
Otherwise great to see development going! Love the watch but some improvements can't hurt Probably gonna grab the system image and poke around a bit.

I had to mount system rw to be able to run the kppd scripts:
This worked:
mount -o rw,remount -t ext4 /system

tiny4579 said:
Right here. It was right under your nose.
http://forum.xda-developers.com/showthread.php?t=3219596
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Tiny, you have the HWatch? I remember you from back in the Incredible days...

Hey skin...looked at your init shell script. I don't think the vibrator stuff works. There are no amp or driving_ms files in the vibrator directory. I saw that elsewhere, too...guessing its for the LG watches.
Also, found where brightness is set:
/sys/class/leds/lcd-backlight/brightness
Looks like it takes a number from 0 to 255
(and yes, it is still lcd-backlight even though we have an amoled screen)

brizey said:
Hey skin...looked at your init shell script. I don't think the vibrator stuff works. There are no amp or driving_ms files in the vibrator directory. I saw that elsewhere, too...guessing its for the LG watches.
Also, found where brightness is set:
/sys/class/leds/lcd-backlight/brightness
Looks like it takes a number from 0 to 255
(and yes, it is still lcd-backlight even though we have an amoled screen)
Click to expand...
Click to collapse
Ot: can you pull the recovery log in twrp? In general thread

dmeadows013 said:
Tiny, you have the HWatch? I remember you from back in the Incredible days...
Click to expand...
Click to collapse
Yes I do.
Was working on building recovery but I hit a snag with fb0 errors.
Also I had a test kernel that wouldn't boot. I didn't get too far on either but didn't work too much on the kernel. I need to give it another shot but I'm pretty happy with the battery life as is.

Is there any way to tell that the kernel has been flashed successfully? I flashed it earlier but dont seem to have better performance or battery life at this stage. Cant seem to check kernel info in "about device"

Llightbar as notification LED

Patches are based on the code that is used in the firmware. The patch is only for this device. The patch is not a program, it changes part of the firmware.
Llightbar path:
- turned off lightbar. in my opinion uselessly glowing after turning on the screen of the tablet.
- lightbar was used as an indicator of incoming messages. It does not work correctly, because it just glows instead of blinking. To fully work see add-on.
Compatible with android 8.x firmware. Tried on the official firmware.
Installation via TWRP.
To fully work in the mode of indication of incoming messages, you need to execute the following commands on the terminal command line.
Code:
chown system system /sys/class/chromeos/cros_ec/lightbar/program
chmod 0660 /sys/class/chromeos/cros_ec/lightbar/program
Later I'll add this to the patch.
Install two archives. One adds the modified files to the systems partition. The second patchy kernel adds the necessary lines.
Sourse https://github.com/vartom/android_device_google_dragon

Vartom said:
Patches are based on the code that is used in the firmware. The patch is only for this device. The patch is not a program, it changes part of the firmware.
Llightbar path:
- turned off lightbar. in my opinion uselessly glowing after turning on the screen of the tablet.
- lightbar was used as an indicator of incoming messages. It does not work correctly, because it just glows instead of blinking. To fully work see add-on.
Compatible with android 8.x firmware. Tried on the official firmware.
Installation via TWRP.
download
Add-on.
To fully work in the mode of indication of incoming messages, you need to execute the following commands on the terminal command line.
Code:
chown system system /sys/class/chromeos/cros_ec/lightbar/program
chmod 0660 /sys/class/chromeos/cros_ec/lightbar/program
Later I'll add this to the patch.
Sourse https://github.com/vartom/android_device_google_dragon
Click to expand...
Click to collapse
Thank you for this patch.
I have 2 questions before install you patch:
- how to remove it? Any backup of original files?
- Need to be re-flashed every time after flashing a new vendor.img ?

tebra said:
Thank you for this patch.
I have 2 questions before install you patch:
- how to remove it? Any backup of original files?
- Need to be re-flashed every time after flashing a new vendor.img ?
Click to expand...
Click to collapse
1 - The patch replaces 4 files (power.dragon.so, lights.dragon.so 32 and 64 bit version) in the system partition. In zip you can be sure of this.
2 - To return to the original, you can flush the original system.img of the current OS system partition. In the case of custom ROM, install the firmware again. Vendor partition does not change.

Vartom said:
1 - The patch replaces 4 files (power.dragon.so, lights.dragon.so 32 and 64 bit version) in the system partition. In zip you can be sure of this.
2 - To return to the original, you can flush the original system.img of the current OS system partition. In the case of custom ROM, install the firmware again. Vendor partition does not change.
Click to expand...
Click to collapse
Will it works with any notification? Email, Hangout, message... ?

tebra said:
Will it works with any notification? Email, Hangout, message... ?
Click to expand...
Click to collapse
Yes, with any notification.

Does not work for me on Februar Security Patch....
edit: It works. I think the first command should be:
Code:
chown system:system /sys/class/chromeos/cros_ec/lightbar/program

It works on LineageOS 15.1
Thanks

Hi,
I have a bug:
on my device chown and chmod on /sys/class/chromeos/cros_ec/lightbar/program came back to default after a reboot

tebra said:
Hi,
I have a bug:
on my device chown and chmod on /sys/class/chromeos/cros_ec/lightbar/program came back to default after a reboot
Click to expand...
Click to collapse
Without changing the ramdisk it will be.

Vartom said:
Without changing the ramdisk it will be.
Click to expand...
Click to collapse
Is it link to lineageOS or Magisk ?

tebra said:
Is it link to lineageOS or Magisk ?
Click to expand...
Click to collapse
Ramdisk is part of the boot.img

Added a second file for changes in the ramdisk.

I know it's been a while since this was last time updated.
But - is there a chance that you could make it compatible to the LOS 17 ROM? It seems that Android 10 (which runs fine on Pixel C) uses a 4x-Kernel. And your Patch is not longer working. And the standard Google-LED-Bar is as stupid as it was before your little hack .
[edit: Even if the constant glow would just be disabled, that would be really nice.]

+1
Dagazz said:
I know it's been a while since this was last time updated.
But - is there a chance that you could make it compatible to the LOS 17 ROM? It seems that Android 10 (which runs fine on Pixel C) uses a 4x-Kernel. And your Patch is not longer working. And the standard Google-LED-Bar is as stupid as it was before your little hack .
[edit: Even if the constant glow would just be disabled, that would be really nice.]
Click to expand...
Click to collapse
+1 on this request!

In Android 10, the files responsible for controlling the backlight/lightbar were moved. Because of this, you need a new version of the patches. A patch to turn off the lightbar is not difficult to do. It will be more difficult to make the notification indicator due to a complete change in the backlight/lightbar control code.
I will make a patch to turn off the lightbar when I have time for this.

Vartom said:
I will make a patch to turn off the lightbar when I have time for this.
Click to expand...
Click to collapse
Thanks for the explanation. As written before: Just to turn off that stupid LED-Bar would really be a big enhancement (at least for me). Notification ist "nice to have" - but not the reason why I installed your patch in the first place. The main reason was just an simple that useless glow.
And thanks in advance for updating it, when you find the time.

Dagazz said:
Thanks for the explanation. As written before: Just to turn off that stupid LED-Bar would really be a big enhancement (at least for me). Notification ist "nice to have" - but not the reason why I installed your patch in the first place. The main reason was just an simple that useless glow.
And thanks in advance for updating it, when you find the time.
Click to expand...
Click to collapse
I agree with all you're saying.
At least for now, if we could at least have a patch to disable the glowing bar, it'll be fine.
Do not stress too much for the notifications fix.
Disabling it would be awesome for battery health

[CLOSED][Overlay] Dil3mm4's Overlays for Prague Series devices (all variants)

This overlay APK it's "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .
What it does exactly?
Nothing more than adding AOSP overlay matching our device capabilities and also, inherits Prague power profile.
Do I need it?
Well, better having than don't.
This will conisderably enhance your experience on every GSI ROM giving better functionality overall.
Why you did that?
Because I'm sick of inheriting stuff that belongs to /vendor, in system.
Project Treble it's all about separating vendor implementation from system.
So why we should keep adding OEM stuff in there, if it doesn't belong no more in /system?
I have XYZ device with ZYX firmware can I use it?
As long as you're on a PRA-*** device (with a non-EMUI firmware), you're good to go.
Otherwise DO NOT USE IT FOR THE LOVE OF MANKIND.
I don't have PRA, but I want it on my Huawei device !
Well, that's fine, join the Telegram group @GSI_HI6250, so that you could help me with stock files grabbing to make an overlay for your device.
Overlay configs (aka "what does dis do, ser tell pl0x"):
Allows all rotations;
Configs autobrightness levels;
Configs autobrightness Lcd values;
Configs BLE;
Sets Doze Component;
Sets Doze After screen off;
Configs autopowermodes (doze related);
Configs power management on:
screen off due to proximity sensor interaction;
decouple on suspend state;​
Configs brightness doze value;
Configs Intrusive led;
Configs dual band wifi support (where available);
Configs hotswap (where available);
Configs Color Transform on HWC;
Configs VoLTE available (even tho it needs support on GSI side);
Configs WFC over IMS;
Configs wifi background scanning support.
Installation Instructions
Download the overlay from the Downloads session.
With root, push the overlay to /vendor/overlay. Create the folder if it doesn't exist.
Run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/dil3mm4-overlay-PRA.apk
XDA:DevDB Information
[Overlay] Dil3mm4's Overlays for Prague Series devices (all variants), Device Specific App for the Huawei P8lite/P8 Lite
Contributors
Dil3mm4
Version Information
Status: Stable
Created 2018-06-26
Last Updated 2018-06-26

Definitely will be useful. Thanks a lot, Dil3mm4!

Hi Dil3mm4,
Thanks for your work, but I'm not sure what this app does exactly, will it help me for example with substratum themes? Thanks

Hi @Dil3mm4 let me understand correctly:
- i'm under LineageOS 14.1 (Haky86 version). Am i concerned with your fixes ?
- i plan to go to LOS 15.1. Should i flash LOS 15.1 before, then install your fixes ?
- if i can go to LOS15.1 from Prject Treble, what device should i choose ? A or A/B ? I assume this is ARM64.
Thank you VM back in the ROM selection after 1 year, and i have things to understand

Graveen said:
Hi @Dil3mm4 let me understand correctly:
- i'm under LineageOS 14.1 (Haky86 version). Am i concerned with your fixes ?
- i plan to go to LOS 15.1. Should i flash LOS 15.1 before, then install your fixes ?
- if i can go to LOS15.1 from Prject Treble, what device should i choose ? A or A/B ? I assume this is ARM64.
Thank you VM back in the ROM selection after 1 year, and i have things to understand
Click to expand...
Click to collapse
Our device is arm64 A only (PRA-LX1 is my device)
If the APK is included in the rom u want to flash just run the command below, if not, after flashing just install the overlay according to the instructions. Have a nice day!

I will probably make a question that doesn't make sense since it's probably hardware related. But will this overlay add 5ghz support to our devices?

mannas said:
I will probably make a question that doesn't make sense since it's probably hardware related. But will this overlay add 5ghz support to our devices?
Click to expand...
Click to collapse
Nope

UPDATE
-P compatibility
-Improved brightness levels
DOWNLOAD

Hey Dilemma! I have an issue with all the Treble Roms. After listening to music for a while, the playback stops and I have to restart it, or when I plug a headphone in and then out, sound usually doesnt come out of the speaker. Will this overlay fix the issues I have with treble Roms? Thanks in advance

Please help with a little overlay
Dil3mm4 said:
This overlay APK it's "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .
I don't have PRA, but I want it on my Huawei device !
Well, that's fine, join the Telegram group @GSI_HI6250, so that you could help me with stock files grabbing to make an overlay for your device.
Click to expand...
Click to collapse
Hello Dil3mm4.
Sorry to send you PM, i see after sending that's not ok. I really want to solve Overlay issue for my Huawei Fig-LX1.
I try to join Telegram group indicated by you but could not find it. Maybe is not existing anymore. So - my last chance is you to respond here.
I just want you to make an overlay for my phone to work better with Phusson Treble 8.1. Just tell me what files do you need and i will do it.
Maybe you answer me.
Thanks!

Hi, by fixing BLE, you mean bluetooth low energy, like huawei band, fossil Q ?
thanks

Thanks! U did great!

Hi
I've tried to install this file but after I've enter the code, it says system is readable only.
I've tried with adb shell and terminal(booth of them rooted) and it didn't work
I've even tried to mount system as rewritable but it didn't work.
I'm on Aex 6.6 latest version(and I was on PRA-LA1 8.0.0.370 C185 before i flashed this custom rom)
What should I do to fix this error?

Traceur017 said:
Hi
I've tried to install this file but after I've enter the code, it says system is readable only.
I've tried with adb shell and terminal(booth of them rooted) and it didn't work
I've even tried to mount system as rewritable but it didn't work.
I'm on Aex 6.6 latest version(and I was on PRA-LA1 8.0.0.370 C185 before i flashed this custom rom)
What should I do to fix this error?
Click to expand...
Click to collapse
install terminal emulator , put the .APK (be sure to rename the last build taking the -P ) in the mencioned directory but first run the following command:
su
mount -o remount,rw /vendor
after this you can run the command for the apk.
It worked for me. or at least.. didnt gave an error... so.. lolol

I think I've installed it correctly but How can I see changes? Nothing added!

Hello, I have a PAR-AL00 device. Can you make an overlay for me.and Telegram group @GSI_HI6250, I can't find it.Thank you verymuch.

I don't understand, where is the overlay link?
Edit : Sorry, I didn't know it was in the download tab.

I can't find it where is it?
artus777 said:
I don't understand, where is the overlay link?
Edit : Sorry, I didn't know it was in the download tab.
Click to expand...
Click to collapse

Is this overlay necessary under Lineage 18.1 (PRAGUE device and EMUI 8.0.0.390)?

@Dil3mm4 Thread closed! Please advise the moderators team (best via the report function) to re-open the thread when ready to provide a download link for this former DevDB thread.
Regards
Oswald Boelcke
Senior Moderator