yashsingh1/xdaforums huggingface dataset:
[Huawei Mate 20 X Questions & Answers] Linxy420:
So in emui 9 there is no ramdisk.img file so everyone says no root. I dont want to write 30 pages so ima make it short. I was wondering that since ramdisk.img files are intergrated into system.img i could extract these files and repack into a ramdisk.img file then patch boot image e.g ramdisk.img with magisk, then upack patched ramdisk.img into sub files like init.rc etc. And repack into the system.img and flash that? Will this cause issues with dm_verity.
[Huawei Mate 20 X Questions & Answers] Leechoonhwee:
I heard there's more mechanism built in right now into the rom package and the hardware to make sure that the rom size is not altered and the correct region is being flashed on. So to counter all these require additional files and counter flags to be set.

I remembered hikvision cctv also has this mechanism builtin but it can be overwritten via telnet and changing a flag in hex.

So I guess if someone looks hard enough, maybe we can have unlocked bootloader, root, etc until the next Mate 30 comes along in a year's time. :D
[Xperia Arc General] DroidArmy:
I decided to revive my old Sony Xperia Arc S using new ROMs and wanted to find out what all is working at present. (my phone was already running CM 11 for a long time). the camera was dead and the keys were a bit wonky but the phone was functional. I decided to try CM13 from this thread https://xdaforums.com/xperia-arc/development/dev-2011-unofficial-cyanogenmod-13-0-t3323975

after tinkering for sometime in my Windows 10 64bit it seems that the fastboot drivers don't work in windows 10 (also 8.1) as they are not signed and I didn't want to mess with my main windows install.

So I installed a windows 7 32 bit in a virtual machine (virtualbox), then installed flashtool drivers (selected options for xperia arc, flashtool drivers and fastboot drivers).

then downloaded the latest build of CM13. as the phone already had CM11 I booted into recovery and went into fastboot mode but for some reason I got an error saying 'not able to attach sony device to the virtual machine' or something like that. luckily opening virtualbox as administrator solved the problem and the phone was detected. followed the instructions in the CM13 thread - formatted a 32gb class 10 card (kingston) as ext4 for data partition using minitool partition wizard, then sideloaded the CM13 zip and HDPI gapps. rebooted to system but only CM logo was looping. tried different things but nothing worked. after I removed the card and used a different one (sandisk 32gb class 4 :( ) and repeated the install, it booted and worked.

as the phone was very slow with CM13 (mainly due to my slow card) I wanted to try if it can be flashed to the original gingerbread ROM. it was very difficult to search for the ROM as almost all links were just dead. my old backups came to the rescue. also for some reason the latest flashtool version in its homepage doesn't install a 32-bit version and also doesn't recognise the ICS firmware ftf file. so installed flashtool v0.9 that I found from my old backups. booted the phone in flash mode and flashed the gingerbread ROM. though it is outdated and not much features the phone was fast. after using it for sometime, flashed the ICS ROM. it also worked as expected. then rooted the phone using eroot (https://xdaforums.com/showthread.php?t=2219711). it also worked and SuperSU was installed in the ICS ROM.

now I came across the lineage 14.1 ROM in the CM13 thread and decided to give it a try. then found out that my option key is not working properly and was not able to enter fastboot mode. fortunately 'adb reboot bootloader' worked and the phone booted into fastboot. flashed the LOS14.1 boot.img and used the same microsd card that I used for CM13. followed similar instruction for the CM13 now using the TWRP recovery for LOS14.1. everything went well and phone booted up. the setup closed a couple of times but then eventually worked. calling, 3g data, wifi working in LOS14.1. as said above due to my slow card the phone is very very slow. I have ordered a sandisk class 10 32gb card. will test with that to see if it is better.

if anyone is looking for India ROM or the old flashtool, ask me I will attach/upload here.
[Xperia Arc General] ITomaz:
You can use tweaks to faster the phone

Set sdcard read ahead to 512/1024

Set cpu min to 368/460 MHz

Try it
[Xperia Arc General] rasoooli:
To Use FlashTools in Win10 & WIn 8.1 U Must disable the driver signature enforcement

This Guide

I'm Waiting For Your Phone Speed Test After Hi Speed SD Card
[Xperia Arc General] ITomaz:
I use Sa**disk class 10 8GB. The rom goes well, didn't good when running many apps in background like instagram or Facebook. Use lite version.

I try run Whatsapp and Spotify, they run well.

I switched to CM 11 since I bought Xperia z3 compact
[Xperia Arc General] DroidArmy:
just slightly better. not much speed improvement. I guess the limited RAM and outdated CPU are real bottlenecks here.
[Xperia Arc General] psxpetey:
heyif youve rooted this I was wondering if you could send me whatever is in the /sys/kernel file my phone wont initialize hdmi it keeps saying

error: cannot open /sys/kernel/hdmi_sii_kset/hdmi_sii_state_kobj/hdmi_sii_state_obj

so im thinking if I get that file my hdmi will work im on a stock rom , maybe cwm flashing doesnt keep this file however i cannot just repair the firmare as this is a debug phone with debug software according to this site : https://tthtlc.wordpress.com/2011/12/29/playing-with-ftrace-option-on-my-xperia-arc-s/ i should have the file in my sys/kernel so if you could send it to me id love you forever lol this has been driving me nuts
[ZTE Axon 7 Questions & Answers] dbekan%5:
Hi!

I bricked my axon7 g.. I had a running CM15.1 and wanted to restore a CM14.1 backup. First of all i downloaded and flashed the modem and bootloader for cm14.1. after that i wiped system and data and rebootet into recovery. Here I noticed a bug wich i already had when I updated to CM15.1: the data and system partition are unable to mount. So i download and installed a other recovery (nfound) and rebooted. And here is the Problem: I'm unable to go into the recovery.

After some hours of trying different methods I need your help. This is what I found out:

1) I can boot into FFBM and fastboot

2) when I boot into fastboot the windows device manager shwos me Android ADB Device

3) when i try to use the adb tool i says:

Search >>> interface found >>> Android ADB Interface

Checking ADB Interface:

Command execution adb devices >>> !!! Error !!! no answer from phone

This is becuase usb debugging was not enabled.

4) When i use the dfu tool and wnat to confirgure the ports it only says: this device has no usb ports or (when i turn of virus scanner and reboot..) "the tool is running"

Is there any way to flash a recovery?

Thank you!
[ZTE Axon 7 Questions & Answers] dbekan%5:
I solved it via fastboot and adb :)
[General Questions and Answers] rythan:
So my girlfriend recently asked me something that I have no clue about on messenger she said she gets 2 notification sounds the normal ding and sometimes the camera shutter sound effect will play well when I took a look into her notification sounds for her phone it was set as a phone number so I selected to change it but in the sound list it offered none were selected there was not a "more" option or anything so I'm lost on what was going on with that hopefully someone here can shed some light on the situation
[General Questions and Answers] ceelos218:
Sounds like some pervert hijacked her phone and is taking pictures of her. Uninstall and reinstall the app. Check the permissions
[Samsung Galaxy S9+ Questions & Answers] aaronisham95:
Hi everyone

I bought my att s9 a few months ago. And I believe it came with baseband version arf4. I've did a couple update packages / update. Zip. And long story story I've wound up stuck on g960usqu3arg2. I really wanted to get to ARIB OR ARI6. but I cannot get Odin to work. I don't really know where to find the right files to flash. I'd rather just keep using reboot to recovery method. Can anyone help me find a g960usqu3arg2 to (any more recent version) update.zip package
[Samsung Galaxy S9+ Questions & Answers] rmarinella:
You probably already found it. The S9 thread is here:

https://xdaforums.com/galaxy-s9
[Samsung Galaxy S9+ Questions & Answers] aaronisham95:
Yes. I am having issues though. Im not sure if its me using Odin wrong or what. When flashing. Do I have to have a USERDATA file selected?
[Asus Zenfone Max ROMs, Kernels, Recoveries, & Othe] REIGNZ3:
PixelExperience for Asus Zenfone Max [Z010D]

What is this?

Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)

Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device

Based on Android 8.1

Whats working?

Wifi

RIL

Mobile data

GPS

Camera

Flashlight

Camcorder

Bluetooth

FMRadio

Lights

Sound / vibration

Facelock

Known issues

EDL MODE

OFFLINE CHARGING

DON'T FLASH GAPPS, ALREADY INCLUDED

Download from here

Donate

Liked our work? Donate us to by a server!! Private message me for donation

[/url]

Translation

Help with project translation

Telegram channel

Stay tuned

​

Android OS version: 8.1

Security patch level: October 2018

Build author: blitzfire3

Source code: https://github.com/PixelExperience

ROM Developer: [https://xdaforums.com/member.php?u=6549853]blitzfire3[/url]

​

XDA:DevDB Information

Pixel Experience Z010D, ROM for the Asus Zenfone Max

Contributors

blitzfire3, shadowreaper1, sakilmondal, blitzfire3

Source Code: https://github.com/PixelExperience

ROM OS Version: 8.x Oreo

Based On: AOSP

Version Information

Status: Beta

Current Beta Version: PixelExperience

Beta Release Date: 2018-11-04

Created 2018-11-04

Last Updated 2018-11-04
[Google Pixel 3 XL Themes, Apps, and Mods] LXative:
Saw a few people show screenshots of their versions, but here is mine. And I've attached a full-res version just in case anyone wants to try it out. :cowboy:
[Google Pixel 3 XL Themes, Apps, and Mods] LXative:
With Zwart icons
[Google Pixel 3 XL Themes, Apps, and Mods] Zorachus:
Good idea, we need more wallpapers like this.
[Google Pixel 3 XL Themes, Apps, and Mods] LXative:
Green was a little much, did a few black themed.

Pretty easy to edit, if someone wants a variant of these just give me a sample color for the wallpaper and Android logo.
[Google Pixel 3 XL Themes, Apps, and Mods] LXative:
Screenshot with the Google logo Android and Tersus icon pack.
[MX Player] fede01_8:
I have to manually select it every time I play a video because I don't get any sound with HW
[Touch Dual, MDA Touch Plus General] tacia:
Hi,

We've been having the same problem on disabling XT9 and there were no solutions. Good thing I found this. And few people including me tried it and it really really works! so, i share this with you all.. Cheers! :D
[Touch Dual, MDA Touch Plus General] ronnylaborada:
I have tested this and it is confirmed working! Thanks.
[Touch Dual, MDA Touch Plus General] dtm203:
nothing new this was posted a few weeks back..
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sys01:
Hi everyone

As title shows, this is a WIP project

(I don't own the device, all builds are blind!)

What is EAS?

Energy Aware Scheduling (EAS) is an enhancement to Linux power management, unifying CPU power control under the Linux kernel. EAS extends the Linux kernel scheduler to make it fully aware of the power/performance capabilities of the CPUs in the system, to optimize energy consumption for advanced multi-core SoCs including big.LITTLE. With EAS, the Linux kernel will use the task load and a CPU ‘Energy Model’ to control task placement to select the optimal CPU to run on.

Google thinks, EAS is the way to go for the future. With this kernel you can get pixel (2) experience even before the pixel (2) is released.

Interesting links for further research:

https://www.xda-developers.com/google-pixel-fastest-android-phone-eas/

https://developer.arm.com/open-source/energy-aware-scheduling

Features

- Full EAS 1.3 implementation (based on EAS Project and LineageOS official kernel)

- Works on HMP ROMS too (you need to use sched/schedutil, HMP stuff are removed from kernel, otherwise you'll face freqs stuck at 100%)

- STune Boost for better battery and performance

- F2FS supported

- Tweaks and changes under the hood

Feel free to try and report your feedback (and logs too)

Download here

Installation

- Reboot to TWRP

- Backup your current boot.img

- Flash the kernel

- Reboot!

Sources here

Credits

[MENTION=5027381]OrdenKrieger[/MENTION]

[MENTION=5672995]jcadduono[/MENTION]

[MENTION=6745491]joshuous[/MENTION] (EAS Project)

And everyone worked for this device and LineageOS bring-up
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sys01:
Changelog

04/11

- Initial release

07/11

- Completely rebased over the latest CAF Oreo Tag (LA.UM.6.6, it *should* work on Pie, but not guaranteed!)

- 3.18.124

- Completely re-done EAS

- New LMK for better RAM managment

- Android upstream for AIO (check if MTP works better or worse than before)

- Better battery and performance
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sklaes:
EAS - Energy Aware Scheduling

WIP - Work in Progress

HMP - Heterogeneous Multi-Processing

HAL - Hardware abstraction layer

Do you plan to update the kernel on a regular base?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sys01:
When there are major changes to be applied - then yes

Otherwise makes no sense to push update with little to no changes at all

You tested it?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Gases:
Currently testing it on LOS16. Boots just fine, I'm charging the phone to 100% now to give it a go and I'll be back with some feedback tomorrow. So far everything I've tested works fine.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sklaes:
Not jet, but EAS sounds interesting

Update: installed - currently testing
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] AnonVendetta:
[MENTION=5825602]sys01[/MENTION]: You've said that it works on ROMs based on LineageOS. But does it work on ROMs that are based on AOSP? Is F2FS supported for data and cache partitions?

Thanks!

---------- Post added at 07:47 AM ---------- Previous post was at 07:46 AM ----------

[/COLOR [MENTION=5825602]sys01[/MENTION]: You've said that it works on ROMs based on LineageOS. But does it work on ROMs that are based on AOSP? Is F2FS supported for data and cache partitions?

Thanks!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
i use this now on dotos oreo with f2fs data.But on interactive the cpu freq stays on max,whatsup with this?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] AnonVendetta:
[MENTION=7288053]Predatorhaze[/MENTION]: So, you say this kernel works with F2FS data on DotOS Oreo? I literally just tried that a few days ago, but with Hellsgate/Schwifty kernels, no go. But maybe I'll try again now. Thanks for the heads up!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sys01:
This is an EAS kernel, you need to use sched/schedutil (interactive gov won't work anymore)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sys01:
F2FS is supported, I'll update the thread to explain that better
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
i have data in f2fs,and yes it boots and everything works till now.

Only is that dolby atmos dont work anymore,dont know why.On previous build with ext4 it worked.

I was confused because the freq on interactive,but already read a answer and that is due its eas kernel.

good we have eas now,i use helix engine also

if anyone got a working dolby atmos,pls let me know
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
ok.untill now everything seems stable.

can you set schedutil as default on next update? and you think about adding kcal feature (saturations etc) and some wakeblocks?

running on dotos 2.5 oreo,magisk 17.3,crimson kernel,f2fs data partition and los universal v2 bootstack
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ChrisFeiveel84:
an update to the current lineage OS kernel would be great since September has changed a lot on the go kernel

Your kernel works with AOSP Basis Rom

(have your kernel briefly tested with the havoc 2.0 Rom)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] levp:
Running this right now on LOS 15, for the entire day, without any issues that I can see. :good:

Used EX Kernel Manager to set governors.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Gases:
The kernel runs pretty well on Pie, but I think it's pretty aggressively throttled. Once the temp gets to 40°C the LITTLE cores get set to 960 MHz and the big cores to around the same. It's also kind of sluggish when the phone is taken out of deep sleep, and scrolling isn't that great. However, deep sleep works wonders. The discharge rate with screen off is ~0.3% per hour.

Oh, and it may just be me, but playing audio thtough the speakers makes the phone temp get pretty high, which again makes it get throttled and really slow.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sys01:
New version coming soon, hopefully this time around should be way more smooth and stable

Also, EAS takes time to make it perfect, but soon or later it will!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] wannaskoo:
Thank you for your work. This kernel is great and really shows the benefits of EAS on an older SOC like the S820. Sure, it needs polishing, but it's a great start :cool:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Gases:
For sure, not complaining at all! Just wanted to give some honest feedback in case you wanted to keep tweaking it :D
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nsane:
Thank you very much! Great work
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
i have read something here about dynamic stune boost https://xdaforums.com/u11/development/kernel-kirisakura-eas-0-7-energy-aware-t3647471

still not sure how to set it up

can you recommend something in op?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] yarecco:
Not working with HavocOS 8.1
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Penoro123:
Can't wait until get the EAS fully working and stable on our phones :D.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JTruj1ll0923:
Both links are broken on my end
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sys01:
Okay, this is a big update

Changelog

- Completely rebased over the latest CAF Oreo Tag (LA.UM.6.6, it *should* work on Pie, but not guaranteed!)

- 3.18.124

- Completely re-done EAS

- New LMK for better RAM managment

- Android upstream for AIO (check if MTP works better or worse than before)

- Better battery and performance

Download removed

As usual it's a blind build, let me know if it works or not
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] free_axon:
Havoc OS 2.0, clean over stock, f2fs Data and Cache.

Just booting to DFU.

The previous one booted fine.

Thanks for your work by the way
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Gases:
Same here, using LOS 16. I guess it's not compatible with Pie.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] troy5890:
Just flashed and it seems I couldn't reboot into the OS
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Gases:
Yeah, also tried flashing it on Oreo and got rebooted into DFU immediately.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sys01:
Sorry for the trouble guys, I will investigate once I come back home!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
Can we dirty flash over previous build

---------- Post added at 11:00 AM ---------- Previous post was at 10:57 AM ----------

Can you guys mention on what system you try to boot?! I use Oreo and never ever a pie gsi
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sys01:
I've completely re-done everything making it all clean

Hope boot this time around

Download
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] troy5890:
Everything boots up and is running great. Thanks for the fix
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Gases:
Installed this version on LOS 15.1. It runs way better than the previous version, the phone stays nice and cool (haven't seen it go above 40°C. It's also way smoother than the last time. Haven't had the chance to charge fully so I can talk about the battery life, but I'll do that tomorrow. Thank you so much!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sys01:
Really glad to see my stuff work as they should! Can you please check deepsleep also? And can you send here a screenshot of kernel version?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Dodgexander:
Works great so far for me. It's not as snappy as usual but if this is all for more battery it's worth it.

Havoc pie GSI using vendor partition from dotos.

A feature request would be to add external storage support for exFAT and or NTFS filesystems.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
Deep sleep bad here in dotos.Maybe caused by helix engine and add on.

I try now with other mod(NFS)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ChrisFeiveel84:
Havoc Pie GSI

And los Vendor

:good:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EwertonR19:
I'm on AEX 5.8 Treble with the F2FS partition. Can I flash your kernel normally and after that Wipe Dalvik / cache?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sys01:
Just flash it

You don't need to wipe dalvik / cache
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ibphantom:
Really laggy on scrolling. Snapchat takes fooooorreeeevvvveeerrr to load. I changed the big cores to performance but no change. I'm on AOKP latest nightly.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
only schedutil gov is supported,and you need rom that support eas
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] frodoswaggins:
Do you think I could get this to work with the k88/Trek 2?

http://phonedb.net/index.php?m=device&id=10513&c=zte_trek_2_hd_lte_k88

As in compile the kernel for it?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
Can you create a telegram group for discus about this kernel?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
Download gone...what happened?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sys01:
Fixed
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Infy_AsiX:
Hi sys01, thanks for the nice work. I've only just started using a compatible ROM and I"m really glad to have your work. I've seen comments from a few weeks ago about the small cores being locked to max frequency while the screen is touched on LOS15.1 device tree sources. I confirmed it by testing it today. However I'm pleased to notice your kernel's schedutil doesn't suffer the issue. I found the performance a little lacking compared to stock interactive and I prefer to tune for fast smooth performance without being too inefficient. With some testing I discovered using EX Kernel Manager I can simply set CPU Boost Settings, /dev/stune/top-app/schedtune.boost 33 giving me high performance.

To anyone curious on having a little more performance they could put 11, 17, 22 or 27 as fractions of my preference. I'd guess at least some setting increase is required to at least match stock interactive performance. Also try overlaying CPU frequencies and turn on Profile GPU Rendering in your favourite laggy media heavy scrolling app. There's a quick settings developer tiles for it near the top of developer settings. Use that to compare your other stock performance and using stune to choose your desired performance/battery trade off.

For me some missing wish list stand out features are Hotplugging, KCAL, Skrem's CAD audio mod and Adrenoboost. That'd be a dream, regardless it's an already worthwhile impressive kernel.

edit note: schedtune.boost 33 runs a little hotter than my old setup. I think 25 is a good compromise. Also ROM thermal throttling will need to be edited to maximise performance