[ROM] [OFFICIAL] LineageOS for the Shield Portable - Shield Android Development

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 6.0.1 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
LineageOS 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 below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds : https://download.lineageos.org/roth
Root addon : https://download.lineageos.org/extras
Google Apps : http://opengapps.org/
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console_ramoops. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
LineageOS for the Shield Portable, ROM for the Nvidia Shield
Contributors
Steel01
Source Code: https://github.com/LineageOS
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Current Stable Version: 13.0
Created 2017-02-25
Last Updated 2017-02-25

Wow nice work! Thanks for porting Lineage OS to Nvidia Shield Portable. So before I want to do download and install it... Does everything work? The Nvidia controller, Power button, etc?

edtide25 said:
Wow nice work! Thanks for porting Lineage OS to Nvidia Shield Portable. So before I want to do download and install it... Does everything work? The Nvidia controller, Power button, etc?
Click to expand...
Click to collapse
All the hardware works, yes. Some of the software features aren't ported like touch mapping for the gamepad, wireless controller support, gamestream, etc. But for the normal use cases I have of retroarch, a handful of controller enabled native games, and kodi, everything works beautifully. So, depends on your use cases.

Is this full android or ATV like the one you built for me?

This is a normal build. Probably won't do atv for officials unless the userbase really asks for it. Need to fix gapps before that would even be considered, though. Only 32 installs atm, and half of them are probably me testing.
So, haven't had a bootloop on the new build myself. Anyone having any troubles at all? Seeming really solid to me finally.

When using snes9x ex the performance is way down in comparison to nvidia update 110. The screen refresh rate as reported in the emulator is 48.85hz. If that's correct its far too low.
In addition there appears to be another bug where ui animations stutter and loop back a few frames on themselves. Not sure if this is related to the apparent refresh rate issue.
I would also like to chime in on the possibility of an atv build. Without the right stick mouse functionality of the stock firmware the tv interface makes a whole lot more sense.
Thanks for the build and the work you've put in on this and fixing nvidia messes over the years.

That's great to know!!
Once they manage to port the touchmapper and some other software from this device to it, I'm pretty sure to stick with it forever.
I'm using lineage at my MotoG3 and i'm lovng git!!

Thanks for this. I just installed it. I had been running your 12.1 CM ROM the last week. I decided to try it out after had enough of the buggy stock ROM. I would install apps, and they would (seemingly) randomly disappear. I would install them over and over again. Anyways, your custom builds of CM/Lineage have been working beautifully.
The only thing that I'm really missing is the gamepad touch mapper. I know you've said that you don't use it, but it seriously hurts not having it, because you can so quickly and easily make most touchpad only games work so quickly and easily.

Ziontist said:
The only thing that I'm really missing is the gamepad touch mapper. I know you've said that you don't use it, but it seriously hurts not having it, because you can so quickly and easily make most touchpad only games work so quickly and easily.
Click to expand...
Click to collapse
The problem is that Nvidia's touch mapper is mostly in the stock framework. That's code I don't have access to and even if I was interested in trying, I don't have near the time needed to try and recreate it. And tincore is still an option. I know it's a major pain to set up, but it does work.

Steel01 said:
The problem is that Nvidia's touch mapper is mostly in the stock framework. That's code I don't have access to and even if I was interested in trying, I don't have near the time needed to try and recreate it. And tincore is still an option. I know it's a major pain to set up, but it does work.
Click to expand...
Click to collapse
Gotcha. What a shame. I guess Tincore Mapper it is. It seems like something that probably is really awesome, once you invest the time into learning it. There's probably way more in depth options and things you can do with it, than Nvidia's mapper (but I'll still miss the ease and convenience lol).

Hello,
Are there any plans to get Noughat on board of Nvidia Shield Portable?
thank you

Well, good news. I actually got the portable to boot N / 14.1. Bad news. It's a jerky mess. I took the advice of one of the other Tegra 4 devs and stuffed the blobs from the Jide Ultratablet in there. Flipped a couple flags, and voila, it boots. No sound, no touch, and quite jerky. But at least I finally found a graphics stack that works. I can work with that, find out which specific pieces I need to pull of the graphics stack and leave the other Roth stuff in place. Should be able to make it usable. No guarentees on when, but I'll keep working on it.

Is it somehow possible in this rom tu use nvidia's shield hub app to use gamestream and geforce now? When you install and run the app those options dissapear from the app. I know I can use moonlight to stream, just curious why it doesn't work on this rom, maybe the app detects that it's not an official firmware and disables it or some libraries missing?

Try installing nvidia games from google play.

Yeah tincore mapper is a pita the stock nvidia mapper is way easier.

For the these two platform, which do I download? Cause last time I tried to update, the device was bricked and somehow magically started up today and went back to thinkering with my shield lol
i'm currently on android 6.0.1 with CyanogenMod Version 13.0 Nightly build
Root addon : https://download.lineageos.org/extras
Google Apps : http://opengapps.org/

What's different between this and CM13?

Lineage is the continuation of CM. No one is working on CM anymore.
@danny_boi: Unfortunately flashing from CM to Lineage official builds will require a wipe due to a change in signing keys. Then you want the 13.0 arm su zip and one of the arm 6.0 opengapps packages. I personally use micro, which I also believe is the largest that will fit on this devices small system partition.

painkiller_93 said:
Is it somehow possible in this rom tu use nvidia's shield hub app to use gamestream and geforce now? When you install and run the app those options dissapear from the app. I know I can use moonlight to stream, just curious why it doesn't work on this rom, maybe the app detects that it's not an official firmware and disables it or some libraries missing?
Click to expand...
Click to collapse
fr500 said:
Try installing nvidia games from google play.
Click to expand...
Click to collapse
Hello about to flash this rom and wanted to findout if the shield hub works as this is not mentioned when I searched. Does installing nvidia games from Google play work please?

marvi0 said:
Hello about to flash this rom and wanted to findout if the shield hub works as this is not mentioned when I searched. Does installing nvidia games from Google play work please?
Click to expand...
Click to collapse
You can install the app from the play store but it won't show you the options to use gamestream or geforce now. If you want to use gamestream you can install moonlight app.

Related

[DISCONTINUED] [8.1.x][OFFICIAL][DISCONTINUED] CarbonROM | cr-6.1 [kagura]

{
"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"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash!
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
We recommend MindTheGApps. OpenGApps should work, but please make sure you clearly mention the gapps you're using when reporting bugs.
Notice:
For this ROM to work you need to use the latest ODM Images. If you need additional guidance on how to do that, please refer to Sonys Guide on how to flash an ODM Image.
Get CarbonROM
Changelog
Join the CarbonROM Discord server
GitHub
Gerrit
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Sony Xperia XZ
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Nightly
Created 2018-03-31
Last Updated 2018-07-19
No one tried this rom yet? I have a problem over here. It keeps asking for password after the CarbonROM logo even though I wipe everything clear, any ideas? What I was doing was flash 41.3.A.2.99 with everything wiped, flash ODM, flash TWRP, flash the rom and then Pico OpenGapps. Something wrong with my procedure? Thanks in advance.
EDIT1 : Oh yeah, forgot to mention my device is F8332, it isn't supported?
LuthfiKun said:
No one tried this rom yet? I have a problem over here. It keeps asking for password after the CarbonROM logo even though I wipe everything clear, any ideas? What I was doing was flash 41.3.A.2.99 with everything wiped, flash ODM, flash TWRP, flash the rom and then Pico OpenGapps. Something wrong with my procedure? Thanks in advance.
EDIT1 : Oh yeah, forgot to mention my device is F8332, it isn't supported?
Click to expand...
Click to collapse
Use the "format data" option in TWRP to get rid of encryption, wipe doesn't clear encryption. If coming from stock, thats necessary unfortunately due to differences in the encryption used. Otherwise (if coming from AOSP) the password its asking for would be the one you used before.
Dual sim support?
Myself5 said:
Use the "format data" option in TWRP to get rid of encryption, wipe doesn't clear encryption. If coming from stock, thats necessary unfortunately due to differences in the encryption used. Otherwise (if coming from AOSP) the password its asking for would be the one you used before.
Click to expand...
Click to collapse
Alright format it is.
agentsandy007 said:
Dual sim support?
Click to expand...
Click to collapse
No it isn't. At least out of the box. You can find a patch on Sony AOSP Build thread.
Volte Supported??
First of all, thanks alot @Myself5 and all other devs, who are working hard to bring this to our XZ :good:
My experiences after 1 day:
- rom is very smooth and snappy.
- root via Magisk v16 & Xposed 90.1-beta3 (systemless) works flawlessly
- the fp sensor always works, but it's not as sensitive as with stock
- night light worked - until I've installed Substratum and a Substratum theme, but after that it doesn't work anymore (even after deactivating, uninstalling the theme, a system restart and deinstalling the Substratum app it sill doesn't work). Also a dirty flash of the rom.zip didn't help to get it working again.
- the build-in camera takes acceptable pics (not as well as the stock camera, but acceptable); also focussing is a little slower than stock. Another thing is, it's not possible to chance the location to save the pics to the ext. sdcard.
- formatted as a portable storage, the ext. sdcard item on the left of the status bar can't be removed (see attachement)
- the battery consumption is a bit high (from 100 % to 98 % in 1 h - without doing anything)
But in the whole, it's really promising for th 1st official build :good::good::good:
Klaus N. said:
First of all, thanks alot @Myself5 and all other devs, who are working hard to bring this to our XZ :good:
My experiences after 1 day:
- rom is very smooth and snappy.
- root via Magisk v16 & Xposed 90.1-beta3 (systemless) works flawlessly
- the fp sensor always works, but it's not as sensitive as with stock
- night light worked - until I've installed Substratum and a Substratum theme, but after that it doesn't work anymore (even after deactivating, uninstalling the theme, a system restart and deinstalling the Substratum app it sill doesn't work). Also a dirty flash of the rom.zip didn't help to get it working again.
- the build-in camera takes acceptable pics (not as well as the stock camera, but acceptable); also focussing is a little slower than stock. Another thing is, it's not possible to chance the location to save the pics to the ext. sdcard.
- formatted as a portable storage, the ext. sdcard item on the left of the status bar can't be removed (see attachement)
- the battery consumption is a bit high (from 100 % to 98 % in 1 h - without doing anything)
But in the whole, it's really promising for th 1st official build :good::good::good:
Click to expand...
Click to collapse
Hello, is the battery life when used good ? As good as stock ?
And does it have that bug when if you record video the result will be green ?
Can you upload screen recording of rom from home to settings and other functions.
I plan on flashing this soon, but I figured I'd tell you, your link to the Carbon FAQ is broken.
ilininja said:
Hello, is the battery life when used good ? As good as stock ?
And does it have that bug when if you record video the result will be green ?
Click to expand...
Click to collapse
The battery consumption while in use is ok. But my device doesn't go into deepsleep while the screen is off. So I had lost about 23 % in 10 hrs - leaving the device untouched!
Video recording works; I haven't noticed that bug.
Saroj11488 said:
Can you upload screen recording of rom from home to settings and other functions.
Click to expand...
Click to collapse
Sorry, I went back to stock for now, as there's a new stock fw (41.3.A.2.107).
I have a few bugs to report. First, the fingerprint sensor is extremely slow, about half or even one third of the speed compared to stock. Second, could you guys please fix the deepsleep? That one is not working for now. And third, Night Light does not work at all...
Thank you for updating the XZ to Android 8.1 I am glad to see carbon rom on this device although it is not that stable for now.
Really nice ROM and I'm looking forward to make this my daily driver, I tried it for two days and these are the bugs I found:
1: GPU performance is really bad with 2d games and google maps lagging all the time when they never do on stock
2: CPU performance is inferior compared to stock, especially single threaded
3: enabling 120 hz display won't do anything and the settings or UI will crash when leaving the page
4: fingerprint seems to be sometimes less responsive, usable but can be improved
Camera is not so bad and the modded google camera works well, hopefully this will become the first proper AOSP based platform for this device that has only seen failures until now, keep up the good work.
Can I dirty flash this rom for just update?
I use Carbon Rom 3/31 version, but I can't use delta update because my device cannot receive the stock script.
I must change the rom script with Notepad+.
So...can I use dirty flash or....could you manage it?
Thanks for continously updating this rom and thank you for fixing the bug with the fingerprint sensor.
I'm not sure if deepsleep has been fixed but there is a big problem with playing music. I can't even play any music track at all...
Hello, looking forward to make this my daily driver, is it possible ?
What I would want is decent battery life and camera.
Hello. I tried to listen to music after installing the ROM, but the earphones are disconnected as soon as they are connected to the smartphone.
The earbuds pfe 132 and are made up of earphones with an iphone microphone.
L'ily said:
Clean flashed the 10th build along with Rytekk's dual-SIM patch, Pico Open GApps and Magisk 16.3 to my F8332 and other than that annoying SD notification (which can be banished to the notification drawer by making System UI notifications low priority) and Night Light not working, the only other major issue raised ITT of the CPUs not entering Deep Sleep is fixed according to Adiutor.
Great stuff. I haven't been able to standardise on one ROM since the CM days (interesting side note, it looks like you built the kernel for the NOCT build on my Z2 tablet).
I recommend this to anyone for daily use. Also, lower your expectations to realistic levels guise. I remember when XDA threads were for flagging major broken functionality, not complaining that a few amateur enthusiasts weren't putting out work that competed on every indicator against the finished product of a multibillion-dollar for-profit international conglomerate.
Sent from my Sony Xperia XZ using XDA Labs
Click to expand...
Click to collapse
Could you please give a link to that dual SIM patch?I have flashed this ROM on my F8332 successfully but none of my SIM cards works
Hello, with the 10th build I have a problem with the installation, it keeps telling me that Google services framework stopped.
Any help ?
(V11 vendor image odm, formated data)
BigMixman said:
Could you please give a link to that dual SIM patch?I have flashed this ROM on my F8332 successfully but none of my SIM cards works
Click to expand...
Click to collapse
Add these lines in build.prop, and reboot.
Code:
persist.multisim.config=dsds
persist.radio.multisim.config=dsds
ro.telephony.default_network=9,0

[ROM][9.0.0_r52][A2017X][UNOFFICIAL] ArrowOS 9.x

YAPR [YET ANOTHER PIE ROM]​
{
"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
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Click here (read more on our website)
Checkout more documentation at (maintainership/contributing): Check this out
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : check how to
DOWNLOADS
ROM:
ArrowOS 9.x
Arrow-v9.0-axon7-UNOFFICIAL-20191117
LATEST Arrow-v9.0-axon7-UNOFFICIAL-20200126
Gapps: Click Here for GApps
Note : Pico, Nano or Micro Gapps are recommended.
ROM Source: https://github.com/ArrowOS
--------------------------------------------------------------------------------------------------------------------------------------
Installation :
1. wipe system, vendor, data, cache
2. install ROM
3. GApps, Magisk
4. reboot
Contributors
@raystef66
Credits to
ArrowOS Team
LOS Team
KERNEL SOURCE: https://github.com/OrdenKrieger/andr...el_zte_msm8996 thnx @OrdenKrieger
ROM OS Version: 9.x PIE
ROM Kernel: Linux 3.18.x
ROM Firmware Required: Unlocked Bootloader, Latest TWRP Recovery
Based On: LineageOS device, vendor, kernel
Version Information : 9.x
Status: Pure & Stable...afaik
Sec. Patches : 2020.01.05
Created : 2019.10.12
Last Updated : 2020.01.26
Thanks Raystef66, I'm using this ROM as of tonight. I have successfully upgraded from AOSP 6.5 (May) on my A2017 (chinese).
Much smoother and quicker, although that is expected with a new ROM install after so long! I hope to give you more feedback.
Dungeon Maker had issues installing, which i think may be due to CTSmismatch in magisk (v20). I still have not been successful in passing it.
Do you have a kernel recommended? Or which kernel do you have with this ROM?
Thank you for all of your hard work in keeping the Axon7 ROMs active.
darth_antz said:
Thanks Raystef66, I'm using this ROM as of tonight. I have successfully upgraded from AOSP 6.5 (May) on my A2017 (chinese).
Much smoother and quicker, although that is expected with a new ROM install after so long! I hope to give you more feedback.
Dungeon Maker had issues installing, which i think may be due to CTSmismatch in magisk (v20). I still have not been successful in passing it.
Do you have a kernel recommended? Or which kernel do you have with this ROM?
Thank you for all of your hard work in keeping the Axon7 ROMs active.
Click to expand...
Click to collapse
Install MagiskHidePropsConfig and Busybox and run "props" via terminal and choose f.e. the axon7 oreo FP. You'll pass cts. I run magisk 20.0 and all ok.
I suggest installing the RC1.2 kernel which you can find HERE.
In my next build I was planning to take that one within the ROM. But you can install it without probs tho
Btw, picture below is on new crDroid but MHPC should give u the same results on ArrowOS
Thanks Ray, I appreciate your reply and knowledge of this.
The app updated and worked without needing the ctsmismatch pass, so i'll just wait for your update.
In the 3 days since I've been using this ROM, I can appreciate the following coming from AEX 6.5. A freshly installed ROM does have some of these benefits so I'm probably biased.
1. Arrow has a faster boot into the rom. the loading screen is awesome and the loading effect is great.
2. Arrow uses half as much ram, 1.7gig compared to 3.2gig. This is probably a fresh install thing though, as i have a lot less apps now.
3. quicker and cleaner.
Thanks, the only thing i hope you have in future builds is the cts, and the option for when you reset the phone, there are the extra options to boot into recovery.
*found this option under 'buttons' in the android menu, apologies.
Ive been using this for a month now and its been awesome.
The only bug or issue I've had is the dictionary and auto-correct. Auto-correct does not work at all, and it doesnt recognise mis-spelt words. Android keyboard seems to have limited option.
Thank you for developing this ROM.
NEW ARROW BUILD 2019.11.17
Arrow-v9.0-axon7-UNOFFICIAL-20191117
changelog :
* november sec. patches
* added RC1.2 baddar kernel
* added proper thermal fix
Hi raystef66,
Thank you so much for your great efforts and sharing with this amazing ROM.
The only issue for me is so far - Gesture Typing of AOSP Keyboard is not working.
I have checked its setting to make sure the gesture typing function turned on, but still not working.
Is it experiencing only me? how about other people?
I'm sure that this is an ignorable minor bug for me, otherwise this ROM is finely matured exquisite PIE ROM.
In the next update, however, would you mind adding the advanced settings option?
Thanks again.
BUILD 2019.11.17 First Impressions
Pretty happy with this ROM coming from the most recent (now deprecated) Lineage 15.1 Official Nightly and really loving Arrow.
The only thing I'm missing is the ability to slide finger on status bar to adjust brightness.
I noticed the battery life seems noticeably better. I was hours away from replacing my Axon due to the battery just being horrible, even after being recently replaced. Everything seems buttery smooth besides the Gcam app I'm using. It works, but very sluggish.
Please do recommend your favorite camera app for this ROM.
I'm passing SafetyNet after installing Pixel Android 9 Props.
GPS took over a minute to get a lock the first time around, but now works within 15 seconds as expected.
USB tethering has been temperamental. I disabled hardware acceleration via Developer Settings and it seems to be working better.
I can confirm that swipe texting on AOSP keyboard does not work, however works fine with Gboard.
Hardware keys work as expected however even with the home button Long Press Action set to activate Google Assistant it does nothing. It seems that the Google Assistant action does not work with any of the button settings including the on screen navbar.
I haven't been able to get USB-OTG to work on any ROMs since ditching stock. Maybe someone knows a fix. It doesn't work in TWRP either, so maybe it's my hardware.
Besides a few minor quirks, I am hugely grateful for this ROM providing Pie and rekindling my love for this aging Axon. Thank you!
Swipe typing on the aosp keyboard just means it's missing the libs. Seen it before. Last I checked open gapps aroma let you restore the libs.. But using a different keyboard is a better idea.
Thank you for the update and fixes! Still using this since September.
As above, the keyboard (and in my case, autocorrect doesnt work as well as other roms) is the only thing thats not going so great.
Apart from that, its flawless. Thank you again!
Hi,
Thank you for this very good ROM!
Tested several days, I only noticed a bug in the Google camera with the GAPPS stock. When the application is updated, it stops working.
I also wonder if wifi calls work. Maybe I didn't find the right option to activate them.
(and the GPS sometimes remains blocked at a location and does not update itself).
Everything else is perfect!
Wi-Fi access point and usb modem do not work ....
Wi-Fi access point and usb modem do not work .... sometimes attempts to turn on those options cause a system lock and forced hard reset
PS I turned off hardware acceleration as someone wrote here - USB tethering works ... the problem with the wireless hot spot remains ...
PS2 I don’t know why, but during a 10-kilometer trip, GPS is lost several times, and somewhere near the final destination of the trip, the phone suddenly starts to show the right way this is already becoming a tradition.....
I my location on this ROM i have a problem with conersation. Before i used AOSP 5.7 based on Oreo and in my room i could talk by phone. Acctually i must go to kitchen because only there i can normally talk.
It's look like worse signal or not all bands compatible. My Axon have B20 (it isn't china version). Sometimes i have problem with internet - connecting by LTE isn't possible. When i was in London i couldn't use internet. Phone found transmitter, about 3/5 signal strange but any page or facebook lite no load.
NEW ARROW BUILD 2020.01.26
Arrow-v9.0-axon7-UNOFFICIAL-2020.01.26
changelog :
* Merge branch 'android-9.0.0_r52'
* jan 2020 sec. patches
Thank you for not abandoning our dear Axon 7. Please continue to develop ROMs for him!
Thank you very much for the rom, my Axon 7 is now back to life.
Dark mode isn't forced in other apps, like google photos.
larsky said:
BUILD 2019.11.17 First Impressions
Pretty happy with this ROM coming from the most recent (now deprecated) Lineage 15.1 Official Nightly and really loving Arrow.
The only thing I'm missing is the ability to slide finger on status bar to adjust brightness.
I noticed the battery life seems noticeably better. I was hours away from replacing my Axon due to the battery just being horrible, even after being recently replaced. Everything seems buttery smooth besides the Gcam app I'm using. It works, but very sluggish.
Please do recommend your favorite camera app for this ROM.
I'm passing SafetyNet after installing Pixel Android 9 Props.
GPS took over a minute to get a lock the first time around, but now works within 15 seconds as expected.
USB tethering has been temperamental. I disabled hardware acceleration via Developer Settings and it seems to be working better.
I can confirm that swipe texting on AOSP keyboard does not work, however works fine with Gboard.
Hardware keys work as expected however even with the home button Long Press Action set to activate Google Assistant it does nothing. It seems that the Google Assistant action does not work with any of the button settings including the on screen navbar.
I haven't been able to get USB-OTG to work on any ROMs since ditching stock. Maybe someone knows a fix. It doesn't work in TWRP either, so maybe it's my hardware.
Besides a few minor quirks, I am hugely grateful for this ROM providing Pie and rekindling my love for this aging Axon. Thank you!
Click to expand...
Click to collapse
##############################
1- To enable assistant you have to choose the google app for the default assistant in the default apps settings.
2- I have trsted nearly 80% of all gcam apks, and the best one so far and the newest is Urnyx05 latets version, you can find it here
https://1-dontsharethislink.celsoazevedo.com/file/filesc/GCam_7.3.018_Urnyx05-v2.2-fix.apk
3- Aosp keyboard is a just terrible, just get Gboard.
4- Clean flashing the rom will solve GPS and USB problems, always clean flash.

[11][OFFICIAL] CarbonROM | cr-9.0 [fajita]

{
"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"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled ROMs, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best ROM we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub...
What is R?
Our release of Android 11, titled CR-9.0.
It provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. R delivers a set of unique features, like a system-wide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! As always, make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has addressed it already. Especially if you're even close to new at this.
2) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
3) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Install Instructions:
You should start off with the latest Android 11 OxygenOS stable build on both slots and then proceed to flash Carbon.
The easiest way to do that is by installing the latest Version and then copy it by flashing the copy-partitions script made by LineageOS in the recovery. (See install Instructions for the recovery)
The recommended way to install is using the CarbonRecovery linked below.
Download the ROM and optionally GApps, reboot to recovery by flashing the boot.img using
Code:
fastboot flash boot fajita-YYYYMMDD-HHMM-boot.img
followed by booting to recovery through the bootloader.
Sideload the ROM. (Apply Update -> Apply from ADB -> Connect to PC ->
Code:
adb sideload CARBON-CR-9.0-R-WEEKLY-fajita-YYYYMMDD-HHMM.zip
Reboot recovery (to switch between slots)
Flash GApps/MicroG through sideload like above (optional)
Factory reset -> Format data/factory reset (Make sure to have a backup of your data)
Done
Followup builds can be updated through the builtin CarbonDelta Updater or by dirtyflashing.
Download
Download CarbonRecovery
Homepage
Join the CarbonROM Discord server
Meet us on Telegram
GitHub
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
​
FINALLY! YES! WOOHOO!
I just want to confirm based on the top post, that for the 6T we are indeed using the A10 base since that is still the "Latest Stable Build"?
Void4ever
void4ever said:
I just want to confirm based on the top post, that for the 6T we are indeed using the A10 base since that is still the "Latest Stable Build"?
Void4ever
Click to expand...
Click to collapse
Indeed, the current required base is the latest Android 10 stable.
Thx @Myself5 I appreciate the info. Hopefully I don't run into the same Android Auto issues I did with 8.0. However to be 100% fair I ran into those issues with multiple other roms as well. Something to do how OxygenOS handles the detection of USB vs ASOP I assume on the 1+ hardware. Literally the only thing thats kept me from running custom roms.
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
void4ever said:
Thx @Myself5 I appreciate the info. Hopefully I don't run into the same Android Auto issues I did with 8.0. However to be 100% fair I ran into those issues with multiple other roms as well. Something to do how OxygenOS handles the detection of USB vs ASOP I assume on the 1+ hardware. Literally the only thing thats kept me from running custom roms.
Click to expand...
Click to collapse
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Myself5 said:
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Click to expand...
Click to collapse
I would be happy to provide logs if/when i run into an issue.
I can give some background right now, which may not be very useful since we don't know if 9.0 is going to have the same issue. I don't recall if it was you @Myself5 or the dev from Paranoid, but we had a short discussion about this a while ago. If I recall one of you suggested it might be the modules you were using from the ASOP libs maybe? I'd have to go search through the old threads.
The only car I have to test with is my 2019 Traverse. AA works perfect everytime with stock Oxygen, and the only other ROM I ever ran into that seemed to work fine was AOSIP, however the rom itself was unstable on my hardware and I had to remove it due to my alarm not going off cuz the phone would crash overnight. So perhaps there's something in the way they implemented USB detection.
The last rom I tested (I forget which) I noticed that the phone wasn't even popping up the USB notification (where you can select File Transfer, USB tethering, MIDI, PTP, No data transfer) when connecting to the car.
Anyways this is far more info than we need until I can test it. Hopefully this weekend if not sooner.
Bit rusty running custom Rom
I was able to install perfectly fine, running perfectly just a bit iffy on Rooting afterward.
Can we install Magisk through CarbonRecovery? Do we need to keep the Carbon Recovery as the defacto Recovery for this Rom? Can I go back TWRP?
Mckillagorilla said:
Bit rusty running custom Rom
I was able to install perfectly fine, running perfectly just a bit iffy on Rooting afterward.
Can we install Magisk through CarbonRecovery? Do we need to keep the Carbon Recovery as the defacto Recovery for this Rom? Can I go back TWRP?
Click to expand...
Click to collapse
Yes you can install Magisk through Carbon Recovery. TWRP should be just fine, especially as the Recovery isn't used for updates etc as that is all done through Seamless updates in CarbonDelta on the system itself.
When i installed the rom i had to install the gapps after i was done with the phone setup. Otherwise the Android Setup would crash as soon as android booted.
The screen would then go cracy (blinking button icons) and I couldn't do anything.
I also can't update using the ota update.
Just tells me "Update could not be installed".
Other than that it works great
Edit: I didn't see the message about the video playing fix in some apps.
Updated from to latest version and now all videos work
Myself5 said:
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Click to expand...
Click to collapse
Thank you for this great rom .
I had a problem with Android Auto, It's solved but I report if someone faces the same issue.
With Nikgapps basic on cr-9.0, Android Auto was not working: the phone was detected by the car (Peugeot 2008 from 2018), but when I initiated the connection the phone hangs and freeze, nothing happens on the car and I often had to reboot the phone.
It was an error related to usb permission in the logs.
It was solved using the stock package of Nikgapps (the problem is reported on other other devices as well). I was using the basic package of nikgapps on carbonrom cr-8.0 without problem, I don't know what changed that made the stock package needed.
I did not try for other gapps providers, but at first glance, this problem doesn't seems related to the rom itself but more to the gapps package.
My facebook and insta videos r not playing.. can't able to see them .. how to fix it
Prabhuraj 0 said:
My facebook and insta videos r not playing.. can't able to see them .. how to fix it
Click to expand...
Click to collapse
By updating to the latest build as mentioned a few posts above yours.
On that note:
I've found and fixed an issue where the device would not be reported as an A/B device properly which resulted in the integrated updater being broken. It will be fixed in wednesdays build (along with August ASBs) but you will need to manually update (through recovery) to that build.
So I haven't had a chance to install because I had to be OnCall for my job this week, no messing with my phone...... BUT that may have been a blessing?
I see the Stable A11 was released today for the 6 and 6T. Are there plans to rebase Carbon 9.0 to this?
Void4ever
Solid ROM! I haven't used Carbon since the Epic 4g phone. I'm running latest without Gapps, and I have to ask is there a better camera available outside of the play store? I know its a long shot but thought I'd try.
Google Camera, just google up gcam ports
only reason fr nt using Carbon is there is no
face unlock
Why is there no new download link from 25/8 for fajita. I can see the update on my phone but I want to flash the update.zip file from recovery.
Thanks
Wishmasterflo said:
Why is there no new download link from 25/8 for fajita. I can see the update on my phone but I want to flash the update.zip file from recovery.
Thanks
Click to expand...
Click to collapse
The last version also took a while (~4-7 days, not sure) until it was available on the website
I see it now. Probably didn't wait long enough!
Also @Myself5 is this by chance based on A11 now, or still A10?

[ROM][UNOFFICIAL][11] LineageOS 18.1 for Fire TV Stick Lite/3rd gen (sheldon/p)

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS 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 below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.​Instructions:
Reboot to TWRP
Wipe data, system (/system_root) and cache
Flash the ROM and the GApps
Reboot and enjoy!
Downloads:
Builds: https://github.com/mt8695/android_device_amazon_sheldon/releases
GApps: Open Gapps (arm/11/tvmini)
Reporting Bugs:
DO NOT Report bugs if you're running a custom kernel, you installed Xposed or you installed Magisk
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Known issues:
Dolby Digital Plus™ E-AC-3
Netflix
Notes:
SELinux is in Permissive mode
The ROM supports both sheldon (Fire TV Stick Lite) and sheldonp (Fire TV Stick 3rd gen)
Do not ask for ETAs
How do i...
Unlock and install TWRP?
Follow the instructions of the unlock thread
Go back to the original/stock ROM?
Download the stock update.bin (sheldon | sheldonp) and flash it using TWRP
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Contributors
R0rt1z2, k4y0z, t0x1cSH, diegocr
Source Code: https://github.com/mt8695
Kernel source: https://github.com/mt8695/android_kernel_amazon_mt8695
Screenshots
Reserved
Great Work!
Hello, many thanks for this rom, it's awesome, I thought I'd never get rid of that Amazon garbage
In case anybody else gets stuck in the remote pairing, just press the home button for 10+ seconds.
Edit
Anybody knows how to adjust display size?
bloot said:
Hello, many thanks for this rom, it's awesome, I thought I'd never get rid of that Amazon garbage
In case anybody else gets stuck in the remote pairing, just press the home button for 10+ seconds.
Edit
Anybody knows how to adjust display size?
Click to expand...
Click to collapse
I'm not sure with what do you mean by adjust display size but you can try to change it through ADB with adb shell wm size 1080x1920 (you can change the 1080x1920 part).
Rortiz2 said:
I'm not sure with what do you mean by adjust display size but you can try to change it through ADB with adb shell wm size 1080x1920 (you can change the 1080x1920 part).
Click to expand...
Click to collapse
Hello, I mean changing the size of the displayed area, not the resolution itself, in my TV the stock display size is too large and I'm missing part of the content
bloot said:
Hello, I mean changing the size of the displayed area, not the resolution itself, in my TV the stock display size is too large and I'm missing part of the content
Click to expand...
Click to collapse
I see, I think there's an option somewhere in the Settings (I can't check right now, sorry), it was called OverScan if I'm not mistaken. If it's not there, I'll include it in the next build.
Rortiz2 said:
I see, I think there's an option somewhere in the Settings (I can't check right now, sorry), it was called OverScan if I'm not mistaken. If it's not there, I'll include it in the next build.
Click to expand...
Click to collapse
I've been looking all over the settings but found nothing to adjust it, maybe I missed it though.
bloot said:
I've been looking all over the settings but found nothing to adjust it, maybe I missed it though.
Click to expand...
Click to collapse
Disabling overscan is typically a setting that can be configured on your TV.
Usually it's where you can also set aspect ratio for video sources, sometimes it's called "Just Scan"
k4y0z said:
Disabling overscan is typically a setting that can be configured on your TV.
Usually it's where you can also set aspect ratio for video sources, sometimes it's called "Just Scan"
Click to expand...
Click to collapse
How dumb I feel, I never found an overscan setting on my TV, it turns out the 16:9 aspect ratio does indeed an overscan, just changed to "screen fit" and it did it. Thanks.
It work like a charm , thank you for your hard work @Rortiz2
Everything work for me except Netflix ,could you upload your functional apk please ? since it's not on the Playstore and I get signature mismatch when I try to install the original amazon one (netflix.ninja) , I can connect with the Aptoide one but no video playback.
AMAZING! Smooth operation, nice and clean layout with the launcher present giving the Android TV theme with working playstore and modest settings menu. This rom has totally transfomred this device. Good work
Cheers again Roger + co
Regards
Out of interest is this a full 64-bit os instead of Amazon's 32-bit on top of a 64 bit processor?
Tech0308 said:
Out of interest is this a full 64-bit os instead of Amazon's 32-bit on top of a 64 bit processor?
Click to expand...
Click to collapse
This is a 32-bit OS
yacinecino said:
It work like a charm , thank you for your hard work @Rortiz2
Everything work for me except Netflix ,could you upload your functional apk please ? since it's not on the Playstore and I get signature mismatch when I try to install the original amazon one (netflix.ninja) , I can connect with the Aptoide one but no video playback.
Click to expand...
Click to collapse
I'll try to extract the APK later
Hi, I was wondering whether there is also a rom in the works for mantis, the fire tv stick 4k. If there is, I'd be happy to help test it on my own firestick.
If there isn't, could I do anything to make the sheldon one work on mantis (I know the general answer is absolutely no, so not holding my breath here)?
famus484 said:
Hi, I was wondering whether there is also a rom in the works for mantis, the fire tv stick 4k. If there is, I'd be happy to help test it on my own firestick.
If there isn't, could I do anything to make the sheldon one work on mantis (I know the general answer is absolutely no, so not holding my breath here)?
Click to expand...
Click to collapse
Unfortunately there is no way this ROM will work for mantis as sheldon's firmware is completely different. We actually tried to boot the sheldon firmware on mantis, but the kernel didn't boot at all (it failed to initialize some stuff). A friend of mine is willing to do 14.1 for mantis, we'll see if he pulls it off.​
Rortiz2 said:
Unfortunately there is no way this ROM will work for mantis as sheldon's firmware is completely different. We actually tried to boot the sheldon firmware on mantis, but the kernel didn't boot at all (it failed to initialize some stuff). A friend of mine is willing to do 14.1 for mantis, we'll see if he pulls it off.​
Click to expand...
Click to collapse
Thank you for the answer! That would be quite nice if your friend succeed. Had part of the work for 14.1 on mantis already been done, making it more viable than 18.1? And do you know if there are ''fundamental'' feature differences between both (a non-objective term obviously).
Hello, how can you come back to FireOS if wanted/needed? Cheers!

[ROM] ubuntu touch 16.04/20.04 community port

{
"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"
}
Credits​
https://github.com/8890q/ for LineageOS 18.1 device tree, kernel, hardware support, blobs
https://forum.xda-developers.com/t/treble-aosp-g930x-g935x-project_pizza-trebleport-v2-0.3956076/ for libsensor blobs
https://github.com/NotKit for giving me very helpful hints about ubports/halium specifics
https://github.com/ExpressLuke for testing the edge on my behalf
these awesome people gave me useful pointers for https://github.com/Kethen/herolte_treble to come to fruition, and is used in this port:
https://github.com/ivanmeler
https://github.com/ExpressLuke
https://github.com/00p513-dev
​Status​
Samsung Galaxy S7 (Exynos) • Ubuntu Touch • Linux Phone
Flash your Samsung Galaxy S7 (Exynos) with the latest version of the Ubuntu Touch operating system, a privacy focused OS developed by hundreds of people.
devices.ubuntu-touch.io
There might be other instabilities that I do not know of, use at your own risk
while 20.04 development builds are available through ubport installer, note that 20.04 is still in heavy development
Installation​ubport installer now supports Galaxy S7 exynos
alternatively zips for the latest twrp can be found below, herolte for flat, hero2lte for edge
Downloads​note that these releases are extremely outdated, for updated builds, use ubports installer
Releases · Kethen/samsung-exynos8890
halium 11 ubports for herolte, hero2lte and gracerlte - Kethen/samsung-exynos8890
github.com
Building and more information​
GitHub - Kethen/samsung-exynos8890: halium 11 ubports for herolte, hero2lte and gracerlte
halium 11 ubports for herolte, hero2lte and gracerlte - GitHub - Kethen/samsung-exynos8890: halium 11 ubports for herolte, hero2lte and gracerlte
github.com
Reporting Issues​
Issues · UBports / Porting / Community Ports / android11 / Samsung Galaxy S7 / samsung-exynos8890 · GitLab
Samsung Galaxy S7/S7 Edge
gitlab.com
Unofficial Waydroid Images​This is no longer required, waydroid has official h11 support and should be able to download official images during init. The waydroid helper app from openstore should be able to setup waydroid without using custom images.
Releases · Kethen/waydroid_build
personal waydroid build script. Contribute to Kethen/waydroid_build development by creating an account on GitHub.
github.com
Telegram discussion group​
S7/Edge/NoteFE Exynos Ubuntu Touch
S7/Edge/NoteFE Exynos Ubuntu Touch discussions Use the bug tracker at https://gitlab.com/ubports/porting/community-ports/android11/samsung-galaxy-s7/samsung-exynos8890/-/issues if you have an issue Try to be nice to eachother and stay on-topic /notes
t.me
If you have an issue please use the bug tracker above instead
Hi, does Anbox work on this ROM?
Ex novo said:
Hi, does Anbox work on this ROM?
Click to expand...
Click to collapse
waydroid has no halium 11.0 support at the moment, but it should work once that is out
does sms out work
King081 said:
does sms out work
Click to expand...
Click to collapse
yes
Cool
I love this port and I've been able to pull off daily driver activities with it so far on my S7 edge. Still testing.
I've been working with the daily builds and at version 140, I can't tell much significant difference with each one though my phone freezes less randomly and heats up less (I think this is specific to my particular phone or maybe because I tried tinkering with waydroid for so long before giving up for the time being?) the random freezes persist after a good number of hours of constant use, still great. As with the calling, it works quite well on my device, both recieving and sending calls. Only major issue seems to be with the USSD codes as they would go through but the further responses after the first dial do not work (maybe something with the mms situation?). This is something I am quite new to, so I don't know how useful this feedback is but this OS is definitely something I'm keeping on this device.
childoftext said:
I've been working with the daily builds and at version 140, I can't tell much significant difference with each one though my phone freezes less randomly and heats up less (I think this is specific to my particular phone or maybe because I tried tinkering with waydroid for so long before giving up for the time being?) the random freezes persist after a good number of hours of constant use, still great. As with the calling, it works quite well on my device, both recieving and sending calls. Only major issue seems to be with the USSD codes as they would go through but the further responses after the first dial do not work (maybe something with the mms situation?). This is something I am quite new to, so I don't know how useful this feedback is but this OS is definitely something I'm keeping on this device.
Click to expand...
Click to collapse
some mitigations against random freezes were added last Friday, the issue is being tracked here https://gitlab.com/ubports/porting/...msung-galaxy-s7/samsung-exynos8890/-/issues/4
While I can do ussd codes consecutively without issues, a cellular issue fix was also added recently https://gitlab.com/ubports/porting/...msung-galaxy-s7/samsung-exynos8890/-/issues/2, and no one ever sends mms here so idk if that could get in the way
katharinechui First of all, congratulations for the excellent work, I tested this rom and it is excellent!.
I really love Ubuntu Touch, but I need to have dualboot because I have a lot of apps I need to work that don't work on waydroid...
Do you happen to have a ready-made Halium-boot image to use with the Ubports GSI? or any way to use your Halium11 image in dual boot?
I've been trying to do a dualboot on the S7 for a while, I know that with a GSI image you can just change the boot.img to halium-boot, I've already done that on Redmi, but on the S7 I really didn't find anything working for a dualboot with ubports.
I've already compiled the Redmi Note 4X image (mido) once following the ubports tutorial, but I don't have time to research this on the S7 Edge anymore, I also don't have the patience anymore..
mcgragor said:
katharinechui First of all, congratulations for the excellent work, I tested this rom and it is excellent!.
I really love Ubuntu Touch, but I need to have dualboot because I have a lot of apps I need to work that don't work on waydroid...
Do you happen to have a ready-made Halium-boot image to use with the Ubports GSI? or any way to use your Halium11 image in dual boot?
I've been trying to do a dualboot on the S7 for a while, I know that with a GSI image you can just change the boot.img to halium-boot, I've already done that on Redmi, but on the S7 I really didn't find anything working for a dualboot with ubports.
I've already compiled the Redmi Note 4X image (mido) once following the ubports tutorial, but I don't have time to research this on the S7 Edge anymore, I also don't have the patience anymore..
Click to expand...
Click to collapse
starting from https://gitlab.com/ubports/porting/...mmit/0342d2858fd431a8f0c5e4118141cad615a8c835, the halium bootscript will prefer booting from /data/ubuntu.img or /data/halium-rootfs/ if available
you can find the new boot.img on CI once that's ready, ubuntu.img is also available on CI
that should enable your use case of dual booting by swapping between halium boot.img and android boot.img, while having android system.img installed to partition and ubuntu.img installed to /data
note that this is not and will not be the default installation method so OTA will not work
katharinechui​Thank you for your help. This will help me a lot in my personal project...
I'm doing everything to banish systems like android from my life, I managed to completely abandon windows last year, but unfortunately android is still necessary until I can run the apps I need on wayroid or anbox, but using dual boot with Ubuntu I can minimize the amount of data that can be exposed, because I'm going to use E-foundation's GSI firmware that already drastically reduces the exposed data and I'll only use it when strictly necessary.I'm doing everything to banish systems like android from my life, I got it completely windows in the last year, but unfortunately android is still needed to work until I can run the apps I need on wayroid or anbox, however using dual boot with Ubuntu I can very much avoid my data being exposed, because I will only use android when necessary.
I took the ubports_GSI_installer_v10.zip file that I had here and changed the rootfs.img to your ubuntu.img and flashed the boot.img, it worked perfectly, even though I used a Lineage Pie.
About OTA, I can do the update manually when a new update is released.
I forked your gitlab repository to keep up with the changes and try out some ideas.
Thank you so much!
You saved my life and my data privacy! XD
mcgragor said:
katharinechui​Thank you for your help. This will help me a lot in my personal project...
I'm doing everything to banish systems like android from my life, I managed to completely abandon windows last year, but unfortunately android is still necessary until I can run the apps I need on wayroid or anbox, but using dual boot with Ubuntu I can minimize the amount of data that can be exposed, because I'm going to use E-foundation's GSI firmware that already drastically reduces the exposed data and I'll only use it when strictly necessary.I'm doing everything to banish systems like android from my life, I got it completely windows in the last year, but unfortunately android is still needed to work until I can run the apps I need on wayroid or anbox, however using dual boot with Ubuntu I can very much avoid my data being exposed, because I will only use android when necessary.
I took the ubports_GSI_installer_v10.zip file that I had here and changed the rootfs.img to your ubuntu.img and flashed the boot.img, it worked perfectly, even though I used a Lineage Pie.
About OTA, I can do the update manually when a new update is released.
I forked your gitlab repository to keep up with the changes and try out some ideas.
Thank you so much!
You saved my life and my data privacy! XD
Click to expand...
Click to collapse
If you know how to use adb, all you need to do after installing boot.img is adb shell mount /data; adb push ubuntu.img /data/ubuntu.img in recovery instead of splitting android-rootfs.img and rootfs.img from ubuntu.img then adding them to the zip. Unlike other halium 9+ ubuntu touch ports, the port for s7 provides it's own vendor image and does not use a vendor partition at all, ubports_GSI_installer_v10.zip is very very incompatible here and would likely cause you to pair a halium 9 system.img with the android 11 vendor inside ubuntu.img if you did not update system.img with a halium 11 one
Also note that since ubuntu.img contains it's own vendor image, you can use any device native roms without a vendor partition in this dual boot use case, without treble converting the device
On the other hand, E is rather questionable in my opinion
While I really respect their phone refurbish business and they do bring relatively hassel free installation and beyond official LineageOS device support to the table, their OS is often a month to three months behind LineageOS security updates, the built-in app store ships playstore apps from a shady french apk mirror, ships closed source magic earth that they've been saying "it will be opened source" for years and it's still closed source now, forked multiple open source applications to serve as their core apps but does not have the man power to keep them updated timely after the initial rebrand (you can see them getting mutiple releases behind on their gitlab), and all they really did towards privacy was to use another time server for ntp and another web server for checking whether internet is up, rebrand bromite and change the default search engine to not be google
They did all that rebranding to make a less secure LineageOS release that had very insignificant "degoogle" changes just to market and bundle their nextcloud fork ecosystem
I suppose they are capable of improvement, I'm very happy to see that their k9 fork has been pretty close to upstream as of late; but then overall they still put more effort into rebranding opensource projects rather than contributing to upstream, and are not keeping up with core things like keeping up with LineageOS security updates, stopping their iOS minic launcher from breaking deep sleep keeping your phone warm in your pocket and overnight draining battery, keeping their rebranded bromite fork up-to-date (current official release) (e bundled version)
If you don't use ecloud and don't need microg in your android dual boot, I'd really recommend Ivan_Meler's LineageOS builds; if you need microg and find it too cumbersome to manually install microg as system app on top, I'd recommend checking out Exodusnick's LineageOS for microG builds
Nowadays my main focus is being on the privacy of my data...
It's been a very difficult and complicated search, initially I thought of using /E/ for the data filter they claim to have, but your considerations about application repositories sparked an alert, even though I don't use the custom to install applications from stores, I always prefer to manually download apks, but this practice of them really opens up the security holes
about /e/ wake lock issue on 0.17-q, I tested version 1.4-q in the official repository and didn't report this problem, on the contrary, I noticed excellent battery life with no battery drop for long periods.
I will take your considerations and recommendations into consideration and I will check those lineage builds you mentioned, I intend to use android only when necessary but with microg, and ubuntu on a daily basis, but even in the short period of use of android I want to maintain a certain level of privacy.
Thank you very much for your advice
cant install 20.04
lentas said:
cant install 20.04
Click to expand...
Click to collapse
I'm not sure what issue you are having, just tested the AppImage version of the installer on fedora linux and it works; it might be an issue with the ubports installer for windows
meanwhile, make sure you have drivers installed for adb and heimdall
katharinechui said:
I'm not sure what issue you are having, just tested the AppImage version of the installer on fedora linux and it works; it might be an issue with the ubports installer for windows
meanwhile, make sure you have drivers installed for adb and heimdall
Click to expand...
Click to collapse
it worked with using linux app, windows app is buggy

Categories

Resources