Database Info

[ROM(ABANDONED)] [4.4.4] [UNOFFICIAL] CyanogenMod 11 for ChaCha [07.22.2014]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
We've done it! Thanks to the androidarmv6 team's work, and the great people over at Team Simplicit(Especially Olivier, as he got it working on the Wildfire S and a couple other devices),
we now have a functional KitKat rom for the ChaCha!
This rom SHOULD now be daily driver ready. Please leave feedback on any issues.
I will also note that it takes a rather long time to boot. I don't know if it will stay this way or not, so don't ask.
And lastly, I recommend leaving the device for at least a minute after first boot, before going through the setup wizard. Otherwise it will be very laggy.​
NOT WORKING/BROKEN/ISSUES
Bluetooth
Screen video recording (I believe we have a fix in the works)
ART (doesn't support ARMv6)
SELinux
USB/WiFi tethering
Camera orientation is sideways
Phone takes a long time wake during call or alarm
Symbols/zero key bringing up the input method selection window, regardless of whether alt is pushed.
Arabic keyboard not working?
incoming call crashes ui. dialer crashes when you try to open it after ui crash.
Trebuchet launcher crashes repeatedly, making phone unusable
MTP and PTP Modes cannot be selected under USB Connection menu, Settings Crashes. Setting does not save.
Trebuchet unable to remove widgets due to missing "X"
CHANGELOG
Code:
[B][U]07/22/2014[/U][/B]
[LIST]Updated recovery to 6.0.5.3[/LIST]
[LIST]Fix for flashing older zips[/LIST]
[LIST]Fix for partitioning SD card from Advanced menu[/LIST]
[B][U]07/22/2014[/U][/B]
[LIST]Trebuchet now able to remove widgets(Temporary workaround)[/LIST]
[LIST]Version bump to 4.4.4_r2[/LIST]
[LIST]Kernel updated to 2.6.36.1 (as well as various tweaks)[/LIST]
[LIST]Changed default governor to SmartAssH3, as it seems to be stable now on the ChaCha[/LIST]
[LIST]Arabic keyboard SHOULD be fixed, please give feedback[/LIST]
[LIST]Symbols/Zero key should now bring up the Symbols menu, and allow FN+0 to type "0" (thanks [URL="http://forum.xda-developers.com/member.php?u=3517907"]WinSuk[/URL]![/LIST]
[LIST]"F"(Facebook) key has been re-enabled and now launches the Browser[/LIST]
[LIST]Re-fixed camera orientation[/LIST]
[LIST]Recovery updated to 6.0.5.2, Softkeys now work, Swipe should work, Lights removed(no need for it)[/LIST]
[B][U]06/13/2014[/U][/B]
[LIST]Dialer and Contacts List no longer crash on incoming/outgoing calls[/LIST]
[LIST]Trebuchet no longer crashes repeatedly[/LIST]
[LIST]Changed default CPU Governor to minmax[/LIST]
[B][U]06/08/2014[/U][/B]
[LIST]Fixed Camera Orientation/Rotation (thanks [URL="http://forum.xda-developers.com/member.php?u=5095490"]Kevinjoa[/URL]!)[/LIST]
[B][U]06/07/2014[/U][/B]
[LIST]CM/androidarmv6/Google/AOSP upstream (incl. Android 4.4.3)[/LIST]
[LIST]Disabled fading edges on text for a small speedup - [URL="http://winsuk.net/screens/liberty/fadingbefore.png"]before[/URL], [URL="http://winsuk.net/screens/liberty/fadingafter.png"]after[/URL][/LIST]
[LIST]Switched to gps.conf with SUPL (assisted GPS) support[/LIST]
[LIST]Changed default CPU Governor to ONDEMAND[/LIST]
[LIST]Changed default min. CPU frequency to 245 Mhz[/LIST]
[B][U]06/04/2014[/U][/B]
[LIST]Included additional Keyboard Layouts (the Symbols/zero key currently isn't behaving properly. fix for this soon I hope)[/LIST]
[LIST]Wifi Fix.[/LIST]
[LIST]New Simplicit-ULTiMATE kernel[/LIST]
[LIST]Included Bare Minimum GApps[/LIST]
[LIST]Disabled First Boot Setup Wizard[/LIST]
[B][U]05/30/2014[/U][/B]
[LIST]First Build.[/LIST]
CREDITS
TeamSimplicit (Olivier, izi501, feroxx, Kevinjoa, thehacka1, WinSuk, Mazer.One)
benjamingwynn, niks255
androidarmv6
JDevs and the OWL Team
luzifer1984, adlx.xda
CyanogenMod
DOWNLOAD
ROM | Mirror
GApps to Cache | Mirror - Thanks to WinSuk for this (original thread)
SCREENSHOTS
RECOVERY
Recovery gets built with rom, I will update this anytime the recovery is changed.
Current Version is 6.0.5.3
Download Here | Mirror
How to flash recovery:
Terminal Method:
Stick the "recovery.img" file on the root of your sdcard. Open a terminal emulator, and type:
Code:
su
flash_image recovery /sdcard/recovery.img
After typing "su" you'll want to allow terminal emulator root access.
Fastboot method:
Stick the "recovery.img" file in the same directory as your fastboot executable binary.
Put your phone in fastboot mode.
Open a command prompt and use the fastboot tool to type:
Code:
fastboot flash recovery recovery.img
PH06IMG.zip method:
Put your phone in fastboot mode, and use the fastboot tool to type:
Code:
fastboot getvar all
You'll want to make note of the "version-main" value, the "cidnum" value, the "modelid" value, and the "hbootpreupdate" value.
Stick the "recovery.img" file in a folder somewhere, and create a new text document called "android-info.txt"
Put the values you noted earlier into the "android-info.txt" in the following format(this one works for my device):
Code:
modelid: PH0613000
cidnum: TELUS001
mainver: 1.60.0.0
hbootpreupdate: 12
note that "mainver" is the value you noted earlier from "version-main".
Now zip the "recovery.img" and the "android-info.txt" together, and name it "PH06IMG.zip"
Put that file on the root of your sdcard, and reboot into the bootloader. It should detect the zip, and ask you to update. choose yes, and you're off to the races!
SOURCES
androidarmv6/android
androidarmv6/android_device_htc_chacha
androidarmv6/android_device_htc_msm7x27-common
androidarmv6/android_kernel_htc_msm7x27
androidarmv6/proprietary_vendor_htc

Removed

Finally CM 11 in HTC chacha, i will Test it as soon as i can
i Made this Key Character Map File for "Arabic", Please add it to your Build
chacha-keypad-ara.kcm.zip
Thanks kronflux, Olivier, and all the Simplicit Team for this Great Effort :good:

Will add that, thanks.
Gesendet von meinem Xperia S mit Tapatalk

I am Really Enjoying Kitkate right now
———
Installing Steps:
1) I Tried to install the Recovery using the boot loader method but it failed with an error "CID incorrect, update fail”.
So i used fast boot Method with my PC & this command "fastboot flash recovery recovery.img”
2) Installed The Rom
3) Installed “CronMod-INT2EXTV2+_signed.zip” (Great INT2ext mod to increase internal Memory form SD card, now 1.5GB) :angel:
The system Feels good, but i couldn’t live with it without updating the minimum CPU frequency to 245 MHZ
Problems i faced At my first look
System:
Wifi & Hotspot NOT working
Bluetooth NOT working
USB Mass Storage Mode (UMS) NOT working ( I can Not connect my phone to the pc with any mean )
3G Stop working after WAKE - I Must Manually disable and re-enable it
Battery Still Testing
Apps:
Camera image is rotated !
Phone app buttons really needs to be reorganised
Keyboard:
@ and ~ are misplaced , should be switched (FN+y) with (FN+p)
No Number “0”
Lang, & Facebook Keys are not Functional
No Arabic Keyboard
Overall, Very Good for a First Build. I am Excited to Test the Next Build and i am ready for Testing

Yehia2amer said:
[*]USB Mass Storage Mode (UMS) NOT working ( I can Not connect my phone to the pc with any mean )
Click to expand...
Click to collapse
I will say that mass storage mode works perfectly for me. but I will do some testing with other micro sd cards, and see what happens.
But thanks for testing!

((
Good JOB...
Lot's of problems... it's better that we think about a new KERNEL:good: instead of a new ROM...

mortal19xx said:
Good JOB...
Lot's of problems... it's better that we think about a new KERNEL:good: instead of a new ROM...
Click to expand...
Click to collapse
Keep in mind, this is absolutely NOT a stable release. entirely a testing/dev release.
That having been said, if you want to start the efforts of working on a new kernel, I certainly wouldn't complain, and I'd even try my best to help.

[A]
kronflux said:
Keep in mind, this is absolutely NOT a stable release. entirely a testing/dev release.
That having been said, if you want to start the efforts of working on a new kernel, I certainly wouldn't complain, and I'd even try my best to help.
Click to expand...
Click to collapse
Keep going... :good:

Hey guys,
you can flash my kernel if you want. I have fixed wifi.
Gesendet von meinem Xperia S mit Tapatalk

thanks
i m glad to see our chacha reborn with new build and developers, thank you guys for the time you spend on this phone
keep up
i'll test and report

Olivier said:
Hey guys,
you can flash my kernel if you want. I have fixed wifi.
Click to expand...
Click to collapse
When talking about a new kernel: Is it possible to enably 2-way-call-recording there?

Flexmaen said:
When talking about a new kernel: Is it possible to enably 2-way-call-recording there?
Click to expand...
Click to collapse
It's certainly possible. I don't know if I'll do it to my own fork of the currently used kernel, or if maybe Olivier will do it, but I will definitely look into it in the next few days, see what I can come up with. I have found a patch used on a samsung device that uses the msm7227 like our device, so as long as it's similar enough, and still works with kitkat, it shouldn't be too hard.
No promises though

kronflux said:
It's certainly possible. I don't know if I'll do it to my own fork of the currently used kernel, or if maybe Olivier will do it, but I will definitely look into it in the next few days, see what I can come up with
Click to expand...
Click to collapse
Ah ok great.
Anyway, the biggest downside of the custom roms for the Chacha is the bad keyboard integration. If you compare it with a Nokia E71, the original ROM is already bad. But if you use a custom ROM, than you are lacking even more keyboard shortcuts (especially when handling calls). So I guess improving this would be the best thing for this phone.
But let's see... whatever you decide it's great there there is still so much work going on for this phone!

Flexmaen said:
the biggest downside of the custom roms for the Chacha is the bad keyboard integration.
So I guess improving this would be the best thing for this phone.
Click to expand...
Click to collapse
Unfortunately, I can only judge by the English keyboard configurations, because I don't know any other languages xD
But the next build(which, if all goes well, will be later this afternoon/evening) will have the keyboard configs the same as the other recent custom roms, primarily the ones by adlx.xda, as it's his repos we got the configs from.
But after I release this new update, if you tell me what's wrong with the keyboard specifically, I may be able to help out a little.

ohh finally ! , how good of you , i will try it sure and tell you if there is anything wrong .. but is the kernel support swap ? , and the keyboard support arabic language and the buttons ? thanks alot

mohabmoka said:
ohh finally ! , how good of you , i will try it sure and tell you if there is anything wrong .. but is the kernel support swap ? , and the keyboard support arabic language and the buttons ? thanks alot
Click to expand...
Click to collapse
the next release(which is currently compiling. takes a LONG time xD) SHOULD have proper arabic support, and I believe it does support swap, but I don't know for sure.

good xD , and please if you can , attach pics of the rom

Is it mandatory to install recovery v 6 to flash this?

swashie said:
Is it mandatory to install recovery v 6 to flash this?
Click to expand...
Click to collapse
no, however it is recommended, and I can't guarantee that future releases of the rom won't require it.

[ROM][5.0.2] CyanogenMod 12 for Acer A510[UNOFFICIAL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review.
These unofficial builds are based on the CM t30 Kernel available at https://github.com/CyanogenMod/android_kernel_acer_t30
All my specific device tree can be integrated in the CyanogenMod project.
https://github.com/Shr3ps/device_acer_a510
https://github.com/picasso-m-mf-dev/android_device_acer_a510
These builds are based on some Graphic Legacy code, thanks to pawitp for his patches : https://gist.github.com/pawitp/c8a4b32ecd838146192b
Downloads
cm-12-20150409-UNOFFICIAL-a510_lvm (9f521876a716178e8b5711afb53a8d22)
cm-12-20150201-UNOFFICIAL-a510-exp_lvm (c1e94281ae53ff70852e40312d7e07f0)
http://acer.shreps.fr
Requirement
An unlocked Bootloader - JB Version
CWM recovery or TWRP recovery
version 6.0.5.0+ with LVM Support (Look at the CWM thread) or TWRP with LVM Support (called bigsystem by Elibl)
Installation
Do a Nandroid Backup!
Wipe data/factory reset if coming from another ROM or version of CM. If you are already on CM11 or CM12, just make Wipe Cache & Wipe Dalvick-Cache for a proper upgrade.
Install the ROM using Recovery
Install the adapated Google Apps (I recommend minimal Gapps 5 on my website gapps-lp-20141109-signed.zip but you can use Latest Paranoid Gapps for 5.0.x
Note: The partition layout of CM12 is identical to that of CM11 with LVM and thus you may use CWM with LVM to backup/restore.
Bugs & FAQ
Known Issues:
RIL not compatible with A511
Flashing L might take a while in recovery (please be patient)
First boot might take a while too !
Frequent random crashes
Bootanimation crashes after a while (but the boot process continues normally)
Setting brightness to minimum while on auto brightness may cause the screen to go completely dark with no way to set it back except for guessing where the brightness setting is or using adb to force set a higher brightness.
If you have a black screen at first boot or after bad settings manipulation, use this commande in adb :
Code:
adb shell "echo 255 > /sys/devices/platform/pwm-backlight/backlight/pwm-backlight/brightness"
If it doesn't work, push power to enable your screen and try the command again.
If the bug comes with auto-brightness enabled, you can put your sensor on a light to force it to level up the brightness.
SELinux not in enforcing mode
Bluetooth may not work properly
​
XDA:DevDB Information
[ROM][5.0.2] CyanogenMod 12 for Acer A510[UNOFFICIAL], ROM for the Acer Iconia A700 and A510
Contributors
Shreps
Source Code: https://github.com/picasso-m-mf-dev/
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.1.x
ROM Firmware Required: JB Unlocked Bootloader
Based On: CyanogenMod
Version Information
Status: Beta
Stable Release Date: 2015-04-09
Beta Release Date: 2015-02-01
Created 2015-02-03
Last Updated 2015-04-10

Here we go with the first public build !
cm-12-20150201-UNOFFICIAL-a510-exp_lvm (c1e94281ae53ff70852e40312d7e07f0)

Bravo shreps
Nice to see pawtip works used.
is there another tegra3 with lollipop , to mutually work ?

BENETNATH said:
Bravo shreps
Nice to see pawtip works used.
is there another tegra3 with lollipop , to mutually work ?
Click to expand...
Click to collapse
I'm not sure, the t30 kernel is very Acer specific on many driver part.
We need a good Kernel dev to manage to make it "clean" and remove all the Acer specific code, that would be great in order to properly upgrade the Kernel next.
Actually, we're stuck on 3.1 Kernel version because of these Acer code.
But I'm not this person, I'm lacking kernel skills (and also free time) to do this.

Unfortunately we had only one kernel dev.
But we lost him, because he has no tab anymore.
CM12 ist running on my A510 since 0:45 (in germany) without any problems, except brightness minimum.
I wiped system, cache, dalvik and internal memory (to delete all data from older installations)
Than I flashed CM12 and Gapps with TWRP.
I didn't tested Bluetooth.
Acer Iconia A510 | CM12 | Android 5.0.2

HornetRider said:
Unfortunately we had only one kernel dev.
But we lost him, because he has no tab anymore.
CM12 ist running on my A510 since 0:45 (in germany) without any problems, except brightness minimum.
I wiped system, cache, dalvik and internal memory (to delete all data from older installations)
Than I flashed CM12 and Gapps with TWRP.
I didn't tested Bluetooth.
Acer Iconia A510 | CM12 | Android 5.0.2
Click to expand...
Click to collapse
Yes, it's bad news for Zyian ?
But thx for your feedback on the build !
Envoyé de mon One+

kernel work is really a pain, i agree.
It requires a lot of time to get something working..

CM12 isn't rooted?
It's no problem, I flashed SuperSU 2.45 to get root.
Acer Iconia A510 | CM12 | Android 5.0.2

I have a bug in gallery app
https://docs.google.com/file/d/0B_Ls_Pd3r1HIR0s0UlhGUlpUbE0/edit?usp=docslist_api
There are grey fields between my pictures.
All real existing pictures are shown, but between them are this grey fields.
Cyanogen Gallery shows all pictures correct.
When I try to use G+ Foto App, Android media server crashes.

HornetRider said:
I have a bug in gallery app
https://docs.google.com/file/d/0B_Ls_Pd3r1HIR0s0UlhGUlpUbE0/edit?usp=docslist_api
There are grey fields between my pictures.
All real existing pictures are shown, but between them are this grey fields.
Cyanogen Gallery shows all pictures correct.
When I try to use G+ Foto App, Android media server crashes.
Click to expand...
Click to collapse
Gallery and Photos G+ app working fine on My tab.
Try to clear cache and remove thumbnail dir on your memory
Envoyé de mon One+

Didn't work for me.
This grey fields are no missing pictures or missing thumbnails.
All real existing pictures have thumbnails.
Acer Iconia A510 | CM12 | Android 5.0.2

Me too, I can't open Photo app. It will be force closed after I ignore first cloud backup prompt.
Sent from my A510 using XDA Free mobile app

Did both of you made a wipe data ? Did you upgrade G+ via play store ?
Envoyé de mon One+

Yes for both.

It's OK for build in gallery but FC happens in Google Photo.
I have wiped both cache and delete cache.
After upgrade process finished, I can't go into desktop. So I wiped data as well.
Finally I read install instructions again and figure out that the problem is caused by backlight setting.
Then I install gaaps again.
Sent from my A510 using XDA Free mobile app

About the Gallery app issue, @HornetRider I think you should try to format your internal memory an push back cleaned photos
About the Photos issue from G+, it could be a gapps issue, you can try to flash another gapps package. On my tab, I upgrade Google+ from the play store, and no problem using the Photos app.

First thanks to Shreps for his great work.
For myself I found a solution of this Brightness-Gate.
I played a little bit in the configuration settings.
and then I turned off a funtion, called "Adaptive Brightness".
Look at my picture.
Since then, I have no more issues with calibrating brightness

Shreps said:
About the Gallery app issue, @HornetRider I think you should try to format your internal memory an push back cleaned photos
About the Photos issue from G+, it could be a gapps issue, you can try to flash another gapps package. On my tab, I upgrade Google+ from the play store, and no problem using the Photos app.
Click to expand...
Click to collapse
I suspect the missing thumbnails caused by the scan media process.
Coz I can't run build in Music app as well but I have a solution.
I tried to eject SD card and rebooted my tablet.
While system is running in second boot, insert the SD card again.
Now I ve got most of the thumbnails but still some missing.
Moreover, I can run Google photo now but it shows many missing media icons.
Music app now is running in perfect status. It show all songs and covers.
No more force closed happen.
I'll try to backup all data in SD card and format it.
Sent from my A510 using XDA Free mobile app

Hi,
First of great work Shreps and thank you for continued support.
i have a problem. Made the install (full wipe cache, dalvik, data) after install and first reboot the black screen (tried several clean installs with and without apps). problem is that i cant make connection with ADB to send command. The computer (windows 8.1) recognizes the tablet connection when connecting usb, but adb can't find the device.
any solution for that?
I use twrp recovery and in the recovery mode adb is finding my phone.
i'm kind a noob here
Fixed: use windows 7 for debugging

Shreps said:
About the Gallery app issue, @HornetRider I think you should try to format your internal memory an push back cleaned photos
About the Photos issue from G+, it could be a gapps issue, you can try to flash another gapps package. On my tab, I upgrade Google+ from the play store, and no problem using the Photos app.
Click to expand...
Click to collapse
I wiped the internal storage together with system, cache and dalvik , before I flashed CM12.
But all my photo folders are on my external SD-Card. Maybe I should wipe the card (after backup all important data)?
wallacefung said:
I'll try to backup all data in SD card and format it.
Click to expand...
Click to collapse
Did this solve your problem?
Than I'll try it also.

[6.0][STABLE] Lazy Man's Debloated ROM for Leagoo M8

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The Leagoo M8 is an entry level 5.7" Smartphone running on the MT6580A SOC with 2GB of RAM. Like many budget devices, the Leagoo M8 has decent hardware for the money, but suffers from a poor software experience and too much bloat. I created this project to share a more lightweight and clean software experience so we can get the most out of our device without too much effort
Important note! I am NOT a developer. Don't expect me to know how to recompile a kernel or anything. I'm just a lazy user who has been using Android for a while and much prefers a clean, AOSP-style look and feel There are a few technical issues which are outside of my reach, so if anyone is able to help, please feel free to reach out.
Disclaimer! I am not responsible for any damages you may do to yourself or your device by modifying your device!
What's Working:
- Everything, except some silly Leagoo features which I removed (eg. Supershot, screen recording).
Known issues:
Same issues as stock Freeme OS. Nothing serious and definitely OK as a daily driver, but the following annoy me the most. If anyone is able to suggest fixes, please comment below!
1. Onscreen Softkeys are misconfigured. I'd like to at least re-map the recents button back to recents, and change the long press of recents to menu. Recents should not be a menu button.... this may require recompiling SystemUI.apk (I think) which is out of my depth
2. The fingerprint sensor is silly. Sometimes it won't recognise my finger, despite me adding the same finger three times, and other times the fingerprint sensor is active when using it, and it will trigger some actions if I touch it by accident (eg. when using Chrome it will open the menu, and other time it will just vibrate the phone - strange).
3. Wi-Fi performance and 3G performance are low compared to other devices. Not sure if this can be fixed by software.
4. There are limited language options. I would like to see English (Australia) for example, but this is not a big deal
5. Considering replacing stock Phone and Contacts apps with Google equivalent from Play Store. Will test first.
6. At 10% battery a prompt will appear which asks whether you want to enable "superPowerSave mode" which is a really badly done version of Samsung's Ultra Power Saver mode, which I removed, so clicking OK does nothing. Would be nice to remove this prompt somehow.
Install Instructions:
Since I am lazy, I have just packaged it as a TWRP backup. Root is not included by default, but you can flash SuperSU in TWRP if you like.
1. Install TWRP 3.0.2 on your device via SPFlashTools (If you haven't done so already, download link provided)
2. Download ROM package, unpack archive, and copy contents to /sdcard of the device internal storage
3. Restore the TWRP backup. This will wipe /system, /data and /boot for you, so there is no need to factory reset.
4. Flash SuperSU package from "Extras" folder for Root access (optional)
5. Wipe internal storage to clear up internal storage (optional)
6. Reboot, wait at least 10 minutes for first boot - it takes a while
Downloads:
LM Debloated ROM Backup & Root Package: https://mega.nz/#!SR8iwByZ!k0w4nKzsQp0l02vuIWVIRsgIQGohC7Fvt5v99EriOiU
TWRP Recovery Install Package (if not already installed): https://mega.nz/#!7NlmVCrR!tR2NCZVFHJVueGCwWQvkHsfQxAiYLI4-SZRSngM0Lcc
Credits:
Leagoo for building FreemeOS for this device
XDA:DevDB Information
LM Debloated for Leagoo M8, ROM for all devices (see above for details)
Contributors
stephendt0
ROM OS Version: 6.0.x Marshmallow
Based On: FreemeOS
Version Information
Status: Testing
Created 2017-03-18
Last Updated 2017-03-18

Tips:
- You can enable hotspot tile in quick settings by toggling hotspot on and off once
- You can remove the non-functional tiles from quick settings by enabling SystemUI Tuner (hold settings button)
Changelog:
Version 1.0 (Based on 20161213 ROM)
Installed the following apps as system apps:
Nano OpenGapps (update all core Gapps packages)
Nova Launcher
Android Messages
Google Clock
Google Calculator
GBoard (Replacing Google Keyboard)
MK Explorer
Removed the following apps:
App Store (Not Play Store)
Bookmark Provider
Browser
Calculator
Calendar
Child Mode
com.freeme.theme.Lineart
com.freeme.theem.theme_colourful
Concentric circles
Clock
Dual Tag
Kika for LEAGOO
File Manager
Email
Music
Videos
Weather
Google Pinyin Input
Talkback
Locknow
Power Saver
FreeMe OS Lite
Com.freeme.motionrecognition
Com.freeme.theme.qindefault
Messages
Sound Recorded
GHBL 1.0 (Lock)
Cleantask 3.0.7
Search
Supershot
Screen Recorder

I was able to flash TWRP using the files you uploaded. Now I'm rooted. Thank you so much. More grease to your elbow.

donshady28 said:
I was able to flash TWRP using the files you uploaded. Now I'm rooted. Thank you so much. More grease to your elbow.
Click to expand...
Click to collapse
Glad to hear it, first time I've ever uploaded a ROM. :good: Feel free to use the thanks button and let me know how it goes for you!
Edit: If anyone is able to help out with the wish list, I'd be very appreciative!

Great work and congratulations on your first rom.
Did you run any benchmarks before and after? And how is ram consumption vs. stock?

Palm Trees said:
Great work and congratulations on your first rom.
Did you run any benchmarks before and after? And how is ram consumption vs. stock?
Click to expand...
Click to collapse
I can't say I tested much before and after (I couldn't stand the bloat lol), but it definitely feels a lot more responsive, and I am getting good battery life now - around 6hrs SOT today, few phone calls, but mostly messaging and reddit/facebook and a bit of book reading. I'm very happy so far. There are reviews where people were saying they were getting a lot less SOT than that, so I think it's an improvement.
Next thing I'll add to my wish list is to integrate the Google Dialer and Google Contacts app from the play store to replace the stock Android 6.0 apps, assuming that they work well during my testing on this device. They have a couple more features and being linked to the play store means that as Google adds more features and improves functionality, the ROM will automatically get those updates.

Thank you so much for your effort. You help many others

Update: Xposed works fine, and once I installed gravitybox I was able to remap the buttons with relative ease. More info here: https://forum.xda-developers.com/showthread.php?t=3034811
Edit: was getting some strange issues with Xposed so uninstalled it. For example, my recents key disappeared randomly after a reboot :/

I enjoy this lazy man ROM alot. I have enough juice to make my day. Thank you stephend. I'll advise you a to switch to this ROM.

Greetings.
SP Flash tool returns error 5054

galensbane said:
Greetings.
SP Flash tool returns error 5054
Click to expand...
Click to collapse
You need to retry. There's nothing wrong with the files.

donshady28 said:
You need to retry. There's nothing wrong with the files.
Click to expand...
Click to collapse
I've try many times, with or without battery, after plug in the status bar goes 100% red downloading and after 5 seconds gives the error.
In the proccess from scatter file i've checked only the recovery file is that correct?

Do you have your drivers properly installed??? If not, follow this link and download mtk driver
https://uploads.to/xfwv5rrz2zsx

donshady28 said:
Do you have your drivers properly installed??? If not, follow this link and download mtk driver
https://uploads.to/xfwv5rrz2zsx
Click to expand...
Click to collapse
Thanks for the link.
I've install the driver (both on x86 and x64 windows system).
Same error.
Do i have to check anything else except the recovery?
maybe preloader or dsp_bl??

Just the recovery.
You don't have to check any thing just the recovery okay. I don't understand what's going on with your phone. Use another computer.

donshady28 said:
You don't have to check any thing just the recovery okay. I don't understand what's going on with your phone. Use another computer.
Click to expand...
Click to collapse
Actually i did.
I've tried on win 10 x64 and win 7 x86 provided the drivers you gave me, same thing :S

Reinstall
Reinstall the driver. I used a Windows 7 to flash the recovery.
Try a Windows 7 pc okay

donshady28 said:
Reinstall the driver. I used a Windows 7 to flash the recovery.
Try a Windows 7 pc okay
Click to expand...
Click to collapse
I actually did it!
The problem was in the "how to" engage the process.
I was pressing both volume buttons and then plug in the phone in the computer.
It worked with just plug in the phone!
I did it on windows 10 x64
Thanks for all the help.
Phone is smooth, great work.

Enjoy.

Yes, mediatek phones are a bit funny, all you have to do is click download and then connect the device whilst it is powered off and it will just flash away, no button pressing needed.
I really would like to re-arrange these on-screen buttons though. Preferably on a system level by editing an XML file. Anyone know how to do this?
Edit: Also, has anyone lost vibration after flashing my deblotated ROM? I've just noticed my phone doesn't vibrate, but I think it might be hardware.

[ROM][UNOFFICIAL][7.1.2] OmniROM

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OmniROM is a free, community built, aftermarket firmware distribution of Android 7 (Nougat), which is designed to increase performance, reliability and features over stock Android for your device. It's also about options, which is the beauty of Android.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
OmniROM is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts.
All the source code for OmniROM is available in the OmniROM Github repo.
Homepage:
=================
http://omnirom.org/
Wiki:
=================
http://docs.omnirom.org/Main_Page
Gerrit:
=================
https://gerrit.omnirom.org/
Bugtracker:
=================
http://jira.omnirom.org
Use this thread to report bugs as this is UNOFFICIAL
IRC:
=================
irc.freenode.net #omnirom
Be Advised:
=================
Root access is not included by default. Please flash SuperSU for root (See below).
If problems arise from your use of custom kernels, "performance scripts", etc. etc., we can't be responsible.
Screenshots:
=================
http://abload.de/img/screenshot_20170814-2qlsi5.png
http://abload.de/img/screenshot_20170814-2mssai.png
Installation Instructions:
=================
First time installing OmniROM to your Shield Tablet or coming from another ROM:
- Read known issues and FAQs
- Make sure you're running a proper working Team Win Recovery Project (TWRP) - https://twrp.me/devices/nvidiahshieldtablet.html
- Copy GApps and OmniROM ZIPs to your SDCard
- Boot into Recovery
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Flash OmniROM zip from SDCard
- Flash GApps zip from SDCard
- Reboot
- Don't restore system data using Titanium Backup!
Upgrading from earlier version of OmniROM:
- Copy the OmniROM zip to your SDCard
- Boot into Recovery
- Flash the OmniROM zip from SDCard
- Reboot
Downloads:
=================
UNOFFICIAL builds
omni-7.1.2-20171110-shieldtablet-HOMEMADE.zip md5:196df454441117da0962015063573a95
omni-7.1.2-20170901-shieldtablet-HOMEMADE.zip md5:02b22807016a3e39d0b0e46986fb24d9
omni-7.1.2-20170818-shieldtablet-HOMEMADE.zip md5:1ebc771fa3626a2a2bd7e68d72df9f7b
omni-7.1.2-20170816-shieldtablet-HOMEMADE.zip md5:4710c3ec9347e1c9ca7dc4013fde0bbf
MIRROR: omni-7.1.2-20170816-shieldtablet-HOMEMADE.zip
Gapps: Open Gapps
http://opengapps.org/
SuperSU:
http://www.supersu.com/download
Device Source Code:
=================
Device trees:
https://github.com/Lolzen/android_device_nvidia_shieldtablet
https://github.com/Lolzen/android_device_nvidia_shield-common
Kernel:
https://github.com/Lolzen/android_kernel_nvidia_shield
Nvidia hardware:
https://github.com/Lolzen/android_hardware_nvidia_power
https://github.com/Lolzen/android_hardware_nvidia_thermal
https://github.com/Lolzen/android_hardware_nvidia_libstagefrighthw
Vendor blobs:
https://github.com/Lolzen/proprietary_vendor_nvidia
Credits:
=================
Steel01 for providing device trees and blob sources and doing an excellent job maintaining them
BitOBSessiOn and OmniROM folks for pointing me in the right direction getting past the Black Screen
OmniROM Project for code base and being #swag in General

Thanks ! The only problem is that the video is not working

marcostesvk said:
Thanks ! The only problem is that the video is not working
Click to expand...
Click to collapse
Thanks for reporting! Could you specify which app? I do have mixed results on this, on one hand YT / MX Player are working on the other one Clover can't play webM's.
I'll certainly look into it.

The YouTube app played only sound, and when I installed opengapps Pico or mini the Google play setup crashed. Bean gapps worked just fine. I am using original shield tablet wifi. Should I install k1 staging blob ?

marcostesvk said:
The YouTube app played only sound, and when I installed opengapps Pico or mini the Google play setup crashed. Bean gapps worked just fine. I am using original shield tablet wifi. Should I install k1 staging blob ?
Click to expand...
Click to collapse
I'd advice against that, personally.
However, i have a workaround for the videos. There's some problem with the hardware decoding, i still have to figure out why.
For now i simply disabled hardware decoders, the software decoding seems to work fine, but this isn't a fix by any means.
I'll add the link to the download once the upload finished.
added to OP
Another bug i've encountered is that the Shield Camera's pictures are distorted, however when you activate HDR everything is fine. Again, just a workaround for now. The alternative is to use AOSP Camera.

Charging issue fix available?
Hi. Any input on charging? I was able to flash the latest version but I see it doesn't want to charge above 88%, even when left plugged over night. Thanks very much for any input. Nvidia Shield Tablet, wifi, rooted.

fmcgregor said:
Hi. Any input on charging? I was able to flash the latest version but I see it doesn't want to charge above 88%, even when left plugged over night. Thanks very much for any input. Nvidia Shield Tablet, wifi, rooted.
Click to expand...
Click to collapse
Seems weird.
Does anybody else have this issue?

klo_lol said:
Seems weird.
Does anybody else have this issue?
Click to expand...
Click to collapse
Thanks for trying. And thanks to anyone for replying. In terms of self help, I downloaded some battery apps to see if they can re-align the battery so it can charge up to 100%. Still only charging up to 89%. Tried cleaning the input ports and the chargers. I have wiped cache partitions. I have the latest TWRP. I'm scared to try to re-flash because it was so difficult - "setup wizard keeps stopping."

you could try if this will make any difference, provided by BitOBsessiOn: https://www.androidfilehost.com/?fid=24591000424962292
Did you update the blob from the latest OTA for your Tablet (OG/K1)?
I honestly have no idea otherwise.
In terms of setup wizard, as you are not the only one having this problem apparently. Did you clean flash (aka wiping all necessary partitions) prior to flashing omni?
I personally didn't have any crash setting it up, but that may be sheer luck.. i've seen commits from Steel01 to Lineage which adress that issue, but i want to make as less changes in the general codebase as possible.
As an alternative you can use Bean gapps as marcostesvk pointed out. I may change this in OP if everbody has problems with the setup wizard.
Thanks for the feedback guys!

klo_lol said:
you could try if this will make any difference, provided by BitOBsessiOn: https://www.androidfilehost.com/?fid=24591000424962292
Did you update the blob from the latest OTA for your Tablet (OG/K1)?
I honestly have no idea otherwise.
In terms of setup wizard, as you are not the only one having this problem apparently. Did you clean flash (aka wiping all necessary partitions) prior to flashing omni?
I personally didn't have any crash setting it up, but that may be sheer luck.. i've seen commits from Steel01 to Lineage which adress that issue, but i want to make as less changes in the general codebase as possible.
As an alternative you can use Bean gapps as marcostesvk pointed out. I may change this in OP if everbody has problems with the setup wizard.
Thanks for the feedback guys!
Click to expand...
Click to collapse
I'm very VERY grateful for your replies. I will try the battery link tonight. I didn't update the blob from any OTAs. This tablet is the replacement tablet from the recall. I rooted it and I don't get any OTAs. Perhaps it's something I can get and flash? If so, I would gladly try it. Re. setup wizard, I always clean flash ROMs and in fact I wipe all twice for luck and then again after flashing Gapps. Setup wizard error popped up and you can't swipe down to get to the Settings or the wifi. On the 70th try (and after youtube videos and articles) of trying to quickly slide to the notification bar, I was able to slide down and get to Settings to turn on wifi (ie, the solution). Last thing I did was out of frustration (nothing was flashing, Tesla, Lineage 14.1, etc., and this came closest) I unplugged the charger while sliding down and suddenly the bar came down -coincidence? Don't know. You don't want that error, it's like the android on his back. Full disclosure, I had to go into the updater script file and delete the assert lines so I'd stop getting the TWRP Error 7. Which worked. Learned that from here https://www.youtube.com/watch?v=wed03948gcg. I'll report back. Thank you for your attention and sorry to be a PITA!

fmcgregor said:
I'm very VERY grateful for your replies. I will try the battery link tonight. I didn't update the blob from any OTAs. This tablet is the replacement tablet from the recall. I rooted it and I don't get any OTAs. Perhaps it's something I can get and flash? If so, I would gladly try it. Re. setup wizard, I always clean flash ROMs and in fact I wipe all twice for luck and then again after flashing Gapps. Setup wizard error popped up and you can't swipe down to get to the Settings or the wifi. On the 70th try (and after youtube videos and articles) of trying to quickly slide to the notification bar, I was able to slide down and get to Settings to turn on wifi (ie, the solution). Last thing I did was out of frustration (nothing was flashing, Tesla, Lineage 14.1, etc., and this came closest) I unplugged the charger while sliding down and suddenly the bar came down -coincidence? Don't know. You don't want that error, it's like the android on his back. Full disclosure, I had to go into the updater script file and delete the assert lines so I'd stop getting the TWRP Error 7. Which worked. Learned that from here https://www.youtube.com/watch?v=wed03948gcg. I'll report back. Thank you for your attention and sorry to be a PITA!
Click to expand...
Click to collapse
I'm grateful for the feedback too, no worries!
You can get any OTA here https://developer.nvidia.com/shield-open-source directly from nvidia, labeled recovery images.
Inside the zip are instructions, but the most important parts are the blob and bootloader.
I sincerly hope this fixes any issues.
Regarding gapps: that truly sounds like hell. I'll do a backup and clean flash probably tomorrow. I'll report back on that matter when i have some details.
You are on the latest TWRP, is suppose?

klo_lol said:
I'm grateful for the feedback too, no worries!
You can get any OTA here https://developer.nvidia.com/shield-open-source directly from nvidia, labeled recovery images.
Inside the zip are instructions, but the most important parts are the blob and bootloader.
I sincerly hope this fixes any issues.
Regarding gapps: that truly sounds like hell. I'll do a backup and clean flash probably tomorrow. I'll report back on that matter when i have some details.
You are on the latest TWRP, is suppose?
Click to expand...
Click to collapse
Yes TWRP 3.1.1-1. Thx very much for the OTA link. Just fyi, the battery zip link was dead. But I'll find a working link now that I know the general name..

klo_lol said:
you could try if this will make any difference, provided by BitOBsessiOn: https://www.androidfilehost.com/?fid=24591000424962292
Did you update the blob from the latest OTA for your Tablet (OG/K1)?
I honestly have no idea otherwise.
In terms of setup wizard, as you are not the only one having this problem apparently. Did you clean flash (aka wiping all necessary partitions) prior to flashing omni?
I personally didn't have any crash setting it up, but that may be sheer luck.. i've seen commits from Steel01 to Lineage which adress that issue, but i want to make as less changes in the general codebase as possible.
As an alternative you can use Bean gapps as marcostesvk pointed out. I may change this in OP if everbody has problems with the setup wizard.
Thanks for the feedback guys!
Click to expand...
Click to collapse
Hi, just an update. I re-flashed and used bean gapps this time. No problems this time, but the battery still won't charge above 89%. Just as a by the way, the clock and date start up at factory until I get it on the wifi and it syncs. Every time. If there's no wifi, it's set to Dec. 31, 2012. Anyone else with this?

uploaded a new build. Link in OP.
No major changes, just up2date with omni source as of today

new build in OP.
*updated with latest omni 7.1 changes
*updated with some device changes from Aaron Kling
*updated kernel with latest nvidia kernel sources
i'm still bumping my head against a wall why hwencoders seem to have some sort of problems. You can play media, it's just not working with the configs it's supposed to.

Development [ROM] [UNOFFICIAL] [12.1.0] [TB-J607F] Evolution X Snow

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Evolution X 6.5 for the Lenovo Xiaoxin Pad Plus (Lenovo P11 5G WiFi) [TB-J607F]​
Code:
/*
* Your warranty is void. Or valId, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modifications, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/
Keep Evolving
Pixel UI, customization, and more, we are Evolution X!
- Team Evolution X -
@joeyhuab
@RealAkito
@AnierinB
Reach us on Twitter! @EvolutionXROM​
Just flash and check "The Evolver". We have tons of features combined together from different ROMs.
DO NOT FLASH GAPPS, ALREADY INCLUDED​
* Probable lost frames when dragging the apps from app drawer to the home screen.
* If you open the Wallpaper Picker in 2-Pane layout (Like open it via Settings), the Wallpaper will be zoomed incorrectly and look blurry. (Note: if you want to set the wallpaper, open the wallpaper picker from the Launcher).​
First Time Install / Clean Flash
1. Reboot to Recovery
2. Download the zip for your device
3. Flash whichever recovery you desire in both slots
4. Format Data
5. If you are going to flash from stock ROM, switch to the other slot in recovery, then reboot to recovery
6. Enable ADB Sideload feature, then Sideload the package to your tablet
Code:
adb sideload <path to the flashable zip>
7. Reboot to System and #KeepEvolving
Update / Dirty Flash
1. Reboot to Recovery
2. Download the update for your device
3. Flash the ROM via ADB Sideload
4. Reboot to System and #KeepEvolving​
Android OS version: 12.1.0_r11
Security patch level: July 2022
Build author: bigsaltyfishes
Source code: https://github.com/Evolution-X
Kernel Source code: https://github.com/bigsaltyfishes/kernel_lenovo_J607Z
ROM Developer: Joey Huab

Changelog:
2022-07-07:
Notes: Clean Flash Required
Device Changes:
1. Switch to Proton Clang
2. Switch to SkiaGL Threaded Renderer
3. Import Vulkan Overlay from Pixel 5
4. Enable DT2W
5. Import missing governor script from stock rom
6. Import Lenovo side changes to init scripts
Kernel Changes:
1. Upstream kernel to 4.19.250
2. Merge Tag LA.UM.9.12.r1-14300-SMxx50.0

Very good work. Is it possible to get an EvolutionX rom for the tb-j706f ?

Can we get 606f support as well?

I noticed that you recently merged latest caf on your kernel. Did you recover your device?
If you did, could you please tell me how your touch panel is detected as, in your deviceinfohw? (It would be more helpful if you upload your device info onto deviceinfohw, although I understand that it may be hard to in some regions)
I have a similar but different J606F, and the bad manufacturer lenovo didn't include touch panel driver in the kernel, lol.
Thanks

LegendOcta said:
I noticed that you recently merged latest caf on your kernel. Did you recover your device?
If you did, could you please tell me how your touch panel is detected as, in your deviceinfohw? (It would be more helpful if you upload your device info onto deviceinfohw, although I understand that it may be hard to in some regions)
I have a similar but different J606F, and the bad manufacturer lenovo didn't include touch panel driver in the kernel, lol.
Thanks
Click to expand...
Click to collapse
I've already recover my device. Here are the screenshot of Device info Hw, hope it is helpful for you.

LegendOcta said:
I noticed that you recently merged latest caf on your kernel. Did you recover your device?
If you did, could you please tell me how your touch panel is detected as, in your deviceinfohw? (It would be more helpful if you upload your device info onto deviceinfohw, although I understand that it may be hard to in some regions)
I have a similar but different J606F, and the bad manufacturer lenovo didn't include touch panel driver in the kernel, lol.
Thanks
Click to expand...
Click to collapse
Hi!
I've got an J606L, and I'm going crazy because of Lenovo didn't include the touchscreen driver in the opnesource package... I've tried to make TWRP/OrangeFox recovery, but the touchscreen don't work.
Can we somehow use this J607 kernel source in your opinion? In HWinfo almost everything is the same for me. Touchscreen, wifi, als/ps, acc.meter, gyro etc. Thanks for the dev/screenshot OP!

Marci344 said:
Hi!
I've got an J606L, and I'm going crazy because of Lenovo didn't include the touchscreen driver in the opnesource package... I've tried to make TWRP/OrangeFox recovery, but the touchscreen don't work.
Can we somehow use this J607 kernel source in your opinion? In HWinfo almost everything is the same for me. Touchscreen, wifi, als/ps, acc.meter, gyro etc. Thanks for the dev/screenshot OP!
Click to expand...
Click to collapse
I don't think you can't directly use this J607 kernel source as the soc of J606(sm6115) is different from J607(sm7225), but I found that the kernel version of J606 in stock rom is same as J607, maybe the J607 kernel source code can serve as a reference for you to fix the J606 kernel source code. Also, If you want to fix touchscreen in TWRP/OrangeFox, you need to import touchscreen firmware from stock rom.

bigsaltyfishes said:
I don't think you can't directly use this J607 kernel source as the soc of J606(sm6115) is different from J607(sm7225), but I found that the kernel version of J606 in stock rom is same as J607, maybe the J607 kernel source code can serve as a reference for you to fix the J606 kernel source code. Also, If you want to fix touchscreen in TWRP/OrangeFox, you need to import touchscreen firmware from stock rom.
Click to expand...
Click to collapse
Hi!
Yes I've seen your kernel source. I think it will help me for the building, because there is many similarity. Even the filesystem is 1:1 same. I've got final exams in the next few weeks in the Uni too, but after that I will try to make it.
One question tho. How can you export the touchscreen files from the stock rom? I dont know how look your tablet's firmware, but the J606L has a very stupid firmware structure, with superpartitions, and I cannot get any useful stuff out from it, just the vbmeta, boot/recovery images.
Thank you, and sorry for the offtopic.

Marci344 said:
Hi!
Yes I've seen your kernel source. I think it will help me for the building, because there is many similarity. Even the filesystem is 1:1 same. I've got final exams in the next few weeks in the Uni too, but after that I will try to make it.
One question tho. How can you export the touchscreen files from the stock rom? I dont know how look your tablet's firmware, but the J606L has a very stupid firmware structure, with superpartitions, and I cannot get any useful stuff out from it, just the vbmeta, boot/recovery images.
Thank you, and sorry for the offtopic.
Click to expand...
Click to collapse
You can find firmware you need in /vendor/firmware. If it is hard for you to extract them from your tablet, you can simply extract them from 9008 Images. Partitions in super partition are simply named as super_*.img in 9008 package, they are raw images, you can directly mount them with ro option (They have share_blocks feature, you can't mount them in rw mode).

can i flash it on j706f?

Marci344 said:
Hi!
I've got an J606L, and I'm going crazy because of Lenovo didn't include the touchscreen driver in the opnesource package... I've tried to make TWRP/OrangeFox recovery, but the touchscreen don't work.
Can we somehow use this J607 kernel source in your opinion? In HWinfo almost everything is the same for me. Touchscreen, wifi, als/ps, acc.meter, gyro etc. Thanks for the dev/screenshot OP!
Click to expand...
Click to collapse
The thing that's missing is the kernel module for the NT356(something)_HostDL or something in the kernel's {SRCROOT}/drivers/input/touchscreen/NT35something_HostDL.
The driver, IS available in a P11 LTe or something's kernel source available in lenovo downlooad page. (Sorry, my memory is very inaccurate, I was trying bunch of stuffs when I bought my P11 last year, it's a bit hazy now)
I made the driver located there, modded Makefile, got some kernel compile issue, and I somehow solved it, but the spi read only got value 00000000 and it didn't work. (You can get more info from postmarketOS-offtopic Matrix chatroom, chat history is logged in there, I got help from somebody a long time ago and there are conversations about this)
I got touchscreen to work with a prebuilt kernel (Lost the device tree) but that's it..
I hope we make something out of lenovo's junky kernel source codes.. The device has potentials!

bigsaltyfishes said:
I've already recover my device. Here are the screenshot of Device info Hw, hope it is helpful for you.View attachment 5625467
Click to expand...
Click to collapse
Wonderful that you recovered it!
Thanks a lot for the screenshot. It seems like that you have the himax touchscreen variant. (I was trying to ask you to test the driver for nt365blahblah touch screen, if your variant was the one that had it)

hi sir, i flashed crdroid gsi on my j706f, but the settings doesnt look like your rom which show in two pane, can i edit build.prop to get it show as your rom settings? or what should i edit? thank you very much.

sabosanbosocho said:
hi sir, i flashed crdroid gsi on my j706f, but the settings doesnt look like your rom which show in two pane, can i edit build.prop to get it show as your rom settings? or what should i edit? thank you very much.
Click to expand...
Click to collapse
You can't enable it by simply editing build.prop. This feature related to an optional package called androidx.window.extensions. Ask GSI builder add this package or build it yourself.

great work!
overall pretty pleasant experience, and nice feature set. However, two problems
1. as mentioned, adding app icon to the homescreen doesn't work sometimes and it laggs out
2. this is the deal breaker for me, as the volume slider doesn't work. and video play back stuffers probably due to this.
---
update:
the second issue ragarding to the volume slider, it only breaks after playing emby, not sure if other app also break it but that's the only one i found so far. a reboot would fix it

Please make Evolution X happen to TB-J606F also! it's with an older SOC, and we don't get A12 update. A lot of people have it, but not much support

Does widevine security L1?

bigsaltyfishes said:
You can't enable it by simply editing build.prop. This feature related to an optional package called androidx.window.extensions. Ask GSI builder add this package or build it yourself.
Click to expand...
Click to collapse
did you add that by yourself or that was included in evox source code?

mdve123 said:
Please make Evolution X happen to TB-J606F also! it's with an older SOC, and we don't get A12 update. A lot of people have it, but not much support
Click to expand...
Click to collapse
you can flash google gsi (android 12), its works good.
Generic System Image releases | Platform | Android Developers
developer.android.com