Hi People!
I have an SM-T355Y which does not have any official or unofficial LineageOS ports. So, I am using a ROM for a similar device (SM-T350) which has some unofficial ROMs..
The screen has some scaling difference between the SM-T350 and T-355Y models due to which touches in around 75% of the screen get scaled to entire 100% - so to click something at the right bottom corner, I have to touch a point which is around 1.5 inches from bottom and 0.5 inches from right. Crude representation below:
Touching blue point will click at orange point:
{
"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"
}
Is there some config file that I can edit to scale the touch response so that I get the click below the point I touch?
Or is there a 'mapping' file that I can use?
Do let me know if I can try some other tricks.
Rahul.raj said:
Hi People!
I have an SM-T355Y which does not have any official or unofficial LineageOS ports. So, I am using a ROM for a similar device (SM-T350) which has some unofficial ROMs..
The screen has some scaling difference between the SM-T350 and T-355Y models due to which touches in around 75% of the screen get scaled to entire 100% - so to click something at the right bottom corner, I have to touch a point which is around 1.5 inches from bottom and 0.5 inches from right. Crude representation below:
Touching blue point will click at orange point:
Is there some config file that I can edit to scale the touch response so that I get the click below the point I touch?
Or is there a 'mapping' file that I can use?
Do let me know if I can try some other tricks.
Click to expand...
Click to collapse
You need a kernel that is compatible with your model number. Your device and the similar device have slightly different hardware, therefore, the kernel from the other device is slightly different than yours.
This isn't the kind of thing where you can just edit some system files, this has to be done by installing a compatible kernel. You will have to try finding a kernel that is already made for your specific model number or you will have to build a new kernel from the ground up yourself by compiling the new kernel using the source code for your device(if it is available). Or, you can try using a kernel from other similar devices. Or, you can try porting a kernel to make it work on your device.
If you are lucky, you might find something that is already compatible that you can just install as it is. If you can't find something compatible, you'll have to compile a new kernel or port an existing kernel.
Droidriven said:
<...>
Click to expand...
Click to collapse
Thanks for the guidance.
Possibly dumb questions:
1. Can a kernel specifically compiled for my device be 'flashed' into the currently installed setup, through PC or TWRP, or do I need to 'integrate' it into the ROM and flash the ROM again?
2. As I said, my device is unsupported by LineageOS. What would be a good resource for me to follow to build a device specific kernel?
Rahul.raj said:
Thanks for the guidance.
Possibly dumb questions:
1. Can a kernel specifically compiled for my device be 'flashed' into the currently installed setup, through PC or TWRP, or do I need to 'integrate' it into the ROM and flash the ROM again?
2. As I said, my device is unsupported by LineageOS. What would be a good resource for me to follow to build a device specific kernel?
Click to expand...
Click to collapse
1) the kernel can be flashed via TWRP if it has been converted into a flashable .zip file, can can take a copy of your lineageOS ROM .zip and delete the ROM system.img from the .zip and replace it with the kernel file. It is risky if you don't edit the .zip file correctly, you might want to consider using a method that converts your kernel file directly into a flashable .zip the same way ROM .zips are created.
2)first, you need to do some Google searching to see if your device's stock kernel source has been released to the public. If it isn't publicly available, you will not be able to build a device specific kernel. Or you can try finding LineageOS ROMs for similar devices and extract the kernel from those ROMs and flash them on your device. You could also find the lineagOS kernel source code for those other devices/ROMs and try compiling your own kernel from those lineageOS kernel sources.
Thanks a ton for the feedback.
There is no ROM/ kernel for my device and the 'similar' device has the scaling issue.
Having said that there was a Marshmallow kernel from Ashyx: But I am not confident that it will work with a Nougat ROM.
I looked at the compile instructions for LineageOS, but that has a step where it needs to download proprietary files from a device already running LineageOS ROM. Kind of chicken and egg problem it seems.
Looks like there is no way ahead on this.
Related
{
"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"
}
Quote:
Disclaimer: OctOs is a WIP. It has been evaluated as being stable, and is suitable for daily use in most cases. While it may be considered stable, there may be unknown bugs. The development team is not responsible for any damage to your device or your information.
Click to expand...
Click to collapse
Team OctOs presents Oct-L
Frequently Asked Questions
Q: Is this Android 5 (Lollipop)?
A: Yes, this is Android 5.1.1
Q: What code is Oct-L based on?
A: Starting with Oct-L, we've rebased OctOs on the CyanogenMod 12.1 code.
Q: What happened to AOSP?
A: All Android code is based on the Android Open Source Project (AOSP). Under previous releases, we tried very hard to limit the number of "Not from Google directly" repositories that we used. Unfortunately, issues with devices, the need for Code Aurora Foundation (CAF) repositories for Qualcomm devices, and compatibility issues meant fighting code more often than not. We decided that since the code-base for many repositories were the same across most ROMs, picking a starting point to build the user experience on outweighed the desire to craft code from scratch, or fix broken code to make it work with other changes we already had.
Q: Why isn't there XXXXXXX feature.
A: Shoot us a Suggestion if you want to see something added. While we are not going to promise to implement, we will always look into it
Q: But CM and all the others have..
A: ROM developers, including CM, build something they want to use. The ROM developer that includes something they won't run implies less than 100% effort to ensure it does work. As a team, we have similar goals and objectives. If XYZ ROM has a feature you want, and we don't include (or don't want to include), feel free to use XYZ ROM, or build your own custom version of Oct-L.
Q: Superuser or SuperSU?
A: Team OctOs uses SuperSU and is installed automatically.
Bugs:
Bugs happen. Our testers are very good at breaking things, but no where near as good as the rest of the Android public. In order to investigate and fix issues, we need the help of the users who are going to report them. The Android OS has many nifty features to help us in this, but only if we can engage the user to assist us.
Download Links:
ROM Link: https://drive.google.com/file/d/0B-2fxJZPPqPKejB0VjVKNExyeTg/view?usp=sharing
Gapps: https://drive.google.com/open?id=0B-2fxJZPPqPKYnZHQlZIZ3BTODQ
Workaround fixes:
Youtube 480p fix: https://mega.nz/#!kEcnTKAb!fdPgfulZi26fFIpQ1FpPUAh-QxNrA5MFUMH-oh8am_g
Install latest Youtube app first, then flash through recovery.
Click to expand...
Click to collapse
Flashing Procedure
Please use this recovery. https://mega.nz/#!tYQylL5K!N-is8LoHaEi3UmlOVOIuIjsNs1BNv-7gIEkM1XadW-A
Click to expand...
Click to collapse
Boot to recovery
Go to Wipe section
Wipe System, Internal Storage, Cache, Dalvik Cache, Data.
Go to Install section, select OctOS_5.1.1r35_based-A536.zip
Flash gapps.zip
Go to Wipe section, wipe Cache and Dalvik Cache
Reboot
Credits:
Team OctOS
@ajit Guraya
Cyanogenmod
is this ported ???
BKhandual said:
is this ported ???
Click to expand...
Click to collapse
Lol yeah
Sent from my MT6582 using XDA-Developers mobile app
~cyandrew said:
Lol yeah
Sent from my MT6582 using XDA-Developers mobile app
Click to expand...
Click to collapse
Everything works great. but in file manager sdcard showing as Navigate up and Internal storage showing as Navigate Home........
Any way to fix this...
link youtube 480p not found upload again
BKhandual said:
Everything works great. but in file manager sdcard showing as Navigate up and Internal storage showing as Navigate Home........
Any way to fix this...
Click to expand...
Click to collapse
Just download ES File Explorer and you will be good to go
when i am trying to call it says cellular notwork not available.. please help me to
when i am trying to call it says cellular notwork not available.. please help me to fix this issue
DISCLAIMER: I am not responsible if your device gets messed up royally, explodes or causes you to go nuts because you couldn't get this thing to work. I'm no expert coder either, but I am willing to fix things as much as I can.
I actually did this as there's practically no support whatsoever for that counterfeit phone of mine (yeah I know, you get what you pay for, but I bought this Galaxy S7 clone mostly for science). None of the existing porting tools work for the MT6580, and while manually porting an existing TWRP image to my phone works, it simply isn't cutting it as most of these recoveries are designed for a conventional framebuffer setup, not on devices with flipped LCDs. Fortunately there's this source tree for the Infinix Hot 2 TWRP port, and as the partition setup seems to be largely the same apart from differing capacities and the aforementioned LCD issue, this had to be done.
This should theoretically work on HDC S7 clones and a few others albeit with a few modifications, though I ported this from source with the Z6U030/GXQ6580 in mind. I know the latter isn't as widely known as the HDC model, let alone the original, but oh well...
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"
}
DOWNLOADS:
You may download the initial recovery release here: https://github.com/huckleberrypie/android_device_alps_z6u030_twrp/releases
The recovery should work best on this ROM, but may also work on other devices provided you replaced the kernel with the one that came with your device:
http://www.4shared.com/rar/6mMhYIk5ce/Galaxy_S7_mt6580_Z6U030HA_V105.html
And as for the sources, you can download the device tree here: https://github.com/huckleberrypie/android_device_alps_z6u030_twrp
Credits
My biggest props to the TeamWin team for making this little project of mine possible, as they're basically the ones who made this in the first place; I merely forked it to account for my device's configuration anyway. I'd also like to thank my pals over at American Girl Adult Collectors especially Amy and Molly, Arnee Libelo and Arturo of Driving Passion, and my buds Andy Vandjick and HardcoreHacker for the fun and expertise they shared.
plz rom
MT6580_alps_gxq6580_weg_l_Android5.1_Z6U030HA_V107En
---------- Post added at 02:23 PM ---------- Previous post was at 02:01 PM ----------
How to install twrp
Here are the /lib and /usr files that you requested.
hi. did USB Storage is working on yours? I tried to port another version of this recovery(Jemmeni's port) and seems to work fine except for error in mounting USB Storage. I need to work on that.
Yup, everything works apart from the lack of USB-OTG.
maybe i'll try your copy. maybe it work. and also, after screen time out, the screen was turned on again. how to fix that? i removed otg from mount points. that is the only solution if your kernel didn't support otg
Not sure what to do with the screen issue tbh; I just wanted a recovery for this rather obscure knockoff I use. Feel free to post your fork when you're done with it, aight?
i cant download the file at dev-host and it prompts as dangerous website warning instead. please upload to another file hosting site or attach here instead.
PAPalinskie said:
i cant download the file at dev-host and it prompts as dangerous website warning instead. please upload to another file hosting site or attach here instead.
Click to expand...
Click to collapse
I posted it on my Github page - there are two releases, one for v105 and another for v106.
blakegriplingph said:
I posted it on my Github page - there are two releases, one for v105 and another for v106.
Click to expand...
Click to collapse
thanks brother.
PAPalinskie said:
thanks brother.
Click to expand...
Click to collapse
No problem mate.
custom recovery mt6580
Hey will it work on my swipe konnect plus mt6580
aksthecount said:
Hey will it work on my swipe konnect plus mt6580
Click to expand...
Click to collapse
If your device has a similar partition scheme, just change the kernel and a few other settings, and it should work.
i just test it on a g930f with a mt-6580 processor and it doesn't work
need twrp scatter file
MT6580__samsung__A9__A9__5.1__Z8054_5.1_V2.9_20161017-193505. .twrp scatter file for this . .thanks
Bro I have a Yezz 5E3 with Chipset Mediatek MT6580M, can this work in it?
PieNs7 said:
Bro I have a Yezz 5E3 with Chipset Mediatek MT6580M, can this work in it?
Click to expand...
Click to collapse
Try extracting the stock recovery off your phone, then open it using Carliv's IMG Kitchen. Then see if you could add the mount points from your phone to the recovery I compiled. Beware though, the recovery I made is for a flipped LCD so I am not sure if it will work without removing the flipped LCD flag and recompiling TWRP from source.
hi
i have an archos 101 3g platinum with mt6580 (android nougat)
any chance to succeed to install twrp on it ? i already have a samsung a5 and an asus zenphone 2 rooted with twrp installed
adb shell is working and i have access to bootloader mode
and fastboot is working too, i only need a valid twrp.img
ty
phoenixpb said:
hi
i have an archos 101 3g platinum with mt6580 (android nougat)
any chance to succeed to install twrp on it ? i already have a samsung a5 and an asus zenphone 2 rooted with twrp installed
adb shell is working and i have access to bootloader mode
and fastboot is working too, i only need a valid twrp.img
ty
Click to expand...
Click to collapse
I don't have access to a build environment atm, so I am not sure if I could do a TWRP source port for you. :/
blakegriplingph said:
I don't have access to a build environment atm, so I am not sure if I could do a TWRP source port for you. :/
Click to expand...
Click to collapse
well thanks for your reply anyway
i continue digging
Hello Everyone, I am new to porting custom ROMs and I would like to start to Port custom ROMs for this device, could anyone help me get started?
MaybeDontAsk said:
Hello Everyone, I am new to porting custom ROMs and I would like to start to Port custom ROMs for this device, could anyone help me get started?
Click to expand...
Click to collapse
Try building lineage first. https://wiki.lineageos.org/devices/kebab/build
Thanks for telling me what to start with, I was successful on everything until the "Brunch Kebab" command on that one I got the following Vendor Error I believe it is - hope you can help me
{
"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"
}
MaybeDontAsk said:
Thanks for telling me what to start with, I was successful on everything until the "Brunch Kebab" command on that one I got the following Vendor Error I believe it is - hope you can help meView attachment 5541455
Click to expand...
Click to collapse
You used this for the vendor files, https://github.com/TheMuppets/proprietary_vendor_oneplus right?
Nope I didn't even know I needed that, thanks I'll try this tomorrow, if I need to extract this, do I extract it to the vendor folder?
MaybeDontAsk said:
Nope I didn't even know I needed that, thanks I'll try this tomorrow, if I need to extract this, do I extract it to the vendor folder?
Click to expand...
Click to collapse
Yeah, just (in the source location):
Code:
cd vendor/
git clone https://github.com/TheMuppets/proprietary_vendor_oneplus.git -b lineage-18.1 oneplus
Then you should be good to go.
Make sure these exist too:
kernel/oneplus/sm8250
hardware/oneplus
Alright if I success building lineage tomorrow, should I try to port another custom ROM? And if yes do I need to download any other files other than the source cuz I believe everything is pre installed for the OnePlus 8t on the lineage os 8T build guide.
MaybeDontAsk said:
Alright if I success building lineage tomorrow, should I try to port another custom ROM? And if yes do I need to download any other files other than the source cuz I believe everything is pre installed for the OnePlus 8t on the lineage os 8T build guide.
Click to expand...
Click to collapse
Yes of course you can try building other ROMs. Lineage is already built for the 8T, but is a good place to start. You will need to download the source of each ROM you want to build. However, Lineage has all of the needed files to be downloaded for the 8T. For other ROMs, you will need to edit some files in the device trees and possibly make your own.
Do u know if there's a guide or examples to editing files like that or making my own?
MaybeDontAsk said:
Do u know if there's a guide or examples to editing files like that or making my own?
Click to expand...
Click to collapse
Hmm, this guide may help - https://blog.arrowos.net/compilation-guide/
But also, this telegram group can be helpful to start - https://t.me/AndroidBuildingHelp
Hi thanks, so I was ready (Kinda) to start building DotOS 6.0 (Android 12) For This Device (OnePlus 8T) right after finishing the lineage build but I got the following error after one hour -
Sorry for the bad quality, rn I have the project 404 rom on my phone that came with no camera so had to get gcam ported apk to take this picture.
MaybeDontAsk said:
Hi thanks, so I was ready (Kinda) to start building DotOS 6.0 (Android 12) For This Device (OnePlus 8T) right after finishing the lineage build but I got the following error after one hour -View attachment 5542333
Sorry for the bad quality, rn I have the project 404 rom on my phone that came with no camera so had to get gcam ported apk to take this picture.
Click to expand...
Click to collapse
That looks like youre building lineage still right? Also, A12 will be a little more difficult to build and may need a more extensive guide..
And more code is needed to figure out the error
Hi, I want to build KangOS from source, I know all basic commands to sync repo and all of that but I don't know how to buil/port/make it for this device (Oneplus8T) any guide on if I need stock filmware or edit any files?
Hello, after a long time, I have decided to try porting a rom again, I am trying to port an Android 12L rom, but I've come upon an error when I am about to compile the rom
Code:
"Brunch Kebab"
and I get "No config file found for Target Device Kebab (I have already cloned vendor, device tree and kernel files for 12L) I have been trying to fix this error for around an hour or 2 now. I would appreciate if you helped me
MaybeDontAsk said:
Hello, after a long time, I have decided to try porting a rom again, I am trying to port an Android 12L rom, but I've come upon an error when I am about to compile the rom
Code:
"Brunch Kebab"
and I get "No config file found for Target Device Kebab (I have already cloned vendor, device tree and kernel files for 12L) I have been trying to fix this error for around an hour or 2 now. I would appreciate if you helped me
Click to expand...
Click to collapse
Hi,
anyone have any kernelSU that works with oneplus 7 pro?
Ive never heard of this however if you are able to compile the kernel with your hardware then you can set it up yourself, Let me know if you end up doing so cause I would like to check it out too! Id build it myself but I have 3gb left on my hard disk...
kernel-assisted-superuser - Kernel assisted means of gaining a root shell for Android
git.zx2c4.com
RolandStoner said:
Ive never heard of this however if you are able to compile the kernel with your hardware then you can set it up yourself, Let me know if you end up doing so cause I would like to check it out too! Id build it myself but I have 3gb left on my hard disk...
kernel-assisted-superuser - Kernel assisted means of gaining a root shell for Android
git.zx2c4.com
Click to expand...
Click to collapse
I don't know how to build it , if you can guide me I will build it .
I just so happened to acquire a few development machines to work with so once I get setup Ill let you know o7
RolandStoner said:
I just so happened to acquire a few development machines to work with so once I get setup Ill let you know o7
Click to expand...
Click to collapse
if you can save a video or screenshots for the steps and share it later it will be appreciated, a draft will be enough
Youll have to excuse my incoherent babbling then
Im almost finished with setting up my devices, after that its going to take a moment for android to dl then ill give it a go
Gotta restart today, didn't expect it to actually cost 200+gb for setup
No Problem, take your time really appreciate your work here,
it will work with android 11 right? as A12 is not stable for oneplus 7 pro
RolandStoner said:
Gotta restart today, didn't expect it to actually cost 200+gb for setup
Click to expand...
Click to collapse
sorry to ask , any update?
loshabih said:
sorry to ask , any update?
Click to expand...
Click to collapse
having some trouble compiling the kernel :/ working on it
going off of lineage 20 btw: https://github.com/LineageOS/android_device_oneplus_guacamole
GitHub - LineageOS/android_kernel_oneplus_sm8150
Contribute to LineageOS/android_kernel_oneplus_sm8150 development by creating an account on GitHub.
github.com
im going to try getting the .config off of my device as a base since i cant seem to find the guac defconfig. After that it should just be running the script and compiling
Alright, I think I figured it out. 3 reinstallations and 1tb later my env is almost complete
Alright I finally know what the **** im doing. Ill post the kernel once it compiles and here is a doc for building yourself
To compile the Android kernel source code, you will need to have a Linux-based d - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
RolandStoner said:
Alright I finally know what the **** im doing. Ill post the kernel once it compiles and here is a doc for building yourself
To compile the Android kernel source code, you will need to have a Linux-based d - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
Click to expand...
Click to collapse
sorry for asking ..did you successfully compiled the kernel ?
I have not, i dont think my hw can do it, all my machines keep stalling at some point. if you have the storage space and recommended hardware i can send you all the stuff i have
loshabih said:
sorry for asking ..did you successfully compiled the kernel ?
Click to expand...
Click to collapse
I compiled the kernel.
{
"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"
}
boot.img for LineageOS 20 with KernelSU
https://drive.google.com/file/d/1xUprcgTg-nsxBIS5I_VDaBju0LLFkKDO/view?usp=sharing
KernelSU for OnePlus 7/7 Pro (Flashable Zip)
https://github.com/snowwolf725/android_kernel_oneplus_sm8150/releases
https://drive.google.com/file/d/1c6Z0dHCXSxmV223L0Ta1gSSJo0tnSpkb/view?usp=share_link
KernelSU Manager APK
https://github.com/tiann/KernelSU/releases
snowwolf725 said:
I compiled the kernel.
View attachment 5829085
boot.img for LineageOS 20 with KernelSU
http://dstats.net/track/2y5x97
KernelSU for OnePlus 7/7 Pro
http://dstats.net/track/2y5yb6
Click to expand...
Click to collapse
URL is not working ..it show disabled .
also does it work with stock OOS11 or i must have LineageOS ?
loshabih said:
URL is not working ..it show disabled .
also does it work with stock OOS11 or i must have LineageOS ?
Click to expand...
Click to collapse
I have updated the links.
The boot.img is only for LineageOS 20.
I'm not sure it work with OOS11 currectly or not.
You should try it by yourself.
You can flash the zip file through TWRP.
snowwolf725 said:
I have updated the links.
The boot.img is only for LineageOS 20.
I'm not sure it work with OOS11 currectly or not.
You should try it by yourself.
You can flash the zip file through TWRP.
Click to expand...
Click to collapse
i will try ..
thanks
zip file caused boot loop, TWRP touch not working, I had to fastboot boot twrp.img
then restore the boot.img backup
RisingOS for the Google Pixel 7/7 Pro [pantah]
What is RisingOS?
* risingOS is An OpenSource Aftermarket Android Operating System that aims to deliver unique and refreshing android experience..
Based on Android 13 QPR2
Screen Shots
{
"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"
}
Whats working?
Everything I know of
Known issues
Nothing yet
You tell me
Downloads
*FASTBOOT METHODS*
Required platform-tools 33.*.*
(Stay away from 34.*.* as it gives an error)
*Cheetah*
risingOS-v1.1-Babylon-202306172142-cheetah-GAPPS-OFFICIAL-fastboot.zip
*Panther*
risingOS-v1.1-Babylon-202306180124-panther-GAPPS-OFFICIAL-fastboot.zip
Install Instructions
Reboot to bootloader
fastboot update 'path to downloaded zip file'
Data wipe can be done by adding -w (fastboot update -w 'path to downloaded zip file')
Android OS version: 13.0.0_r45
Security patch level: May 5, 2023
Build Device Maintainer: Niv
Kernel Source code: Source
Source code: https://github.com/risingTechOSS
ROM Developer: minaripenguin
Changelog: coming soon
Telegram Chat: RisingOS Pixels
Runs very well, can only recommend this ROM
I'm sorry, what is "unique and refreshing" about this ROM? Screens do look nice, but...
So far very good and stable rom. Thanks to Niv
gogoffm said:
So far very good and stable rom. Thanks to Niv
Click to expand...
Click to collapse
Just a breath of fresh air!
Is this 32 bit compatible by chance too?
Or only 64 bit.
jgrubbs said:
Is this 32 bit compatible by chance too?
Or only 64 bit.
Click to expand...
Click to collapse
Only 64
О_о Babylyon v.1.1 ?!
I'm already downloading))
RisingOS v1.1 runs great. Thanks for the update
just started running this rom today but so far everything buttery smooth no random app not respondings no hang ups, just buttery smooth with some of the most customization ive ever seen in a rom hands down. even brought back quick settings bg images! man i missed those. and the little things it does like theming for the settings app and the image header in setting options.. or the quick settings icon animations.. now THIS deserves the name CUSTOM rom, unlike most builds nowadays are just GSI's with a couple copypasta options in it.. MAJOR props to the dev for this rom i think ill stay a while.. One opinion on the post here on xda; you need a features list.. i mean it would really suck to type the extensive list out, but if people could see the amount of hard work put in, this rom would blow up so quick.
regardless, it's gonna blow up.. So excited to check this ROM out further! Thanks again.
wrong thread.sorry
Thank you Nivla, Rom is running great.
Anyone using AA with this rom. It doesn't connect with my headset.
Does this ROM support custom kernels?
jake.99x3 said:
Does this ROM support custom kernels?
Click to expand...
Click to collapse
Using Kiri kernel rn without any issues
yurishouse said:
Using Kiri kernel rn without any issues
Click to expand...
Click to collapse
Yes using radioactive ☢
Running sultan kernel..
Working flawlessly
cultofluna said:
Running sultan kernel..
Working flawlessly
Click to expand...
Click to collapse
Mind linking the download link for Sultan kernel?
Pixel86 said:
Mind linking the download link for Sultan kernel?
Click to expand...
Click to collapse
Still on testing currently
Will be published soon
Been running the whole day and it's super stable. Customizations are just enough to satisfy what I need.