{
"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"
}
Droidian for Poco F1
This rom is based on Droidian distribution. Its not a typical android ROM. Droidian is a mobile version of the Debian operating system.
THIS ROM IS IN BETA Stage.
DISCLAIMER: This group has nothing to do (and not affiliated) with UBports and droidian foundation, as this is an unofficial port.
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
XDAevDB Information
Droidian, ROM for the Xiaomi Poco F1
Contributors
@joelselvaraj @thomashastings
Source Code: https://github.com/Unofficial-droidian-for-pocof1/linux-android-xiaomi-beryllium
Dev works: https://github.com/orgs/Unofficial-droidian-for-pocof1/repositories
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Used: https://xiaomifirmwareupdater.com/download/
Based on: https://droidian.org/
Version Information
Status: Beta
Droidian for the Poco F1A collection of tips to install and use Droidian on the Pocophone F1 (beryllium)
Requirements
A computer with fastboot and adb access to the phone
A USB 2.0 port/hub with actual USB 2.0 controller (fastboot on USB 3.0 can be problematic with Poco F1)
Unlocked bootloader
Backup all your data, as your phone will be WIPED
It is also recommended to take a note about your Acces Point Name in Android Settings before starting the procedure (you will need it for mobile data)
Installation0. Download files
Latest nightly or stable release of droidian-rootfs and droidian-devtools for arm64 from the Droidian repo
Latest boot image
Latest adaptation zip
Vendor image
Android 9 Pie official firmware
Latest TWRP
1. Install TWRP
Boot to fastboot mode by pressing the Vol- and Power buttons until the phone vibrates
Check that the phone is recognized by running fastboot devices
Install TWRP by running fastboot flash recovery twrp-*-beryllium.img
2. Install Droidian in TWRPTWRP:
Boot into TWRP by pressing Vol+ and Power buttons until the phone vibrates
Go to Wipe and Format data (type yes)
IMPORTANT: Reboot into TWRP again
PC:
Connect the phone via USB
The internal storage is now available over MTP from the PC
Copy the downloaded files to the internal storage of the phone
TWRP:
Install image: boot.img to Boot partition
Install image: vendor.img to Vendor partition
Install zip file: fw_beryllium_miui_POCOF1Global_9.6.27_6673f8a455_9.0.zip
Install zip file: droidian-rootfs-api28gsi_arm64_YYYYMMDD.zip
Install zip file: droidian-devtools_arm64_YYYYMMDD.zip
Install zip file: android-recovery-beryllium-adaptation.zip
Go back to main menu and reboot to System (TWRP might complain that there is no OS installed, but that's fine)
The first boot may take longer, and at least one spontaneous reboot is expected during the process
If all goes well, your phone will boot to the Droidian lock screen, the unlock code is 1234
Now open the King's Cross terminal app and run this command: sudo systemctl enable enable-ipa (the password is 1234)
Reboot the phone (long press power button)
Installation is complete
Flashing the devtools zip enabled SSH over USB. To use it, connect your phone to your computer and type ssh [email protected], the password is 1234 (on Windows, you may need PuTTY)
NotesSIM slotDual-SIM mode is not supported as of now. Only the SIM2 slot is active, so a microSD card can be used at the same time.
Mobile dataMobile data should work, but it needs to be set up manually. The good part is that the configuration is persistent, so you need to do this only once.
Open the Settings app and tap Mobile, then tap Access Point Names
Tap the + in the top right corner of the pop-up
Fill out the textboxes based on your settings in Android. The Name can be anything, e. g., the name of your carrier. The APN is likely some sort of an URL, like internet.carrier.net or something similar. If you didn't see a Username and Password in Android, you can skip these.
In some cases, rebooting your phone or turning mobile data on and off a few times is enough. Otherwise we'll have to give the same settings to oFono as well.
Open the King's Cross terminal app or use SSH and type cd /usr/share/ofono/scripts
To check your current setup, type ./list-contexts, look for the first context, called [ /ril_1/context1 ]
Notice that context has Name, Type, AccessPointName, Username, and Password attributes among others, we'll need to change these to match the valid settings from Android.
Now deactivate this context to be able to make changes to it: ./deactivate-context 1
And now make your changes like this: ./set-context-property 1 $ATTRIBUTE $VALUE, where the 1 is for [ /ril_1/context1 ], the $ATTRIBUTE is one of the attributes listed above, and the $VALUE will be the value you need to enter. make sure that the Name and AccessPointName match the Name and APN you entered in the settings menu. If an attribute needs to be empty, set it to "".
When you make your changes, you can use ./list-contexts to see them.
When everything looks good, activate the updated context: ./activate-context 1
If all went well, by running./list-contexts again you should see that the Active attribute is now 1, and under the Settings attribute you can see the network parameters (Address, Netmask, Gateway, etc.) assigned by your carrier.
You may need to reboot or turn mobile data on and off a few times, but mobile data should be working now.
Pro tip: once you configured everything, you can type history to see your previous commands. Save them to a script that does all of this for you next time.
Additional tweaksFor other tweaks, open the King's Cross terminal app, and run beryllium-extras.sh. The following options are available:
Notch fix (moves the clock from its original invisible position to the right side)
Switching between dark mode and light mode (Adwaita theme)
Automated installation of Waydroid
CreditJoel Selvaraj
1petro
Droidian
UBports
Yunior
@thomashastings
For further assistance, visit the Droidian for Poco F1.
Device Checklist for Pocophone F1 (beryllium) on DroidianThis represents the state of the Droidian port when flashed according to the guide.
Working
Actors: Manual brightness
Actors: Notification LED
Actors: Torchlight
Actors: Vibration
Bluetooth: Driver loaded at startup
Bluetooth: Enable/disable and flightmode works
Bluetooth: Pairing with headset works, volume control ok
Bluetooth: Persistent MAC address between reboots
Camera: Ensure proper cameras are in use
Camera: Flashlight
Camera: Photo
Camera: Switch between back and front camera
Cellular: Carrier info, signal strength
Cellular: Change audio routings (Speakerphone, Earphone)
Cellular: Flightmode works
Cellular: Incoming, outgoing calls
Cellular: Voice in calls
Cellular: SMS in, out
Endurance: Battery lifetime > 24h from 100%
Misc: Waydroid
Misc: AppArmor patches applied to kernel
Misc: Battery percentage
Misc: Date and time are correct after reboot (go to flight mode before)
Misc: Online charging (Green charging symbol, percentage increase in stats etc)
Misc: SD card detection and access
Sensors: Automatic brightness
Sensors: Rotation works in Phosh
Sensors: Touchscreen registers input across whole surface
Sound: Loudspeaker, volume control ok
Sound: Microphone, recording works
Sound: System sounds and effects plays correctly (Camera shutter, Screenshot taken, Notifications)
USB: SSH access (ssh [email protected])
WiFi: Driver loaded at startup (see instructions for first boot, otherwise works)
WiFi: Enable/disable and flightmode works
WiFi: Hotspot can be configured, switched on and off (network is working, no internet access)
WiFi: Persistent MAC address between reboots
Working with additional steps
Cellular: Data connection (Please, see the Instructions on enabling mobile data)
Cellular: Enable/disable mobile data
Cellular: Switch connection speed between 2G/3G/4G works for SIM2 (no mobile data)
Cellular: Switch preferred SIM for calling and SMS (no dual SIM support)
WiFi: Hotspot cannot serve data to clients (no mobile data)
Misc: Reset to factory defaults (can be done in recovery)
Not working
Camera: Video (creates an empty .mkv file and freezes; in Waydroid camera functions fully)
Sensors: Fingerprint reader, register and use fingerprints (fingerprint sensor just wakes up screen)
Misc: Shutdown / Reboot (phone hangs after both, long press Power button to turn on again)
Misc: Offline charging (Power down, connect USB cable, device boots to Droidian)
GPU: Hardware video decoding (no support yet)
USB: ADB access (use SSH instead: ssh [email protected])
USB: MTP access (use SCP instead: scp your_file_to_copy [email protected]:/home/droidian)
Not tested
Cellular: MMS in, out
Cellular: PIN unlock
Misc: logcat, dmesg & syslog do not spam errors and service restarts
Sensors: GPS
Sensors: Proximity works during a phone call
Sound: Earphones detected, volume control ok
Endurance: No reboot needed for 1 week (let us know if you achieved this)
VoLTE support ?
sunilbanhal said:
VoLTE support ?
Click to expand...
Click to collapse
I don't have that service here in my country, so i can't test it...
UB port for Pocophone f1 doesn't have it yet that means no fo it too !!!!
pimmelbingo said:
hy xda users
i have installed this rom...vodafone mobile
data dont work.....and vodafone wifi germany
dont work to.....the setup for mobile data
web.vodafone.de make me nuts.....please help....
regards
Click to expand...
Click to collapse
did you followed this part of the guide?
Mobile dataMobile data should work, but it needs to be set up manually. The good part is that the configuration is persistent, so you need to do this only once.
Open the Settings app and tap Mobile, then tap Access Point Names
Tap the + in the top right corner of the pop-up
Fill out the textboxes based on your settings in Android. The Name can be anything, e. g., the name of your carrier. The APN is likely some sort of an URL, like internet.carrier.net or something similar. If you didn't see a Username and Password in Android, you can skip these.
In some cases, rebooting your phone or turning mobile data on and off a few times is enough. Otherwise we'll have to give the same settings to oFono as well.
pimmelbingo said:
hy i have set the apn....web.vodafone.de
the setup with ofono is for me to
complicatet...a zip file for flashing
the mobile settings would be great.....
Click to expand...
Click to collapse
Name Vodafone
Internet
APN web.vodafone.de
Proxy: Not Set
Port: Not Set
Username: Not Set
Password: Not Set
Server: Not Set
MMSC Not Set
MMS Proxy : Not Set
MMS Port: Not Set
MCC: 262
MNC : 02
Authentication Type: Not
Set
APN type default
APN protocol: Ipv4
Ipv4
APN roaming protocol:
Ipv4
Enable/disable APN:
APN Enabled
Bearer: Unspecified
MVNO type: None
MVNO Value: Not set
Awesome job thank you can't wait for stable version.
BTW is there anyway to record phone calls?
pimmelbingo said:
Hy
i have changed some settings in advance" network " 4g mobile data vodafone germany works
only one question how can i disable ore remove some apps?
how to run the beryllium-extras.sh..........??????????????
Thanks
Click to expand...
Click to collapse
in terminal run the command
Deleted
pimmelbingo said:
big problem is the mobile settings .....
after reboot or turn off gone lost.....
Click to expand...
Click to collapse
you lose mobile data after reboot?
Any new update coming up?
SyntaxError said:
Any new update coming up?
Click to expand...
Click to collapse
Unfortunately i don't think so, it's almost all working so don't really need a update and base it's updated from droidian itself
Hello,
Thanks for porting this device!
I would like to build the source. I'm trying to do it with droidian releng tools, but getting some build errors. I guess the reason is the toolchain version. Can you tell me wich toolchain (gcc or clang) and which version is needed?
Best regards!
Hello,
I have been able to solve the problem.
Some vdso modules are 32 bit, so also is needed the arm32 toolchain and pass it to make with CROSS_COMPILE_ARM32 var.
Best regards!
Related
Please Observe the Note about Gapps/Recoveries in the Downloads Section.
GSM'rs Please read message 1977 BEFORE complaining about SMS Texting. Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod 11.0 is a free, community built distribution of Android 4.4 (Kit Kat) which greatly extends the capabilities of your phone and increases performance and reliability over "stock Android" for your device.
Code:
* Your warranty is now void.
* We are not responsible for bricked devices, dead SD cards,
* or you getting fired because the alarm app failed. Please do
* some research if you have any concerns about features included
* in this ROM before flashing it! YOU are choosing to make these
* modifications, and if you point the finger at us for
* messing up your device, we will laugh at you.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked near the bottom of this post is a package that has come from another Android project that restores the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Features:
CM11.0
Koush's SuperUser as default (built in)
Android KitKat 4.4.4
Root
Apollo
CM's "File Manager"
cLock Widget
Quick Settings Panel
Swipe option for Quick Settings
Quick Pull-down option for Quick Settings
Notification Drawer Quick Access Ribbon
New CM Wallpapers
Theme Engine
Scroll typed text with vol -/+
Multi Language Support
Whisper Push
Zipaligned
All images optimized
Whats Working:
Alarm/Clock/Countdown Timer/Stop Watch
Audio (alarm, music, ringtones, ui)
Automatic Screen Rotation
Battery Stats
Bluetooth Calling and Streaming
Bluetooth Tethering
Camcorder - see below
Camera
Count Down Timer
Data (3g/4g LTE)
Data Transfer Arrows
Developer Options
Display (for the most part. See not working for further details)
Exchange E-Mail
Google Sync: Account/Calendar/Contacts
Gallery
Google Voice Typing
GPS
Hangouts (Gtalk replacement)
HD Video Playback
LEDs
Mms (sending/receiving)
Performance Controls
Phone (making/receiving calls)
ScreenShot
Security (Blacklisting /Privacy guard /Screen Lock)
Signal Bars and dBm signal strength
Simultaneous Voice and Data
Sms (receiving /sending)
Sms messaging via hangouts (new integrated sms ability)
Sound Recorder
Stereo Sound Headphones (some static present when screen comes on and goes off)
Stereo Sound (rear speaker)
Storage (external /internal)
Superuser
Swipe Keyboard and Auto Correct
Terminal Emulator
Torch/Torch Toggle
USB Mass Storage (Access via pc connection): External /Internal
USB Tethering
Vibration (calls , haptic feedback, notifications)
Vibrator Intensity settings
Video Chat (ie: Skype, Hangouts, etc.)
Video Playback (Youtube, Camcorder)
Voice Dialer
Voice Search
Live Wallpapers /Wallpapers
Weather from network location
Widgets
WiFi
WiFi Hot Spot (native WiFi tethering)
Youtube App/streaming video
What's Not Working:
Netflix: However, there is a workaround for this via use of the Xposed module: [Xposed][HACK] Workaround for Netflix This was discovered by member @hochoch. Thanks be to him. I have attempted to place the install instructions here. However, IF you feel confused please refer to the Workaround site.
To install:
Download and Install the Xposed Installer APK http://dl.xposed.info/latest.apk.
... > move to the dir containing the file
... > adb install de.robv.android.xposed.installer_v32_de4f0d.apk
You will be asked if you will allow this. Say yes.
Switch to the phone and the app directory. Install the Xposed framework:
... Find Xposed Installer... Tap it... Tap Frameworks... Tap ok... Tap Install/Update...
. . select Remember choice forever... Tap Allow... Tap ok to ReBoot
Download and Install the APK linked in this post: linked apk
... > move to the dir containing the file
... > adb install XposedCM10.1NetflixWorkaround.apk
Startup the Xposed Installer... Tap Modules.. Tap the check box.. Tap ret key twice
After enabling the module in Xposed Installer ... Reboot your phone. Enjoy Netflix.
If your PC hangs on one of the adb install commands... look at your phone and Tap the OK.
And this works on our CM11.0 (4.4.4) xposed-framework
Click to expand...
Click to collapse
Bluetooth Calling: It's hit or miss. Either doesn't work for some, or has bad quality for others.
Bluetooth will NOT "turn on" our ReZounds. Hardware is not designed for it. In order to make a "Hands free call" you must at least "Activate" the phone. Only has to show the "Lock Screen". Then your Bluetooth must be of the type that has a "Button" you can press to activate voice calling. Mine is a Plantronics Pro and the sequence goes like this:
Naturally your Bluetooth and phone have to be paired.
Push Power Button on Phone.
Push or Press your Bluetooth button.
Listen for command request.
Recite the name in your call list you desire to call.
Hope that the voice to text translation was correct...
MHL/HDMI: This most likely will never work on AOSP and should be considered a "don't hold your breath"
Camcorder: Built in one will scramble the pic IF started in portrait mode. Horizontal mode works ok. However, in both modes you can only get 3 video saves and then you have to reboot to get another 3. Repeat.
Installation InstructionsI recommend users of this rom to be on the latest firmware and Hboot with an s-off device. If you are not on the latest global firmware: Here or Here.
NOTE: For recovery I use CWM Touch 6.0.3.6 but you can also use TWRP. Some wipe options below may not be included in other recovery options. Still wipe what is available the best you can.
1. Put the Rom on the root of your SD Card
2. Compare MD5 Sum
Windows: MD5 Calculator
LINUX: Open Terminal and type: md5sum [path to the rom on your sd card]
Mac: Open a terminal and type: md5 [path to the rom on your sd card]
3. Reboot to Recovery
4. Scroll down and select "Wipe"
5. Wipe the following:
Wipe ALL data/factory reset
Wipe /data
Wipe /cache
Wipe Dalvik-cache
Wipe /boot
Wipe /system
Optionally wipe:
Wipe battery stats
Wipe rotate settings6. Scroll to and press return
7. Install Rom from SD Card
8. Reboot and enjoy!
Further questions about the ROM
Please check the FAQ in the second post.
Note: Please do not mirror the Rom. Thanks.NOTICE: I do not provide a changelog. However, you may view the official CM changelog by clicking CHANGELOG (Not yet available for cm-11.0)To those complaining about Battery usage, please view message: 2429
The Battery tests have been updated: Sep 7th, 2014Downloads:
ROM: DOWNLOAD
----------------------------------------------------------------------------------------
4.4.4 GApps: gapps-kk-20140620-signed.zip
4.4.4 BaNkS GApps: GApps from BaNkS
4.4.3 GApps: gapps-kk-20140606-signed.zip
4.4.3 BaNkS GApps: GApps from BaNkS
Check out the message 2322 for a proper TWRP and CWM to install the "Standard" Gapps.
Thank You to the following individuals for their heavy involvement in making Kit Kat possible for the HTC Rezound and for their continued efforts to improving the platform (in Alphabetical Order):
Flyhalf205 -Donate
kkozma - Donate
_litz - Donate
REV3NT3CH - Donate
Snuzzo - Donate
TheBr0ken - DonateSource:
Google - Android
Cyanogen - Source
Vigor - Beta builds
Vigor - Kernel
Please note that CM-11.0 is super fresh and no where ready for prime time action. However, it is stable enough to use daily. Over time, the CyanogenMod team will add back features that are currently missing and adding some never before available as development continues.
Please see post two for additional notes.
Frequently Asked Questions
HTC Rezound UNOFFICIAL CM11.0 (KK-4.4.4)
This is a short list of Q&A that should help you find answers to the questions you might have concerning flashing and using this ROM.
[SIZE=+1]Q1: What version of Android is this?[/SIZE]
This Rom is CM11.0 which is currently built on Android 4.4 "Kit Kat"
[SIZE=+1]Q2: Lost root?!? Built in Superuser doesn't work?[/SIZE]
Go into Developer options and change Root access to "Apps and ADB"
[SIZE=+1]Q3: Is this ROM S-On compatible?[/SIZE]
By default, no. Follow these instructions to flash on an S-On device:
NOTE:
You must have the Android SDK downloaded and installed onto your computer.
You must be familiar with the SDK's install directory structure.
You must be familiar with using terminal and know how to cd to the platform-tools folder of the Android SDK's install directory.
1. Open the Rom zip with an archive tool such as 7zip and extract the boot.img from it.
2. Place the boot.img into the platform-tools folder of the Android SDK's install directory.
3. Put the Rom and GAPPS on the root of your SD Card
4. Compare MD5 Sum
Windows: MD5 Calculator
LINUX: Open Terminal and type: md5sum [path to the rom on your sd card]
Mac: Open a terminal and type: md5 [path to the rom on your sd card]
5. Reboot to Recovery
6. Scroll down and select "Wipe"
7. Wipe the following:
Wipe ALL data/factory reset
Wipe /data
Wipe /cache
Wipe Dalvik-cache
Wipe /boot
Wipe /system
Optionally wipe:
Wipe battery stats
Wipe rotate settings
Click to expand...
Click to collapse
8. Scroll to and press return
9. Install Rom and gapps (in that order) from SD Card
11. Return to the main menu of the recovery and select "Developer Menu".
12. Select "Reboot to bootloader
13. Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
14. Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
15. Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
16. Watch the output of the terminal, it should say something like "sent successfully".
17. Finally send this command:
Code:
fastboot reboot
This command reboots your device into Android. Wait for it to boot up and enjoy your new freshly installed CM10.12
Note: If you are having issues connecting your device to your windows computer in fastboot, please insure the drivers are up to date by installing the latest version of HTC Sync for the Rezound.
[SIZE=+1]Q4: Where did the Developer options in settings go?[/SIZE]
Google/Android has hidden this feature in JB 4.x+ and up. Follow these steps to re-enable the feature:
Go to settings > about phone. Tap Build Number 7 times. Tapping Build Number 7 times re-enables the Developer Options in settings.
[SIZE=+1]Q5: Where did the reboot menu go?[/SIZE]
In Android 4.4 this menu is hidden by default in CM11.0 and must be enabled.
Step 1: Enable Developer options using the method described in Q4.
Step 2: Go to Developer options and check the Advanced reboot box.
Step 3: Go to System settings > System > power menu. Insure the Reboot menu box is checked.
Click to expand...
Click to collapse
[SIZE=+1]Q6: What is the recommended HBOOT and Radio for this ROM?[/SIZE]
RADIO: 2.23.10.0123r, 2.23.10.0124r
HBOOT: 2.28
Click to expand...
Click to collapse
If your device is not using this firmware and HBOOT, its very simple to update. Just follow the guide [URL=" http://forum.xda-developers.com/showthread.php?t=2509770 [/URL] to get updated.
[SIZE=+1]Q7: Is this ROM GSM compatible?[/SIZE]
Yes. You must enter Mobile Networks and change preferred network list to GSM.
[SIZE=+1]Q8: Why isn't my WiFi working?[/SIZE]
You're most likely s-on then. You must flash the boot.img that comes with the .zip inside of fastboot.
[SIZE=+1]Q9: What recovery is recommended?[/SIZE]
ClockworkMod 6.0.3.6 or higher... TWRP 2.6.0.1 or higher...
[SIZE=+1]Q10: I can't mount my phone to my computer as a mass storage device. How can I manage my internal/external storage with my computer?[/SIZE]
If you have the most recent HTC drivers installed and are still experiencing issues, reboot into your recovery, and try mounting your storage that way. If you are still having issues, try a different cable, USB port, or computer. Lastly, try to avoid using an external USB hub. Those may cause issues, as well.
Please be smart and use the search bar first before posting any questions...
【ROM】【4.4.4】【UNOFFICIAL】CyanogenMod 11.0【06-30-14】【GPL】【HYBRID】
Reserved
Thank you!!
Flashing with twrp is ok?
Sent from my ADR6425LVW using Tapatalk
For those of you who wish to contribute to it's progress and may not be as code or tech savvy, feel free to look over the things that are "untested" in post number 1 and let the rest of us know if it works or not!
This helps a lot so thank you.
-Neo
bbgreen said:
Thank you!!
Flashing with twrp is ok?
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
I believe so. Although I'm unsure of what version may/may not be compatible as I do not use it. FlyHalf would be the best person to answer this.
IAmTheOneTheyCallNeo said:
I believe so. Although I'm unsure of what version may/may not be compatible as I do not use it. FlyHalf would be the best person to answer this.
Click to expand...
Click to collapse
I use 2.6.3.0 with no issues
kkozma said:
I use 2.6.3.0 with no issues
Click to expand...
Click to collapse
as i used 2.6.3.3
I want to try it so bad, but I need the browser and camera... I'll wait until it's awesome!
Sent from my Rezound using Tapatalk
I used 2.6.3.0 from here : http://goo.im/devs/OpenRecovery/vigor
Just make sure you properly wipe/etc if doing a clean install, and after any "dirty flash", wipe dalvik and cache before you reboot.
Is this ion based?
Sent from my ADR6425LVW using Tapatalk
mavpts said:
Is this ion based?
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
No
---------- Post added at 09:00 PM ---------- Previous post was at 08:51 PM ----------
For any and all gsm users installing this...there is a few trick to get things working and we are still working on this. I may also do my best to release a pure gsm version of 4.4 for our device
does art work or are we to stay on dalvik?
PMEM vs. ION
mavpts said:
Is this ion based?
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Forgive my ignorance on this one, but I simply don't know enough about it to reason this out for myself. Can you guys get an ION version booting? The reason I ask is because I remember the reason you guys stuck with PMEM was because you still had the ability to use the camera/camcorder with that type of memory management. Would building with ION alleviate any of the existing problems since that's more or less the direction that Android wants to take memory management? I'm sure you guys had already thought of all of this, just curious if there was any advantage in trying to get it built with ION (and admittedly it's a selfish "want to know" on by behalf). Congrats and thanks to Fly, Litz, Rev, Neo, KKozma, TheBroken and everybody else responsible for getting this done. It's been awesome to watch you guys work.
Also Bluetooth streaming works. Not sure about bluetooth calling though.
I don't think any of us have tried ion with cm11 yet. I did build cm10.2 ion and it boots, but the camera doesn't work at all.
That said, I am going to give the old college try on using a different display hal for cm11 which requires ion. There's a very small chance it could help with the camera, but don't hold your breath.
iamwalterwhite said:
Forgive my ignorance on this one, but I simply don't know enough about it to reason this out for myself. Can you guys get an ION version booting? The reason I ask is because I remember the reason you guys stuck with PMEM was because you still had the ability to use the camera/camcorder with that type of memory management. Would building with ION alleviate any of the existing problems since that's more or less the direction that Android wants to take memory management? I'm sure you guys had already thought of all of this, just curious if there was any advantage in trying to get it built with ION (and admittedly it's a selfish "want to know" on by behalf). Congrats and thanks to Fly, Litz, Rev, Neo, KKozma, TheBroken and everybody else responsible for getting this done. It's been awesome to watch you guys work.
Click to expand...
Click to collapse
As this is still very new even to the cyanogen source...many things are still being pushed to cm11 as well as commits...it will all be ironed out in PMEM soon...ION will take some time
Doh. Stupid double post
So far so good, usb tethering works, alarm, stopwatch and countdown timer work as well.
i have noticed if i change runtime to art i get fc of gmail, gapps and a few other apps, it is in a loop to so only fix was to turn back runtime to dalvik.
other than that keep up the great work! all the devs here are a joy to be apart of this community
update - Also i have been a rom toolbox user since the beginning and it has always worked, but in this rom i am unable to uninstall apps, i can freeze them tho, just thought id share
mavpts said:
Also Bluetooth streaming works. Not sure about bluetooth calling though.
Click to expand...
Click to collapse
Blue tooth calling works.
Sent from my ADR6425LVW using Tapatalk
{
"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"
}
About the Rom:
http://slimroms.net/
https://plus.google.com/communities/104509876514579429216
Build has been optimized using JustArchi's ArchiDroid Optimizations - Unleash the power!
As written by Archi
- Optimized for speed yet more all instructions - ARM and THUMB (-O3)
- Optimized for speed also parts which are compiled with Clang (-O3)
- Turned off all debugging code (lack of -g)
- Eliminated redundant loads that come after stores to the same memory location, both partial and full redundancies (-fgcse-las)
- Ran a store motion pass after global common subexpression elimination. This pass attempts to move stores out of loops (-fgcse-sm)
- Performed interprocedural pointer analysis and interprocedural modification and reference analysis (-fipa-pta)
- Performed induction variable optimizations (strength reduction, induction variable merging and induction variable elimination) on trees (-fivopts)
- Didn't keep the frame pointer in a register for functions that don't need one. This avoids the instructions to save, set up and restore frame pointers; it also makes an extra register available in many functions (-fomit-frame-pointer)
- Attempted to avoid false dependencies in scheduled code by making use of registers left over after register allocation. This optimization most benefits processors with lots of registers (-frename-registers)
- Tried to reduce the number of symbolic address calculations by using shared “anchor” symbols to address nearby objects. This transformation can help to reduce the number of GOT entries and GOT accesses on some targets (-fsection-anchors)
- Performed tail duplication to enlarge superblock size. This transformation simplifies the control flow of the function allowing other optimizations to do a better job (-ftracer)
- Performed loop invariant motion on trees. It also moved operands of conditions that are invariant out of the loop, so that we can use just trivial invariantness analysis in loop unswitching. The pass also includes store motion (-ftree-loop-im)
- Created a canonical counter for number of iterations in loops for which determining number of iterations requires complicated analysis. Later optimizations then may determine the number easily (-ftree-loop-ivcanon)
- Assumed that loop indices do not overflow, and that loops with nontrivial exit condition are not infinite. This enables a wider range of loop optimizations even if the loop optimizer itself cannot prove that these assumptions are valid (-funsafe-loop-optimizations)
- Moved branches with loop invariant conditions out of the loop (-funswitch-loops)
- Constructed webs as commonly used for register allocation purposes and assigned each web individual pseudo register. This allows the register allocation pass to operate on pseudos directly, but also strengthens several other optimization passes, such as CSE, loop optimizer and trivial dead code remover (-fweb)
- Sorted the common symbols by alignment in descending order. This is to prevent gaps between symbols due to alignment constraints (-Wl,--sort-common)
Click to expand...
Click to collapse
Sources:
Slim: https://github.com/SlimRoms
SlimLPXperia: https://github.com/SlimLPXperia
How to install :
- Download the ROM
- Extract boot.img and flash it
- Copy the ROM to your SD Card
- Boot into recovery
- Wipe data, cache, dalvik cache, system (Wipe -> Advanced Wipe)
- Install the ROM (it will take some time)
- Bootup
- Reboot into Recovery
- Install Gapps
Click to expand...
Click to collapse
Credits:
@munjeni: Kernel, porting Android Kitkat to Xperia 2012 devices and bugfix
AOSX team: For their work on Xperia 2012 devices
Agontuk: For patches
HubDroid: For providing server
Downloads:
http://builds.hubdroid.com/SlimLP/final/pepper/
CM 12/12.1 Gapps
Changelog:
Gerrit Code Review
Code:
[SIZE="4"][B]Slim 5.1[/B][/SIZE]
Slim weekly 2 (20/05/15)
- Slim version Alpha 0.2
- Source updates
Slim Build Alpha 1.0 (13/05/15)
- AOSP 5.1
- JustArchi's ArchiDroid Optimization V4
- Kernel compiled with Sabermod toolchain
- Enabled SELinux thanks to HandyMenny
- Enable USB OTG storage options
- Device and kernel updates
- TWRP 2.8.6.0
- Slim Source updates
[SIZE="4"][B]Slim 5.0[/B][/SIZE]
Slim Build Alpha 1.0 - Build 2 (24/02/15)
- Keep InCallUI in memory for faster response times
- Source cleanup and updates
- Kernel updated
- Enabled kernel recommended configurations
- Fixed some logcat errors
Slim Build Alpha 1.0 (19/02/15)
- Fix Camera
- Fix Media Sound
Slim Build Alpha 1.0 (17/02/15)
- Complete RIL fix
- Enable KSM
- Enable zRam
- Reduce lag and improve performance
- TWRP 2.8.5.0
- Bluez 5.28
- Updated Slim sources
- Source tree updates from XperiaSTE
Slim Build Alpha 0.8 (10/12/14)
- Partial RIL fix
Slim Build Alpha 0.8 (09/12/14)
- AOSP 5.0.1
Slim Build Alpha 0.6 (02/12/14)
- initial build
F.A.Q.
1) How to increase system memory?
Follow the instructions at this thread to create a swap file http://forum.xda-developers.com/showthread.php?t=2359182
I have found the recommended configurations to be quite effective, Only one swap file of the recommended size i.e. about 188MB will fix many things.
What's working and what's not
Working
RIL / Mobile Data
Camera
Torch
Mic
Audio
Vibration
Auto Brightness
SD Card
Airplane Mode
LEDs
WiFi
Auto Rotation
System Monitor
Bluetooth
Audio recording
TWRP Recovery
Reboot to recovery
Not Working
Camera Video Recording
FM Radio
NFC
WiFi direct
A2DP(media over A2DP)
That's even bettere than aosx 5.0 Thanks again! :good::good::good::good:
Wow, fix mobile data and we're right where SlimKat stopped
wow looking forward to this rom dev
Pushed a little update to latest AOSP, and Gapps
minfree values are set very high by default, to make keyboard usable use these values or lower them as desired.
Connect device in adb,
1. adb shell
2. echo "2048,3072,11520,16640,24320,42240" > /sys/module/lowmemorykiller/parameters/minfree
Click to expand...
Click to collapse
alwaysadeel said:
Pushed a little update to latest AOSP, and Gapps
Click to expand...
Click to collapse
Flashing gapps failed when trying to flash it in the same cycle as SlimLP. It says
Installing files...
Cleaning up and setting metadata...
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/external_sd/Download/SlimLP/Slim_mini_gapps.BETA.5.0.x.build.0.x-416.zip'
Error flashing zip '/external_sd/Download/SlimLP/Slim_mini_gapps.BETA.5.0.x.build.0.x-416.zip'
It worked when doing this sequence: flash ROM, reboot, flash gapps. I guess this is needed only on a first install.
Booting up now... will share my experiences soon.
mstreibe said:
Flashing gapps failed when trying to flash it in the same cycle as SlimLP. It says
Installing files...
Cleaning up and setting metadata...
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/external_sd/Download/SlimLP/Slim_mini_gapps.BETA.5.0.x.build.0.x-416.zip'
Error flashing zip '/external_sd/Download/SlimLP/Slim_mini_gapps.BETA.5.0.x.build.0.x-416.zip'
It worked when doing this sequence: flash ROM, reboot, flash gapps. I guess this is needed only on a first install.
Booting up now... will share my experiences soon.
Click to expand...
Click to collapse
try this gapps http://fitsnugly.euroskank.com/?rom=banks&device=gapps
Ril and mobil data is the important think, hope you guys fix it soon. May God help you
My first SlimLP steps
1) First boot took >5 min.
2) Problems with the setup assistant:
Activating cellular service doesn't succeed, I guess this is because of RIL not working yet, right?
Wifi setup worked.
Afterwards it stays a long time in "Checking connection...".
Adding the google account FCs after entering the first char of my password. The setup assistant then goes back to the language/country selection. I tried without signing in to google but it restarts nevertheless.
The only other thing besides the setup assistant that I could reach was the settings via the status bar. Here I could sign in to my google account, but it worked only when typing the password chars very slowly.
After that I had to go once more through all the setup assistant steps, to finally get to the home screen.
3) App download and installation in google play is very slow, and it is not my Wifi connection. File transfers via file manager are as fast as usual.
4) In "settings -> apps -> running" it shows all apps except the foreground app permanently restarting, with ca. 140 MB free RAM. Is this due to the high minfree values? I don't have an adb at hand so I installed android terminal emulator and set the minfree values with it, but it didn't seem to help. I also installed PerformanceControl but it FCs when trying to navigate to the memory settings.
5) Many if not all Slim customizations are missing.
6) Changing lcd_density in build.prop didn't seem to have an effect.
7) Overall UI performance wasn't all that bad.
Going back to SlimKat now because I need to use my phone
Looking forward to the 1.0 release...
cant turn debug mode on cause i cant set up my device after google acc registration my phone goes back to the beginning
what to do ? 0_o
thx in advance
AgroCPU said:
cant turn debug mode on cause i cant set up my device after google acc registration my phone goes back to the beginning
what to do ? 0_o
Click to expand...
Click to collapse
If you succeeded with the google account, just go through the setup process again. It went through the end afterwards here.
cant go trough google acc -__-
is it possible to turn usb-debug on via init.d script?
AgroCPU said:
cant go trough google acc -__-
Click to expand...
Click to collapse
Can you describe what goes wrong? I had issues too, see my post #11. The registration always failed when trying to enter the account password. At one point it worked, though, when I typed the PW very slowly, waiting a sec or 2 between each char.
BTW at some stage during the setup I was able to enter the settings via the status bar. I think it was right at the time when it jumped back to start. There you could enable the developer options and enable USB debugging.
mstreibe said:
Can you describe what goes wrong? I had issues too, see my post #11. The registration always failed when trying to enter the account password. At one point it worked, though, when I typed the PW very slowly, waiting a sec or 2 between each char.
Click to expand...
Click to collapse
i cant enter my gmail acc (email-adress)
AgroCPU said:
i cant enter my gmail acc (email-adress)
Click to expand...
Click to collapse
This worked for me, it failed when it asked me to enter the PW.
Does the dialog open for you, but when you start typing your email address it jumps back to the language setup?
Did you try typing very slowly?
Did you check if you can enter the settings via the status bar?
mstreibe said:
This worked for me, it failed when it asked me to enter the PW.
Does the dialog open for you, but when you start typing your email address it jumps back to the language setup?
Did you try typing very slowly?
Did you check if you can enter the settings via the status bar?
Click to expand...
Click to collapse
when i want to type one letter it jumps back to the language setup -__-
and nope i cant enter settings
AgroCPU said:
when i want to type one letter it jumps back to the language setup -__-
and nope i cant enter settings
Click to expand...
Click to collapse
Did you try with german language? Try English(US). That's what I did. And do the inputs very slowly. When the input field appears, wait a sec or 2 before typing, and wait again between each character.
It's a pain I know, especially as it is for testing only. Maybe wait for the 1.0 release
i tried this.. well, very buggy due to initial release .. my steps are :
- Wipe everything needed.. use a kernel with 'Sony Xperia Sola' device name (not MT27i). Kitkat Kernels are fine..
- Install the ROM first.. then reboot the phone. wait for the Android upgrade/build cache
- After its done, reboot and flash the LP Gapps. Then reboot..
- Done.. (well.. my navbar is broken so.. i edited the build.prop via PC and voila.. ohh, i dont recommend you to use this rom for everday use..
Android Lolipop 5.1
Let’s emphasize that-- THIS IS AN ALPHA, RELEASED FOR YOU TO PLAY WITH AND GET A SENSE OF WHAT’S TO COME. AND SOME THINGS DOESN’T WORK. REALLY. IF YOU ARE EXPECTING ANYTHING CLOSE TO PERFECTION, WALK AWAY FROM YOUR COMPUTER, LOWER YOUR EXPECTATIONS FOR AN HOUR OR SO, THEN COME BACK. MORE EXCITING DISCLAIMERS/WARNINGS IN ALL CAPITAL LETTERS CAN BE FOUND BELOW. READ THEM.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
KNOWN BUGS (what doesn't work):
- Modem in 2G mode work incorrect(Network registration don't work with some SIM cards, permanent full signal straight, problem is with audio in calls)
With 3G all is OK, Use this: Settings -> More.. in "wireless&network" category -> Mobile Network -> Preferred Network type -> 3G only
- Conference Calls
- Some problems with audio codec settings, but generally it should
- After Recovery time to time incorrect capacity of battery
- disabled SELINUX
- Camera key don't start camera app
- TV out removed, because it is not working yet
- many custom features from omni is still not merged
SUPPORT
You get none. Zero. Zip. We obligate ourselves to providing nothing further. You are on your own and will have to help each other via this thread. This is provided “as-is”, and if you don’t like it, use Bada or other releases.
We basically lack time to give full dedication to this rom, and we’re looking for skilled devs who know the Android, and/or other things that might be relevant.
Please join us on IRC: some people are on #badadroid (freenode).
NOTE: DEVELOPERS WANTED. Please contact us if you are a developer with something to contribute.
I do heavily encourage to work together on the better, common project instead of making kang releases and demanding money for somebody else's work.
Read as: If you think you can make something better than this by doing less and muchazo Ctrl+C Ctrl+V - you suck, go figure the rest.
INSTALLATION
FIRST INSTALLATION
Bada 2.0 is required
Warning! It will remove Bada!
Download BOOTFILES, Kernel and FOTA for your device:
for 8500:
BOOTFILES https://yadi.sk/d/KhxqKyg4bP2nu
"start" kernel https://yadi.sk/d/ilhyKTaEfTo6L
FOTA https://yadi.sk/d/OtpVoaXpfNggE
for 8530
BOOTFILES https://yadi.sk/d/cBPD41VEbP2od
"start" kernel https://yadi.sk/d/wVGzUA96fGW55
FOTA https://yadi.sk/d/-WnbHbFHfNgZK
Flash BOOTFILES, "start" kernel and FOTA using Multiloader.
After reboot it will open android recovery
Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
Wait before on screen you will see "Partitions had been prepared"
Back -> Back -> Back -> Reboot -> Recovery -> Swipe to Reboot
Mount -> Enable MTP (if you see disable MTP - it is already activated) on this step PC can ask to install driver, use Android MTP driver
Copy Zip with ROM to Internal Storage or Sdcard -> Disable MTP -> Back
Install -> choose zip with ROM(mount point /sdcard for Internal storage and /external_sd for SD card) -> Swipe to Confirm Flash
Wait for flashing (about 10 min) -> Reboot System
First start take about 10-15 min, be patient.
Enjoy OMNI!
You can remove installation .zip from Android level by connecting through USB in MTP mode.
TWRP Recovery mode is available using VolUp + End keys
Every next update you can just flash .zip through CWM.
UPDATE from OMNI 4.4 (version after 09.09.2014)
Warning! you will lose all data, because it is highly recommended to wipe data, during changing rom base
- Go to Recovery
- Wipe -> Advanced wipe -> check "data" and "system" -> Swipe to wipe -> waiting for wipe -> Back
- Mount -> Mount USB storage
- Copy zip with Rom from PC -> Unmount -> Back
- Install -> choose zip with ROM -> Swipe to Confirm Flash -> wait for flashing (about 10 min) -> Home
- Reboot -> System
For activation Performance and Developer Options categories in Settings you need Settings->About Phone and tap 7 times on Build number
ROOT
Omni is without root support from default
To activate root flash zip via Recovery from XDA thread http://forum.xda-developers.com/showthread.php?t=1538053
GAPPS
GAPPS make our ROM slowler, because also slim GAPPS take about 15-20 MB RAM permanently
https://mega.co.nz/#F!G0QXXRAC!pZ063qCaa5lxdD73SarU6Q
HOW TO UNINSTALL
Just reflash bada via Multiloader
CHANGELOG:
22.03.2015 https://yadi.sk/d/UAs4xDLlfTm4U
Warning! You need updated FOTA!!!
- Omni sorces 22.03.2015 Android-5.1
- Updated Zram driver
- And many other fixes to make our Wave more stable on Android-5.1
07.02.2015 https://yadi.sk/d/SeW7BBgkeXqZz
- Omni sorces 07.02.2015 + some chery-picks from gerrit
- fixed front camera
- fixed flashlight tile in Quick Settings
- updated Wi-Fi driver
- Added F2FS driver, not tested by me yet (just change file system during format /data in recovery to F2FS and it should work)
27.01.2015 https://yadi.sk/d/7sK0awO7eHWbM
- Omni sorces 27.01.2015 + some chery-picks from gerrit
- updated sensors
15.01.2015 https://yadi.sk/d/JyRL5wqfe26xo
- Initial release
- Omni sorces 15.01.2015 + some chery-picks from gerrit
THANKS TO
Special thanks to Rebellos for his CM10 ROM, for his good sources and many time, what he spent for my learning
Another Badadroid devs: Oleg_k, mijoma, nbates66, anghelyi, mikegapinski, hunktb, autra, Tigrouzen, Benzox and many others.
OMNI team for base ROM
Pawitp, kasper_h and all other aries developers
Paulk and Replicant project for good base for bada-modem RIL
and many other who help us.
BUG REPORTS
This is the format for a bug report: “XXXXX isn’t working. Here is how to fix it: [INCLUDE SOLUTION]” Don’t have source? Too bad.
You’ll have to wait then.
If you report bugs, please don’t be disappointed if we can’t fix them immediately (or even never). It’s not because we don’t care, but because we don’t have time or don’t know how to fix it.
Please attach logcat and dmesg dump in your bug report. Dmesg should contain messages from both - bootup and issue occuring (you can't dump it 1 hour after bootup, rather 2 minutes after)
How to dump logs - Google for "android logcat dmesg" Or... whatever, here's one of 3204109 methods available.
In the Terminal Emulator enter:
"su"
Accept request for SuperUser access.
"dmesg > /storage/sdcard1/dmesg.txt"
"logcat -b system -b radio -b events -b main -d -f /storage/sdcard1/logcat.txt *:V"
"logcat -b radio -d -f /storage/sdcard1/radiolog.txt *:V"
Download them from phone, archive and upload them.
Privacy warning: Your logcat might contain sensitive information like your IMEI, IMSI, cell stations you were nearby, numbers you called and got calls from and SMS sent and received. If you don't want to publish this info - send them privately to one of developers.
Click to expand...
Click to collapse
Bug reports without logs are completely useless.
well well well , what we got here :highfive: :victory:
you're the best
The Rom is amazing , fast and responsive ,better than omni 4.4 , some little bugs to report
1- Battery save mode won't activate stupid me usb was connected
2- (screen pinning) , you can't unpin it , task manger and back keys won't work together , i'm not sure ..... you must reboot the device
3-when you install apps from sd card , installation keep showing that it is on progress , but when you turn screen to landscape mode , it shows that the apps is installed
volk204 said:
Warning!
you will lose all data
installation take about 10 min, and first boot is also about 10 min or more
Click to expand...
Click to collapse
backed up my data , flashed the rom ,boot , all my data and config are still there
A quick video review :
Thank you very much Volk204
You are simply great Volk204. Congratulations. :laugh:
Awesome work. :good:
Please continue your work and give us a better and stable Lollipop Omni Rom for wave.
Thanks volk204, you are the beast and the best developer
Thanks for continuing to work on this as "old" mobile phone and so little support from Samsung.
You're the only developer that follows the "gap".
Continuous and hopefully not abandon us.
A greeting.
ice_ice said:
The Rom is amazing , fast and responsive ,better than omni 4.4 , some little bugs to report
1- Battery save mode won't activate
2- (screen pinning) , you can't unpin it , task manger and back keys won't work together , i'm not sure ..... you must reboot the device
3-when you install apps from sd card , installation keep showing that it is on progress , but when you turn screen to landscape mode , it shows that the apps is installed
backed up my data , flashed the rom ,boot , all my data and config are still there
Click to expand...
Click to collapse
It is recommend to do full wipe, when you change rom base, duty flash bring many problem. i think it is the reason of not working battery save mode for you.
don't understand problem of screen
volk204 said:
It is recommend to do full wipe, when you change rom base, duty flash bring many problem. i think it is the reason of not working battery save mode for you.
don't understand problem of screen
Click to expand...
Click to collapse
1- stupid me charger was connected ; so every time i activated it goes off
2-it was about screen pinning feature in security settings , once activated (you pinned an app) you can't disable by clicking on overview(recent apps) and back ,so
tried modifying custom keys settings , and tried different combination without help
than i flashed soft key http://forum.xda-developers.com/nexus-s/development/mod-softkeys-ics-jb-roms-t1918632 , and it worked
maybe this feature doesn't support hardware keys , or bug
(see screenshots)
3-Battery draining and voltage controle i noticed this on omni 4.4 the first time
{
"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"
}
there was a big difference between the computed and observed power use
i did some testing on Omni , i played with the voltage control entries , and observing the time in state, i came to this conclusions :
100 Hz and 200 Hz work on the same voltage , seeing that most of time in state are in 100 HZ and in this frequency ,CPU would take more time to accomplish tasks than in 200HZ , it is only logical to reduce the voltage on 100 HZ ,
tried doing that but you can not apply values , without a 3rd party app like Setcpu , kernel bug i don't know .
i played with value and here is the value the phone freeze at it (governors was set to performance , and max value is the freq tested) :
100HZ-750mv 200HZ-800mv 400HZ-875mv 800HZ-1075mv 1000HZ-1175mv
i used 125 mv above this setting , with no freezing or problems :highfive: , but it needs more testing
battery life :good: improved notably
i use interactive with 200HZ-1200HZ , more voltage on 1200HZ but it do tasks in less time than 1000HZ
Mr @volk204 why there is no low frequency like 500HZ 600HZ , rather than jump from 400HZ to 800HZ
4-
Contrary to my thoughts expressed in other thread. Volk204 did not give up and is, again, succeeding to deliver against all the odds. Hats off and big thumbs up. Send this guy some beer.
Thanks!!
Hi volk204, you did a very good job all over from the beginning, and now we have android lolipop on wave devices! isn't that amazing?!
Thank you very much for what you did! You gave the wave another future! "cheers" :good:
Gapps Lolipop
Hi guys, i've found a link for android lolipop gapps (mini, normal, full).
Here you go : Link
Have a good day! :good:
Edit: i just tried to install it for the first time, it is very laggy and reboot much every time it reboots it restart from beginning, we should wait to see why.
Edit 2: Updated link
Majd7667 said:
Hi guys, i've found a link for android lolipop gapps (mini, normal, full).
Here you go : Link
Have a good day! :good:
Edit: i just tried to install it for the first time, it is very laggy and reboot much every time it reboots it restart from beginning, we should wait to see why.
Click to expand...
Click to collapse
I would try with the smallest package available here if i had a wave : http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
Maybe laggy but shouldn't crash (not tested).
BenzoX said:
I would try with the smallest package available here if i had a wave : http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
Maybe laggy but shouldn't crash (not tested).
Click to expand...
Click to collapse
You're right, i didn't search more for that i thought that the minimum is the link i included but what it says just apply for the package and not all.
Thanks for the link i'm gonna test.
Edit: Tested and working great, there is no lag compared to the link i provided!
Hi volk204..
Any updates to this rom..??
First of all, volk204, thanks a ton for all your time and brain, that you engaged for this project. I really appreciate it. :good:
I was just wondering if it was possible to modify camera driver for Omni 5.0 Lolipop to support RAW image capturing ?
@volk204 Turko CFW 10.2 is running on my Samsung Wave device. I flashed bootfiles, kernel and fota. Then I did this: Advanced -> Terminal Command -> Select -> Type "sh partition.sh". When I try to flash the Rom from Internal Storage, It says "E:Error executing updater binary in zip." I don't know why.
m90ultimate said:
First of all, volk204, thanks a ton for all your time and brain, that you engaged for this project. I really appreciate it. :good:
I was just wondering if it was possible to modify camera driver for Omni 5.0 Lolipop to support RAW image capturing ?
Click to expand...
Click to collapse
u Guys are still using waves ?
i bought Galaxy Alpha 50 days ago.
Rom updated
volk204 said:
Rom updated
Click to expand...
Click to collapse
Thanks volk204..
{
"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"
}
Sailfish OS was originally developed for Nokia phones and was named Meego OS. The project was joint collaboration between Nokia and Intel. The project was later dropped by Nokia but Meego enthusiasts picked up the project and continued the Meego project under Sailfish OS and INTEX was the first ever company to officially tie it's phone to Sailfish OS ROM. For further info checkout : https://en.wikipedia.org/wiki/Sailfish_OS and https://sailfishos.org/
This is the Alpha stable release still has many bugs so don't complain about it. Enjoy your newly built SFOS 2.0.5.6 for Xiaomi Redmi 2 device. This is not Android, this is pure Linux similar to Ubuntu based upon libraries from Android.
For Newbies who don't know the difference between Sailfish OS and Android OS respectively a here is a compact difference list:
1. Pure Linux vs Modified Linux kernel
2. A real multitasker vs Naah not so much of multi-tasking.
3. Store sucks vs Tons of Apps
4.Android apps support too. vs Only Android app is supported.
Change LOG (Compact):
1. Kernel Patched for faster bootup.
2. Wlan, BT, MultiSIM, PulseAudio,GPS fixed.
3. Jolla Store is enabled
4. Multi ROM support
Steps:
1. Go to TWRP recovery mode.
2. Wipe All data except media.
3. Flash CM-12.1 for Redmi 2
4. Flash SailfishOS ROM.
5. Reboot the system after wiping Cache/Dalvik Cache.
There you go. Your SFOS 2.0.5.6 is now loaded. To skip the tutorial touch upper left corner of the screen and clockwise till bottom left corner.
To debug and report error open terminal in Linux and type "telnet 192.168.2.15 2323". For Windows probably install telnet related services and libraries and use the same command in cmd prompt.
Bugs:
1. Front Camera doesn't work. Instead switching between them might lead to camera app crash, to resolve it switch back again to front or back cam.(Temporary soln).
2. Media Player will not play song, to resolve it do the following
3. 4G won't work (as of now). My 4G signal is too weak so it didn't work, my bad.(For JIO users : Go to Settings>Cellular Networks>Data Access point : Change Access point name from "jionet" to "www".)
4. Android Apps won't work (as of now)
5. Battery drain leads to bootloop
SFDROID (Android App Support):
How to install (For Linux Users only):
1. Download the RPM files mentoioned here
SFDROID:https://drive.google.com/open?id=0B8I9RnxIQmQea0xxU3puYnc4Ymc
2. Create a folder for these files separately.
3. In your device goto Settings>Developer Settings and set your password and note down the I.P. address for USB if you are using USB for file transfer or Wifi for Wifi file transfer.
4. Now go to the folder where RPM files are located and right click to open terminal
5. Enter scp *.rpm [email protected]"I.P. address for USB/Wifi": (Add colon ":" sign after the I.P. address, also if you are using USB for file transfer, use the USB I.P. Address mentioned in your developer settings and similarly for Wifi)
6. Enter your password you have set previously and file transfer would begin.
7. Now for USB connected phone open a new terminal and type telnet 192.168.2.15 2323 (If this is not the I.P. address for USB you can see the relevant I.P. address as shown in the Developer Settings of your phone and enter the same after telnet except for 2323(port number))
8. Type su
9. Now type cd /home/nemo
10. Type ls to confirm that all files have been transferred successfully.
11. Type rpm -i --force *.rpm
12. Now type reboot
13. After reboot again in the terminal type telnet 192.168.2.15 2323 and type killall surfaceflinger zygote system_server main servicemanager
14. Now run SFDROID and wait for sometime your Android will load.
15. For Wifi connected phone (Make a Wifi Hotspot on your computer and connect to the hotspot for the mobile device, don't use Wireless router, use direct connection b/w computer and mobile) open a new terminal and type ssh [email protected] (Your I.P. address for Wifi as shown in the Developer setiings of your phone)
16. Now type devel-su
17. Now type in your password
18. Now type cd /home/nemo
19. Now type rpm -i --force *.rpm
20. Now type reboot
21. After reboot again type ssh [email protected]
22 Type killall surfaceflinger zygote system_server main servicemanager
Note: Android is bit sluggish and not perfect as a native Android, but hey at least you got your Android running.
Thanks especially to @saidinesh5 for debugging SFDROID and ofcourse other members of #sfdroid on IRC freenode channel
Bootanimation(default):
https://forum.xda-developers.com/redmi-2/themes/mod-sailfish-os-t3561208 thanks to @taalojarvi
Thanks to adeen-s (www.github.com/adeen-s) @saidinesh5, @mal-, @m4r0v3r, sledges and other member of #sailfish-porters IRC channel.
The CyanogenMod and Kernel isn't my proprietary it is the proprietary of CyanogeMod team and @ketut.kumajaya respectively. However the kernel has some changes made in accordance to SFOS and also I have patched it to decrease the boot up time delay.
Download Link:
https://drive.google.com/open?id=0B8I9RnxIQmQeV3VMM1FFU0RzazQ
https://www.androidfilehost.com/?w=files&flid=153058
SFDROID:https://drive.google.com/open?id=0B8I9RnxIQmQea0xxU3puYnc4Ymc
Edit: Now Lollipop bootloader is supported. Tested it and SFOS was able to boot up.
Github : https://github.com/nrdnandan
Wiki-MER: https://wiki.merproject.org/wiki/Adaptations/libhybris/porters
Name : Sailfish OS
Version : 2.0.5.6 (latest)
Kernel : 3.10.49
Release type: User-Release
Build : Stable
Boolader : Lollipop (Here is the link : http://en.miui.com/thread-386154-1-1.html)
CM/Android base: 12.1(wt88047)/5.1.1
GG! Here's an upvote
Great job
nrdnandan said:
This Alpha release still has many bugs so don't complain about it. Enjoy your newly built SFOS 2.0.5.6 for Xiaomi Redmi2 device. This is not Android, this is pure Linux similar to CentOS based upon libraries from Android.
Change LOG (Compact):
1. Kernel Patched for faster bootup.
2. Wlan, BT, MultiSIM, PulseAudio fixed.
3. Jolla Store is enabled
Steps:
1. Go to TWRP recovery mode.
2. Wipe All data except media.
3. Flash CM-12.1 for Redmi 2
4. Flash SailfishOS ROM.
5. Reboot the system without wiping Cache/Dalvik Cache.
There you go. Your SFOS 2.0.5.6 is now loaded. To skip the tutorial touch upper left corner of the screen and clockwise till bottom left corner.
To debug and report error open terminal in Linux and type "telnet 192.168.2.15 2323". For Windows probably install telnet related services and libraries and use the same command in cmd prompt.
Bugs:
1. Front Camera doesn't work.
2. Media Player will not play song, to resolve it do the following:
i). rm -rf /etc/audio_platform_info.xml (similarly for media_codecs_google_video_le.xml,flp.conf, firmware,mixer_paths_qrd_skui.xml)
ii). ln -s /system/etc/audio_platform_info.xml /etc/audio_platform_info.xml (similarly for media_codecs_google_video_le.xml,flp.conf, firmware,mixer_paths_qrd_skui.xml)
Thanks to @saidinesh5sh5, mal, ghosalmartin, Nexit and other member of #sailfish-porters IRC channel.
Download Link:
https://drive.google.com/open?id=0B8I9RnxIQmQeV3VMM1FFU0RzazQ
Click to expand...
Click to collapse
Thanks for the build. Please hide your imei in the screenshot.
Is it multirom bootable as secondary or primary ROM.
Downloading.....
does this support 4g mobile data,i found a phone named intex aqua has sailos with jio 4g support can u port that to enable data
---------- Post added at 12:57 PM ---------- Previous post was at 12:54 PM ----------
2. Media Player will not play song, to resolve it do the following:
i). rm -rf /etc/audio_platform_info.xml (similarly for media_codecs_google_video_le.xml,flp.conf, firmware,mixer_paths_qrd_skui.xml)
ii). ln -s /system/etc/audio_platform_info.xml /etc/audio_platform_info.xml (similarly for media_codecs_google_video_le.xml,flp.conf, firmware,mixer_paths_qrd_skui.xml)
plz tell how to do this
Please reply.
*4G working?
*Android apps working?
ROCKY_ME said:
Is it multirom bootable as secondary or primary ROM.
Downloading.....
Click to expand...
Click to collapse
I have not checked. I will report back to you later
Superraju said:
Please reply.
*4G working?
*Android apps working?
Click to expand...
Click to collapse
they already mentioned this is not andriod rom,so no andriod apps ok
suresh001 said:
they already mentioned this is not andriod rom,so no andriod apps ok
Click to expand...
Click to collapse
It is not true, 4G won't work because ROM doesn't support VOLTE, and as far as JIO goes, it requires 4G and VOLTE for full activation.
Android Apps will work. That is what SFDROID is for.
suresh001 said:
does this support 4g mobile data,i found a phone named intex aqua has sailos with jio 4g support can u port that to enable data
---------- Post added at 12:57 PM ---------- Previous post was at 12:54 PM ----------
2. Media Player will not play song, to resolve it do the following:
i). rm -rf /etc/audio_platform_info.xml (similarly for media_codecs_google_video_le.xml,flp.conf, firmware,mixer_paths_qrd_skui.xml)
ii). ln -s /system/etc/audio_platform_info.xml /etc/audio_platform_info.xml (similarly for media_codecs_google_video_le.xml,flp.conf, firmware,mixer_paths_qrd_skui.xml)
plz tell how to do this
Click to expand...
Click to collapse
I will upload a new version soon, so don't worry about that.
suresh001 said:
they already mentioned this is not andriod rom,so no andriod apps ok
Click to expand...
Click to collapse
Dont comment without any proper informations dude
@nrdnandan @ROCKY_ME
Here's the process for booting SailfishOS as a secondary ROM in MultiROM. Please put appropriate CM zip name and everything else is the same.
https://forum.xda-developers.com/redmi-2/how-to/guide-how-to-boot-sailfish-os-secondary-t3434696
Good news, Lollipop bootloader is supported.
Superraju said:
Dont comment without any proper informations dude
Click to expand...
Click to collapse
The developer mentions in the OP that android apps are not working!
part 1994 said:
The developer mentions in the OP that android apps are not working!
Click to expand...
Click to collapse
Read it again my friend, it is a bug or I may say a non-availability now. Ported phones don't support Android apps straight away, I will make sure in later builds Android apps work.
nrdnandan said:
Read it again my friend, it is a bug or I may say a non-availability now. Ported phones don't support Android apps straight away, I will make sure in later builds Android apps work.
Click to expand...
Click to collapse
I got that from the OP.
Was just responding to that person's query whether android apps are working that is all.
Also the ROM does not seem to boot for me
Wonderful I was waiting for this, had good times with SFOS , but one provided by adeen-s was not booting from LP bootlader. Good to know that this does boot. I will wait for some time.. Let it get a bit stable. (Its still Alpha)
part 1994 said:
I got that from the OP.
Was just responding to that person's query whether android apps are working that is all.
Also the ROM does not seem to boot for me
Click to expand...
Click to collapse
dmesg
part 1994 said:
I got that from the OP.
Was just responding to that person's query whether android apps are working that is all.
Also the ROM does not seem to boot for me
Click to expand...
Click to collapse
i guess you are using Lolipop bootloader?
Why? Custom Super.tar
-Flash system GSI is normal process but Flash Custom Super.tar is not.
Our sources: @xyrn23
https://github.com/ponces/treble_build_pe/releases/tag/v2023.03.29-plus
Note:
》Sync with latest sources of TrebleDroid then no problem with setting UI and swipe from bottom screen to show all icons menu.( Can set any value of Smallest width dp.)
》Why FW XXU1CWA2 ?
-it's the last Firmware for T220 & T225 which can downgrade.
= The T220.T227 can't uses my "Custom super.tar"
SM-T225
( XXU1CWA2 )SM-T220
( XXU1CWA2 )odm.img 4349952odm.img 4349952product.img 1238544384product.img 1234505728vendor.img 652824576vendor.img 640036864super.raw 6094323712super.raw 6023020544
-------------------------
☆☆☆ Howto install?
1. Flash Firmware "T225XXU1CWA2" with Odin.> connect internet reboot then enable "OEM unlocking" + "USB debugging" + configure update Magisk.
(update 3in1.tar with Magisk v.26.1)<- Download from Attachment below
{
"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"
}
2.Flash "super.tar" at AP Slot. [ PixelExperience_Plus_arm64-ab-vndklite-13.0-20230329]
4.94 GB file on MEGA
mega.nz
☆☆☆- you will get "Pixel Experience Plus 13.0" with R/W Super Partition ( can modify "Product" "System" "Vendor") plus frees up a same amount of free space in /system or different ones =150 MB/each.
☆☆☆-Auto Screen Brightness. is ready to use.
By Enable:
1.Setting>System>Status bar > Enable Brightness slider.
2.Setting>Status bar > Enable Auto Brightness. (Show auto brightness button)
3. Set Developer Options: Smallest width= 723 dp
3. Configure bluetooth devices.
=》Bluetooth devices.(Headphone / True Wireless)
Enable Phh Treble Settings (Misc features)
☆☆☆ Do Enable the same as I show below.☆☆☆
-Use alternate way to detect headsets.
-use System Wide BT HAL
-reboot
4. Task menu came with "Recent apps" -had changed itself from your last selected app.
***Don't set Smallest width = 598 dp , you will lost ability of Multi-tasking Menu.
The Purpose of this type menu is for Multi-tasking windows. ( Split screen apps).
5. Google assistant can call from your contact number. (After update all Google apps .)
6. Sync with latest sources of TrebleDroid then no problem with setting UI and swipe from bottom screen to show all icons menu.( Can set any value of Smallest width dp.)
7. Can setup "always show keyboard"
8. Battery usages does not conflict with Auto screen brightness and specific every duration.
9. Charging when power-off device.
it can cut-off (break) informed warranty bit error state. (below)
10. Test before updating.
Its supported Vega Bobo DSU.
11. Phone Calling sound when we wear earbuds or headphone.
Samsung buds 2 earbuds with no problem through calling sound > Calling sound can came from both tab and inside buds2. Same can uses microphone from buds 2 also. ( Call Google assistant)
12.TV Casting with nightly VLC.
13. MTP USB on Dev Option.
Default USB configuration
-USB
Select File transfer/Android Auto
(U can transfer files with Computer.)
14. How2update without lost historical data.
-Update Pixel Experience Plus 13.0 v2023.04.21 Download
Dirty flash
Code:
adb devices
adb reboot fastboot
fastboot flash system PixelExperience_Plus_arm64-ab-vndklite-13.0-20230421-UNOFFICIAL.img
reboot system.
Dirty Update✓ NEW fastbootD- Recovery_patched For T225XXS3CWC2
Download from Attachment below.
The Competitor you must try.✓The crDroid 9.4 A13 GSI .
✓The LineageOS 20 TD
✓The sparkOS GSI.
✓ The Alpha Droid A13 GSI.
(Unofficial)
Release v20230419 · ChonDoit/treble_alphadroid_patches
| Sync with sources | Fixed Settings Crash
github.com
Extended Features From
"Pixel Experience Plus"Note: Only the bad thing is not yet supported "exFAT sd card", and Google Assistant Bugs.
1. Task menu came with "Recent apps"
2. Auto screen brightness.
3. ADB ROOT Menu from Developer options.
4. Control Google Services GMS & Core.
Smart Charging. ( Set max
Waiting For Next version.
}=================={
All my tutorial. (Link)
CustomAPFastbootDLineage OS TD GSIPixel Experience GSISpark OS GSImicroG with GSITWRP for A11
How2 ? install Lineage OS "TD" with SM-T225.(Samsung Tablet)
Light doesn't have VNDKLite builds.
Click to expand...
Click to collapse
Light doesn't have Old PHH Treble Setting.
Click to expand...
Click to collapse
This light build has never worked for any Samsung tablets since the dev has expressed his disinterest in making it compatible.
Sure, it flashes successfully...but it always does get stuck on the boot screen. There is nothing that can be done at this point
Click to expand...
Click to collapse
Actually I believe offline charging display isn't working at all, and whether it charges while the logo freezes depends on the device.
Click to expand...
Click to collapse
In "Light" I didn't do any special treatment to offline charging, whereas TD-based does have a few related patches.
Click to expand...
Click to collapse
All of this came from XDA.
Begin with "what does variant to use ?"
More...
LOS 20 Treble Droid.
new pop up Task menu.
Is this only for t225 ? How about t220 ? Thanks
I was able to get the Pixel Experience to work on my SM-T220 with a lot of messing around.
First, I followed this to get TWRP on my S7 Tab Lite: https://forum.xda-developers.com/t/...lite-wifi-t220-unofficial-android-13.4576343/
Once I was in TWRP, you need to hook up a wired mouse via the USB-C port, which means you need a USB-C adapter ("OTG mouse"). Then you can use TWRP, since the touch screen doesn't work until you have a non-Samsung OS installed
Once I had TWRP on the system, I always used TWRP to boot into Fastmode, then followed along with this video:
The video isn't the most intuitive, but if you have some awareness on how to load custom OSes on a Samsung device, you should be just fine. Otherwise, follow along and Google the commands he uses in the video to see the expected outcome. Again, whenever he's in fastboot mode on here, I used TWRP to get there instead of ADB.
YES, I also installed the fbe_disabler_gta7lite.zip and gta7litewifi_kernelsu.zip from TWRP, then flashed Pixel Experience
4. I had to use PixelExperience_Plus_arm64-ab-13.0-20230329-UNOFFICIAL to get anything to boot.
fonixmunkee said:
I was able to get the Pixel Experience to work on my SM-T220 with a lot of messing around.
First, I followed this to get TWRP on my S7 Tab Lite: https://forum.xda-developers.com/t/...lite-wifi-t220-unofficial-android-13.4576343/
Once I was in TWRP, you need to hook up a wired mouse via the USB-C port, which means you need a USB-C adapter ("OTG mouse"). Then you can use TWRP, since the touch screen doesn't work until you have a non-Samsung OS installed
Once I had TWRP on the system, I always used TWRP to boot into Fastmode, then followed along with this video:
The video isn't the most intuitive, but if you have some awareness on how to load custom OSes on a Samsung device, you should be just fine. Otherwise, follow along and Google the commands he uses in the video to see the expected outcome. Again, whenever he's in fastboot mode on here, I used TWRP to get there instead of ADB.
YES, I also installed the fbe_disabler_gta7lite.zip and gta7litewifi_kernelsu.zip from TWRP, then flashed Pixel Experience
4. I had to use PixelExperience_Plus_arm64-ab-13.0-20230329-UNOFFICIAL to get anything to boot.
Click to expand...
Click to collapse
ok same environment as when i used A11 TWRP with ( OTG Mouse). but this time (no have A13 TWRP for T225), then my best friend is always Odin and fastbootD. Don't worry about it.
abc1054 said:
Is this only for t225 ? How about t220 ? Thanks
Click to expand...
Click to collapse
I don't have T220 then can't make custom-super.tar for this device but you can uses fastbootD or fastboot mode from new TWRP.
New Competitor Alpha Droid.
CRDROID 9.4 GSI