Related
Android 10 QP1
2019-09-07
Bugs: VoLTE, Bluetooth and Cast doesn't work, SystemUI can crash
Features: All Android 10 Final Features
How to Install
1 : Download ROM and flash.
2 : When you boot, install Google Play Services and Google Play Store APK's
3 : When Google Play and Google Play Services is installed, reboot two or three time to have more stability
4 : Profits !
Note: If you want to change Kernel flash Permissiver_v4 and FixZygote_v2 after flashing your Custom Kernel
Downloads
ROM Download
Recommended Recovery (PBRP)
Permissiver_v4 from erfanoabdi
FixZygote_v2 from erfanoabdi
Google Camera configs
F.A.Q.
Q1: I don't have data services
A1: Try different Kernel. If doesn't work, go to stable Pie rom.
Q2: How to add gcam configs xml file
A2: Follow this guide
Q3: Battery drain issues ?
A3: No, it depend kernel you use
Thanks to @erfanoabdi for GSI and @MactavishAO for LagFix
ChangeLog
Android 10 Final 2019-09-07
• Android 10 DP6 20190904 Erfan GSI
• Switch to KangarooX r5.1 OC
very Good
thank you
How to install via Google play services adb command
wich camera app do you use? I tried install Mi Camera but it isn't compatible with Android Q yet. Gcam doesn't work for me either
I get
There's an internal problem with your device. Contact your manufacturer for details
Click to expand...
Click to collapse
I also don't have data service with it turned on and showing that I am connected to LTE.
John Amin said:
How to install via Google play services adb command
Click to expand...
Click to collapse
I would just rename the apk to playservices.apk then run this command. You just have to be booted into the system, not recovery. I just run adb devices in order to prompt authorization.
Code:
adb install playservices.apk
.
daggorlad said:
I would just rename the apk to playservices.apk then run this command. You just have to be booted into the system, not recovery. I just run adb devices in order to prompt authorization.
Code:
adb install playservices.apk
Click to expand...
Click to collapse
Ok,thanks but am facing another issue
Tried camera and not working and tried another version also force closes
And flashlight not working also
The rom work very fine, i hope you will release new Android Q Developer Preview,thanks for your effort
Thanks for this ROM
Regarding VoLTE
What happens when you try *#*#4636#*#* code ? Can You move the switches ?
Since Android 10 have the new "Scoped Storage" Feature, I wanted to know if File Explorers and SD-Cards still works like in previous Android versions? Since that is important for me, cause I need access to my own phone storage like always.
Waiting for stable version
I'm looking forward to try the Rom, that's the first thing I do when I'm able to unlock my Bootloader in 3 days exactly. Just can someone write a short review if the Rom is Stable enough except the few minor issues mentioned in the first post? And is Magisk 19.3 working in this Rom? And which recovery is recommended, Orangefox or Offical TWRP?
Have battery drain issue?
Smooth or butter?
So a short review of me after using the Rom a few days: I'm very impressed how well it works on our Redmi Note 5, I use the 4/64GB Global version, and I faced 2 bugs that wasn't mentioned here, first often when I lock the phone and wanna unlock it again, it just freezes and become unresponsive so I was forced to do a force reboot and Whatsapp voice messages doesn't work. But luckily, I honestly don't know why, both problems got fixed with installing the latest Updated PureCAF Kernel x6, overall Android 10 performance is very good and now it's stable too.
Why is this thread so quite?
xell75 said:
So a short review of me after using the Rom a few days: I'm very impressed how well it works on our Redmi Note 5, I use the 4/64GB Global version, and I faced 2 bugs that wasn't mentioned here, first often when I lock the phone and wanna unlock it again, it just freezes and become unresponsive so I was forced to do a force reboot and Whatsapp voice messages doesn't work. But luckily, I honestly don't know why, both problems got fixed with installing the latest Updated PureCAF Kernel x6, overall Android 10 performance is very good and now it's stable too.
Click to expand...
Click to collapse
Tnx for review, overall Android 10 performance is very good and now it's stable! these words are enough to try this rom. Next week I'll. Tnx to all developers
vijaymk said:
Tnx for review, overall Android 10 performance is very good and now it's stable! these words are enough to try this rom. Next week I'll. Tnx to all developers
Click to expand...
Click to collapse
No problem, btw. When you want your microphone to work in every app including Whatsapp, the fix is to just turn off Googles Voice Match if it's enabled, since it seems that it Blocks the microphone completely.
Now that the Umidigi One Max has TWRP, it is now very easy to flash GSI ROMs.
I will try to keep track of different GSI that works (or not !) here, alongside with bugs. Testers are welcome !
I highly recommend GSI based off phhhuson's work, as he did great job to fix MTK issues. Some other GSI may work better. We definitely need testing !
10
Apparently it works as shown here: https://forum.xda-developers.com/showpost.php?p=80319007&postcount=13 credits to @4ctiv_
9.0 Pie
phhusson's AOSP :
Everything works as expected. Notification bar is of the wrong size, may need to create a patch for it. Tethering doesn't work with data ON !
Camera is good ! All cameras are recognized. Fingerprint sensor OK. Torch not working under 15% like in stock, this seems like a hardware thing.
Ongoing calls and SMS will not work first boot. Just reboot and it'll work.
Magisk 19+ doesn't show root prompts. Fix here
Pixel Launcher crashes, but it seems that it's the only google app that doesn't work. Google Phone works.
NFC doesn't appear at all. There is a fix with magisk tho ! See here (NFC4PRA)
ctsProfile doesn't pass. Using MagiskHidePropsConfig fixes the issue, but choosing "vendor fingerprint" bootloops
Testers needed
8.1 Oreo
Testers needed
Do not hesitate to post what you find or your testing.
NOTE : Installing a GSI can be done via 3 methods : TWRP Image Flash, SP Flash Tool, or fastboot (needs unlocked bootloader)
For the first two methods, unlocked bootloader is not required ! TWRP can be flashed via SPFT aswell.
Enjoy your beautiful and modded phone
Make sure to check out my guide on installing GSIs at https://forum.xda-developers.com/android/development/umidigi-one-max-custom-rom-modding-t3942521/
I downloaded system-arm64-ab-gapps-su.xz, extracted the file, booted into TWRP, did a full wipe, and installed "image" system-arm64-ab-gapps-su.img. TWRP asks which partition to install it to. I selected "system". However, after install I go to reboot, and TWRP complains there is no OS. Am I missing something?
I did a complete backup in TWRP of all important partitions first (nvram, modem, system Etc.), so going back to my stock setup was not difficult. Those trying this, backup all important partitions from TWRP on to microsd!
For everyone, make sure you download AONLY images, not AB !
_cab13_ said:
Now that the Umidigi One Max has TWRP, it is now very easy to flash GSI ROMs.
I will try to keep track of different GSI that works (or not !) here, alongside with bugs. Testers are welcome !
I highly recommend GSI based off phhhuson's work, as he did great job to fix MTK issues. Some other GSI may work better. We definitely need testing !
10 Q Beta
Beta 4 : Probably not working, as our device is not system-as-root (but is VNDK isolation compatible)
Still needs testing
9.0 Pie
phhusson's AOSP :
Everything works as expected. Notification bar is of the wrong size, may need to create a patch for it. Wifi access point doesn't work.
Camera is good ! All cameras are recognized. Fingerprint sensor OK. Torch not working under 15% like in stock, this seems like a hardware thing.
Ongoing calls and SMS will not work first boot. Just reboot and it'll work.
Magisk 19+ doesn't show root prompts. Fix here
Pixel Launcher crashes, but it seems that it's the only google app that doesn't work. Google Phone works.
ctsProfile doesn't pass. Using MagiskHidePropsConfig fixes the issue, but choosing "vendor fingerprint" bootloops
Testers needed
8.1 Oreo
Testers needed
Do not hesitate to post what you find or your testing.
NOTE : Installing a GSI can be done via 3 methods : TWRP Image Flash, SP Flash Tool, or fastboot (needs unlocked bootloader)
For the first two methods, unlocked bootloader is not required ! TWRP can be flashed via SPFT aswell.
Enjoy your beautiful and modded phone
Click to expand...
Click to collapse
I posted this in another forum, but for the life of me I do not know what is causing this issue. I installed RR rom located here:
https://get.resurrectionremix.com/?dir=gsi/
system-190120-arm64-aonly-vanilla-nosu.img
I also install, Gapps (pico), and Magisk.
It runs great, for the most part. However, if I start streaming a video from any app or start streaming music, after a short amount of time my Umidigi One Max:
A.) Announces, "Powering Down"
B.) Boots directly into TWRP
C.) If I reboot, it again boots directly into recovery. Almost as if the partition became corrupted.
D.) Try to recover a backup I made in twrp, reboot, again boots straight into recovery.
E.) If SP Flash can communicate with the phone, I can usually push all the stock images back to the phone. If not, I have to push the images via fastboot with my Ubuntu PC.
If I do any other CPU intensive task under a GSI ROM, it doesn't have this issue, only when I stream video. I haven't tried any games to see if it causes this behavior.
I have tried multiple GSI Roms located here too, same problem:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
I do not believe the device is overheating, it's usually around 32-34C from the TWRP menu at that point. I really like the RR Rom, but if I cannot figure out what is causing this, I'll have to stray away from GSI for now.
As a sidenote, this issue of the device suddenly powering down after starting to stream a video, does not happen with the stock ROM. I am kind of at a loss on this one.
Weirdest thing I have experienced running a custom ROM.
Yeah it happened to me sometimes as well... The phone goes straight into recovery and then never goes to system again. I haven't found the cause of it.
Did you try the NFC fix for the one pro (I got it from the umdigi forum one Pro and then the thread custom ROMs)
phhusson's AOSP is mostly good. But I noticed the wifi often gets disconnected and has performance issue too.
w1lh3lm3d said:
Did you try the NFC fix for the one pro (I got it from the umdigi forum one Pro and then the thread custom ROMs)
Click to expand...
Click to collapse
I posted a fix that works. Here it is if you didn't see : https://forum.xda-developers.com/p8...pment/flashable-nfc-kirin655-devices-t3811916
tomprc said:
phhusson's AOSP is mostly good. But I noticed the wifi often gets disconnected and has performance issue too.
Click to expand...
Click to collapse
I don't get any performance issue. The only issues is that some ongoing calls doesn't come, and sometimes 4G totally glitches out. Other than that it's pretty much all.
@ _cab13_
i cant find the vendor folder in twrp in the mount section or in the file manager.
what have i done wrong? ok i started from scratch and then it worked porfectly
thx you for your work and help
Engineering mode access or work around
On the 9.0 ROM I cant seem to access engineering mode via the keypad, I need to sort the handset speaker out. Is there any other way to access it or some way of tweaking the voice settings through the shell?
Any help would be appreciated.
Please help
I'm trying to get the new phh Android q to boot and and I'm a newbiew
Just booted from Android 10 GSI 200 c. by PhhTrebble without any problems (flashed latest stock before). Just to let you guys know Will update bugs and working stuff tomorrow.
[Update]
Missing features
_________________
NFC missing and magisk patch did not work for me
Media playback in for exampel youtube/instagramm/reddit etc. not working in apps but in browser it workes.
Bugs:
_________________
Sometimes apps crash
SD-card "has to be formated to use" // I did not try formating yet
Sometimes Youtube playback fixes itself if you tab out and go back to the video or if you open the help page of YT (top right corner question mark symbol) and go back to the video
Be aware that the 200.c phh gsi i used is still in development but as you can see it is totally capable to use as daily driver
[UPDATE 2]
- Missing features is still NFC
- In PHHSolution "AOSP 10.0 v211" mediaplayback got fixed (Tested with "system-quack-arm64-aonly-gapps.img.xz" )
On Phh's 9 v119 Is the headphone jack sensor working for anyone. (If so how)
4ctiv_ said:
Just booted from Android 10 GSI 200 c. by PhhTrebble without any problems (flashed latest stock before). Just to let you guys know Will update bugs and working stuff tomorrow.
[Update]
Missing features
_________________
NFC missing and magisk patch did not work for me
Media playback in for exampel youtube/instagramm/reddit etc. not working in apps but in browser it workes.
Bugs:
_________________
Sometimes apps crash
SD-card "has to be formated to use" // I did not try formating yet
Sometimes Youtube playback fixes itself if you tab out and go back to the video or if you open the help page of YT (top right corner question mark symbol) and go back to the video
Be aware that the 200.c phh gsi i used is still in development but as you can see it is totally capable to use as daily driver
Click to expand...
Click to collapse
did you use the a only or ab image?
I've tried flashing multiple android 10 GSIs from the phhusson GSI wiki list.
I've tried phhusson's AOSP ROM, CAOS, Lineage 17.1 and POSP. It seems like they all freeze at the splash screen and get stuck loading forever (confirmed, I left it on all night last night). I've tried disabling force encryption, I've tried not installing magisk. Not really sure where to go from here with Android 10.
I've also tried Android 9 with much more success: it boots, it works, but the only thing I can't seem to get is NFC. Has anyone found a way to get NFC to work on any android version with this device? Or do I have to go back to stock android 8?
Thanks!
seiyria said:
I've tried flashing multiple android 10 GSIs from the phhusson GSI wiki list.
I've tried phhusson's AOSP ROM, CAOS, Lineage 17.1 and POSP. It seems like they all freeze at the splash screen and get stuck loading forever (confirmed, I left it on all night last night). I've tried disabling force encryption, I've tried not installing magisk. Not really sure where to go from here with Android 10.
I've also tried Android 9 with much more success: it boots, it works, but the only thing I can't seem to get is NFC. Has anyone found a way to get NFC to work on any android version with this device? Or do I have to go back to stock android 8?
Thanks!
Click to expand...
Click to collapse
I'm in the same boat bro. I've just tried both the latest phhusson AOSP 10 ROM as well as an older version of the same ROM, and both time I get caught in a loop after install. Completely wiped beforehand, tried installing with and without Magisk/Disable-Force-Encryption. Going to have to bring it back down to Android 9. I wonder how 4ctiv_ got it working?
so first you have to no encryption then erase and format data
flash android 10 arm 64 a without gapps build (image) to system i use havoc 3.5 and everything exept nfc works
then install gapps (it failed for me so i had to resize system in twrp and install gapps again
last step is to flash the custom phhson magisk
then just reboot wihout wipping
Thank you so much for your work...
Hi, I'm a long time Android user and I used to code apps, if I can be of any help please let me know but I'm now disabled wheel chair user with dystonia so I find it extremely difficult to type now so I use voice to text... I really enjoy using the umidigi one max it has the storage and usability of a much more expensive phone, also functionally for me the wireless charging and NFC make my life so much easier as I find cables akward and payments at shops much easier.
I read about the Treble programmea while ago and recently read this article and if it is possible to get the NFC working on this update, I will be so greatful as it will extend the life of this great phone for me.
Good luck with your work and thank you in advance.
4ctiv_ said:
Just booted from Android 10 GSI 200 c. by PhhTrebble without any problems (flashed latest stock before). Just to let you guys know Will update bugs and working stuff tomorrow.
[Update]
Missing features
_________________
NFC missing and magisk patch did not work for me
Media playback in for exampel youtube/instagramm/reddit etc. not working in apps but in browser it workes.
Bugs:
_________________
Sometimes apps crash
SD-card "has to be formated to use" // I did not try formating yet
Sometimes Youtube playback fixes itself if you tab out and go back to the video or if you open the help page of YT (top right corner question mark symbol) and go back to the video
Be aware that the 200.c phh gsi i used is still in development but as you can see it is totally capable to use as daily driver
[UPDATE 2]
- Missing features is still NFC
- In PHHSolution "AOSP 10.0 v211" mediaplayback got fixed (Tested with "system-quack-arm64-aonly-gapps.img.xz" )
Click to expand...
Click to collapse
DICLAIMER
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
This is still mostly a LineageOS team / PHH @phhusson effort, credits to them and all associated for making all this possible.
No guarantees that everything would work. This is a GSI, bugs are bound to happen.
[GSI][10.0] Lineage OS 17.0 Galaxy J6
LineageOS is a free, community built, aftermarket firmware distribution of Android, 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. 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, Gerrit code
Click to expand...
Click to collapse
SO, Here Is The Unofficial Lineage OS 17.0 GSI Working On Galaxy J6.
Follow The Instructions To Flash It .
REQUIREMENTS/DOWNLOADS :
Unlocked Bootloader
TWRP Installed
GSI Image : DOWNLOAD
10.0 j6 Vendor : DOWNLOAD
Flashing Instructions
[*]Unzip Downloaded GSI Image , You Got an .img file
[*]Boot In TWRP
[*]Wipe system, data, dalvik&cache, cache
[*]Install Vendor.Zip file
[*]Reboot To Recovery
[*]Select Install Image Option In TWRP
[*]Install extracted Image File
[*]Again Reboot To Recover (Don't worry if no OS installed error comes just go ahead )
[*]Now, At last reboot to System
[*]OPTIONAL : Flash Gapps (DOWNLOAD) After first Boot (It Takes Around 10min For First Boot )
SCREENSHOTS
https://ibb.co/CsLdW2k
https://ibb.co/mFFPMv3
https://ibb.co/8smXSqM
https://ibb.co/MRX7sQr
https://ibb.co/f9SDK0n
https://ibb.co/YtHrsXp
video tutorial :
https://youtu.be/Zz-VZ9sXlX0
creditsAndyYan
Sent from my J6 using XDA-Developers Legacy app
Ok so I have a bug while using this rom(j600fn). Except from the casual sim calls, I also get this even in apps,for example messenger. The problem occurs not all times, but it's not rare, someone calls me, I pick it up and I can hear them but they can't hear me. After they hung up and call me again everything works fine. Any piece of advice? Thanks for reading and also thanks for keeping the j6 alive.
Kostas172 said:
Ok so I have a bug while using this rom(j600fn). Except from the casual sim calls, I also get this even in apps,for example messenger. The problem occurs not all times, but it's not rare, someone calls me, I pick it up and I can hear them but they can't hear me. After they hung up and call me again everything works fine. Any piece of advice? Thanks for reading and also thanks for keeping the j6 alive.
Click to expand...
Click to collapse
Hi @Kostas172
Thats a bug,no solutions till now .wait for next build.
Sent from my [device_name] using XDA-Developers Legacy app
This is from telegram right ? Nice kang man
Help
Can this be installed on 32bit one ui? Asking this because i saw many arm64 gsi where it said not to install on 32bit one ui
some things that i can relate and maybe will help you with debbuging
!!this was meant to be posted on reddit but lineage community is all sicko about unofficial builds!!
model: Samsung Galaxy J6 (j600GT/DS) 64GB 3G
Let's get started:
IMGUR link: imgur. com /gallery/E76ffQF
Camera issues:
1- video streches and morphes as i turn the camera (SOLVED: downscale video settings to 720p)
2- recorded video file corrupted (3 seconds video turn into 30sec video with just a static image and sound) (FIXED: install camera2api module with magisk)
Calling/Broadband issues:
3- LTE/phone signal too low, sometimes NO SIGNAL
4- Calls don't work in loudspeaker mode
Battery issues:
5- Battery takes hella time to charge (2 hours in ONE UI, and in LOS i plug the phone, go to sleep, and wake up in the next day in 80-90% [still charging]. Comparison made with a non-turbo charger, starting at 15%)
6- Battery drains hella fast, i need to keep my phone in Battery Saving mode to make it last almost to the end of the day (on ONE UI it last until midnight with 10% left) (i also tried deactivating the AOD, but it is not what is consuming all of the battery). (ammenized by turning off AOD)
Play store issues (it's more of a question):
7- some apps (like netflix) count as "This app is not compatible with your device", is that because of the security of lineage not being approved by google?
i also have some questions on things as:
q1- does lineage have a app like samsung's theme store? and can you customize the AOD?
q2- will i receive normal updates as i'm using an UNOFFICIAL release?
EDIT 1:
-whatsapp video call gets all black, but the video is rolling on the other user's phone
I have a fairly serious bug every 20/30 minutes the device restarts me on my own. is there a solution?
henks99 said:
I have a fairly serious bug every 20/30 minutes the device restarts me on my own. is there a solution?
Click to expand...
Click to collapse
Yes, get a new ROM and kernel.
The rom is very wonderful ... Thank you very much ...
henks99 said:
I have a fairly serious bug every 20/30 minutes the device restarts me on my own. is there a solution?
Click to expand...
Click to collapse
From recovery. Wipe Cache and Dalvik Cache..
If problem Still Exists..
Reinstall rom...
Sent from my [device_name] using XDA-Developers Legacy app
Is work samsung pass with root?
Its support VOLTE ?
Well,
I gave it a fair shot. Had trouble getting superuser, untill I read somewhere that Magisk is breaking things like adb. Also some other functions apparently... So SuperUser it was..
However... things happened that made me revert to the previous version:
- The device reboots regularly, like twice an hour.
- LastPass refuses to start...
- Battery drain
- File Transfer over USB (mtp) is broken
pity...
FreakyJoost said:
Well,
I gave it a fair shot. Had trouble getting superuser, untill I read somewhere that Magisk is breaking things like adb. Also some other functions apparently... So SuperUser it was..
However... things happened that made me revert to the previous version:
- The device reboots regularly, like twice an hour.
- LastPass refuses to start...
- Battery drain
- File Transfer over USB (mtp) is broken
pity...
Click to expand...
Click to collapse
well, it took me a few nights but i found the problem.
so basically, when you flash the vendor file it flashes magisk 20.X
but the rom has it's own su built in!
so magisk and the phh su fight and cause random reboots.
this is the procedure to fix the issue:
1. open adb
2. type "adb shell"
3. type "su 0"
4. type "/system/bin/phh-securize.sh"
5. download magisk 22 apk, and rename it to be a zip file(just change the .apk to .zip at the end)
6. flash it in twrp
7. rename the zip to apk and install it, or just download it again and install it.
8. you're done!
i got mine to work perfectly after that. no battery drain(except for AOD), mtp started working again and all the problems were fixed.
please let me know if it had worked out to you!
Well, been a long time now... Good to hear someone did find a solution.
I never read this until now, and I got a different phone now.
But hey, maybe I'll give it a try once I find some spare hobby-time. I still have the device.
Cheers on you for making it work!
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
Special thanks to Exynos5420 team and LineageOS for all the sources.
Use SM-T900 build at your own risk. I can't guarantee you it will work, because I have no device to test it on.
Work
Almost everything
It has pretty much the same functionality as Lineage 14.1
Known Issues
Built in mic not working
USB problems
You tell me...
Installation:
1. Flash latest official Samsung Firmware with ODIN
2. Flash latest TWRP Recovery: SM-T520 - SM-T900
3. Backup all partitions
4. Wipe Cache and Data
5. Install ROM.ZIP
6. Install latest GApps (ARM/Android10) https://opengapps.org/
7. Reboot and Enjoy
8. Optional: Install Magisk
For SM-T520 TWRP recoveries 3.1.1.0 and older will not flash this rom ending up with error 7: incompatible device.
Make sure to flash TWRP mentioned above.
Download:
SM-T520
SM-T900
I ll probably create builds with updated security and device code patches occasionally.
Enjoy fresh new Android!
Sources:
https://github.com/LineageOS (LineageOS 17.1)
https://github.com/exynos5420/ (Kernel, Device, Vendor)
Damn!! Just installed and working.
Really good work! Thanks!!!!
i found a bit problem, starting android it loops between voice assistant and set lock for tablet. i needed connect earphones with microphone to finish voice assistant configuration and then it continued.
Thanks for rom!
@TechDriver can You build a LineageOS 17.1 ROM for SM-T900 who is used the same Exynos5420 CPU?
If is necessary I can be a beta tester.
manix01 said:
@TechDriver can You build a LineageOS 17.1 ROM for SM-T900 who is used the same Exynos5420 CPU?
If is necessary I can be a beta tester.
Click to expand...
Click to collapse
You got it there try it out!
Larision said:
Damn!! Just installed and working.
Really good work! Thanks!!!!
i found a bit problem, starting android it loops between voice assistant and set lock for tablet. i needed connect earphones with microphone to finish voice assistant configuration and then it continued.
Thanks for rom!
Click to expand...
Click to collapse
Did you install on the t520 or the t900? Did you really go back to the Samsung official build first? (I'm on t900 lineage 14.1)
pjotrski1000 said:
Did you install on the t520 or the t900? Did you really go back to the Samsung official build first? (I'm on t900 lineage 14.1)
Click to expand...
Click to collapse
You don't need to go stock, just backup your data using TWRP and follow installation steps above. I am little unsure about build for T900 because I do not own this device, so I wait for someone who can report me if it works or not.
@TechDriver Clean flashed 17.1 over 14.1 without flashing stock on T900 using twrp-3.5.1_9-0 and it flashed great. I plugged in a headset but my Hey Google was already recorded and didn't give me any trouble. I don't know what would have happened if I hadn't plugged in the headset. Play Store does not recognize my already purchased apps. This usually means something is not right and I wonder if not flashing stock first is related to this? Can be very smooth but can be a little glitchy as well. Still experimenting and trying things. Bluetooth Keyboard and Mouse work great. Thank you for this.
kb8no said:
@TechDriver Clean flashed 17.1 over 14.1 without flashing stock on T900 using twrp-3.5.1_9-0 and it flashed great. I plugged in a headset but my Hey Google was already recorded and didn't give me any trouble. I don't know what would have happened if I hadn't plugged in the headset. Play Store does not recognize my already purchased apps. This usually means something is not right and I wonder if not flashing stock first is related to this? Can be very smooth but can be a little glitchy as well. Still experimenting and trying things. Bluetooth Keyboard and Mouse work great. Thank you for this.
Click to expand...
Click to collapse
It has probably something to do with missing play protect certification. I will try to sign device for certification but need someone with T900 who will cooperate with me. For now easiest way to avoid problem is going to browser version of play store and installing paid app to specific device from there. It should work fine. Also thanks for testing and reporting that T900 build works.
Just for understanding, these are still 32 bit builds, vor did you switch to arm_64?
@TechDriver SELinux is not enforcing. That may be why Google Play does not recognized my purchased apps. Installing purchased apps trick from Google Play on the web worked as expected. Booting tablet, it does not accept passcode on the first try, but works on second try. This is repeatable. I will be happy to be your T900 tester if you make some test builds.
hamudistan said:
Just for understanding, these are still 32 bit builds, vor did you switch to arm_64?
Click to expand...
Click to collapse
Exynos5420 is 32bit SoC. It doesn't support arm64
@TechDriver The pass code works the first time if you are not impatient and click the accept arrow before the last number changes to a dot. There is a delay and the passcode entry is laggy and you have to be patient for a few seconds. twrp-3.5.1_9-0 is able to back up and restore 17.1 with no problem.
@TechDriver The first login with PIN after booting will fail. The second and future screen saver logins will work with the caveat that you are patient until the last number turns into a dot.
Pixel launcher does not work correctly with mouse clicks and has a focus graphics glitch. It works right as long as you don't click the mouse. If you click with the mouse to open a group of icons in a folder it leaves a residual grey box behind. You can see this same grey box where the PIN numbers appear on the screen saver as well. I changed to Nova Launcher and the problem improved with the grey box occurring if I open the icon folder and actually open an app but then disappearing on moving into a different folder. This is all with the exception of the PIN screen saver which causes the same grey box on both launchers. Something is not quite right with the graphics using mouse.
I mostly use this tablet with keyboard and mouse and Nova is more acceptable now. I prefer Nova Launcher anyway as it is much better at using the whole screen.
The camera is extremely basic. Open Camera seems to be an improvement. Any Google Camera port available that might work?
Just to make things clear, I am not developer of code and not skilled enough to make changes in it. For this job, there is team exynos5420 and other cool contributors to make device sources. I use their device sources from exynos5420 and LineageOS github to build together final product... Rom.zip you install on device. I can't fix bugs, i only can wait until some contributor fixes it and I will build rom with fixes and updated security patches included.
@TechDriver Got it. Will the devs be watching this thread for feedback?
kb8no said:
@TechDriver Got it. Will the devs be watching this thread for feedback?
Click to expand...
Click to collapse
I am unsure about that, most of original devs for n2awifi and v2awifi stopped developing code for this devices. Keep an eye on exynos542X github for new commits.
First of all I want to thank you for the this ROM.
I tried this ROM with the latest TWRP version for two days and I want to inform that it is working good with some small non-conformities:
I had some random reboots and the system crashed and freezing
After rebooting there is a long time after entering the unlock pattern, sometimes it is necessary to enter the pattern several times.
I have installed ROM, gapps nano rebooted and after that install Magisk 22.1
my model is SM-T900
@TechDriver ,Great work on this build! Never thought I would see this accomplished. Many thanks and keep up the good work. This is fully usable with Nova beta 7.0.27.
Works perfectly on my T900, many thanks! Keep up the good work!
stanl56 said:
@TechDriver ,Great work on this build! Never This is fully usable with Nova beta 7.0.27.
Click to expand...
Click to collapse
Can you provide a link for this latest Nova beta? APK mirror seems booked.
Nova 7.0.27 Works smoother and scrolling and moving icons is better. PIN screen on first login is same problem and will not work on the first try. Mouse clicks and mouse related screen painting remains an issue. If you don't use a mouse you may not notice any problems other than first login. Come to think about it, 7.1 had issues with the mouse most noticeable when I used Collabora and I had attributed it to the app.
I'm not a fan of Android 12's Material You, i.e. dull color schemes, ginormous headers and copious amounts of whitespace. Screens got bigger over time, but information density is getting lower and lower. It's crazy. Anyway, I'll spare you the rant.
As the LineageOS project stopped publishing builds for LineageOS 18.1, but they continue to patch their 18.1-branch with Android's monthly security updates, I decided to start building it myself following the instructions here.
You can download the builds here:
LineageOS 18.1 for Pixel 4a (sunfish) - Browse Files at SourceForge.net
Unofficial builds for those who wish to stay on 18.1 a bit longer.
sourceforge.net
I usually publish an update every month.
Additional tweaks
Default maximum lockscreen password length of 64 characters (instead of 16) [more info]
FirmwareIt's probably best to run the latest Android 11 firmware, since this is Android 11. You can download the last official Android 11 factory image from Google and flash it from fastboot mode (your data will be erased).
Clean install
Download the latest lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish-boot.img and lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish.zip from aforementioned link
Boot to bootloader a.k.a. fastboot
Flash the boot image with this command (replace filename with actual filename):
fastboot flash boot lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish-boot.img
Boot to recovery
Factory reset > Format data/factory reset > confirm (your data will be erased)
Apply update > Apply from ADB
Sideload the ROM with this command (replace filename with actual filename):
adb sideload lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish.zip
(If it asks "Signature verification failed. Install anyway?" answer Yes)
Optionally flash Gapps or anything else:
Advanced > Reboot to recovery
Run adb sideload with your zip
Reboot system now
UpdatingUpdates are delivered through the built-in updater (Settings > System > Updater).
If you use Magisk, deny the Updater's request to reboot at the end of the update process, open Magisk, tap Install and then "Install to Inactive Slot (After OTA)". Tap reboot after the process completes.
Migrating from last official LineageOS 18.1 buildSo it turns out builds are signed with a secret cryptographic key and when you install an update it has to have the same cryptographic signature or bad things will happen. This means you can't directly update from the last official build (signed by the LineageOS team) to my build (signed by me).
The solution: build and install (as an update a.k.a. dirty flash) a so called "migration build", which "resets the keys on all packages at every boot." I guess after booting into this build once, you can just update to the regular build using the updater (the LineageOS wiki is very concise on this topic and doesn't explain much).
You can download the migration build and boot image from the aforementioned link, they are marked MIGRATION instead of UNOFFICIAL. Don't run this build any longer than necessary, it's a security risk by its very nature.
When I tried this migration, my system wouldn't boot (stuck on boot logo). ADB worked and I could see in dmesg or logcat that, among other errors, SystemUI failed to start. Was it because I didn't reflash Gapps? But I never reflashed Gapps when using LineageOS' builtin updater...
Later I did some testing. I did a clean install of the latest official build, then my migration build, then my normal build, all was fine. Then I did a clean install of the latest official build WITH Gapps, then flashed the migration build WITHOUT Gapps, and the system booted up just fine. Huh? Then I flashed my normal build DIRECTLY over the latest official build, without migration build in between, and all was STILL FINE! So uhm... what's happening, how does this signing work and when does it become a problem? I have no clue.
If you decide to try the migration route, make sure to backup any data you don't want to lose and let us know how it went!
AcknowledgementsThanks to the original maintainers PeterCxy, cdesai and mikeioannina for bringing LineageOS 18.1 to the Pixel 4a!
Source code
LineageOS
A free and open-source operating system for various devices, based on the Android mobile platform. This is a mirror of https://review.lineageos.org/ - LineageOS
github.com
GcamYou can just install it from the Play Store. There are a few bugs:
In photo mode, slide up to record video doesn't work
Motion Photos doesn't work
It doesn't scan QR codes without Google Lens
App versions without Material YouIf, like me, you try to avoid Material You like the plague, here's a list of the last versions of Google apps that I use(d) that don't have Material You. Note that LineageOS includes its own versions of some of them and all of them are optional anyway. You can find them on e.g. APKMirror.
Calculator 7.8
Calendar 2021.35.3
Camera 8.2.400
Clock 6.4.1
Contacts 3.49.2
Gboard 10.8.05
Maps 10.80.1
Phone 68.0.3
Photos 5.58.0
Translate 6.24.0.02
Is it wise to run older software? You decide. In an ideal world security updates and bug fixes would be separate from UI and "we decided you don't need this functionality so we removed it" updates. I've long ago stopped regularly updating my apps (i.e. turned off automatic updates) because I like to be able to trust my device will look & work the same tomorrow as it did today.
P.S. After you've installed the regular 20220815 build, the updater will keep showing an August 16 update which is actually the build you're already running. This is because I had to move the timestamp one day forward in order to enable updating from the MIGRATION build, which was also build on 20220815 and wouldn't see the regular 20220815 build as an update otherwise. This will be remedied with the next update I publish.
The September update is now live.
Does banking app works?
My bank's app has always worked fine on LineageOS. Your bank's hasn't?
icantlogin said:
My bank's app has always worked fine on LineageOS. Your bank's hasn't?
Click to expand...
Click to collapse
I had never tried this rom want to try if bank apps works out of box
icantlogin said:
The September update is now live.
Click to expand...
Click to collapse
Been using this for several days now without a hiccup , fast ,,smooth, and google proofed, Thanks!!
Thanks for keeping LOS 18.1 alive with these security updates. I recently upgraded to 19.1 to try it out for a few months but I just couldn't get used to or appreciate the new UI. With every app update they also make it more like A12 and it just wasn't working for me.
Just installed your September update and all is well so far.
The October update is live!
A little background: I'm building this ROM on a Google Cloud Compute Engine instance, which is a virtual computer (also called virtual machine or VM) running in a Google data center. To keep the VM around is very costly, as it uses 300 GB of SSD storage which doesn't come cheap. So I create a new VM every month and dismantle it afterwards. This means I have to set up the build environment from scratch every time, which consists of a lot of steps. So from the beginning, I've put most of those steps in a Bash shell script (the VM runs Ubuntu 20.04) to speed things up drastically.
Last week I added some code that generates the updater.json file (that's read by your phone when it checks for updates) which I had been creating by hand before. I also added code to automatically upload the build to SourceForge. So yesterday all I had to do was create the VM, upload the script and run it. Six hours later, your phone was able to download the update without any further intervention on my part.
What can I say, the geek in me is very happy
Hi, I thank you for your work. Would you know if I can install microg without magisk, maybe via nanodroid or similar while maintaining OTA updates?
I have no experience with that. I assume you would have to apply the signature spoofing patch and install microG before booting from the updated system partition. So after installing the OTA update boot into recovery and do this?
Hello ! How to you push the google apps on this one ?
I'd like to get a pico gapp installed to get some game running
It's in the instructions in the first post, after flashing the ROM:
Optionally flash Gapps or anything else:
Advanced > Reboot to recovery
Run adb sideload with your zip
I'm using NikGapps Core myself.
This only works if you do it before first boot by the way, as far as I know you can't put Gapps on an installation you're already using.
Hi! Do you know if this will retain microg if I dirty-flash it on top of a lineage.microg.org build (the last official release) using your MIGRATION build? If you're not sure I'll back up my stuff and give it a shot and report back Thanks a lot for your your work!
Well... I don't think that would work, since this ROM doesn't include microg and the needed signature spoofing, so my guess would be you'll just loose that—if the migration works at all. Let me know what your findings are though!
icantlogin said:
Well... I don't think that would work, since this ROM doesn't include microg and the needed signature spoofing, so my guess would be you'll just loose that—if the migration works at all. Let me know what your findings are though!
Click to expand...
Click to collapse
Here is what I found, in case it helps someone: flashing the migrate ROM and then the latest proper ROM works perfectly, however I did lose microg, system f-droid, etc, and anything which is in the lineage.microg.org build but not in this one.
Now since you are building monthly ROMs, would you consider applying the signature spoofing patch to your builds? This would make it easy for those who want to run microg instead of google play framework/gapps. As far as I understand it you just need to apply this patch with `cd android_frameworks_base; patch -p1 -i /path/to/android_frameworks_base-R.patch`. Thanks again for your efforts
I'm open to consider this, but as I somewhat but not fully grasp the security implications of enabling signature spoofing, and not everyone might want to have this enabled by default, it would have to be a toggle in Developer Options and disabled by default, or I would produce a separate build with the patch applied.
If you could find a patch for me that implements the toggle in Developer Options, that would be great. As I researched it a bit I read that some ROMs have this.
Interesting that the migration worked, by the way!
Some more thoughts on this: it seems with signature spoofing enabled on the ROM, an app still has to ask for the permission to spoof its signature, so for advanced users like us who know what we're doing, I guess that's good enough. I'll have to read up on this a bit more though. I know the LineageOS devs are against implementing it but most everyone else says it's actually not that big of a security risk.
I just reply to show you my gratitude for maintain LoS 18. I updated to 19 two weeks ago and I was literally suffering with the system theme. IDK what they were thinking but it was terrible. Also for me, on 4a, was having lag: An example is when I shuffle songs on Musicolet, they take a good while to update the information (song name, basically) while with 18 it updates as soon as I press next.
BTW, can you recommend me a good KERNEL? Thanks!