Related
I'm pleased to present my MoDaCo Custom ROM for the Samsung Galaxy S! READ THIS WHOLE POST BEFORE YOU START! No, really, it contains everything you need to know. wink.gif
This ROM is the 'starting point' for my Galaxy S custom ROMs.
About MoDaCo Custom ROMs
MoDaCo Custom ROMs are based on official ROMs - either shipping or leaked. A MCR release is designed to feel as far as possible like a stock ROM, with optimisations, tweaks and complimentary additions that enhance the user experience. The aim of a MCR is to be ultra reliable for use on an everyday device.
Requirements
In order to use this ROM on your device, YOU MUST ALREADY BE RUNNING THE JFB ROM FROM HERE. Do NOT use this ROM with any other base, unpredictable things will happen, the most likely being you'll have to reflash your device via Odin.
Features Included
* Based on the JFB release
* Rooted with Superuser 2.1 by ChainsDD
* Built with the MCR build process which reduces the size and boosts the speed of the ROM
* busybox with Droid Explorer support
* Updated Google Maps
* MCR version displayed in 'About' screen
* Optional Google Voice Search
* Optional Google Voice Dialer
* Optional Fancy Widget
* Optional Beebplayer
* Optional baked in Wavesecure via the online kitchen (installed to system partition for maximum security)
Changelog
Please see 2 posts below this one for the changes in each release.
Installation
To install this ROM:
* Ensure you have the JFB ROM installed (linked above)
* Download the zip file of your choice from the links below (or the online kitchen) and copy to your SD card named 'update.zip'
* Restart your device in recovery mode by running 'adb reboot recovery' (download adb if you do not have it already, use adb-windows, adb-mac or adb-linux as appropriate)
* Select the option to apply an update zip, and select the zip file you copied to your memory card
Upgrading
No wipe is explicitly required in order to use this ROM, however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Downloads
This ROM is currently only available in the online kitchen - prebakes to follow.
Thanks
It's impossible to mention everyone who contributes to the Android community by name, but to everyone out there who does great work and shares it with us all - you have my gratitude and respect.
And finally...
If you would like to show your appreciation for the ROM, please consider supporting MoDaCo by signing up for a MoDaCo Ad Free or MoDaCo Plus account, both of which also give you early access to Beta ROM releases and access to the the online kitchens.
Enjoy!
http://android.modaco.com/content/s...rom-for-samsung-galaxy-s-with-online-kitchen/
Does this ROM fix the ram issue so that all 512MB of ram is utilized?
Congrats on being the first custom rom here.
Congratulations! I don't have a phone yet but I am very pleased to see a custom rom already!
woohoo custom ROMs already. Guess I'll be getting myself the phone after all.
umm.. but in another thread people where saying that it wasn't gonna be possible because samsung encrypt their drivers etc. so this mean they did release they drivers? and there is gonna be alot of custom rooms for galaxy gravity?
Perrosky said:
umm.. but in another thread people where saying that it wasn't gonna be possible because samsung encrypt their drivers etc. so this mean they did release they drivers? and there is gonna be alot of custom rooms for galaxy gravity?
Click to expand...
Click to collapse
No I said it would be near impossible to get roms from other sources like Sense roms or Froyo on because of the driver issue. I never said you would never see custom roms. The only roms you are going to see are one's based off of Samsungs release.
Hold on, hold on. So even though Samsung released the Galaxy S' driver source code to the public, it's going to be "near impossible" to port Sense and FroYo to the phone? I may be ignorant but I'll just ask with ignorance, how do you figure?
Javalu said:
Hold on, hold on. So even though Samsung released the Galaxy S' driver source code to the public, it's going to be "near impossible" to port Sense and FroYo to the phone? I may be ignorant but I'll just ask with ignorance, how do you figure?
Click to expand...
Click to collapse
Download the source code..... ok now open it and go to GalaxyS_Kernel.tar.gz. Now in there just enter the first folder then go to modules. Go to Dpram. Open up any of those files in notepad. You should see written non-compiled code right? That is fine now go back to the module folders and go to S3cbc. Now open up s3cbc_module.o. Does that look like non-compiled code? No it doesn't. It's either already compiled or encrypted. That's what I mean
psychoace said:
No I said it would be near impossible to get roms from other sources like Sense roms or Froyo on because of the driver issue. I never said you would never see custom roms. The only roms you are going to see are one's based off of Samsungs release.
Click to expand...
Click to collapse
Quick question, does that mean any custom rom that is release will be based off the official rom they release which has Touchwiz backed in? If so, does that rule out a plain vanilla android rom for this device? Thanks for your help and appreciate the knowledge.
Papa_I said:
Quick question, does that mean any custom rom that is release will be based off the official rom they release which has Touchwiz backed in? If so, does that rule out a plain vanilla android rom for this device? Thanks for your help and appreciate the knowledge.
Click to expand...
Click to collapse
No it doesn't rule out plain vanilla android rom. Yes they will all be based on Samsung but rom makers can take out all the touchwiz garbage and throw in another launcher like adw or Launcherpro.
That's what I wanted to hear. Thanks for the help. Now if I only could decide if I should keep the Nexus One or purchase this phone..... Decisions, Decisions.
psychoace said:
Download the source code..... ok now open it and go to GalaxyS_Kernel.tar.gz. Now in there just enter the first folder then go to modules. Go to Dpram. Open up any of those files in notepad. You should see written non-compiled code right? That is fine now go back to the module folders and go to S3cbc. Now open up s3cbc_module.o. Does that look like non-compiled code? No it doesn't. It's either already compiled or encrypted. That's what I mean
Click to expand...
Click to collapse
How lame. Have other handsets had similar problems?
what are talking about .o files and unix compiled modules same on all versions of unix. o stands for object module.
Javalu said:
How lame. Have other handsets had similar problems?
Click to expand...
Click to collapse
Yes the Behold 2, the original Galaxy, and the Moment all made by Samsung have only had Samsung roms on them.
lgkahn said:
what are talking about .o files and unix compiled modules same on all versions of unix. o stands for object module.
Click to expand...
Click to collapse
So they can easily be decompiled? If it's source code why is it already compiled?
dont go too deep into specific things that we may not even need (we are not coders here) but the source code for basic hardware that we need to get things going are already there.. things like camera, wlan, etc. btw, do u know what s3cbc is for?
raspdeep said:
dont go too deep into specific things that we may not even need (we are not coders here) but the source code for basic hardware that we need to get things going are already there.. things like camera, wlan, etc. btw, do u know what s3cbc is for?
Click to expand...
Click to collapse
What about s3clcd? Here is a little copy and paste of some of the garble that was in the compiled file
screen width=%d height=%d va=0x%x pa=0x%x
I would go out on a limb and say those are video drivers. The one's that have been encrypted on all other samsung phones.
Also in s3cbc there is some code at the bottom
PVRSRV_PIXEL_FORMAT_YUY2 PVRSRV_ERROR_FIFO_SPACE char ui32ByteStride psDevInfo PVRSRV_PIXEL_FORMAT_PAL1 PVRSRV_PIXEL_FORMAT_PAL2 pfnOpenBCDevic
If you don't know the Galaxy's gpu is PowerVR SGX540 and YUY2 is a colol format for video screens
http://www.fourcc.org/yuv.php#YUY2 and Pal is of course a European video standard.
they are not encrypted, they are object codes in machine language for arm.. and why we need that again for custom roms?
Wanted to test modaco ROM but they are not free.. Any kind souls upload and share ?
well feedback on the R1 rom its clean and smooth, worked even better when i did the stall tweak posted here
http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
the phone seriously got 2 times faster, opening apps playing game very quick .. happy as here
Ferdimage said:
well feedback on the R1 rom its clean and smooth, worked even better when i did the stall tweak posted here
http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
the phone seriously got 2 times faster, opening apps playing game very quick .. happy as here
Click to expand...
Click to collapse
How much free ram have you got? Considering flashing and rooting, but not sure if it's worth it right now. Meh 10£ isn't that much think I'm gonna give it a try.
EDIT: Just flashed, but now I don't have root access(says access denied when I try to access the /data/data folder). Thought this included the rooted PDA file or do I have to flash that again with odin?
EDIT2: Scratch that I forgot to press the allow-button on my phone after sending the Super-user request..
I am working on porting the latest upstream version and will update this post as things start working.
Things to do:
[DONE] Create boot image that boots into the Ubuntu Touch rootfs.
[DONE] Create Android container started by Ubuntu.
[WIP] Customize configurations and work on kernel and android system to make things work properly (e.g. audio).
[TODO] Setup apparmor security.
Testing, debugging and optimization...
Any help is welcome!
The information and images below are very out-of-date.
The port of Ubuntu Touch to our beloved TF300T is more or less working now.
Please see section "Known Issues" below.
And please read the instructions carefully, including the linked threads, before doing anything to your tablet that might result in a very expensive paper-weight.
Known Issues
Just listing major issues that are specific to the TF300T port.
This is not the place to discuss general issues with Ubuntu Touch.
Camera is broken.
Dock not fully supported.
There are probably more; please follow this thread and report any new issues you find.
Downloads
Please read the section "Installation" below carefully, if you are not sure what these files are.
That section also contains verbose information on the different bootloader versions.
The binaries are generated automatically by Jenkins.
Generally they are not tested and may be broken.
Please report any issues in this thread, so they can be fixed and broken binaries can be removed.
Bootloader 4.2
These are the latest binaries that should be up-to-date with respect to Canonical's binaries.
Well, sometimes allow a day or two...
Android Base-System
The Android base-system is a stripped-down version of CyanogenMod 10.1 with some additional patches.
This is, where the major effort for porting Ubuntu Touch goes into.
Ubuntu Touch Root FS
This is the Ubuntu Touch file system.
Flashing this ZIP will preserve network settings and the phablet home directory, if you had installed Ubuntu Touch before.
It should work for all devices, however a stripped-down version with some changes for our TF300T is provided.
Please see the list of changes below.
Media Files
These media files are part of Canonical's root fs, but they rarely (never?) change.
Splitting the media files into a separate image significantly reduces the size of the rootfs that receives regular updates.
Unless you manually remove /data/ubuntu, these files will persist re-flashing the rootfs.
Bootloader 4.1
These are out-of-date and are no longer being maintained.
They will be kept, till dev-host deletes them (30 days after the last download):
Android Base-System
Ubuntu Touch Root FS
The rootfs for bootloader 4.1 also includes the media files. There is no separate download.
Android Source Code
The patched repositories of the Android/CyanogenMod/Ubuntu source trees are available on GitHub.
For details, please see section "Building the Android Base-System from Source" below.
Ubuntu Touch Root FS Changes
The "official" Ubuntu Touch root fs does not quite work on our TF300T yet.
So a stripped-down version with the following changes is provided:
Run amixer on boot to fix mixer levels.
Disable save/restore of alsa settings.
Split media files into a separate image.
Remove several big and unnecessary files.
The official Ubuntu Touch image does work, but for these issues:
Flashing with TWRP fails.
For details, see the bug report on launchpad.
There is no sound, unless you adjust alsa mixer levels manually.
Rebooting from Ubuntu goes into a boot-loop.
When Ubuntu is properly shut down, it saves the current alsa settings.
Restoring them on the next boot crashes the system and causes the boot-loop.
Note that rebooting from Android or using adb works fine.
If you happen to run into the boot-loop, use the TWRP file manager (in the Advanced menu) to remove /data/ubuntu/var/lib/alsa/asound.state.
Installation
Please read the following instructions carefully, and make sure you understand each step and what it will do to your tablet.
The steps are working for me, but you are ultimately responsible, for what you are doing with your own tablet.
I will not be responsible, if you brick your tablet, or if your wife gets angry at you for being too preoccupied with your tablet.
Step 1: Unlock Your Tablet
If you want to give Ubuntu Touch a try, your tablet needs to be unlocked.
There are lots of threads helping with this, please use search to locate this information.
Step 2a: Which Bootloader Do I Have?
Unfortunately, Asus has released several incompatible bootloaders.
To find out, if you can use this port of Ubuntu Touch, go to the bootloader screen by holding the power and vol-down keys.
Once you see the bootloader screen with three or four icons in the center, check the long version number at the top of the screen.
It looks something like: "WW_epad-10.6.1.15.3-20130416".
The first two letters are your SKU and should not matter.
The version number following "epad" is what will be referred to in the following.
Version 10.6.1.15.3
This is the latest version from Asus, generally referred to as "bootloader 4.2" in the XDA forums.
The latest Ubuntu Touch binaries are developed and tested on this bootloader, so you should be fine.
Version 10.6.1.8
This is an older version of the bootloader 4.2.
The latest Ubuntu Touch binaries might work for you, though upgrading your bootloader is recommended (see below).
This version is known to cause issues with the latest TWRP recovery, so be careful.
Version 10.4.2.20
This is the old incompatible bootloader, generally referred to as "jb bootloader" or "bootloader 4.1" in the XDA forums.
The latest Ubuntu Touch binaries will not work for you, upgrading your bootloader is strongly recommended (see below).
Older binaries that work with this bootloader are still available for download though.
Any older version not listed
Your bootloader is really out of date and you should upgrade as soon as possible (see below).
Any newer version not listed
You are on uncharted territory. Proceed with care!
Let us know about your experience in this thread!
Step 2b: Upgrade Your Bootloader
If you have not yet installed bootloader 10.6.1.15.3, it is recommended to upgrade.
Please check the following threads (and several others; search might be helpful):
[GUIDE][26/04]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices
[HOW-TO] Upgrade or Downgrade to any stock JB Firmware
Step 3: Install TWRP Recovery
You need a custom recovery installed for flashing the Ubuntu Touch binaries.
Please check the following thread for getting and installing TWRP recovery:
[RECOVERY][TF300T/TG] TWRP 2.5.0.0 Touch Recovery!
Step 4: Backup and Wipe Your Android System
Before flashing Ubuntu Touch, you need to wipe some parts.
It is strongly recommended to make a backup of your Android system too.
Check section "Restore Android" below on how to restore it.
If you are running CyanogenMod 10.1:
Use TWRP to backup "boot" and "system".
Backing up "data" is not strictly necessary, but recommended.
Wipe "cache", "dalvic cache" and "system".
In TWRP 2.5 you should use "Wipe -> Advanced Wipe" and check the respective boxes.
Note that this will not wipe the contents of your "/sdcard" Android folder.
If you are not running CyanogenMod 10.1, but another ROM:
Use TWRP to backup "boot", "system" and "data"
Wipe "cache", "system" and "data".
In TWRP 2.5 you should use "Wipe -> Advanced Wipe" and check the respective boxes.
Note that this will not wipe the contents of your "/sdcard" Android folder.
Step 5: Flash Ubuntu Touch
If you want a clean start or you had installed Ubuntu Touch for bootloader 4.1, please remove /data/ubuntu manually before flashing.
You can use the TWRP file manager in the Advanced menu for that.
If you want to upgrade from a previous Ubuntu Touch for bootloader 4.2, please see section "Upgrade Ubuntu Touch" below.
Flash the following images (see above for downloads):
ubuntu-touch-system-XXXXXXXX-tf300t-bl4.2.zip
ubuntu-touch-rootfs-raring-XXXXXXXX-tf300t-bl4.2.zip
ubuntu-touch-media-XXXXXXXX.zip
Step 6: Reboot Your Tablet
Note that there is no boot animation yet, so the screen will be black, till the shell is starting up.
This make take some time, please be patient!
Restore Android
Boot into TWRP recovery.
Wipe "cache" and "dalvic cache".
Select the last backup done before installing Ubuntu Touch.
If you were running CyanogenMod 10.1:
Restore "boot" and "system".
If you were not running CyanogenMod 10.1, but another ROM:
Restore "boot", "system" and "data".
Reboot your tablet.
Upgrade Ubuntu Touch
Generally, the system and the rootfs can be upgraded individually.
However, sometimes Canonical introduces breaking changes, that require them to be upgraded together.
Upgrade ubuntu-touch-system-XXXXXXXX-tf300t-bl4.2.zip
If you are running an older version of that ZIP, you can just flash the new one.
If you have returned to your Android system, please follow "Backup and Wipe Your Android System" under "Installation" above before flashing the new ZIP.
Upgrade ubuntu-touch-rootfs-raring-XXXXXXXX-tf300t-bl4.2.zip
You can flash this ZIP anytime.
Network settings and the phablet home directory will be preserved. This includes the media files from the separate ZIP:
If you want to start clean, remove /data/ubuntu manually and re-flash both rootfs and media.
Upgrade ubuntu-touch-media-XXXXXXXX.zip
You can flash this ZIP anytime.
It will just overwrite existing files and add new files; old files will not be deleted.
If you want to start clean, remove /data/ubuntu manually and re-flash both rootfs and media.
Building the Android Base-System from Source
Basically you can follow the guide for building CyanogenMod with one exception.
Initialize your CyanogenMod source repository with:
Code:
repo init -u git://github.com/f69m/android -b phablet-10.1-tf300t
You can also run this command in an existing repository.
Thats great, but ...
f69m said:
Current Status:
Ubuntu Touch is booting and can be accessed via adb, but the screen stays black.
Click to expand...
Click to collapse
I have the exact same issue even on the official build released for nexus 4 ... The current release of Ubuntu is just such a mess, nothing more than a buggy preview with loads of fake apps and content, and very limited functionality.
I'd love to see Ubuntu on tf300, but I would say (in my humble opinion,) lets wait for a better release, and then we'll get started.
Shu. said:
I have the exact same issue even on the official build released for nexus 4
Click to expand...
Click to collapse
Oops, that is intersting, thanks!
I'd love to see Ubuntu on tf300, but I would say (in my humble opinion,) lets wait for a better release, and then we'll get started.
Click to expand...
Click to collapse
Agreed, if your interest is to have something to play with.
On the other hand, I'd like to see, what is already there and possibly help improve it by contributing to Canonical. And any work we do now will speed up porting, once there is a better release available.
Just trying some more Kernel tweaks after looking at the TF700 port that seems to work (see http://forum.xda-developers.com/showthread.php?t=2162472).
Re: [DEV] Porting Ubuntu Touch Preview to TF300T
Shu. said:
I have the exact same issue even on the official build released for nexus 4 ... The current release of Ubuntu is just such a mess, nothing more than a buggy preview with loads of fake apps and content, and very limited functionality.
I'd love to see Ubuntu on tf300, but I would say (in my humble opinion,) lets wait for a better release, and then we'll get started.
Click to expand...
Click to collapse
Agreed but I have gotten it up and running on my nexus 4 without much issue, its cool for about 20 min( being generous) but then you realize you can't actually do anything. I feel that its gonna be an awesome platform especially for a transformer tablet though if it goes where they say it will. Full Ubuntu when docked and then touch when not....sounds like what these tablets were made for.
Sent from my Nexus 4 using xda premium
Still not working build ? (
It's pity, i would like to try it, I know, that there is only something functions, but I can try the UI, and how it is look like
Maybe someone from TF700 thread who port it for TF700 can help us.
matonka007 said:
Still not working build ? (
It's pity, i would like to try it, I know, that there is only something functions, but I can try the UI, and how it is look like
Maybe someone from TF700 thread who port it for TF700 can help us.
Click to expand...
Click to collapse
Just checked the wiki.ubuntu.com/Touch/Devices site, looks like someone has committed to porting it. Though I wouldn't be in a rush to get it just yet seeing as it barely functional. I guess time will tell where this leads.
ColMustard said:
Just checked the wiki.ubuntu.com/Touch/Devices site, looks like someone has committed to porting it. Though I wouldn't be in a rush to get it just yet seeing as it barely functional. I guess time will tell where this leads.
Click to expand...
Click to collapse
lol, if you looked at the developer on the wiki you would realize that the developer on it is the originator of this post
Re: [DEV] Porting Ubuntu Touch Preview to TF300T
doubljdog said:
lol, if you looked at the developer on the wiki you would realize that the developer on it is the originator of this post
Click to expand...
Click to collapse
Yes I realized that after I posted this. Just pointing out that someone has committed to porting this.
Edit: Thanks for pointing out the obvious though,I'm sure nobody else would have figure this out
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
So, is there someone working on it, or not?
I installed the one from tf700 on my tf300 and it works decent, except wi-fi, so I'm guessing its not that hard, but i'm not a dev..so...
How did you load the patch in your make file? I am adapting your patch to my device.
secosan said:
So, is there someone working on it, or not?
Click to expand...
Click to collapse
Yes, I am working on it, and so are some others.
I installed the one from tf700 on my tf300 and it works decent, except wi-fi, so I'm guessing its not that hard, but i'm not a dev..so...
Click to expand...
Click to collapse
That is interesting, thanks!
What happens on the tf300t using the CM tf300t base code is a segmentation fault.
The nv video drivers send a null file pointer to fputc() in the Ubuntu libc.
Just trying to do a quick fix, by building my own libc that silently ignores the null pointer, but that is sure not a final solution.
Eventually we need to figure out, where the null pointer comes from and avoid it.
I'll let you know, how it works, once the lenghthy ARM compilation has finished and I had a chance to try it.
WLAN is working fine, BTW, just the display is black.
giveen said:
How did you load the patch in your make file? I am adapting your patch to my device.
Click to expand...
Click to collapse
Are you referring to my patches on GitHub?
Not quite sure, what you are asking for.
Anyhow, the patches for the package makefile and for the kernel are on GitHub
https://github.com/f69m/ubuntu-touch-tf300t.
The changes to the Android repository manifest are described on
https://github.com/f69m/ubuntu-touch-tf300t/wiki/Build-Ubuntu-Touch-for-ASUS-Transformer-TF300T
Apart from those patches it is really the same as building CyanogenMod. Just faster, as only a part of the CM tree is built.
Does that answer your question?
Canonical started the daily building of Ubuntu Touch, good news I tryied the build for TF700 too, but it have bad DPI.
PS: f69m, I do not know about developing, but if I can help you write.
Re: [DEV] Porting Ubuntu Touch Preview to TF300T
f69m said:
Are you referring to my patches on GitHub?
Not quite sure, what you are asking for.
Anyhow, the patches for the package makefile and for the kernel are on GitHub
https://github.com/f69m/ubuntu-touch-tf300t.
The changes to the Android repository manifest are described on
https://github.com/f69m/ubuntu-touch-tf300t/wiki/Build-Ubuntu-Touch-for-ASUS-Transformer-TF300T
Apart from those patches it is really the same as building CyanogenMod. Just faster, as only a part of the CM tree is built.
Does that answer your question?
Click to expand...
Click to collapse
I was referring to the screen res patch, but I figured it out from your guide.
The problem I am having that my kernel not compiling with Ubuntu options even though I sent them in my defconfig.
They should be working but they are not.
Sent from my Nexus 7 using Tapatalk 2
What is this link?
http://ubuntuone.com/06vcR0nyoTd9DYb2OgRSlT
Is on https://wiki.ubuntu.com/Touch/Devices as Android Base image, it is your build f69m ?
matonka007 said:
What is this link?
http://ubuntuone.com/06vcR0nyoTd9DYb2OgRSlT
Is on https://wiki.ubuntu.com/Touch/Devices as Android Base image, it is your build f69m ?
Click to expand...
Click to collapse
Definitely not my build, I have no images out yet, but mine should be coming soon!
The entry in the device table was not added by me.
Woohoo, I am seeing something!
The Ubuntu package build for my patched libc is still running tests, but I pulled the libc.so binary from the build directory.
This is a manual hack right now, I need to repackage the root FS for flashing and then will make it all available via Dropbox.
Hope that will allow quick downloads for everyone.
It sound great
Yes, Dropbox is good choice
And http://d-h.st/is not bad for sharing files
f69m said:
Woohoo, I am seeing something!
The Ubuntu package build for my patched libc is still running tests, but I pulled the libc.so binary from the build directory.
This is a manual hack right now, I need to repackage the root FS for flashing and then will make it all available via Dropbox.
Hope that will allow quick downloads for everyone.
Click to expand...
Click to collapse
Oh and then also please dont forget to update the install instructions on the official ubuntu page and here because on Ubuntu it links to your building guide on Github
-angel* said:
Oh and then also please dont forget to update the install instructions on the official ubuntu page and here because on Ubuntu it links to your building guide on Github
Click to expand...
Click to collapse
Of course, l will make sure to update everywhere, once the image is released, though the entry in the Ubuntu wiki was not done by me.
Got a flashable filesystem now, but that version is crashing on me. Must be something small I am overlooking atm.
So taking a little break and then will finish with refreshed spirit.
XDA:DevDB Information
[ROM][OFFICIAL] RESURRECTION Remix OPPO Find7 [MM 6.x][LVM], ROM for the Oppo Find 7
Contributors
opposeeker, RoppoFon
Source Code: https://github.com/resurrectionremix
Source Code: https://github.com/find7s
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 5.7.4_r72
Created 2016-07-28
Last Updated 2016-10-07
[A] - INTRODUCTION
This is a continuation of a previous port of Resurrection Remix for the FIND7.
The predecessor was discontinued by the foregoing maintainer soon after its start within a month's period. This port was set up independently from it, all new from scratch, escpecially with proper LVM-Implant (i.e. w/out corrupted sdcard0, see images in the upper screenshot compartment of this page)
... more?
A lot of maintainers stopped their activies for the FIND7. It happened several times to me with different ROMs since I own this device. I really got fed up with the situation:
Only a limited number of ROMs left available for the FIND7 - shrinked down even more when counting only those with LVM-support. As soon as you get used to it, the individual maintainer in charge doesn't care anymore.
I prefer reliability and continuity in real life and therefore - surprise! - I'm really not in the mood exchanging my "technical assistants" on a monthly basis just because the geeks have left the playground for new toys...
Since Resurrection Remix is an awesome, well balanced ROM, I wanted to keep using it! Including enhancements and security fixes in future, of course. And I didn't want to buy a new (maintained-for-how-long?) phone just for that reason. The Devs @ RR are dedicated and strive for sustainment and stability just as I do.
Obviously, they can't take care for each and every piece of hardware on the market. - What to do...?
<b>If nobody else does it - you'll have to do it yourself!</b>
So I did. Still wondering about it, since I didn't have a clue : -)
---
I'd like to share this port with you to enlarge the (limited) choice for us FIND7 users. BTW, since it has eaten an enormous budget of my time and resources, it would be real waste (and blame) not to ... especially as I participated from the work of so many people plus individuals supporting me personally to get this whole thing together.
Hall of Fame:
Being myself an advanced user who had no deal with "porting" or "maintaining" until very recently, I'm very grateful to the following individuals for their personal support:
@Schneiderle - not even owning this device by himself, he was a patient teacher to me "Android Infant" helping me understand the basics and preparing the ground
@maxwen - for his useful hints on LVM, since he has done it properly for Omni and TWRP
@anders3408 - implemented LVM for DU and let me share his work (+ lots of useful hints!)
Thank you, guys!
Thanks to:
Google for creating an alternative to the "fruit monopoly", CyanogenMod and ResurrectionRemix-Team, among many many others, I'd like to express my respect to those in the communicty who spent their time in creating Tutorials and How-To's, so beginners have a chance to get into this without attending University.
I'm also thankful to people like @Entropy512 who made LVM available to the FIND7 initially and therefore saved a lot of people from claiming their Oppo as "real bad buy".
(B) - LEARN MORE about RR, support and unwanted features
If you have specific questions concerning features, requests, bug reports etc., visit the capitol of ResurrectionRemix directly and get involved.
You'll also get there a full list of all features, support and up-to-date info.
Don't blame/flame if something doesn't work - check with others first: if other people with other devices have equal "unwanted features" - then post in the RR-forum - not here.
[C] - MISCELLANEOUS
I am not a dedicated maintainer nor will I be 24hrs around to nanny. I don't code anything (except for the purpose of mixing things up : - )
I just brought existing stuff of other genius' together, so the whole mixture works in this specific device. No more - not less.
This needs to be re-done for fixes and enhancements from the "ethereous" (=>genius) part of the Android world from time to time. I'll take care for these updates as time allows and as long as I will be using the device myself - this should should be for a while from now, at least up to mature "Nougat", let's see from there.
However - by downloading und using this port you declare: not to ask for ETA(!)
This ROM is a well-balanced and sophisticated one, that's why it's my favoured.
Go and try it if you haven't done so - and you'll see why!
Here we go:
[D] - FLASHING INSTRUCTIONS:
---------------------------------------------------------------------
BEFORE FLASHING - SAVE YOUR DATA!
---------------------------------------------------------------------
Like in real life, you should have a basic understanding about what you are doing. Whatever you do: You'll do it at your own risk. I'll take no liability for anything. If you don't agree - don't touch it!
Coming from whatever (everlasting-beta) stock ROM by Oppo:
If you previously changed your partition type with Oppo, revert to the original (default) FIRST.
(Should you have created it with 2.1.5 and up (without resizing,) you can leave it as it is).
Then
- Connect your phone to a PC via USB and
- Unlock your phone if this is your fast attempt to install a ROM (fastboot oem unlock)
- Flash TWRP recovery (fastboot flash recovery TWRP-Version.img)
- Reboot to Recovery
Proceed with steps below
Preparing for LVM
Setting up the whole internal storage partition w/out splitted
storage for apps / data requires the following prerequisites:
- TWRP Recovery installed (nothing different)
- Using setuplvm.zip (get from upper download compartment of this thread and save on your external sdcard for later use)
Setting up LVM
- Go to TWRP-Recovery
- Be super-pedantic: Wipe system/data/cache/dalvic
- Flash setuplvm.zip (will wipe everything incl. internal storage!)
- Reboot to recovery
- Flash ROM
- Flash GApps
- Reboot
Errors while setting up LVM?$&%??
- Reboot to TWRP Recovery and flash setuplvm.zip again.
- Reboot to TWRP after that again to proceed flashing.
Coming from another ROM
Note:
It's Aliens's Law to flash modem first to avoid problems with immigration. Travelers from Oppo Stock ROM have a visa and don't have to.
- Get modem files (from upper download compartment of this thread - save on your external sdcard)
- Book into Recovery
- Flash modemxxxx.zip
- Be super-pedantic: Wipe system/data/cache/dalvic
- Reboot to Recovery
- Flash ROM
- Flash GApps
- Reboot
Note: If you currently use whatever Unified XX flavor : Revert to the default partition layout with the tool by the respective provider prior to flashing this ROM.
Then proceed with above steps. Failure to do so may result in unwanted behaviour. The least you may expect is a "corrupted" sdcard.
Download Links:
ROM downloads see Post #3
3rd party add-ons see Post #4
Little Q & A
Check the General FAQ of Resurrection Remix Headoffice
This port is designed for the *FIND7s (X9076)*,
since that's the device I own. It has been reported working with the Find7"a" version, too. Make sure you'll reduce the screen density to "480" in settings after successfull flash. Applies to "A"-users only. EDIT: The last version of RR w/ MM (5.7.4) has an extra build for the Find7a. See Post #3 below (Download links).
New LCD support? - No.
It has been reported that this port does not support the new LCD. Although it is built-in the sources, users report it simply doesn't work.
There are kernel patches available in the net, though, they have side effects beyond your control - so no recommendation from this side. Sorry.
This port comes with proper LVM support. Any other?
You can use LVM if you want. Or keep using the original partition layout. That's the freedom of choice you'll get with this port. No other flavors are being supported (see OP, Section D)
This ROM comes pre-rooted. Is it possible to un-root?
Yes. Install SuperSu (see Download Section abv). In the settings of SuperSu you'll see options for unrooting your device.
Do I have to donate if keep using this ROM?
You don't have to at all, no matter if you just give it a try or keep using it forever....it's all open and free of any charge! If you are very satisfied and feel like donating, well, I won't reject : - )
See the "Donate to me" button on the left or in my profile. Thank you!
Download Links:
ROM: Resurrection Remix 5.7.4_r72 | Changelog | Mirror Download
ROM (FIND7a only): Extra build for the Find7a. | Mirror Download
GAPPS: Choose any, I prefer BaNkS
Recovery: TWRP (mandatory for LVM-use!)
Modem: see upper download compartment of this thread
LVM: see upper download compartment of this thread
SuperSU : This ROM is pre-rooted. Here you'll get SuperSU.
3rd Party Add-ons
Oppo Camera Mod
http://forum.xda-developers.com/oneplus-one/themes-apps/port-coloros-camera-cm11s-t3030369
MaxxAudio
http://forum.xda-developers.com/oneplus-one/themes-apps/app-maxxaudio-cos13-cm13-t3355120
...anything else...? Yes.
Greenify
App singing lullabies to background apps so they'll get to sleep while not being used- saves battery!
Bettery Battery Stats
What's giving me an empty battery so fast...? Here you'll get better statistics who's eating too much!
thanks for your great work!
o my god !!!! Thanks you !!
Working great... Now Just need to be officialize the incoming builds :laugh: :good: :highfive: :laugh:
Thanks for continuing Resurrection Remix builds. Does this rom supports F2FS partitions on /data, /cache, /externalsd? and does this also support Coldbird Unification Method? Thanks.
@opposeeker thank you man! Works great. And like before it is working on my find 7a x9006 version so you can edit the post to support this version as well
---------- Post added at 09:17 AM ---------- Previous post was at 09:15 AM ----------
hulicow said:
Thanks for continuing Resurrection Remix builds. Does this rom supports F2FS partitions on /data, /cache, /externalsd? and does this also support Coldbird Unification Method? Thanks.
Click to expand...
Click to collapse
Don't know about coldbird, but this does work with the chinese partition layout; tried it myself
Tested now and I confirmed that only external sdcard is supported to use F2FS partition. It won't boot when /cache partition is formatted to F2FS, when /data partition is formatted to F2FS, the Encryption Unsuccessful prompt will appear. Coldbird partition will be unify the storage upon using the Chinese unified zip file.
meh... another rom wich have not support for r63419 Display. Useless for me
Thx @opposeeker n @RoppoFon. I love u guys
roi_xordo said:
meh... another rom wich have not support for r63419 Display. Useless for me
Click to expand...
Click to collapse
If you'd kindly asked, whether this may be on the list for the future, you'd have gotten a friendly reply...since this thread is online not even one day(!) and I am still so happy that we have a future now with this ROM.
Too bad you've missed the chance to get on the beta list.
Many of us have this version of find7 (the display r63419 ), and your rom , like many others are not suitable for our devices. If this were a new problem , I would understand that it was not covered , but it is something that happens many months (or years) ago, and developers follow cooking roms that do not solve this. Inconceivable and useless . But calm down my friend, do not bother to fix it, I dont need this useless rom, in fact, I will sell this phone soon, with Omnirom installed , which works fine from the beginning.
Tried this rom on a 7a. It works perfectly (just have to adjust the dpi) but I noticed there's a big battery drain from Cyanogenmod System.
Hi dev could please see this, Problems or Features Request:
Can not disable hardware navigation keys when enabling software navigation keys. *problem*
Can not use F2FS partitions properly on /data and /cache partitions *feature request* I hope this will be added in this rom and take the speed advantage of F2FS over EXT4.
Enable Coldbird partitioning method out of the box without using chinese unify zip. *feature request*
QS Tiles must like crDroid/Cyanogenmod style where user can add multiple tiles without like clutter on the long list. In CyanogenMod and crDroid, you can scroll and select QS Tiles from left to right, in RR you can add but it is listed on a long list manner. *feature request*
@opposeeker installed this, choose SD card as internal storage, Unable to copy backup from system to phone using USB even after changing from charging to file transfer
Flashed this last night, running very well so far. I haven't found any issues yet. Thanks for this amazing rom
Charging is running out quickly. I wonder if there will be improvement in the new version?
Does this support the newer lcd?
thanks
A-Team Digital Solutions
*Exclusive Release*
E6 AIO ToolKit
-Model Supported-
Moto E6
-OS Supported-
Windows
Linux
2 Portable Linux Distro ISO's: AIo Tool_Buntu + AIO Tool_Cinnamon
The AIO Linux E6 Toolkit now helps u get the unlock device Id for you to enter into Motorola bootloader unlock website, and then uses the key u get in email from Motorola, to unlock bootloader.
Way more convenient than having to do all of the copy paste cut delete crap with fastboot output....
The program does that for u. ( Needs further testing)
Also fixed the images and flash method for linux AIO.
The Linux Tool has several other great options
A reboot menu
A logcat capture tool
Portable USB Bootable AIO Tool_Buntu + AIO Tool_Cinnamon Distros
Portable Linux ISO Distros That Run From USB With AIO ToolKit Preinstalled- AKA Porteus E6 AIO ToolKit
Comes with the ToolKit to Prep & Modify Your E6
Comes with Rom Kitchen to Modify Stock or GSI Roms
Comes with Telegram for Support
**Supports EFI or Legacy BIOS PC's**
Enjoy , and please leave feedback both here and in our telegram group.
**DISCLAIMER**
This is all test software. Please expect and report bugs. You can Report Bugs by Joining our Telegram Group
Windows, Linux & 2 Live Distros vailable live on our website in the free downloads section as promised.
https://a-team-solutions-downloads.myddns.rocks/
**Direct Links**
https://a-team-solutions-downloads.myddns.rocks/freefiles/Moto%20E6/
**Telegram Live Chat & Trouble Shooting Link**
https://t.me/Android_General_Chat
6-24-2020- Initial XDA Testing Phase & Release
7-1-2020- Software Updates, Bug Fixes, Added Windows Version
7-12-2020- Software Updates, Bug Fixes, Added 2 Portable Linux ISO Distros that include the ToolKit
Fastboot based flasher package for windows
LgPWN'd RESERVED
Note #1:
Adding here a separate package,
It works for others on our telegram group
This gets u ready to try any
of pizzaG recovery builds for the Moto E6
Un archive open ,
Make sure adb/fastboot are in path and working.
Unlock boot loader via Moto site.
Boot to bootloader mode
Open this folder and run the .bat file inside.
This is a test package, so it is subject to be removed
from public access without notice
And is not to be redistbuted
I nor anyone else are responsible for anything that happens ...
Unless it gets u the magisk in boot and TWRP with touch.
That's fully expected.
Test recovery builds available at our telegram group
Flash this and join there to get latest test builds from pizzag
NOTE: Linux users, just open the bat and copy paste the lines into terminal.
Somebody show PizzaG some love too.
Update: 06/30/2020
The AIO Linux E6 Toolkit now helps u get the unlock device Id for you to enter into Motorola bootloader unlock website, and then uses the key u get in email from Motorola, to unlock bootloader.
Way more convenient than having to do all of the copy paste cut delete crap with fastboot output....
The program does that for u. ( Needs further testing)
Also fixed the images and flash method for linux AIO.
The Linux Tool has several other great options
A reboot menu
A logcat capture tool
Windows and Linux package both now live on our website in the free downloads section as promised.
https://a-team-solutions-downloads.myddns.rocks/
Direct links
Linux AIO for E6:
https://a-team-solutions-downloads.myddns.rocks/freefiles/AIO-Moto-E6_Linux-Toolkit/
Windows BAT flasher version:
https://a-team-solutions-downloads.myddns.rocks/freefiles/MOTO_E6_AIO_PREP_PAK/
Enjoy , and please leave feedback both here and in our telegram group.
Cheers,
LgPWN'd
LgPWN'd said:
LgPWN'd RESERVED
Note #1:
The unlock bootloader option isn't going to work right, because I forget to make it prompt for device unlock_token
So for now, unlock your bootloader with the instructions available at Moto site.
I'll rewrite that option later on
Option rewritten awaiting uploading incremental update
Adding here a separate package, needs testing but
It works for others on our telegram group
This gets u ready to try any
of pizzaG recovery builds for the Moto E6
Un archive open ,
Make sure adb/fastboot are in path and working.
Unlock boot loader via Moto site.
Boot to bootloader mode
Open this folder and run the .bat file inside.
This is a test package, so it is subject to be removed
from public access without notice
And is not to be redistbuted
I nor anyone else are responsible for anything that happens ...
Unless it gets u the magisk in boot and TWRP with touch.
That's fully expected.
Test recovery builds available at our telegram group
Flash this and join there to get latest test builds from pizzag
NOTE: Linux users, just open the bat and copy paste the lines into terminal.
Somebody show PizzaG some love too.
https://drive.google.com/file/d/1_pTEWmCgBoiMeseZvTDVRuJ3dLiQMzF2/view?usp=sharing
Click to expand...
Click to collapse
Tested this package and everything worked as described. Got root and twrp. First boot may take some time but it works!
I've decided, both tools in this thread will remain free downloads . Tho they may be hosted at our website instead of Google drive later.
We have seen a moderate success with these tools,
And so they shall from here evolve into our final product.
What you see here will be the base for our advanced paid version of our tools.
We will add many more functions and options of course to the finished paid product.
But this base basic fully functional Free version will be here to help all the other poor boys like me !
Cheers
LgPWN'd
Hey I tried using this tool. I managed to get to the TWRP menu but they touch screen is not working still. Also I can't boot up regularly, 'UTAG configure bootmode' pops up on bootloader log
Can you help me?
come see US
tiptop87 said:
Hey I tried using this tool. I managed to get to the TWRP menu but they touch screen is not working still. Also I can't boot up regularly, 'UTAG configure bootmode' pops up on bootloader log
Can you help me?
Click to expand...
Click to collapse
Join the telegram group and i'll try to help troubleshoot,
also, there's 2 packages on this page, which did u try the Linux 1 on top or the windows package?
Just meet us in telegram we will get it sorted
UPDATE :
Scroll UP ^^^^^
LgPWN'd said:
Join the telegram group and i'll try to help troubleshoot,
also, there's 2 packages on this page, which did u try the Linux 1 on top or the windows package?
Just meet us in telegram we will get it sorted
Click to expand...
Click to collapse
Omg I only download from the first one post and not the other 2 packages
tiptop87 said:
Omg I only download from the first one post and not the other 2 packages
Click to expand...
Click to collapse
The first one is broken and I have not had the time to update the link for the new one, use the other two posted below for now
Has this been tested on Boost mobile Motorola E6 build PCB29.73-143?
Pretty sure I'm currently on the latest OTA update, and would like to know if this will work for me. Provides bootloader unlock and root if I understand correctly, but does root require booting into recovery every time as previous roots have for this device?
LMAO How many of you PWN'S Downloaded this????? HAHAHAH!!!!!!
Damn PizzaG That's just cold blooded....I like it.
k0mmand3r said:
LMAO How many of you PWN'S Downloaded this????? HAHAHAH!!!!!!
Damn PizzaG That's just cold blooded....I like it.
Click to expand...
Click to collapse
I must b late to the party, what's wrong and funny?
Broken download links
Works good
link down
OmniROM
Download
Images taged with MICROG contain a pre-installed ready to use
microG setup https://microg.org/
Images tagged with WEEKLY can be used to setup
official Google gapps
64bit build
Tablet mode configuration (not Android TV)
At least 4GB model recommened
No HW accelerated video playback
Mesa support for V3D is WIP so expect some graphic issues (especially on higher resolutions - HD 1920x1080 in general should be fine)
Support of booting from SD or USB by just changing config.txt (check README below)
GPIO support - monitor and set README.gpio
chrome (ium) is broken use alternative browser (firefox, edge)
for screen issues check https://www.raspberrypi.org/documentation/configuration/cmdline-txt.md
if you experience black bars connect to HDM1 or add disable_fw_kms_setup=1 to config.txt files
how to do updates? - check README.update
Adjust screen resolution:
To force a different screen resolution edit in /system/build.prop the line
#debug.drm.mode.force=1280x800
Remove the leading # comment and adjust to the screen resolution you want e.g.
debug.drm.mode.force=1280x720
Make sure to also check the README.txt in there
For questions please also use our official Telegram channel
https://t.me/OmniROM_Community
For current progress and how to build yourself check
README.build
XDA:DevDB Information
OmniROM, ROM for the Raspberry Pi 4
Contributors
maxwen, maxwen
Source Code: https://github.com/omnirom/android_kernel_brcm_arpi/
ROM OS Version: Android 11
ROM Firmware Required: 64bit
Based On: AOSP
Version Information
Status: Stable
Created 2020-10-28
Last Updated 2020-10-28
Builds
https://dl.omnirom.org/tmp/rpi4/
The plan is to have about weekly builds - at some point it will be part of all the other OmniROM devices with regular weekly builds
once the Android 11 cycle starts
20201016
Just a snapshot of the current state
Non microG builds will come later
20201028
WEEKLY and MICROG build
20201105
TWRP included
IMPORTANT
Check new recovery section in README for all the details
EVEN MORE IMPORTANT as posted before to get a working TWRP I had to disable userdata encryption for the moment
that means IF you try to boot this with your old userdata you will get an unpleasent surprise. You must start with
a fresh userdata partition (mkfs + tune2fs). You CAN (if you know what you do) create an backup BEFORE
updating by using adb shell and e.g. create a copy of userdata on an external USB device and copy that back afterwards.
But after all of that hassle from now on updating will be much easier since with TWRP you can create
userdata backups on an external USB device very easy
So going from this release an update could work like this.
1) boot your current install into TWRP
2) create an userdata backup on an external USB device
3) flash the new build - you dont need to care about userdata
just do whatever you always do with it e.g. resize
4) boot new build
5) go into Advanced settings and switch boot mode to recovery and restart
6) in TWRP restore the backup you created before from external USB device
7) flash switch_boot_rom.zip and reboot system
8) enjoy
add boot mode switch in Advanced settings
add audio output switch in Advanced settings
whatever has been done since the last build
20201115
fixed 5GHz WiFi AP
fixed Fondar USB touch screen
actual development
20201122
switch to new kernel base - big thanks to Konsta - with update to 5.4.77
update mesa to v20.2
initial work to support pi camera - not yet working but close
initial work to support gpio - IF you want to use gpio please contact me on tg cause I was too lazy to create a README for this yet
all core system updates and fixes
20201128
performance tuning
November security update
gpio support update
all core system updates and fixes
20201206
added gpioi-fan
cpufreq config in advancded settings
all core system updates and fixes
20201214
property persist.debug.drm.mode.force to adjust screen resolution
all core system updates and fixes
20201224
added disable_fw_kms_setup=1 to config.txt files. This should remove unneeded black bars for some screen when connected on HDM1. I did not see any problems on screens that have no issue with that anyway so I enabled by default. If you face issues remove line and report back please
enabled showing BT device battery level if applicable
all core system updates and fixes
Best Xmas wishes for those who care about it and looking forward to 2021
20201231
add WiFi firmware for p400
kernel update 5.4.85
add userdata resize and project quota enable script in TWRP
reduce dB of max media volume
all core system updates and fixes
Does this build support the original RPI 7" touch screen?
elhennig said:
Does this build support the original RPI 7" touch screen?
Click to expand...
Click to collapse
Not out of the box since I dont have one of those to test myself
BUT it should contain the needed overlays so if you know your way around
give it a try and report back if there is something missing.
Regarding "No HW accelerated video playback", is there a chance this is coming anytime soon?
Thinking about using this for MS xCloud gaming.
maxwen said:
Not out of the box since I dont have one of those to test myself
BUT it should contain the needed overlays so if you know your way around
give it a try and report back if there is something missing.
Click to expand...
Click to collapse
I am afraid I have no idea how to build my own ROM or configure overlays respectively. I guess you just notice from my answer that this is the sad truth
ich_mind said:
Regarding "No HW accelerated video playback", is there a chance this is coming anytime soon?
Thinking about using this for MS xCloud gaming.
Click to expand...
Click to collapse
Depends mostly on mesa development - but nothing I would hold my breath for
elhennig said:
I am afraid I have no idea how to build my own ROM or configure overlays respectively. I guess you just notice from my answer that this is the sad truth
Click to expand...
Click to collapse
well - the thing is that this does not have anything to do with building ROMs
should all be possible by modifying config.txt
Looking at the LOST OS builds might give some hints since I think he supports it
Just one word of wisdom here from me since I saw in some reports as something negative
"It’s stuck in “tablet mode” instead of Android TV mode"
I really dont think a raspi is a well equipped device to be used for ATV when you get
a ATV USB stick from e.g. Xiaomi for about 40E that simply works without issues and
has official google support.
So while everyone feel free to use our repostories to create an ATV build dont ask me for it cause I wont do it.
please help after propper flash to my sd card all i get is the no input screen as if nothing is connected to my tvs hdmi port
Thanks a lot for the work you put into this.
I'm really looking forward to how this project will develop.
If I may I have a stupid question - is there a way foreseen to safely shutdown the pi? I mean I know how to setup a safe shutdown in e.g. raspbian but I doubt it's the same in android.
Growking99 said:
please help after propper flash to my sd card all i get is the no input screen as if nothing is connected to my tvs hdmi port
Click to expand...
Click to collapse
I think you hit me already in TG - but just to reiterate here again - as it is in also the README
Using latest firmware is MANDATORY - 64bit support has been added a few months ago
without you will get the described no boot
Best is to flash latest firmware (which also includes USB boot even if you dont need it)
There are a long list of pages describing how to update. Just linking one here for reference
https://www.tomshardware.com/how-to/boot-raspberry-pi-4-usb
You MUST do that in e.g. Raspberry OS so best do it before even starting with Android
lernfaehig said:
Thanks a lot for the work you put into this.
I'm really looking forward to how this project will develop.
If I may I have a stupid question - is there a way foreseen to safely shutdown the pi? I mean I know how to setup a safe shutdown in e.g. raspbian but I doubt it's the same in android.
Click to expand...
Click to collapse
Long press the power button in the navigation bar -> shut down
That's pretty cool, thanks for hard work.
But it's still not usable for daily use as a media center since there is no HW accelerated video playback.
All Android builds on raspberry pi have the same issue .. :/
I think that these builds are just proof that you can have Android on raspberry pi than anything else.
flyl0 said:
That's pretty cool, thanks for hard work.
But it's still not usable for daily use as a media center since there is no HW accelerated video playback.
All Android builds on raspberry pi have the same issue .. :/
I think that these builds are just proof that you can have Android on raspberry pi than anything else.
Click to expand...
Click to collapse
Welcome captain obvious - tell us something new...
maxwen said:
Welcome captain obvious - tell us something new...
Click to expand...
Click to collapse
It's just an observation lol what I don't understand is that there are almost no differences between Android 9, 10 or 11 for pi, they are all the same.
I wonder what's the real point to make all these builds which all lack the same features.. No disrespect, I'm just wondering.
Captain obvious
flyl0 said:
It's just an observation lol what I don't understand is that there are almost no differences between Android 9, 10 or 11 for pi, they are all the same.
I wonder what's the real point to make all these builds which all lack the same features.. No disrespect, I'm just wondering.
Captain obvious
Click to expand...
Click to collapse
You are just too focused on what you want to do with the device
does it have google apps out of the box
vedforeal said:
does it have google apps out of the box
Click to expand...
Click to collapse
of course not - this would be illegal
We are not in China here ...
PS: I did not find any android-11 gapps out there that would work currently
So the only way is anyway microG for now - which is enough for most people
i tried to boot off 32gb usb and it wont work
and first thing before you say anything about my bootloader being out of date its not here is the bootloader output BCM2711 detected
Dedicated VL805 EEPROM detected
BOOTFS /boot
BOOTLOADER: up-to-date
CURRENT: chu 03 set 2020 12:11:43 UTC (1599135103)
LATEST: chu 16 abr 2020 17:11:26 UTC (1587057086)
FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000137ad
when i try to boot the build (from the website i didnt compile it) with either the microg or the weekly build after flashing the pi just simply wont start and the green and red light just keeps flashing and nothing happens i was able boot twisterOS just fine off this same usb so its this build i dont know if i did something wrong but the file system was present in gparted and i tried booting it without expanding the partition and with doing so. also i tried to "fix" all the partitions using gparted and that did nothing also i noticed that the /boot directory in this build seems a bit empty compared to my manjaro build i know your working hard on this but this might be a bug in your build and id be willing to help you fix it