Develop Bugs

[ROM][LINARO][01/10/13]SentinelROM v5.00-CM10.2 Source- Fast, Stable, Battery[GPL]

{
"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"
}
Welcome to SentinelROM for HTC One X (endeavoru - Tegra 3 Only). Compiled with the Linaro toolchain from modded CM10.2 source. Android 4.3
This is one of the most popular ROMs for Nexus 10 and Nexus 7, and after a month of hard work and optimisation, I am happy to release it for HTC One X.
This ROM is compiled from CyanogenMod 10.1 with all the features you get in a CM10.2 ROM, plus the following features.
Compiled with the Linaro toolchain for extreme performance.
Zip Aligned
Compiled from latest CyanogenMod 10.2 source by me, not a 'cooked ROM'.
OTA Updates supported
Improved Web Browsing performance
Improved 3D gaming performance
Amazing battery life
Additional theming and UI customisation
FAST support via this page and our Facebook Page
A free copy of my music player app
________________________
This ROM has been built to enhance the CyanogenMod 10.2 experience, with faster gaming and web browsing performance (no choppyness in Chrome too!).
Countless hours have been spent making tweaks to settings to squeeze the most performance I can find out of this ROM while still providing excellent battery life and without the dangers of overclocking and kernel level tweaking.
I compile this ROM and Kernel from the latest CyanogenMod source code, add my various tweaks and adjustments, then test for stability, so you get all the benefits of CyanogenMod 10.2, plus my tweaks and extras, all without the instability and inconvenience of flashing CyanogenMod nightlies (which are not designed specifically for the HTC One X like my ROM is.
The kernel source is available from the CyanogenMod's GitHub.
Requires HBOOT 1.29 or newer.
________________________
________________________
*Some users have reported ADB via USB not working. It's not actually a bug, but a difference in the way ADB works and the drivers required for CM vs SENSE based ROMS... If this is you, follow these steps to get ADB working..
Plug your phone in to your pc.
Open up device manager (Right click computer -> Manage -> Device Manager)
Find your phone in the list.
Mine was initially under 'Other Devices' labeled as 'One'
Right click -> Update Driver Software...
Select 'Browse my computer for driver software'
Select 'Let me pick from a list of device drivers on my computer'
Make sure to uncheck 'Show compatible hardware'
Select 'Android Phone' then 'Next'
Select 'Google, Inc' on the left pane and 'Android ADB Interface' on the right pane. Hit Next
Hit 'OK' if there was a warning.
To test if ADB is working, launch a CMD prompt and type 'adb devices'
You should now see you phone in the list!!
p.s. mounting your sdcard should also work.
Click to expand...
Click to collapse
________________________
If installing for the first time:
To install this ROM you will need to have an unlocked bootloader and a custom Recovery such as TWRP or ClockWorkMod installed (personally I recommend TWRP, I have had issues with restoring backups using CWM).
Copy the downloaded SentinelROM zip to your Internal Storage.
Boot into your custom recovery
Back up your stock ROM
[*]Boot into bootloader (power + Vol down) and enter Fastboot mode
[*]Extract boot.img from ROM zip and flash via fastboot [fastboot flash boot boot.img] (there are heaps of guides on how to do this)
Enter custom recovery
Factory Reset and wipe Cache and Dalvik Cache
Wipe System partition
Install the ROM
Install GAPPS package
Reboot - the first boot can take up to 5 minutes
Important: After installation you will be asked if you want to turn on CyanogenMod Statistics, please leave it off as this is an unofficial/modified build.
Note: Use of titanium backup to restore apps and data from another ROM is not recommended, and is the source of 90% of user issues, especially when it comes to battery life. Do so at your own risk.
You may flash other kernels as you wish via recovery. Remember to also flash the correct libraries for any 3rd party kernels. Instructions will be given by the Kernel author. NOTE: Updating the ROM via OTA will also overwrite any custom Kernels you have installed.
________________________
Please visit my FAQ's page before asking questions in the thread. Chances are the answer is already there! I'm always happy to help out with any other questions.
________________________
Thanks very much to all those who have answered my questions through the process of creating my own ROM, you know who you are.
CyanogenMod for their outstanding work. Full credit to them for the bulk of this ROM.
OTA-UpdateCenter.pro for their OTA database support and OTA Updater app source.
________________________
NOTE: Unless otherwise stated, the following mods are developed by SentinelROM users and therefore I can only offer limited support for problems caused by using them.
Clock and status bar mods - Use these for transparent status bar and centre clock, etc - Thanks to "peetu20"
________________________
02/10/13:
SentinelROM v5.00 - See Changelog for details.
NOTE: Remember to update your boot.img via fastboot.
Choose from an increasing range of Premium Themes for SentinelROM here.
Please don't forget to hit the Thanks button too
GAPPS
http://goo.im/gapps >Check the latest package available on top
MD5Sum: check the md5 of the files before flashing it
________________________
I hope you enjoy my ROM. If you do, plase consider a donation to the CyanogenMod team. If you really like my build, please consider a donation to me as well. Donations go towards flowers for my wife so she lets me keep developing!

New development, announcements and pipeline work will be posted on our Facebook page, so be sure to 'like' us if you like SentinelROM
02/10/2013:-
v5.00 -
*ROM rebuilt completely from scratch
*Compiled with new Linaro toolchain v4.8 for a further performance boost.
*Updated to latest CM10.2 source (Android 4.3)
*Adds all the latest CM features.
NOTE: A Full wipe is highly recommended as this is a new ROM base.
NOTE: You must install the latest Android 4.3 GAPPS Package after flashing the ROM.
YOU MUST FLASH BOOT.IMG VIA FASTBOOT.
20/06/2013:-
v4.75 -
*Compiled with new Linaro toolchain v4.8 for a further performance boost.
*Updated to latest Mali graphics drivers for improved performance and stability.
*Updated to latest CM10.1 source (Android 4.2.2)
[NOTE: You must wipe your System and Dalvik caches after upgrading. GAPPS Must be re-installed after updating. Please view the instructions here.
YOU MUST FLASH BOOT.IMG VIA FASTBOOT.
25/05/2013:-
v4.60 -
*Compiled with Linaro toolchain for a huge performance boost.
*Updated to latest Mali graphics drivers for improved performance and stability.
*Updated to latest CM10.1 source (Android 4.2.2)
*Fixes to Camera
*Fixes to Apollo
*Fixes to Clock
[NOTE: You must wipe your System and Dalvik caches after upgrading. GAPPS Must be re-installed after updating. Please view the instructions here.
YOU MUST FLASH BOOT.IMG VIA FASTBOOT.
19/05/2013:-
v4.50 -
*Compiled with Linaro toolchain for a huge performance boost.
*Updated to latest CM10.1 source (Android 4.2.2)
*Kernel and ROM tweaks for improved performance
*Improved Camera
*Updated Launcher
*Increased notifications volume
[NOTE: A clean installation is required for this update. please view the instructions here.
YOU MUST FLASH BOOT.IMG VIA FASTBOOT.
04/05/2013:-
4.40 -
*Camera Fixed.
*Voice activated Camera Shutter option
*Added new LMT pie controls – developed in collaboration with noname81.
(for instructions on how to get started with LMT Pie Controls, visit noname81′s thread and watch the video below).
*Fixed video playback issues and freezes
*Additional tweaks for increased performance and battery life
YOU MUST FLASH BOOT.IMG VIA FASTBOOT.
IMPORTANT: While this update will run with the existing v4.20 kernel. I strongly suggest you extract the boot.img from the rom zip and flash it via fastboot. This applies when updating via OTA also.
NOTE: You may need to reflash GAPPS after the update if some apps are missing.
20/4/2013:-
v4.30 -
*Tweaks and improvements to performance.
*Improve Wi-Fi signal strength.
*Addresses any issues with SystemUI memory leaks.
IMPORTANT: While this update will run with the existing v4.20 kernel. I strongly suggest you extract the boot.img from the rom zip and flash it via fastboot. This applies when updating via OTA also.
NOTE: You may need to reflash GAPPS after the update if some apps are missing.
14/4/2013:-
v4.20 -
*Initial Release for HTC One X
Click to expand...
Click to collapse

Overview Video showcasing some features, general performance and gaming in NFS Most Wanted.
Here's a video proving the extreme battery life.
ROM review by Flow:
A run through of the various settings and configurations.

Nice to see another ROM!

What languages are supported?
...and how do I get the weather forecast, like the one in your first screenshot?

Sounds great! Gotta put it to the test.

thanks for your work
this rom build source same http://forum.xda-developers.com/showthread.php?t=2203331 ?

Hi tc, for some reason all aosp based roms are in original android development, I think you should consider moving your rom there
Thanks for your work
Sent from my HTC One X using Tapatalk 2

This ROM isn't AOSP based. It's CM10.1 based.

nice!:good:

codexc said:
thanks for your work
this rom build source same http://forum.xda-developers.com/showthread.php?t=2203331 ?
Click to expand...
Click to collapse
Will check it then... Does the capacitive buttons is always on ?
Sent from my HTC One X using xda premium

If you turn on "Sweep2Wake" under settings, they stay active when the screen is off, otherwise they turn off when the screen is off.

Sentinel196 said:
If you turn on "Sweep2Wake" under settings, they stay active when the screen is off, otherwise they turn off when the screen is off.
Click to expand...
Click to collapse
That's not what I meant. . . If you used sense based roms you can see that the capacitive buttons are accommodating according to the lighting condition around you... Turns off in bright light and turns on in dark areas...
Ps: this behavior is only working on ICJ by LorD ClockaN not any other aosp or cm10.1 based rom even the official one.
I had a talk with seadersn in his rom thread but I couldn't solve it.
That's what I meant.
Sent from my HTC One X using xda premium

Oh right! Sorry, I misunderstood.
No, they don't automatically light up in dark conditions. they light up as soon as you touch them. You can also choose to have them off all the time, or light up with notifications.

Sentinel196 said:
Oh right! Sorry, I misunderstood.
No, they don't automatically light up in dark conditions. they light up as soon as you touch them. You can also choose to have them off all the time, or light up with notifications.
Click to expand...
Click to collapse
Yes that's I know but I don't like the rule of all or none... But I hope you could check that... may be you can help solve this issue for all the users of cm10.1 and FYI it's not kernel related.
Sent from my HTC One X using xda premium

I can certainly take a look at it for the next build.

Sentinel196 said:
I can certainly take a look at it for the next build.
Click to expand...
Click to collapse
Thanks
Sent from my HTC One X using xda premium

I haven't used your ROM for nexus10.I just try it on my hox.It's very very fast. Thank you mate.

You're welcome. I'm just uploading an overview video onto YouTube now so you guys can try before you buy. I'll post it here as soon as it's uploaded, which will be about 2 hours (I always encode in Full HD).

Sentinel196 said:
You're welcome. I'm just uploading an overview video onto YouTube now so you guys can try before you buy. I'll post it here as soon as it's uploaded, which will be about 2 hours (I always encode in Full HD).
Click to expand...
Click to collapse
F5 F5 F5 refreshing and waiting
Sent from my HTC One X using xda premium

[DEV][KERNEL][CAF] The future of Nozomi kernels - BETA Stage!

{
"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"
}
Hi all!
After all the mess I had while testing MR2 on our Xperia S using the legacy video drivers, I decided it's time to get us a proper base on which all future Nozomi developments can be based. I want this to be a community project, so I'd like to encourage any available developer to contribute, and of course we also need testers to get proper bug reports, logcats, kernel logs. If these sound familiar to you, and you know what you're doing, you might be the person we are looking for!
Before you start reading the following, let me be very clear about one point here:
Never underestimate the power of open source.​
The Xperia S (Codename Nozomi) is based on the Sony Fuji board which itself is based on the Qualcomm msm8660 (8260) platform, which features a Snapdragon S3 CPU chip and together with the Adreno 220 GPU and the integrated tavarua radio forms the SoC.
As of MR1/Android 4.2.X, the msm8660 chipset is officially abandoned by Qualcomm. This means: No official support from CAF for our chipset anymore, which, on a further note, means that we have to adapt >=msm8960 drivers to match the >=MR1 userspace grahpics drivers.
Related to the msm8660 ASoC, we are using MDP 4.1 compatible hardware, whereas recent CAF kernel branches focus on >=MDP 4.2 support for newer chipsets.
Paying attention at the driver merge in the kernel should be top priority, in combination with excessive debugging and hard work, we can achieve a better running system than some other 'officially' supported devices on MR1/MR2, like the Xperia T (msm8960).
Long story short, here is the current progress on my current CAF based kernel:
What is (basically) working:
msm_fb - framebuffer (upgraded to match MR2, sync point support)
msm_vidc - video encoding/decoding drivers (upgraded to match MR2, 1080p support)
msm_rotator - image rotator (upgraded to match MR2, sync point support, fast YUV not yet enabled for msm8660)
msm_kgsl - KGSL driver (upgraded to match MR2 (jb_2.5))
msm_gpu/adreno driver (upgraded to match MR2 (jb_2.5))
msm_iommu - page mapping (upgraded to match MR2 (jb_2.5))
msm_qdsp6v2 (upgraded to match MR2 (jb_2.5))
sound/soc (upgraded to match MR2 (jb_2.5))
What needs to be tested:
ION memory allocation (upgraded to match MR1 (mako) - unsure if it needs to be patched)
What definately needs to be worked on:
msm_fb fence syncing - causes massive lags
..? - Soft reboots when browsing Gallery
Now coming to the resources that I (preferably) use to upgrade our kernel, there are various kernel sources that don't quite match each other's APIs, so please pay special attention when contributing:
1) Samsung Galaxy SII (Skyrocket Board, msm8660): GitHub reference
2) Sony Xperia T (Blue board, msm8960): GitHub reference
3) More to come...
If you take a look at my kernel source, you can easily see the first thing I did was bringin up our kernel space video drivers to jb_mr1_chocolate. Despite being compatible to Android 4.2.X, (and the best branch to do the dirty bringup, because chocolate branches are meant for stabilization) there are a few crucial things to watch out for:
#1 - Do not mess with the ION allocation API unless you really want to change the API kernel-wide. By default, jb_mr1_chocolate uses a different ION api than our mako-based ION and IOMMU drivers. If you just blindly merge LK 3.0.y sources into our LK 3.4.y branches, be prepared to end up having various page mapping/allocation faults.
#2 - Watch out for mdp/rotator IOMMU split changes. In all our current kernels, we use IOMMU domain splitting to gain finer granularity which is needed for secure playback. A very good example on what to look out for is a commit I made recently to patch jb_mr1_chocolate video drivers to use the domain splitting technique again: https://github.com/OpenSEMC/android_kernel_sony_msm8x60/commit/4fed72fb2e12d16df1d137247c63b45477bad624https://github.com/OpenSEMC/android_kernel_sony_msm8x60/commit/4fed72fb2e12d16df1d137247c63b45477bad624
#3 - Watch out for buffer mapping changes (display_iova). As shown in the commit above, jb_mr1_chocolate by default uses diferent code to map framebuffer memory than our LK 3.4.y kernel does.
You can find my current kernel sources at OpenSEMC's GitHub repository:
ALPHA ---GitHub
BETA ---GitHub
I am actively contributing to and mainting this branch. The final goal is to have a kernel that matches the requirements of the latest Android iteration available. It'll be a long way until we reach that goal, but I am sure we can do it.
XDA:DevDB Information
CAF kernel for Fuji boards, a Kernel for the Sony Xperia S
Contributors
RaymanFX
Kernel Special Features:
Version Information
Status: Beta
Created 2013-09-27
Last Updated 2013-10-03

PROGRESS!
[09/28/2013] It boots! Graphic drivers are quite stable, no random reboots. Switching the project over to BETA stage.
[09/30/2013] Succesfully backported msm_vidc and KGSL/Adreno driver from jb_2.5!
[10/02/2013] Upgraded KGSL/Adreno driver to jb_2.6
[10/02/2013] Modified msm_rotator to improve the compability to our video drivers
[10/03/2013] Merged CAF's jb_2.5 sources into our kernel
[10/03/2013] Upgraded sound/soc and qdsp6v2 to jb_2.5
[10/03/2013] Upgraded msm_iommu to jb_2.5
[10/03/2013] Imported UHID driver from Linux 3.8

I'm not a dev,but i'm really happy about the caf, long live this project.
Sent from my LT26ii using XDA Premium 4 mobile app

Awesome! This could be a huge thing, I'll certainly keep an eye on it, sign me up for some testing!

More kernels are always good.

it must be a great job !

@RaymanFX Good Work! Bro.. Looking forward in your Sources.
---------- Post added at 09:37 AM ---------- Previous post was at 09:11 AM ----------
[/COLOR @RaymanFX recommended to add this At XDA News. Thanks.

TrinityHaxxorX said:
@RaymanFX Good Work! Bro.. Looking forward in your Sources.
---------- Post added at 09:37 AM ---------- Previous post was at 09:11 AM ----------
[/COLOR @RaymanFX recommended to add this At XDA News. Thanks.
Click to expand...
Click to collapse
Yeah.. Good work on the recommendation bro.. This is really worth it.. :good:

We reached BETA stage!
I managed to get a cm-10.2 rom with latest CAF display drivers booting!
There are some issues to be fixed, e.g. some minor animation stuttering (probably related to fence syncing) and broken video playback (easy), but this project advances way quicker than I expected it to.
I updated the source links and fixed all compilation errors. You can now build the project yourself
A public beta test version should be out soon!

RaymanFX said:
We reached BETA stage!
I managed to get a cm-10.2 rom with latest CAF display drivers booting!
There are some issues to be fixed, e.g. some minor animation stuttering (probably related to fence syncing) and broken video playback (easy), but this project advances way quicker than I expected it to.
I updated the source links and fixed all compilation errors. You can now build the project yourself
A public beta test version should be out soon!
Click to expand...
Click to collapse
Gooodjob! .
Sent from my LT26ii using xda app-developers app

OMG A GOOD 4.3 GOING TO BE OUT SOON!!!
Sent from my LT26ii using XDA Premium 4 mobile app

Great work, looking forward to it.
Sent from my Xperia SL

RaymanFX said:
We reached BETA stage!
I managed to get a cm-10.2 rom with latest CAF display drivers booting!
There are some issues to be fixed, e.g. some minor animation stuttering (probably related to fence syncing) and broken video playback (easy), but this project advances way quicker than I expected it to.
I updated the source links and fixed all compilation errors. You can now build the project yourself
A public beta test version should be out soon!
Click to expand...
Click to collapse
You are truely a ninja my friend.

Update from today:
* Backported VIDC, IOMMU, ION and KGSL from jb_2.5, so we're on par with recent high-end devices.
This will also save us the hassle of the untested ION/IOMMU stuff (which is on a MR1 level currently anyways.
Additionally, it will bring us proper graphics drivers (atleast I hope so, I did some early testing with GTA III, and it played just fine).
The new msm_vidc encoder/decoder drivers will also allow us to use CAF OMX libraries instead of mako ones which were patched to work with the CAF display drivers.
The next patches will also bring back Bluetooth keyboard support for Jellybean (UHID was needed).
Things are getting proper !

RaymanFX said:
I updated the source links and fixed all compilation errors. You can now build the project yourself
Click to expand...
Click to collapse
I tried and indeed the ROM builds without errors. I can flash it and recovery seems to be working.
But it will not boot. After the "OpenSEMC" boot splash there is no CM-bootlogo and a black screen forever.
I used "cm-10.2" manifest and changed kernel to "jb_mr2_chocolate_beta" prior on sync.

DeJe63 said:
I tried and indeed the ROM builds without errors. I can flash it and recovery seems to be working.
But it will not boot. After the "OpenSEMC" boot splash there is no CM-bootlogo and a black screen forever.
I used "cm-10.2" manifest and changed kernel to "jb_mr2_chocolate_beta" prior on sync.
Click to expand...
Click to collapse
It Just Mean it use dif.. Display drivers. that happens with me before.

TrinityHaxxorX said:
It Just Mean it use dif.. Display drivers. that happens with me before.
Click to expand...
Click to collapse
Well, what are these mysterious dif. display drivers? Do you have a solution or just say it isn't possible to build bootable ROM with current cm-10.2?

DeJe63 said:
Well, what are these mysterious dif. display drivers? Do you have a solution or just say it isn't possible to build bootable ROM with current cm-10.2?
Click to expand...
Click to collapse
Different display drivers?

To a man still learning, if it doesn't say exactly what is meant, then it doesn't mean that.
A lot of words start with dif...
And yes, it is possible to build a bootable ROM. Check the CM10.1 thread, somebody shared his build there.

DeJe63 said:
I tried and indeed the ROM builds without errors. I can flash it and recovery seems to be working.
But it will not boot. After the "OpenSEMC" boot splash there is no CM-bootlogo and a black screen forever.
I used "cm-10.2" manifest and changed kernel to "jb_mr2_chocolate_beta" prior on sync.
Click to expand...
Click to collapse
I havent checked myself but maybe use hardware/qcom/display-caf and audio-caf from cyanogenmod?
Sent from my LG-D802 using xda app-developers app

SNAPPATCH - STOCK OPTIMIZATION PROJECT

WELCOME TO THE SNAPPATCH​[ Featured by DroidViews and XDA ]​
{
"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"
}
SOME THINGS ARE DIFFERENT TO THE AOSP SNAPPATCH
PLEASE MAKE SURE YOU ARE USING THE RIGHT VERSION FOR YOUR DEVICE / ANDROID OS VERSION AND VARIANT​
ABOUT THE PROJECT​Started on the Nexus 6, Years ago is the Patch the Result of evolving custom ROMs to something more. Instead of uploading My Changes combined with a OS, is the POM just delivering the wanted Edits. It can be applied on top of any OS, and makes Android Updates independently from My Work. The latest and already 5th Revision of the POM is called Snappatch, and made for Snapdragon Xperia Devices running the very latest AOSP Systems. Coming with a huge amount of exclusive Configs and Optimizations is the Patch unleashing Your Device on a unexpected Way. You will raise the Performance, Efficiency, and Quality of the whole System, besides adding Features and Services which are not available on unpatched AOSP ROMs. The POM comes also with a Rooting Solution, Busybox and the full set of needed GApps to provide a great Pixel like Experience with the barely minimum of needed Apps out of the Box. Based on 8 Years of research and testing, made with Passion! The Snappatch sets Quality over Quantity...
Already adapted by Others for Stock Firmwares is the Snappatch still the first and Original Patch System. You will face it all over XDA in the next Years! Be Part of the Patch Revolution, get Patched!​
FEATURES
Xperia DRM Fix and Kernels included
Xperia Apps cleaned out and replaced
Night Light and Ambient Display Settings
Latest Busybox with 400+ Applets (Excluded on Stock)
Magisk Stable Root included
SafetyNet Passing Changes
Pixel Bootanimation / Apps
Xperia and Pixel UI Sounds
Added advanced VR Capabilities
Added Features and Services
Optimized Google Apps Set
Optimized Camera Handling
Optimized Display Handling
Optimized Rendering Handling
Optimized Storage Handling
Optimized Services Handling
Optimized Multitasking Handling
Optimized Audio Handling
Optimized Microphone Handling
Optimized 4K & HDR Handling
Optimized Hardware Handling
Optimized Software Handling
(Features are summarized to keep the overview)
(Don't trust Lists, try it out by Yourself)
SUMMARY OF THE DEVELOPMENT
-Camera Configs can be still improved (Implented not all Configs right yet)
-Some Camera Apps may not Work. Recommended are:
--Snap Camera HDR (Play Store)
--Open Camera (Included / Play Store)
--Google Camera Mods (Some are working, others don't)
-Some Equalizers don't Process (Audio is routed different)
SUPPORTED AOSP DEVICES (BLUE)
SPECIAL THANKS TO
@D daydream for buying Me the Daydream View 2017! No VR Development with You!
XDA:DevDB Information
SNAPPATCH, ROM for the Sony Xperia XZ1 Compact
Contributors
Miustone, Miustone, Miustone, Miustone
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: ANDROID 8.0 / SDK 26
Version Information
Status: Snapshot
Current Stable Version: 101
Stable Release Date: 2018-04-27
Created 2018-04-29
Last Updated 2018-04-28

Fundamental:
Feedback:
-Which Device are You using?
-Which Patch Version are You using?
-Which Android Version are You using?
Before posting:
-Read, read, read! Make sure You've seen the whole Thread
-Make sure You've followed the Instructions from Post 3
-Make sure You're using the right Patch for Your OS (STOCK / AOSP)
-Make sure You've not used other Mods which could cause Bugs

Infos:
Instructions:
-Download the latest Firmware for Your Model (XperiFirm)
-Download and place "NewFlasher" in Your Firmware Folder
-Connect Your Device in Flash Mode (Volume Down + USB)
-Execute the NewFlasher Firmware flash
-Disconnect Your Device (Let it powered Off)
-Connect Your Device in Fastboot Mode (Volume Up + USB)
-Flash the latest Recovery from TWRP.me
-Boot the Firmware until You see the Setup Wizard
-Power Off the Device again
-Hold Volume Down and the Power Button to enter TWRP
-Format Data (Not just wipe, FORMAT)
-Reboot to Recovery
-Format Data again (Don't do any Wipes)
-Your Device is prepared, now go over to the Patch Instructions on the Website
-You can also use custom ROMs, but untouched Android is always the best Base for a Patch...
Download:
Snappatch Website
Please consider a Donation if You like My Work! [PayPal.Me] [Gift Code]

Thanks again to @janjan for his great Kernels!
Let me know how it goes on the XZ1 Compact! Happy flashing Folks!

It would seem the updater script for G8441 fails because it thinks the device should be "maple", it should be "lilac"
Code:
(getprop("ro.product.device") == "maple"

NEWS: https://plus.google.com/communities/...57640557144575

Miustone said:
NEWS: https://plus.google.com/communities/...57640557144575
Click to expand...
Click to collapse
Error 404

Raz0Rfail said:
Error 404
Click to expand...
Click to collapse
Trying again: https://plus.google.com/communities/101868357640557144575 :angel:

nuudisco said:
It would seem the updater script for G8441 fails because it thinks the device should be "maple", it should be "lilac"
Code:
(getprop("ro.product.device") == "maple"
Click to expand...
Click to collapse
Same error here

92Greg said:
Same error here
Click to expand...
Click to collapse
I'm soon back with Updates! Check G+ to stay tuned (Links on My Homepage)
BR

Will next release v104 theoretically work with Android 9, if Sony decides to release stock in next week?

Is this project still active and if anyone here is on this rom pls indicate I have some questions

danish0175 said:
Is this project still active and if anyone here is on this rom pls indicate I have some questions
Click to expand...
Click to collapse
bro it is still alive op was in hostipal but now he is okay and back to work you can see his git hub repository every good things take time

uditrawat said:
bro it is still alive op was in hostipal but now he is okay and back to work you can see his git hub repository every good things take time
Click to expand...
Click to collapse
I'm also preparing for Android 9 here besides starting from Scratch. The new Patch will be universal again Thanks to AROMA, so no Device or OS Limits anymore. All in one Zip. You can check out My Git over this Link: https://github.com/Miustone/SOSP
Not much happend the last Time but this is to a lack of Android 9 on My XZ Premium. I'm currently working on a new AROMA and Updater Script which will be up soon. The rest comes when i get Android 9 :fingers-crossed:
BR

Miustone said:
I'm also preparing for Android 9 here besides starting from Scratch. The new Patch will be universal again Thanks to AROMA, so no Device or OS Limits anymore. All in one Zip. You can check out My Git over this Link: https://github.com/Miustone/SOSP
Not much happend the last Time but this is to a lack of Android 9 on My XZ Premium. I'm currently working on a new AROMA and Updater Script which will be up soon. The rest comes when i get Android 9 :fingers-crossed:
BR
Click to expand...
Click to collapse
sir myself has fixed device tree for 9 if you want i can make lineage os 16 but with various broken features

uditrawat said:
bro it is still alive op was in hostipal but now he is okay and back to work you can see his git hub repository every good things take time
Click to expand...
Click to collapse
Thank you for the reply
OP get well soon and thanks for the rom

SnapPatch Google link is dead! Please update!

antoniu200 said:
SnapPatch Google link is dead! Please update!
Click to expand...
Click to collapse
lol
Snappatch isn't existing anymore...
(XRWM if You want to see the latest Project from Me)

Miustone said:
lol
(XRWM if You want to see the latest Project from Me)
Click to expand...
Click to collapse
Well, I didn't know. But why remove all the links to every project you made so far? Was there an issue with SnapPatch? Also, when will you build another kernel for the XZ1 Compact?

Development [Proof of Concept][5.15] Mainline for Pixel 6/Pro

Hello everyone,
To keep it short: Some of you may have noticed. Google uploaded a mainline 5.15 branch for the Pixel 6 Pro.
Here´s a build for those that dare trying or simply want to run a mainline kernel on their phone.
I don´t plan to update this much outside of the scope that googles does and what I already did. It´s more of a proof of concept and I think there are at least some that would be eager to try.
I was able to daily drive it two days without a single crash, due to disablng WiFi Calling and by not using my USB C buds, but rather bluetooth buds.
However now I´m back to 5.10 as it´s really just a piece of concept. Essentially mainline GKI kernel with downstream android driver changes. Some pieces that are in the 5.10 kernel that haven´t been brought to 5.15 yet, are missing.
Feel free to report bugs and I will add them to the list.
However if you have issues you have been warned
Features:
Main Features:
- Based on latest kernel sources from Google for 5.15
Bugs:
- powerhal broken due to several scheduler optimizations still missing , removed faulty hints when running powerhint mainline module
- vibration, fixed when running powerhint_mainline module
- USB-C devices crash the device upon connection usb c hub now works, connect mouse to usb c hub works too
- USB-C headphones do not output sound
- USB-C to 3.5mm adapter is not working
- having wifi calling/vowifi enabled makes a network driver crash the phone
- fast charging is not working correctly on my end
- probably many more I didn´t notice
DOWNLOAD:
Download is always located in this folder:
https://www.androidfilehost.com/?w=files&flid=329868
Changelog:
Android 12
Initial Release
Requirements
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- a device rooted with magisk
- vbmeta flashed with disabling verification and verity flags (check process how to root the phone here)
How to flash the Kernel:
1. Download the images provided in the downloads section to your PC.
2. Download the powerhint magisk module for mainline found in downloads section and flash it via Magisk Manager like any other magisk module.
3. Flash ALL the provided images using fastboot/bootloader and fastbootd (different to the regular Kirisakura Kernel)
4. Don´t forget to patch the boot.img with Magisk Manager prior to flashing it.
3. Magisk-patched boot.img, dtbo.img and vendor_boot.img need to be flashed in fastboot, while vendor_dlkm needs to be flashed via fastbootd
First boot to bootloader, either via the option in Magisk Manager or via adb command:
Code:
adb reboot bootloader
Now in fastboot flash boot.img and dtbo.img
Commands:
Code:
fastboot flash dtbo dtbo.img
fastboot flash boot yourmagiskpatchedboot.img
fastboot flash vendor_boot vendor_boot.img
How to boot to fastbootd
Code:
fastboot reboot fastboot
Once in fastbootd:
Code:
fastboot flash vendor_dlkm vendor_dlkm.img
4. Reboot either via buttons
or by typing
Code:
fastboot reboot
5. Profit!
@osm0sis for all his work on AK3.
@tbalden for being the best HTC, Pixel, OnePlus and Asus wingman!
@LeeDroid and @mwilky for their awesome roms and work I used on multiple devices!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@arter97 for giving me advice
@kdrag0n for his help and advices!
@topjohnwu for magisk and his entire work!
google for all the work on this
Source Code: https://github.com/freak07/Kirisakura_Raviole

mine too
{
"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 belongs to me too.

and the last one

Did you notice any benefit performance/battery wise? I'll probably give it a try, thank you!

Tomatot- said:
Did you notice any benefit performance/battery wise? I'll probably give it a try, thank you!
Click to expand...
Click to collapse
probably both for the worse as several optimizations from google have not yet found their way to 5.15 from 5.10.

Does this mean it would be possible to run a linux operating system on the pixel 6 pro? For example, postmarketos, fedora or manjaro? Just like the pinephone?

deleted

This should work on P6 also correct?

ne0ns4l4m4nder said:
This should work on P6 also correct?
Click to expand...
Click to collapse
Just read the title... (also Raviole = Raven + Oriole)

Krullendhaar said:
Does this mean it would be possible to run a linux operating system on the pixel 6 pro? For example, postmarketos, fedora or manjaro? Just like the pinephone?
Click to expand...
Click to collapse
That would be possible anyway.

Freak07 said:
Essentially mainline GKI kernel with downstream android driver changes.
Click to expand...
Click to collapse
So its not really mainline, its google downstream, just not as big of a delta as usual. What I'd *really* love to see, is this hardware running on a real mainline straight from kernel.org.

So this is what rolling Android looks like lol

It seems to be amazing

bush911 said:
It seems to be amazing
Click to expand...
Click to collapse
have you flashed the kernel? if so, what's your experience like.

Alekos said:
have you flashed the kernel? if so, what's your experience like.
Click to expand...
Click to collapse
not yet, I prefer flash a zip kernel via EXKM, i am afraid of these commands

bencozzy said:
Best kernel period. Fixed all the stock bugs for me.
Only the known kernel bugs exist this is a step in the right direction.
Where can I send funds to buy you some adult beverages?
Click to expand...
Click to collapse
Click "Toggle signature" at the bottom of their post to show the donation link that's in their signature.

Worth looking at 5.17 or nah?
android-mainline-5.17

vassosman said:
Worth looking at 5.17 or nah?
android-mainline-5.17
Click to expand...
Click to collapse
If I find time, I might push out an updated build some time in the future.
but whether it´s based on 5.15, 5.17 or even 5.18 no clue.
I personally don´t think this is daily driver ready in any way, only a proof of concept and uninteresting for most.

Outta curiosity how did you figure out the boot.img config/offsets, or what are they I guess. Everytime I try to parse it through abootimg it crashes on me or complains about a missing page size.
I can boot this image just fine but I haven't been able to make my own yet

[KERNEL][A11/A12][EA][STOCK]"STABLE" Kernel

This Kernel is for EA Android Q version. If you're using TM or ATT, please cross flash to EA.
This Kernel Does not Support for L51A(JP version[DOCOMO])
(I have committed the TM20k change in rebase but not merge in EA version)
NOTE:
1. Your Phone must be unlocked bootloader and have magisk root
2. Your Phone's ANDROID VERSION must be 11/12
KERNEL FEATURE:
01. Merge CAF version into LA.UM.9.12.r1-14000-SMxx50.0
02. Merge DTS version into LA.UM.9.12.r1-14000-SMxx50.0
03. Update Kernel version to 4.19.225
04. Move to PELT
05. Use Sultan Kernel Toast's CPU/Devfreq input boost
06. Use SIMPLE LMK (Sultan Kernel Toast's)
06. GPU overclock to 855Mhz (I've broke the TM varient while oc to 870MHZ)
07. KCAL support
08. Import Juhyung Park arter97's exfat to support LGE's texfat
09. Use Proton Clang 13 for kernel compiling
10. Disable blocking touch while reboot to recovery (TESTING) -> author: SGCMARKUS
HOW TO FLASH:
1. The flashable zip is support Magisk, Flash it just like flashing a module.
DOWNLOADLINK:
MEGA LINK
KERNELSOURCE:
GITHUB LINK
Special Thanks:
* SGCMarkus
* Sultan (kernel toast)
* Arter97
* Ayrton990
* TingyiChen
* LibXZR
* EmanuelCN
* spakkkk
AND Many Other Great Developers!
Final: Sorry about my English
SCREENSHOTS:
{
"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"
}

ChangeLog
Android 12:
V6:
1. Merge ACK (Kernel version: 4.19.267)
2. Update exfat source from namjaejeon
3. Merge latest f2fs-stable
4. Fix LGE wifi private command error
V5:
1. Merge ACK (Kernel version: 4.19.261)
2. Update exfat source from namjaejeon
V4:
1. Merge ACK (Kernel version: 4.19.255)
2. Merge caf tag to LA.UM.9.12.r1-14700-SMxx50.0
3. Merge latest f2fs-stable
4. Update crypto.
Android 11:
V13 (Reupload):
WALT only:
1. Merge ACK (Kernel version: 4.19.255)
2. Merge caf tag to LA.UM.9.12.r1-14500-SMxx50.0
3. Merge latest f2fs-stable
4. Tweak little cpu freq to reduce animation lags
5. Clang 16 support
6. Use LRNG random
V12:
WALT only:
1. Merge ACK (Kernel version: 4.19.251)
2. Merge caf tag to LA.UM.9.12.r1-14300-SMxx50.0
3. Android 12 support And FIX com.android.phone crashed
4. Android 11 final (no longer update)
V11:
WALT/PELT:
1. Merge ACK (Kernel version: 4.19.240)
2. MPTCP update to 0.95.2
3. ZRAM update to 5.15 (Arter97)
BUG:
1. HIGHER CPU JITTER DURATION AND I CAN'T SOLVE IT ANYMORE
2. DON'T KNOW ABOUT WIFI ISSUE

Really fast kernel. It works fine on my V600Ea

If im on the att 60 A10, can i still crossdflash?

FC06 said:
If im on the att 60 A10, can i still crossdflash?
Click to expand...
Click to collapse
It's necessary, but i don't have a guide to crossflash to EA ver

staljin said:
Really fast kernel. It works fine on my V600Ea
Click to expand...
Click to collapse
The v2 version has been rebuilt, details are on the changelog.

Is there a way to use this on tm without crossflash? Crossflash kills volte and TMobile enforces it

crimsonrommer said:
Is there a way to use this on tm without crossflash? Crossflash kills volte and TMobile enforces it
Click to expand...
Click to collapse
I came to ask this question for the exact same reason.

crimsonrommer said:
Is there a way to use this on tm without crossflash? Crossflash kills volte and TMobile enforces it
Click to expand...
Click to collapse
mnt/product/op -> the configs of volte are in this folder

ErickG233 said:
mnt/product/op -> the configs of volte are in this folder
Click to expand...
Click to collapse
Right and what do I do with that info lol?

crimsonrommer said:
Right and what do I do with that info lol?
Click to expand...
Click to collapse
back up your preset folder, and backup your ftm(dev/block/bootdevice/by-name/ftm) block, refurbish to ea 20j, then use hex to open ftm binary file, search "FFF" with asicII(not hex), then change the end number(ea is 11), flash it,then replace all the files in /mnt/product/OP/OPEN_EU/etc and /mnt/product/OP/OPEN_EU/cust.prop then reboot.
maybe one day i will post a thread about OP mod....

ErickG233 said:
back up your preset folder, and backup your ftm(dev/block/bootdevice/by-name/ftm) block, refurbish to ea 20j, then use hex to open ftm binary file, search "FFF" with asicII(not hex), then change the end number(ea is 11), flash it,then replace all the files in /mnt/product/OP/OPEN_EU/etc and /mnt/product/OP/OPEN_EU/cust.prop then reboot.
maybe one day i will post a thread about OP mod....
Click to expand...
Click to collapse
To replace the files in the OPEN_EU folder, where do I get the new files from?
I believe a thread on changing the OP is much needed and appreciated since there are a lot att devices crossflashed to EU FW.

Working well so far on my V600TM Cross flashed V600EA.
Any plans for a suture release or an update?

MrHomebrew said:
Working well so far on my V600TM Cross flashed V600EA.
Any plans for a suture release or an update?
Click to expand...
Click to collapse
Hi, I live in Europe and I have v600tm, I like to put my company's software, i looked everywhere on this site to understand how to cross flash, can you please link me a place to understand how cross flash works, thanks and sorry for my English

MrHomebrew said:
Working well so far on my V600TM Cross flashed V600EA.
Any plans for a suture release or an update?
Click to expand...
Click to collapse
V6 has been released.

Any plans in releasing a kernel that doesn't require crossflash?

crimsonrommer said:
Any plans in releasing a kernel that doesn't require crossflash?
Click to expand...
Click to collapse
Well you can flash anyway, it can boot but not sure NO BUG.
Bootable variant (A11): TM ver.

MrHomebrew said:
Working well so far on my V600TM Cross flashed V600EA.
Any plans for a suture release or an update?
Click to expand...
Click to collapse
How did u crossflashed your V600TM to EA firmware?

Hi, just wanna ask which EA firm should i crossflash? Tried on mine Crossflashed but i got kernel panic

Kratos574 said:
Hi, just wanna ask which EA firm should i crossflash? Tried on mine Crossflashed but i got kernel panic
Click to expand...
Click to collapse
you need to recover the abl from kdzs NOT the factory ABL