Related
Hi friends:
I have an infuse 4g with the infamous power button issue. Somehow I have managed to install kitkat on it (due to power button being too touchy in touching it, it was almost impossible to boot to recovery or download mode using the button combo).
So I flashed AoCP 7.2 which was good. I even liked the fact that the CWM recovery included with it did not need me to press the power button for menu selection but rather the capacitive touch search button worked for menu item selection. The CWM version was 6.0.4.6.
But now I updated to CM11 and it upgraded my recovery to 6.0.4.8 but now capacitive search button does not work for item selection. Option and home capacitive touch buttons are still working for moving up and down but I really want search capacitive touch button to work for item selection.
Can somebody explain how can I enable this?
Edit: the search capacitive button does not work for item selection in the root menu (it works in any of the sub-menus).
Thanks in advance.
anybody please.
@Fullmetal Jun
Hi Fullmetal Jun:
I applied your recently created cm11 image and it seems the latest recovery does not allow search capacitive button on the main screen in cwm.
I checked the recent commits in recovery in the github and there are some changes related to how the search button is handled.
I thought to compile the recovery myself but i need the board specific make file that i want to extract from the boot.img but the unpack tools are not working on the boot.img, can you please provide this or generate a new boot.img with recovery fixes (the fix should be small).
Thanks
[email protected] said:
Hi Fullmetal Jun:
I applied your recently created cm11 image and it seems the latest recovery does not allow search capacitive button on the main screen in cwm.
I checked the recent commits in recovery in the github and there are some changes related to how the search button is handled.
I thought to compile the recovery myself but i need the board specific make file that i want to extract from the boot.img but the unpack tools are not working on the boot.img, can you please provide this or generate a new boot.img with recovery fixes (the fix should be small).
Thanks
Click to expand...
Click to collapse
I'm sorry, but I've never created any files for the Infuse! You sure it's really me?
All I know is that I created a detailed list of procedures to flash ROMs properly for the Infuse 4G!
For selection using touch screen, CWM Recovery supports only the capacitive buttons like you mentioned above!
BUT another recovery called TeamWin Projects(TWRP) allows use of touch screen in recovery while flashing which is what you want! It has a newer interface and is as reliable as CWM!! You'll need to find a stable version though
@rwaterspf1
Ohh I'm sorry. rwaterspf1 did it and I saw one of your reply in that thread. Thanks for your replying.
So yeah search capacitive search button does not work for selection in the root menu (the very first menu that you see when cwm recovery starts).
I want this as my infuse has power button issue and I don't want to use power button for selection.
@rwaterspf1
So i checked the source code in default_recovery_keys.c in https://github.com/CyanogenMod/android_bootable_recovery/blob/cm-11.0/default_recovery_keys.c
earlier it was like this and the search capacitive button was working for item selection:
case KEY_END:
case KEY_BACKSPACE:
case KEY_SEARCH:
- if (ui_get_showing_back_button()) {
- return SELECT_ITEM;
- }
- if (!get_allow_toggle_display() && !ui_root_menu) {
- return GO_BACK;
- }
case KEY_BACK:
if (!ui_root_menu) {
return GO_BACK;
but with a recent commit, it was changed to following and as you can see that search button wont anymore do item selection:
case KEY_END:
case KEY_BACKSPACE:
case KEY_SEARCH:
case KEY_BACK:
if (!ui_root_menu) {
return GO_BACK;
I think it'd be really great to use search button for item selection so that the devices like mine can use it instead of the buggy power button
Model GT-I9505
Model name GALAXY S4 LTE
Country Netherlands
Version Android 5.0.1
Changelist 5659496
Build date Wed, 09 Dec 2015 09:49:25 +0000
Product code PHN
PDA I9505XXUPOL1
CSC I9505PHNPOL1
Flashing Instructions (method 1)
- Unzip the file
- Open Odin 3.09
- Restart phone in download mode (Press and hold Home + Power + Volume down buttons)
- Connect phone and wait until you get a blue sign in Odin
- Add extracted MD5-file to AP
- Make sure re-partition is UNticked
- Start flash, sit back and wait a few minutes.
- If you encounter any issues with the firmware (Any FC, Bootloop etc)
- Boot into recovery mode (Home+ Power + Volume Up)
- Choose to wipe/factory reset. (THIS WILL ERASE ALL OF YOUR DATA INCLUDING YOUR INTERNAL SD CARD!)
- Then choose reboot and you should be good to go!
Flashing instructions (method 2)
**Required** FlashFire - Play BETA - PREVIEW
1. Join the G+ community using the same Google account as you're using for Play on your phone/tablet Here.
2. Sign up to receive the BETA versions from Play Here.
Instrucions:
-place these images onto your device (use either internal or ext-sdcard).
-Open the FlashFire app and "Agree" to the Terms and Conditions.
-Press "(+)" twice to bring up the "Actions" menu.
-Press "Flash firmware package" then locate and select System.img.ext4. FlashFire will scan the .img which may take several minutes to complete. Press "ok" once the scan is complete then press the checkmark to continue.
-Press "Flash firmware package" again then locate and select Cache.img.ext4. FlashFire will then scan the .img. Press "ok" once the scan is complete then press the checkmark to continue.
-Press “(+)” once again to bring up “Actions” and select “Wipe.” Under the “Options” menu select all partitions except “Internal storage” then press the checkmark to continue.
-From the main menu Tap-hold-drag your "Actions" and place them in the following order:
- "Wipe"
- "Flash firmware package"(system.img.ext4)
- "Flash firmware package"(cache.img.ext4)
- "Process Cache" (Use default settings).
- "EverRoot" (Use default settings).
-Last, press the lightning bolt then "Ok" to begin the flash.
The screen will turn black then display the contents of your system before beginning the flashes. Once complete your device will reboot and pause on the Samsung splash screen for about 3 - 4 minutes before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Notes:
1. You must already have a compatible custom kernel installed. Recommended Kernel: http://www.imperiumrom.com/S4/5.0.1/OTA/kernel/Imperium_LL_Kernel_v3.1.zip
2. After flashing I9505 firmware your wifi password may be forgotten upon reboot. To resolve this issue use ES File Explorer with root access enabled to edit the following build.prop line: ro.securestorage.support=true to "false"
3. You may also continuously receive an annoying security message. You can disable this message by using TiBu to freeze or remove the SecurityLogAgent.apk. Thanks to @Nana Ayeh
Download firmware pol1
https://mega.nz/#!RMxmkDRI!6rywz2otK1cpFK6Y1pKJtwsG16iMNrlnPWi-pBo2KLA
Hi there,
What actually is improved?
Sent from my SM-G903F using Tapatalk
Hi,
Is it to possible to upload both modem and bootloader (OK1) separately ? Thanks
mehdoux said:
Hi,
Is it to possible to upload both modem and bootloader (OK1) separately ? Thanks
Click to expand...
Click to collapse
Let me finish downloading the file guys, so I can access them. Make sure to thank my post for rating.
osssinator said:
Hi there,
What actually is improved?
Sent from my SM-G903F using Tapatalk
Click to expand...
Click to collapse
I'll post up a changelog
Download is done, I will soon post up a fast download link for you guys
Make sure to like my post considering it was my first post related to our beloved galaxy s4.
Thread closed, placeholders not allowed..
Whiskey
Forum Moderator
Whiskey103 said:
Thread closed, placeholders not allowed..
Whiskey
Forum Moderator
Click to expand...
Click to collapse
Thread reopened happy downloading
Is this better than OJ2?
NeosHaruki said:
Is this better than OJ2?
Click to expand...
Click to collapse
Not in every way but yea.
Just install this version and can't get Wifi on! It's a fix for this?
Edit: Updating baseband and Wifi Fix do the trick.
Can you post the modem/bootloader here so people can download the files? That would be great.
do you guys notice that 60fps in youtube is only 60fps by holding your finger in the screen and then 30fps when untouching? Or is it just me? Either way youtube is actually rendering a stable 60fps on the gs4! Only way this was possible was whe performance mode was turned on in cm12.1 now its doing it on touchwiz at default, thats big news, at we need to do is find the bug or whatever is causing the unstable 60fps when information dissapears i youtube or pressing the screen to get 60fps
(Edit2) happy day guys a happy thanks giving which i always wanted on this phone 1 of the main reasons why i choose aosp over tw, i can now play 60fps videos on YouTube with real 60fps and not stuttery 60fps before hok1!)) so i notice that youtube was not 60fps when choosing 60fps quality so i go to setting and enable nuplayer and reboot and its flawless :,) aosp please implement this to ur roms! Omg happy day! Bye guys
(Edit3) its stuttering again, -_- any 1 have a permanent fix? Would appreciate
jeffrey1296 said:
do you guys notice that 60fps in youtube is only 60fps by holding your finger in the screen and then 30fps when untouching? Or is it just me? Either way youtube is actually rendering a stable 60fps on the gs4! Only way this was possible was whe performance mode was turned on in cm12.1 now its doing it on touchwiz at default, thats big news, at we need to do is find the bug or whatever is causing the unstable 60fps when information dissapears i youtube or pressing the screen to get 60fps
(Edit2) happy day guys a happy thanks giving which i always wanted on this phone 1 of the main reasons why i choose aosp over tw, i can now play 60fps videos on YouTube with real 60fps and not stuttery 60fps before hok1!)) so i notice that youtube was not 60fps when choosing 60fps quality so i go to setting and enable nuplayer and reboot and its flawless :,) aosp please implement this to ur roms! Omg happy day! Bye guys
(Edit3) its stuttering again, -_- any 1 have a permanent fix? Would appreciate
Click to expand...
Click to collapse
There are possibly two libdivxdrm.so files in /system/lib/ one is about 180kb and the other around 200kb, rename or delete the 180kb one and keep the other in all lowercase name, that may help fix stuttering.
Starnel said:
There are possibly two libdivxdrm.so files in /system/lib/ one is about 180kb and the other around 200kb, rename or delete the 180kb one and keep the other in all lowercase name, that may help fix stuttering.
Click to expand...
Click to collapse
180kb i renamed, i didnt fully understand the all lowercase? 200kb? I seen the libdiv 200kb with all lowercase already,the videos run without any stutter 60fps, but after multytasking apps the videos start to stutter again, i tried clearing memory but no go, theres gotta be a fix.
Starnel said:
There are possibly two libdivxdrm.so files in /system/lib/ one is about 180kb and the other around 200kb, rename or delete the 180kb one and keep the other in all lowercase name, that may help fix stuttering.
Click to expand...
Click to collapse
Out of curiosity I checked my GPE 5.1 rom and there is only one libdivxdrm.so file and its 189kb.
thaidroid said:
Out of curiosity I checked my GPE 5.1 rom and there is only one libdivxdrm.so file and its 189kb.
Click to expand...
Click to collapse
Hmmm! Add the touchwiz libs and maybe it will fix the lag at the beginning!
What is New/Improved as compared to OJ2?
Usama707 said:
What is New/Improved as compared to OJ2?
Click to expand...
Click to collapse
Yes it's much better!
jeffrey1296 said:
First things first HAPPY THANKSGIVING Everyone enjoy this beautiful day drive safe and one more thing gobble gobble. Today Samsung updated the gs4 with official software improving our device I left a link and instructions on how to successfully install.
Model GT-I9505
Model name GALAXY S4 LTE
Country Brazil
Version Android 5.0.1
Changelist 6179422
Build date Wed, 04 Nov 2015 20:28:53 +0000
Product code ZTO
PDA I9505VJUHOK1
CSC I9505ZTOHOK1
Download for install with Odin or flashfire:
Flashing Instructions (method 1)
- Unzip the file
- Open Odin 3.09
- Restart phone in download mode (Press and hold Home + Power + Volume down buttons)
- Connect phone and wait until you get a blue sign in Odin
- Add extracted MD5-file to AP
- Make sure re-partition is UNticked
- Start flash, sit back and wait a few minutes.
- If you encounter any issues with the firmware (Any FC, Bootloop etc)
- Boot into recovery mode (Home+ Power + Volume Up)
- Choose to wipe/factory reset. (THIS WILL ERASE ALL OF YOUR DATA INCLUDING YOUR INTERNAL SD CARD!)
- Then choose reboot and you should be good to go!
Flashing instructions (method 2)
**Required** FlashFire - Play BETA - PREVIEW
1. Join the G+ community using the same Google account as you're using for Play on your phone/tablet Here.
2. Sign up to receive the BETA versions from Play Here.
Download firmware
https://mega.nz/#!hchmxTAA!bOcrA25xY9-MU5wxS0Rs1FULo4crgEokVJ_3bzzieT8
Instrucions:
- Extract the System.img.ext4 and Cache.img.ext4, e.g. I9505VJUHOK1_I9505ZTOHOK1_ZTO.zip then place these images onto your device (use either internal or ext-sdcard).
-Open the FlashFire app and "Agree" to the Terms and Conditions.
-Press "(+)" twice to bring up the "Actions" menu.
-Press "Flash firmware package" then locate and select System.img.ext4. FlashFire will scan the .img which may take several minutes to complete. Press "ok" once the scan is complete then press the checkmark to continue.
-Press "Flash firmware package" again then locate and select Cache.img.ext4. FlashFire will then scan the .img. Press "ok" once the scan is complete then press the checkmark to continue.
-Press “(+)” once again to bring up “Actions” and select “Wipe.” Under the “Options” menu select all partitions except “Internal storage” then press the checkmark to continue.
-From the main menu Tap-hold-drag your "Actions" and place them in the following order:
- "Wipe"
- "Flash firmware package"(system.img.ext4)
- "Flash firmware package"(cache.img.ext4)
- "Process Cache" (Use default settings).
- "EverRoot" (Use default settings).
-Last, press the lightning bolt then "Ok" to begin the flash.
The screen will turn black then display the contents of your system before beginning the flashes. Once complete your device will reboot and pause on the Samsung splash screen for about 3 - 4 minutes before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Notes:
1. You must already have a compatible custom kernel installed. Recommended Kernel: http://www.imperiumrom.com/S4/5.0.1/OTA/kernel/Imperium_LL_Kernel_v3.1.zip
2. After flashing I9505 firmware your wifi password may be forgotten upon reboot. To resolve this issue use ES File Explorer with root access enabled to edit the following build.prop line: ro.securestorage.support=true to "false"
3. You may also continuously receive an annoying security message. You can disable this message by using TiBu to freeze or remove the SecurityLogAgent.apk. Thanks to @Nana Ayeh
Click to expand...
Click to collapse
Dont hit it and quit it guys, leave a quick like, it motivates me to push updates with a fastdowload link as soon as their out.
Thanks
-jeff
{
"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"
}
KatKiss ROM
MarshMallow 6.0.1 ReleaseAsus TF101
Please note that this version is made for and tested on the TF101 model.
This rom is an aosp based rom with my own additions on top of it.
The main motto of the rom being Kiss. Even though the Meerkat could give you a kiss, it stands for Keeps it Sweet and Simple too
Which means that just like the other K.A.T stuff, the rom's main goal is efficiency, speed/res ponsiveness,
while not adding bloated features that will slow things down
DOWNLOADS:
Latest Rom Version: KatKiss-6.0_034.zip | Mirror
[*] Gapps: opengapps pico
SuperSU: SuperSU BETA 2.52
Sound improvements & gps quick fix : K.A.T App
SL101 Compatibility Pack: KatKiss-6.0-sl101-compat-V5.zip (To flash after the rom for the Asus Slider SL101 only, DO NOT flash for the TF101 model)
Install Instructions:
These builds are designed to be installed with a recent recovery.
TWRP 2.8.1 is recommended: available here
Older versions of TWRP like 2.3.x won't work.
Backup everything !
Go to recovery
[*]The first time you install: Format /data (full wipe doesn't format)
(you can skip this step if you're already on the same main version of KatKiss, if ever you encounter a problem redo a full clean install and format /data and try again before reporting )
Then *EVERYTIME* flash (all together):
rom zip
SuperSU zip
[*]gapps zip
Wipe cache/dalvik
Reboot
Rom Main Features:
MultiWindow Support with 2, 3 or 4 panes setup
High speed and responsive oriented
High performance and overclocked KatKernel included
Dock keyboard Support with full special/function keys support
Global Keyboard Shortcuts / KeyOverride Macro association (See post #2 for more info)
HDMI Support
Battery Level Indicator & Dock Battery support + Mods (icon/Text/%)
CIFS, ext4, NTFS, ExFat support
RRO Theme Engine - Themes & more info
Native Android FSTRIM + Manual scripts for Database optimization and fstrim (see post #2)
Media Scanner Filters
Navbar with left, balanced (PixelC like) or middle aligned buttons.
All Wifi channels support
Integrated cpu & io performance settings panel
Custom Navbars buttons long press actions
Advanced power menu with reboot options.
User Immersive mode and actions with automode when docked setting
Advanced per application permission management (AppOps)
Ethernet-auto support
Misc utils Busybox, rsync...
Custom Quick Settings tiles
ChangeLog: http://public.timduru.org/Android/KatKiss/6.0/ChangeLog.html
Rom Source: https://github.com/timduru (branch katkiss-6.0)
Credits:
Original banner concept by i9apps, Bootanimation by mgeniusm, original drawing by BBF
Chainfire for SuperSU
WebPage
How to report
What to include in the report
Disclaimer: The usual
Use at your own risk, I won't be responsible for any damages caused to your Transformer or to yourself.
In most cases if something breaks, flashing a rom on top should fix it.
XDA:DevDB Information
KatKiss-MarshMallow, ROM for the Asus Eee Pad Transformer
Contributors
timduru
Source Code: https://github.com/timduru
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 2.6.x
Based On: AOSP
Version Information
Status: Stable
Created 2016-02-19
Last Updated 2018-10-19
Tips
First Install
Make sure you do a format /data the first time you install the rom
(backup your internal storage first if you want to keep something)
The first boot after a rom flash can take a few minutes as ART is slower than dalvik to optimize the applications, but is faster after the 1st time.
(First boot takes ~4-5 minutes without gapps and 10+ minutes with gapps)
Also keep in mind that after a fresh install, it might take a bit of time to get up to full speed as media scanner & google are checking/scanning and restoring stuff.
Bluetooth
Bluetooth might require to be turned on twice before it scans and displays the available devices.
Wallpaper Modes
Different Wallpaper modes have been added in Settings => Display
** Normal (regular android mode)
** Disable System Wallpaper rendering (set as default)
** Disable Wallpaper service
2nd setting will prevent the wallpaper being rendered by the system making things faster and also freeing resources
That's the recommended setting you want to use if you are using a launcher that has internal wallpaper rendering
The Default included Launcher3 has internal rendering
For Nova: Go to its Settings => Desktop => Wallpaper Scrolling => Force, then set a wallpaper.
(You will see a black wallpaper if you're not using a launcher that can do internal rendering, If wallpaper is important and that you want to keep your current launcher, then switch back to the 1st setting)
Youtube
Depending on your network and tablet load, 720p videos might not play or take longer to buffer.
Switch to 480p in that case.
Some videos are also 720p60fps so you might need to switch back to 480p for these too.
You can also try an older youtube version and disable auto updates: youtube-v5.0.21
Google Play Movies
Our current Widevine DRM libs are not compatible in MM.
So you can't play a movie on the tablet with Google Play Movies as it requires that.
Starting a movie to play on chromecast should be fine as the drm will be the chromecast one in that case.
Now On Tap
Now On Tap requires the nano opengapps version, however our default /system partition is too small to accommodate them.
So if you want to install the nano or bigger opengapps version, you'll need to repartition the storage space first using Bigwheelie for extended partitions
Then activate Now on Tap from google now settings
Hardware keyboard layouts
More languages have been added in the default asusec keyboard
Set the keyboard layout through Settings => Language & Input => asusec => setup keyboard layouts
These also allow live switching without reboot with ctrl + space
Global Key Override/Shorcut Mecanism
Available in Settings => Dock => Add Key Override Actions
This will allow you not only to redefine function keys assignment, and other special keys actions,
but you'll also be able to assign global macro actions / app launch to any key + Meta key combination (shift Left or Right , ctrl..)
You can also add multiple actions to one key combination, simply click again on the "+" button for the same key combination.
For example if you want to assign to one key combination a list of action to run before going to bed for example, like: turn wifi off, Bluetooth off, mute sound, and turn screen off, you can do that
Note that starting multiple applications with one key is kinda a miss and hit for the moment due to some mecanism in android that seems to prevent applications to start too close to each others.
Storage (fstrim) and Database optimization:
Fstrim is native since 4.3 and will happen in the background if your tablet is idle / sleeping and that your battery is > 70%
There is also a script to run it manually in the rom: /etc/kat/optimizestorage
To optimize the Database: /etc/kat/optimizedb
To run both, open a terminal and run:
su
/etc/kat/optimize
MultiWindow
Multiwindow allows you to split the screen in 2, 3 or 4 panes
you can switch an app back and forth between multiwindow mode and regular mode while it's running
NavBar:
- To switch between full screen and split View you can use the
NavBar Buttons
The app that currently has the focus (or the latest used app if you're on the Desktop) will be used for the main pane (left and/or top depending on the mode and rotation)
And it will lay the remaining most recently used apps in the rest of the available 1-2-3 panes depending on the icon you click
- If you press a multiwindow icon again when in splitview mode, it'll bring the focused app back to fullscreen mode.
- To swap the 2 latest focused apps location / pane , long press on the
NavBar Button
- To change focus simply Tap on the app or use the
NavBar Button
That button can also be used in non multiwindow mode to switch quickly between the 2 most recent apps.
Global Actions:
Actions to switch the app between fullscreen / splitview 2-3-4 panes, swap, or switch between the 2 most recent apps have been added
so you can bind them to a key / key combination with the Global KeyOverride or long press on navbar button too.
Note: Most apps works ok in splitview mode, but some of them might crash or not refresh correctly sometime.
To manually position an app in one of the pane:
For the moment either reorder your apps before clicking on an auto mode icon,
or you can also activate the default Marshmallow Multiwindow mode to get extra icons to positions an app in a specific pane (activate it in developer options )
Then position the apps with the icons from the Recents screen. (default MM recents icons are for 2 or 4 panes)
Banners
First
Many thanks, Tim, for keeping the Tf101 alive!
I'm a little afraid to try, but I know I will
Officially my Transformer is one of the oldest devices I own and should really show its age.
But it just doesn't, it sets itself apart from the two other Tegra 2 devices (Notion Ink Adam and Acer Iconia) by being a thoroughly enjoyable device, which reacts very promptly to all input and still is mechanically perfect with great battery life.
Some hardware ingredients like DRAM and Flash seem to be made of better stuff (some benchmark show twice the memory bandwidth than Acer Iconia and NI Adam and the eMMC is lots better than Acer (Adam is notoriously terrible)), but mostly it must be the constant tweaking you (and Google?) have put in, because the performance only got better and better, even if the applications typically got fatter and fatter and 1GB of DRAM is no longer as plenty as it used to be with Android 2.2.
I surely can't say the same for my Nexus 7, which started being somewhat snappier than the Transformer and turned out pretty bad with LP even after turning off the journalling on ext4.
Marshmallow has disappointed me so far (only Nexus 10 migrated yet), mostly because my standard launcher SPB shell 3D no longer works on it and I just like it better than stock or any other.
And then I just don't see any significant improvements beyond Lollipop or rather CM 12 with all the privacy stuff already included. And I just love the fast task switching, which is part of the multiwindow support and which I have on a keyboard shortcut (hope it comes soon).
Somehow I also doubt that Nougat will be better in any sense except "better" Google integration.
But since I'm very much afraid of operating anything without the latest security patches, I'll just have to make the switch.
And I'm sure it will be as perfect as the current LP by the time Nougat comes out.
Thanks Timduru for making it possible
Link is ready, downloading :good:
Thank you. what I've failed to understand, do you need to install a separate root tool? Or is it included in the recommended recovery tool? It's still as i bought it in 2011... Thanks!
Thanks so much Tim gonna test this out
cwouter said:
Thank you. what I've failed to understand, do you need to install a separate root tool? Or is it included in the recommended recovery tool? It's still as i bought it in 2011... Thanks!
Click to expand...
Click to collapse
Just follow the procedure from the 1st post:
once you have the recovery installed:
the first time: format /data
then install all 3 zips at once: rom + supersu + gapps
then reboot.
Thank you Tim! Awesome as always. Gonna try ASAP.
One question...
What is the downside of not having omx codecs working?
xbs said:
Thank you Tim! Awesome as always. Gonna try ASAP.
One question...
What is the downside of not having omx codecs working?
Click to expand...
Click to collapse
No omx codecs means no gpu video acceleration, so it'll use cpu to decode instead.
Wait a bit before trying, 019b is coming fixing the reboots with some apps
New Version #019b
New rom version available: KatKiss-6.0_019b.zip
ChangeLog:
TF101:
- Fix reboots caused by some apps(ES file explorer, play music, youtube...)
- Fix ExFat support
TF101 KatKernel 122:
- net: Handle 'sk' being NULL in UID-based routing
- add native ExFat FS support
timduru said:
Just follow the procedure from the 1st post:
once you have the recovery installed:
the first time: format /data
then install all 3 zips at once: rom + supersu + gapps
then reboot.
Click to expand...
Click to collapse
It sounds so easy... First I don't really know how to install the recovery (hence, i have been spending 'only' app 7 hours on topic by now). I would assume from PWR+VOL- then Vol+ goes to recovery mode, but the device gets stuck with a android red expression mark. I then tried to install the Easyflasher 0.8.3 and managed to first delete the drivers and installed new universal ones. Rebooted and continue to follow the procedure and the Easyflasher on my Windows tells me i have successfully unbricked my Asus Stock. However, when i reboot, it looks all exactly the same, no data lost, no new installation. Then I could, or should?, flash a recovery. However, if i try to do it from the Easyflasher there is only the old TWRP 2.2.1. available and i fail to make use of the downloaded TWRP 2.8.1.1. CLick the Root, doesn't work either.
Then, the frustration goes up and the progress goes down... please advise and push me in the right direction! MUch appreciated!
cwouter said:
It sounds so easy... First I don't really know how to install the recovery (hence, i have been spending 'only' app 7 hours on topic by now). I would assume from PWR+VOL- then Vol+ goes to recovery mode, but the device gets stuck with a android red expression mark. I then tried to install the Easyflasher 0.8.3 and managed to first delete the drivers and installed new universal ones. Rebooted and continue to follow the procedure and the Easyflasher on my Windows tells me i have successfully unbricked my Asus Stock. However, when i reboot, it looks all exactly the same, no data lost, no new installation. Then I could, or should?, flash a recovery. However, if i try to do it from the Easyflasher there is only the old TWRP 2.2.1. available and i fail to make use of the downloaded TWRP 2.8.1.1. CLick the Root, doesn't work either.
Then, the frustration goes up and the progress goes down... please advise and push me in the right direction! MUch appreciated!
Click to expand...
Click to collapse
Installing the recovery is not really the focus of this thread, and it has been a really long time since I installed on mine
But what I would do, since you seem to have easyflasher and drivers working:
- Install TWRP 2.2.1 from easyflasher
- reboot to that TWRP 2.2.1
- Install the TWRP 2.8.1.1 flashable zip from TWRP 2.2.1
- reboot to the recovery and it should now be TWRP 2.8.1.1
Flashed all 3 zip ROM+su+pico but can't boot to Android.
After the Asus logo screen turns black and nothing happens.
Any ideas?
xbs said:
Flashed all 3 zip ROM+su+pico but can't boot to Android.
After the Asus logo screen turns black and nothing happens.
Any ideas?
Click to expand...
Click to collapse
sounds as if the new kernel didn't flash or something.
What recovery are you using ?
Even if the screen goes black you should get adb working after a few minutes, it's still doing things in the background normally.
Try to grab me a logcat + dmesg at that point.
EDIT: Found the problem, yeah kernel not flashing:
Flash it separatly for the moment: Tim_KatKernel_122_MM6.0.zip
that will be fixed in the next version.
xbs said:
Flashed all 3 zip ROM+su+pico but can't boot to Android.
After the Asus logo screen turns black and nothing happens.
Any ideas?
Click to expand...
Click to collapse
Unfortunately me too.
The only step from install note was the "Format" because of lack of time and data cable to copy everything from internal sd to my pc (only way for me is over the air with My Phone Explorer right now).
Tried 19 & 19b together with SuperSu 2.52 and gapps-arm-pico in one flash.
Backlight of screen is on, but then nothing happens over an hour.
---------- Post added at 13:46 ---------- Previous post was at 13:45 ----------
timduru said:
sounds as if the new kernel didn't flash or something.
What recovery are you using ?
Even if the screen goes black you should get adb working after a few minutes, it's still doing things in the background normally.
Try to grab me a logcat + dmesg at that point.
EDIT: Found the problem, yeah kernel not flashing:
Flash it separated for the moment: Tim_KatKernel_122_MM6.0.zip
that will be fixed in the next version.
Click to expand...
Click to collapse
Will do immediately!
---------- Post added at 14:00 ---------- Previous post was at 13:46 ----------
Just booted fine, into MM
New Version #019c
New rom version available: KatKiss-6.0_019c.zip
ChangeLog:
TF101:
- Fix Kernel not being installed
timduru said:
Installing the recovery is not really the focus of this thread, and it has been a really long time since I installed on mine
But what I would do, since you seem to have easyflasher and drivers working:
- Install TWRP 2.2.1 from easyflasher
- reboot to that TWRP 2.2.1
- Install the TWRP 2.8.1.1 flashable zip from TWRP 2.2.1
- reboot to the recovery and it should now be TWRP 2.8.1.1
Click to expand...
Click to collapse
Sounds like a plan, i tried and Easyflasher tells me it runs Wheelie,NV Flash then 'finished new reboot into recovery'. I do so, but android gets stuck in the recovery with an red expression mark, then it'll boot normal again.
Might it be that root access is blocking it? The Easyflasher root access tells me to first falsh recovery and put the superuser on sd.
I have installed both TWRP and SuperSu but both run into issues: the first tells me 'root is required' then closes, the second tells me 'no SU binary installed' then closes.
I then decided to go for a very crappy 1-click root access, see http://forum.xda-developers.com/showthread.php?t=1689193, with an even worse http://www.4shared.com/postDownload/ja5cFLAL/1-Click_Transformer_Root_11.html. This seems to have succeeded and i got root access (!) and the above described issues on TWRP and SuperSu were not gone.
Then in TWRP i couldn't select the zipfile TWRP 2.8.1, and after telling TWRP i had a TF101 i could select an older version like 2.3, which he was going to download. I had to confirm a path but decided to abort. I then tried to boot recovery but unfortunately, and not as i expected, it run into the same red expression mark. I then decided to run APX mode again and see if easyflasher could access root now. Also negative. Then run normal ABD mode and checked if i could do something with SuperSu, also negative.
So it seems my problem is that TWRP doesn't allow me to select the right zip file and as a result i can't run any recovery... any idea?
UPDATE: going back to apx flash the default TWRP2.2.1 then reboot to recovery succeeds in Easyflasher but the same red expression mark with Android. so also negative
[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S7 Edge Stock to Android 13
[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S7 Edge (hero2lte Exynos SOC) Stock to Android 13 / LineageOS 20
Supported models
International & Canada:
- SM-G935F
- SM-G935FD
- SM-G935X
- SM-G935W8
Korea:
- SM-G935S
- SM-G935K
- SM-G935L
This detailed step-by-step guide helps you transform your Samsung Galaxy S7 Edge hero2lte to a powerful one with Android 13.
Make sure your phone is hero2lte/Exynos SOC before going further: in Android, go to Settings > About phone > Check Model number is listed above.
If not, quit this tutorial.
### READ THOSE WARNING COMMENTS
CHANGELOG
v5. Back to TWRP 3.6 (3.7 oversize)
v4. Android 13, TWRP 3.7
v3. BitGApps v1, Magisk 25.2
v2. Update TWRP, add adb to change screen definition, update download link
v1. Initial release for Android 12
1) DOWNLOAD
- djibe Galaxy S7 hero2lte pack: https://bit.ly/djibe-galaxys7edge-pack
(contains Samsung tweaked Odin 3.13.1 + Samsung USB drivers + TWRP 3.6.2_9-0 official recovery + Magisk Root + adb.exe). Unzip files.
+ ROM Unofficial LineageOS 20: https://forum.xda-developers.com/t/...ofing-ota-updates-for-s7-edge-exynos.4484511/
Download latest build: https://ivanmeler.github.io/devices/hero2lte.html
+ BiTGApps Package ARM64 13: https://github.com/BiTGApps/BiTGApps-Release/releases
OR NikGApps T Basic: https://sourceforge.net/projects/nikgapps/files/Canary-Releases/NikGapps-T/
OR MindTheGApps 13 ARM64: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
+ Charge phone to 100%
2) BACKUP DATA
Install Samsung USB drivers (you unzipped earlier).
Then plug phone to PC in File transfer mode.
Collect all .jpg or .mp4
Use Google built-in cloud to backup apps like SMS Backup & Restore to backup texts, contacts, etc.
Backup your WhatsApp messages in Google Drive.
Everything else: podcasts, Authenticators, TODOs etc...
Then copy the backup on your PC.
Make sure you have latest official updates for your phone:
Connect to Wifi and go to Settings > About device > Software update > Update now
### BACKUP NOW, you will lose everything.
3) FLASH TWRP 3.7 RECOVERY
Go to Settings > About phone> Software information.
Tap 7 times on Build number item to unlock Developer options.
Go to Settings > Developer options, switch OEM unlock ON and Confirm.
Shutdown phone.
Boot in Download Mode: hold Home + Power + Volume- until you see blue-green Warning screen and release buttons.
Confirm access to Download mode by pressing Volume+.
Phone now displays "Downloading..., Do not turn off target".
Connect phone in USB, wait for drivers installation.
Then launch Odin.exe (included in my archive) and wait for Odin indicator ID:COM to become blue.
In options: Verify re-partition and Auto Reboot are NOT ticked while F. Reset Time is ticked.
In AP > select twrp-3.6.2_9-0-hero2lte.img.tar
### Same recovery for Korean models (G930S/K/L variants)
### Warranty will be Void after next click ###
Click Start.
Wait until flash Success message appears.
Unplug phone.
Restart phone to recovery :
- hold Power + Home + Volume- until phone screen becomes black...
- and immediatly switch from Volume- to Volume+ (still holding Power + Home) and hold until Samsung's logo is displayed to land in TWRP recovery.
### If Android launches, hold 3 buttons until phone restarts and Samsung logo appears.
4) BACKUP IMEI PARTITION AND SYSTEM (Nandroid backup)
(Boot in Recovery Mode: Hold Home + Power + Volume+ until you see Samsung's logo then release and wait a few seconds for TWRP recovery to boot)
Recovery asks for Keep System Read Only ? > Swipe to Allow Modifications.
Go to Wipe > Format Data.
Type: yes and confirm with bottom right check icon.
Encryption is removed. You can now access partitions.
### If you miss this step you won't have access to any partition.
Back to home menu > Backup.
You can now select the partitions you want to save.
Select at least EFS partition to backup your IMEI. If a flash fails and partition is damaged you will still be able to restore this partition and use the phone.
If IMEI is lost during a flash, phone won't be able to reach cellphone networks.
I prefer to backup Boot, System, Baseband and EFS partitions. In case of problem, you will have your phone in its original state.
Swipe to Backup and wait during process.
Go to Home screen and continue with next chapter.
Save backup: still under TWRP recovery, connect phone to PC.
Go to Mount menu and check Data partition is checked and MTB button is on "Disable MTP" state.
From Windows explorer, access phones memory and copy-paste the TWRP folder (located in root folder, beside DCIM and Music folders) somewhere safe on your computer.
5) FORMAT PARTITIONS
### Make sure you copied TWRP backup from internal memory to somewhere safe.
Go to Wipe > Advanced wipe,
select Dalvik, Cache, System, Data, Internal Storage (if you really made a backup at step 2), then Swipe to Wipe.
Back to TWRP home screen, go to Reboot > Recovery and swipe to reboot.
On next launch, check the checkbox to remember choice and swipe to allow modifications.
6) FLASH ROM, (MAGISK ROOT) AND GAPPS
Back to TWRP main menu, go to Mount menu again to connect phone to PC again.
Connect phone to PC and use Windows explorer to copy files on phone's internal memory.
Copy TWRP folder from your phone to somewhere safe on PC.
This backup can restore your phone to its original Samsung state.
Copy files of ROM + BitGApps + Magisk on phone.
Go back to TWRP Home menu. Then tap on Install > choose lineage*.zip,
Optional for root: Add More zips > Magisk*.zip
then Swipe to confirm Flash.
Wait for operation to end.
Go to Reboot > Recovery and swipe to reboot.
After restart, go to Install, select bitgapps*.zip and swipe to flash.
Then tap Wipe cache/dalvik, swipe to confirm,
then Reboot System and on Install TWRP App? menu, tap on button Do Not Install
Wait for the phone to boot during 5 minutes.
7) ROOT ACCESS
Configure Android as you like.
Don't try to set fingerprints at first setup. It will crash.
No need for extra work to be root.
Magisk launches with Android.
Superuser permissions can be managed from Magisk Manager app.
8) TWEAKS
- Calibrate battery: https://www.ifixit.com/Wiki/Battery_Calibration
- Set dark Mode to improve battery by 30%
Settings > Display > Dark theme.
- For better battery, remove Always on display
Settings > Display > Lock screen > Ambient display
- Activate Developer options
Go to Settings > About.
At bottom, tap 7 times on Build number. You activated Developer options.
Go to Settings > System > Advanced > Developer options.
- Change screen definition for low GPU/CPU usage: from 1440x2560 to 1080x1920
You need developer options to enable USB debugging.
Open a terminal where adb.exe from my pack is located.
Plug phone and Authorize USB debugging.
Then type:
Code:
adb shell wm size 1080x1920 && adb shell wm density 400
// Defaults 1440x2560 and 504
- Screen sensitivity is too low ?
Try to recalibrate screen sensitivity with https://play.google.com/store/apps/details?id=touchcalibration.favoritappindia&hl=en&gl=US
Enjoy,
djibe
Thanks: @Ivan_Meler, LineageOS team, TWRP team, TopJohnWu
---------------------------------------
Coming from another ROM
- Backup
- Recovery: Wipe Cache, Dalvik cache, System and Format Data > yes
- Reboot recovery
- Flash rom
- Reboot recovery
- Flash BitGApps
Enjoy
Force Samsung Galaxy S7 restart
Hold Power + Volume down for 10-20 seconds
Thanks for the detailed instructions.
Please fix two minor typos: In the Odin instructions, the files should be hero2lte* not herolte*.
Re Magisk: 24.0, I suppose, should be used / upgraded to. (I've run into issues with 24.2 on another platform.)
steve8x8 said:
Thanks for the detailed instructions.
Please fix two minor typos: In the Odin instructions, the files should be hero2lte* not herolte*.
Re Magisk: 24.0, I suppose, should be used / upgraded to. (I've run into issues with 24.2 on another platform.)
Click to expand...
Click to collapse
Hi, you are correct and I'll fix glitch.
For Magisk, as you report bugs, I'll wait to move to 24.x. You can create an Issue here: https://github.com/topjohnwu/Magisk/issues
Thanks for sharing
I have a problemi instaled twrp format data and and instal rom after configuration rom when i rebooting to twrp data is encrypted. why ?
zulwik said:
I have a problemi instaled twrp format data and and instal rom after configuration rom when i rebooting to twrp data is encrypted. why ?
Click to expand...
Click to collapse
Hi, did you Format Data then Advanced Wipe > Format Cache, System ?
Then
Reboot to Recovery
Flash ROM
Reboot to recovery
Flash BitGapps
Reboot
I solved problem.
I installed older version TWRP with Odin and new version
hey @djibe89 & other XDA folks, thanks for these steps.
I have a SMG935W8 and currently borked on the BiTGApps step. All proceeded smoothly until there and now I'm seeing an error on TWRP and I'm not really sure how to resolve it.
It's complaining that the install config is not found and that it's an unsupported Android SDK version, which doesn't seem quite right.
Any tips would be highly appreciated
Judging from my deep dive, the current LineageOS 19.1 builds are SDK 32, and the BiTGapps builds only support up to 31... Definitely looking for tips, still.
Going to try this post's GApps
Hi, for now, stick to latest LOS 19 build: https://github.com/ivanmeler/ota_provider/releases/tag/herolte_lineage-19.0_1646935359, not 19.1
Or could you try NikGapps and tell us?
Thanks @djibe89 ! I went with NikGapps and that was a win.
It might be good to edit the top post to say 19.0 or have the NikGapps linked in it, for future readers.
Phone's working great. I appreciate it!
Bujiraso said:
Thanks @djibe89 ! I went with NikGapps and that was a win.
It might be good to edit the top post to say 19.0 or have the NikGapps linked in it, for future readers.
Phone's working great. I appreciate it!
Click to expand...
Click to collapse
Hi, I'll update it.
I hoped a newer BitGapps update would be released by now.
Enjoy, this phone is awesome
Hey again!
Been daily driving this for a bit and here's a laundry list of the issues I see, in no order at all.
I'm not sure if they're Lineage issues or artifacts of being an "unsupported" Lineage build.
1. The screen just stays on despite the power save settings (I've tried 15s, 30s, you name it) if I'm on the home screen. Trebuchet, is it?
It's like it has some keep alive function a la YouTube. It's not 100% but it seems far more than 50% of the time that I have to manually lock the device. Anyone know if I've just configured something wrong or if this is how the launcher is supposed to work?
2. Phone services will not stop demanding my location, no matter what I configure. It's every few minutes and it's creeping me out a ton. Why is it so nosey?
3. The call audio quality is still barely usable. While I *can* have intelligible business conversations when required, they suffer the quality noticeably and are terribly robotic and tinny. For personal calls, I tried to play it off once but immediately was laughed out of the call: they asked before even a "how are you" could pass if we could switch to VoIP since it was so comically bad. After some kind tips from Ivan I tried mucking with the mixer levels to no avail. They did seem a bit "low" compared to the 18.1/19.0 values, so I pumped them in a couple places (NB volume from 22 to 32, call default volume on 917 from 98 to 164 -- I have no clue what any of these mean). It might be louder now? It's not worth an A/B test to confirm what should be the expectation, but my point is that it didn't fix the robotic, tinny quality.
4. Banking app complains of the device being rooted, but it isn't. "Great." I hear the latest Zygisk might fix? I haven't tried yet.
Now, I'm still excited to be on 12L! I'm trying to buff my ability to dev on this ROM and fix up some of these issues, as I really don't think this phone needs to be replaced yet, but being stuck on stock Oreo isn't working either, so I say let's hack this thing till it's stable as stock!
Hi @Bujiraso , thanks for sharing.
Didn't use it on a daily basis
Have you tried another launcher ?
I think bank apps detect custom ROM, nothing can be done. Hope I'm wrong. Some genius of signature spoofing can pass this I believe. But I'm not.
djibe89 said:
- To tweak overclocking and more, use SmartPack-Kernel Manager
SmartPack-Kernel Manager - Apps on Google Play
The ultimate tool to manage your kernel
play.google.com
Enjoy,
djibe
Click to expand...
Click to collapse
We're sorry, the requested URL was not found on this server. New Link please.
SERGE4NT said:
We're sorry, the requested URL was not found on this server. New Link please.
Click to expand...
Click to collapse
Hi, you can try https://play.google.com/store/apps/details?id=com.performancetweaker.app or https://f-droid.org/repo/com.smartpack.kernelmanager_174.apk
hi, is it possible for the model number SM-G9350
Klein44 said:
hi, is it possible for the model number SM-G9350
Click to expand...
Click to collapse
Hi, sadly no.
9350 and 9300 have Snapdragon SOCs, not Exynos.
Only Android 8 ROMs: https://forum.xda-developers.com/f/samsung-galaxy-s7-edge-snapdragon-roms-kernels.5975/
Oh, ok. And is there any good custom rom for the SM-G9350 model?
Klein44 said:
Oh, ok. And is there any good custom rom for the SM-G9350 model?
Click to expand...
Click to collapse
Like you see here: https://forum.xda-developers.com/f/samsung-galaxy-s7-edge-snapdragon-roms-kernels.5975/
No.
This happens with Qualcomm proprietary SOCs
TELEGRAM CHANNEL ADDED: HERE
TELEGRAM CHAT GROUP: HERE
I normally build roms for Oneplus devices, but one of Xperia users donated and asked to build for Xperia XA2 Ultra. XA2 Ultra doesn't have a lot of options, so, here it is:
I have been building Android roms since 2012 for various devices including multiple Sonys, Lenovo Zuk, Oneplus 3, Oneplus 5, 6, 8 and 9. You can check my Oneplus 6 or Oneplus 6T or Oneplus 8 threads and browse my profile.
Jaguar rom is focused on hardening of AndroidOS and kernel. As such, the rom has hardened bionic, art, framework and tightened security.
1 Rom control with custom Power options, Statusbar, Buttons, Navbar, Quicksettings, Lockscreen, Notifications, Gestures, Themes etc...
2. Heavily modified Art, Bionic System/Vold and System/Security
3. Telephony response to Type Zero sms ('silently acknowledged') disabled
4. Toggle to disable Captive Portal logging.
5. Speakerphone proximity sensor toggle - could be set to automatically switch to speaker when not at the ear
6. IMEI and phone numbers hidden in About menu
7. Built-in encrypted DNS providers, such as: Cloudflare (US); LibreDns (Germany); AdguardDns (Cyprus); and PowerDns (Netherlands)
8. Wakelock and Alarmblocker
9. Fully working Call recording with the button visible in Dialer
10. Deskclock app modified to work with PowerOn alarm. The app will boot the phone 2 minutes before scheduled time to trigger the alarm on time
11. Default Dark mode
12. All regular customizations plus. You tell me which feature is missing.
The rom has 2 versions Vanilla (no Gapps) and Full. So, pick according to your needs.
Install instructions
Xperia AX2 Ultra is somewhat easier to deal with (because it doesn't have virtual partitions). So, the only requirement is to be on the latest stock firmware in both slots, and unlocked bootloader, of course. If you have been using Lineageos 18-19, you already have it. If not, install stock and then use Lineage's copy-partitions zip to populate another slot.
1. Either boot official TWRP and flash the rom followed by factory reset, or boot my recovery and sideload the rom also followed by factory reset.:
The command to boot recovery (from fastboot) is simple:
fastboot boot 'recovery name' (without quotes).
The first boot might take longer, because your phone will be encrypted.
2. Magisk: only versions 24.3 and higher will pass Safetynet. However, don't use TWRP, or any other recovery, because you won't boot. Rather install Magisk as a regular app, take boot.img I provide (the same as recovery), put it on your internal storage and patch from the app. Then install the new image (Magisk will tell you where it would save it) via fastboot: fastboot flash boot boot.img.
Download rom V20.2-VANILLA: Here
Download rom V20.2-FULL: Here
Download recovery (same as boot.img): Here
All subsequent releases will be in post #3.
XDAevDB Information
JAGUAR R, ROM for Sony Xperia AX2 Ultra
Contributors
optimumpro
Kernel Source Code (for now Lineage kernel): Here
ROM OS Version: 11.x R
ROM Kernel: Linux 4.x
ROM Firmware Required: no lower than Android 11 + unlocked bootloader
Based On: AOSP/Lineage/DirtyUnicorn/Crdroid
Version Information
Status: Stable
Current Stable Version: See post #3
Stable Release Date: 2021-01-26
Created: 2021-01-29
Updated: 2022-10-18
Credit: AOSP, Lineage, DU, Crdroid, GrapheneOS, CalyxOS
Why not Android 12? Because Google's major new releases don't become stable until at least r50+. Why? Ask Google. My view is: their primary focus is on advertising revenue, hence, everything else is on the back burner.
In addition, I personally dislike Android 12 (12L): you get some minor UI changes in exchange for giving up more privacy..
Screenshots: see Here
Magisk 25 and LSposed are loading now.
October 18. New release V025:
1. October security patches
2. Android r60
3. System webview to 106.x
4. Ability to disable screenshots saving: when disabled, screenshots are taken, but not saved
Native video still doesn't work and probably will never work due to the phone's low ram
Dirty flashing is fine on a previous release
Download rom V25 VANILLA: Here
Download rom V25 FULL: Here
September 13. New release V-24: major update
1. September security patches
2. Android r59
3.Ability to change clock size in statusbar and quicksettings
4. Rom is now compatible with Magisk 25 and Lsposed
5. AOD is fully working
6. DIaler: toggle for post-call snackbar
7. System webview to 105.x
Native gallery still cannot play videos and probably won't ever, as Jaguar takes more ram than Lineage: XA's 4GB of RAM is simply not enough. Use VLC player, which works fine.
Download rom V24-VANILLA: Here
Download rom V24-FULL: Here
August 21. New release V-23
1. August security patches
2. Android r58
3. Video playing may or may not be fixed (no longer have the device)
Dirty flashing is fine on a previous release
Download rom V-23 VANILLA: Here
Download rom V-23 FULL: Here
July 8. New release V-22
1. July security patches
2. Android r57
3. Automatic sleep/suspend mode (scheduled by a user) in Settings/Battery
4. 'Internet permission missing' issue with several apps fixed. Now, all apps including Googleplay, as well as third party apps, have no problems connecting to the internet (no F/C)
5. Many under the hood improvements
Dirty flashing on top of a previous release is fine. Otherwise, clean flash.
Download rom V-22 FULL: Here
Download rom V-22 VANILLA: Here
Does miracast work in this rom, and when mirroring could it black/turn off the screen. This is possible with the stock firmware and i hope that its also possible with the jaguar rom.
July 8. New release V-22
1. July security patches
2. Android r57
3. Automatic sleep/suspend mode (scheduled by a user) in Settings/Battery
4. 'Internet permission missing' issue with several apps fixed. Now, all apps including Googleplay, as well as third party apps, have no problems connecting to the internet (no F/C)
5. Many under the hood improvements
Download in post #3.
Newpipe does not work and possibly other videoplayback applications, doesn 't work in the browser . Only YouTube video plays. And could you integrate audio boost Ainur narsil, Viper or Sound Enhancement Sony Xperia 10 and then magisk is not needed
TheStormRanger said:
Newpipe does not work and possibly other videoplayback applications, doesn 't work in the browser . Only YouTube video plays. And could you integrate audio boost Ainur narsil, Viper or Sound Enhancement Sony Xperia 10 and then magisk is not needed
Click to expand...
Click to collapse
That's because you are using MicroG and you have NOT enabled 'signature spoofing' in Settings/Privacy. Most Google apps will NOT work with MicroG, unless signature spoofing is enabled.
optimumpro said:
That's because you are using MicroG and you have NOT enabled 'signature spoofing' in Settings/Privacy. Most Google apps will NOT work with MicroG, unless signature spoofing is enabled.
Click to expand...
Click to collapse
I am using the full version 22. Everything is already installed there. Changing the settings doesn't help. Newpipe and other software always work without Google services and MicroG. It's sad that not all software works. Your firmware is good, including Bluetooth and security tweaks
TheStormRanger said:
I am using the full version 22. Everything is already installed there. Changing the settings doesn't help. Newpipe and other software always work without Google services and MicroG. It's sad that not all software works. Your firmware is good, including Bluetooth and security tweaks
Click to expand...
Click to collapse
The same for me. Video playback doesn't work. I don't have microg installed. Even the video stored on the phone, or the video recorded with the camera doesn't work. Other than that, everything seems to be working great.
Sorry for my English...
My problem is cannot use Video Playing (From Facebook and other app)
If I play video , it show only black screen . How to fix it
[email protected] said:
Sorry for my English...
My problem is cannot use Video Playing (From Facebook and other app)
If I play video , it show only black screen . How to fix it
TheStormRanger said:
I am using the full version 22. Everything is already installed there. Changing the settings doesn't help. Newpipe and other software always work without Google services and MicroG. It's sad that not all software works. Your firmware is good, including Bluetooth and security tweaks
Click to expand...
Click to collapse
branja6 said:
The same for me. Video playback doesn't work. I don't have microg installed. Even the video stored on the phone, or the video recorded with the camera doesn't work. Other than that, everything seems to be working great.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
One of you would have to post a logcat running when you are trying to play videos.
optimumpro said:
One of you would have to post a logcat running when you are trying to play videos.
Click to expand...
Click to collapse
Ok, I installed a clean V22 full and a Newpipe app. And I attach the logcat. Newpipe works fine on the original firmware and Lineage and others
branja6 said:
The same for me. Video playback doesn't work. I don't have microg installed. Even the video stored on the phone, or the video recorded with the camera doesn't work. Other than that, everything seems to be working great.
Click to expand...
Click to collapse
So far the workaround to an extent is using VLC media player, so this may be some type of codec issue... Hopefully it can be resolved soon
August 21. New release V-23
1. August security patches
2. Android r58
3. Video playing may or may not be fixed (no longer have the device)
Download in post #3.
How long is the first load? I feel like it's been loading for a long time now. At least 10 minutes. Installed in twrp the latest version, was coming from stock 8. Didn't read I needed firmware 11+ until just now. Do I just wait for the phone battery to die and try again? I had planned on installing Magisk after boot, but at this point I'm not sure it is even going to boot.
rjdeleon said:
How long is the first load? I feel like it's been loading for a long time now. At least 10 minutes. Installed in twrp the latest version, was coming from stock 8. Didn't read I needed firmware 11+ until just now. Do I just wait for the phone battery to die and try again? I had planned on installing Magisk after boot, but at this point I'm not sure it is even going to boot.
Click to expand...
Click to collapse
You can always shutdown the phone by pressing 'power key' and 'volume up and down' together for 5-10 seconds.
TWRP doesn't flash well and certainly doesn't work when flashing Magisk (you'll get bootloop).
Don't use V23. Use V22. Get recovery from post #1 and flash it in fastboot like this:
fastboot flash boot_a boot.img
then
fastboot flash boot_b boot.img
Disconnect the phone and start it in recovery by pressing 'power button' and 'volume down' at the same time. Once in recovery, wipe system, then side load V22.
optimumpro said:
You can always shutdown the phone by pressing 'power key' and 'volume up and down' together for 5-10 seconds.
TWRP doesn't flash well and certainly doesn't work when flashing Magisk (you'll get bootloop).
Don't use V23. Use V22. Get recovery from post #1 and flash it in fastboot like this:
fastboot flash boot_a boot.img
then
fastboot flash boot_b boot.img
Disconnect the phone and start it in recovery by pressing 'power button' and 'volume down' at the same time. Once in recovery, wipe system, then side load V22.
Click to expand...
Click to collapse
Thank you, in recovery now about to sideload the V22, then I will reboot into the system and then reboot into recovery and sideload the V23 on top. Should I install Magisk before the V23? Or just go straight into V22 to V23? Again, thank you for responding.
rjdeleon said:
Thank you, in recovery now about to sideload the V22, then I will reboot into the system and then reboot into recovery and sideload the V23 on top. Should I install Magisk before the V23? Or just go straight into V22 to V23? Again, thank you for responding.
Click to expand...
Click to collapse
Don't use v23. I will post v24 tomorrow. I described how to apply Magisk in the OP.
ugh, unfortunately cannot sideload to it for some reason:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I am in ADB Sideload though so who knows, maybe I need to switch computers.
rjdeleon said:
ugh, unfortunately cannot sideload to it for some reason:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I am in ADB Sideload though so who knows, maybe I need to switch computers.
Click to expand...
Click to collapse
That means there is no connection between your phone and pc. May be adb drivers etc. Try to open the terminal as administrator.