Database Info

[ROM] [UNOFFICIAL] LineageOS 13 for Life One X2 [DISCONTINUED]

LineageOS 13 for Life One X2​
This Rom was ported from the Unofficial LineageOS 13 for the Yureka Black. First I need to give credit for all the hard work the developers put into their Rom, I only modified it to work on the Blu Life One X2.
Note: Please remember I'm doing this on my own time and using my own money to cover expenses.
What Works:
Boots
Calls
SMS
Data
GPS
Wifi
Bluetooth
Audio
Video Playback
Sensors
Led
Not Working Yet:
(Please let me know if you find anything else)
Camera
Flash (works but reversed front to back)
Fingerprint
Downloads:
Builds: https://drive.google.com/drive/folders/0BzMHnGbQH3bhVnppRTdHbjZyZEk?usp=sharing (list view recommended)
TWRP: https://drive.google.com/file/d/0BzMHnGbQH3bhRGhuQVNsWUFsa0k/view?usp=sharing
Kernel: https://github.com/meganukebmp/android_kernel_blu_life-one-x2
Gapps: http://opengapps.org
Special thanks to Ieatgravity and Tydraco for all their support.

Screenshots:
(screenshots taken with the PitchBlack | DarkRed CM13/12 theme)
Theme: https://apkpure.com/pitchblack-darkred-cm13-12/com.resurrectionremix.pitchblack

Changelog
Lineage-13.0-08282017-2012-UNOFFICIAL-Life_One_X2:
fixed gapps (fixed "there was a problem communicating with google servers" error)
Lineage-13.0-09042017-2137-UNOFFICIAL-Life_One_X2:
Fixed theme manager crashing
Cleaned up some of my code

Troubleshooting
Encryption Unsuccessful Screen:
Boot into TWRP and format Data (not wipe)

Reserved

Great work! I look forward to testing this.

I was using drax rom, flashed your LOS and i keep getting the encryption unsuccessful. how do i go about this?

Daisuke1988 said:
I was using drax rom, flashed your LOS and i keep getting the encryption unsuccessful. how do i go about this?
Click to expand...
Click to collapse
Go into TWRP and format Data. That fixed it for me.

srgrusso said:
Go into TWRP and format Data. That fixed it for me.
Click to expand...
Click to collapse
Thanks! now one last thing, which gapps did you use? ive tried 3 and they all fail. would it be because of the encryption thing?

Daisuke1988 said:
Thanks! now one last thing, which gapps did you use? ive tried 3 and they all fail. would it be because of the encryption thing?
Click to expand...
Click to collapse
Sorry unfortunately I haven't been able to get them working either. I've been getting "there was a problem communicating with google servers" error. I'm currently trying to fix this. I think it is related to this error from dmesg:
Code:
[ 1398.055688] type=1400 audit(1503798238.823:50): avc: denied { search } for pid=7470 comm="IntentService[P" name="com.google.android.gsf" dev="mmcblk0p46" ino=803248 scontext=u:r:untrusted_app:s0:c522,c768 tcontext=u:object_r:app_data_file:s0:c512,c768 tclass=dir permissive=1
I have been using other apk resources for now. I'll add opengapps to the list.

Ok I think I figured out the gapps problem. I hope to have a fix tomorrow.
Here is a quick fix. Download build.prop
https://drive.google.com/file/d/0BzMHnGbQH3bhLWdIQmd4cVl6LWs/view?usp=sharing
Boot into TWRP and mount system partition rw then:
adb push build.prop system/
adb shell
chmod 644 system/build.prop
reboot
now opengapps should work.

The problem for now will be to operate the cameras correctly, in addition to the fingerprint reader ... But little by little and with this is a breakthrough

srgrusso said:
Ok I think I figured out the gapps problem. I hope to have a fix tomorrow.
Here is a quick fix. Download build.prop
https://drive.google.com/file/d/0BzMHnGbQH3bhLWdIQmd4cVl6LWs/view?usp=sharing
Boot into TWRP and mount system partition rw then:
adb push build.prop system/
adb shell
chmod 644 system/build.prop
reboot
now opengapps should work.
Click to expand...
Click to collapse
man youre awesome!

kiomet said:
The problem for now will be to operate the cameras correctly, in addition to the fingerprint reader ... But little by little and with this is a breakthrough
Click to expand...
Click to collapse
im assuming once the finger print sensor is working we can use it as gesture navigations right?

Daisuke1988 said:
im assuming once the finger print sensor is working we can use it as gesture navigations right?
Click to expand...
Click to collapse
I could be wrong, but I don't think this phone supports that. Hopefully someone will correct me if I am wrong.

New build uploaded with gapps fixed.
Lineage-13.0-08282017-2012-UNOFFICIAL-Life_One_X2.zip

srgrusso said:
I could be wrong, but I don't think this phone supports that. Hopefully someone will correct me if I am wrong.
Click to expand...
Click to collapse
Not natively. Probably will work with an additional app. But the rom itself doesn't have this built in. (not even swipe for back option from stock X2 )

ieatgravity said:
Not natively. Probably will work with an additional app. But the rom itself doesn't have this built in. (not even swipe for back option from stock X2 )
Click to expand...
Click to collapse
on the stock rom it has the option to use it as a agivation option under the finger print settings

Daisuke1988 said:
on the stock rom it has the option to use it as a agivation option under the finger print settings
Click to expand...
Click to collapse
Yes but the lineage os for this rom was ported from another phone. It wasn't compiled for our phon so the option for navigation isn't included. Now with that said. If someone would like to experiment and see if they can extract that from the stock settings and merging it with the lineage settings then maybe we can add that functionality. Either way it will be useless without a working fingerprint scanner.

ieatgravity said:
Yes but the lineage os for this rom was ported from another phone. It wasn't compiled for our phon so the option for navigation isn't included. Now with that said. If someone would like to experiment and see if they can extract that from the stock settings and merging it with the lineage settings then maybe we can add that functionality. Either way it will be useless without a working fingerprint scanner.
Click to expand...
Click to collapse
well it will come. over all, the rom is working great.

[MOD][Nougat] Stock File Manager has some hidden features, enable them! (How-To)

I noticed that S8 and Note FE ROMs have some extra features that the regular Note5 didn't have, at least not without rooting and modifying it. Some of them are very easy to enable like this but a modified device is required. This time is about the My Files app, the stock Samsung file explorer.
system/csc/others.xml add this lines:
cachanilla86 said:
<CscFeature_MyFiles_EnableDirectorySearch>TRUE</CscFeature_MyFiles_EnableDirectorySearch>
<CscFeature_MyFiles_SupportApkCategory>TRUE</CscFeature_MyFiles_SupportApkCategory> <CscFeature_MyFiles_SupportPinLock>TRUE</CscFeature_MyFiles_SupportPinLock>
<CscFeature_MyFiles_SupportFolderDescription>TRUE</CscFeature_MyFiles_SupportFolderDescription>
<CscFeature_MyFiles_SupportRmvbFileFormat>TRUE</CscFeature_MyFiles_SupportRmvbFileFormat>
<CscFeature_MyFiles_ConfigDataUsageWarning>TRUE</CscFeature_MyFiles_ConfigDataUsageWarning>
Click to expand...
Click to collapse
system/etc/floating_feature.xml add this line:
cachanilla86 said:
<SEC_FLOATING_FEATURE_MYFILES_SUPPORT_OPTIMIZE_STORAGE>TRUE</SEC_FLOATING_FEATURE_MYFILES_SUPPORT_OPTIMIZE_STORAGE>
Click to expand...
Click to collapse
After a Reboot the changes will appear, if not try clearing the app's data.
I attached MY OWN files for reference, you can use the .zip to install yours. My phone is a Sprint model (SM-N920P) so don't try to flash it on any other model.
This is a good time to enable the unit converter in the stock calculator app and some other mods.
Do you Want to enable call recording? add this lines to system/csc/others.xml
cachanilla86 said:
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
<CscFeature_VoiceCall_EnableCallButtonInFdnList>TRUE</CscFeature_VoiceCall_EnableCallButtonInFdnList>
Click to expand...
Click to collapse
Good luck!

you can simply get it by installing latest version from apkmirror. It installed without any problem on stock unrooted

Ijaz Farooq said:
you can simply get it by installing latest version from apkmirror. It installed without any problem on stock unrooted
Click to expand...
Click to collapse
Doesn't work that way. If you don't modify at least the floating_feature.xml you won't get the hidden features, no matter how updated the app is. I tried, that's when I came to understand that was a "CSC mod". If you are on a custom ROM of course it will work because S8 or Note FE have this already enabled.

cachanilla86 said:
Doesn't work that way. If you don't modify at least the floating_feature.xml you won't get the hidden features, no matter how updated the app is. I tried, that's when I came to understand that was a "CSC mod". If you are on a custom ROM of course it will work because S8 or Note FE have this already enabled.
Click to expand...
Click to collapse
yes it's work, i have already try install latest MyFile apk from apkmirror, i'm not rooted

cachanilla86 said:
Do you Want to enable call recording? add this lines to system/csc/others.xml
Click to expand...
Click to collapse
Well. Watch out.
There is a missmatch in that line:
<CscFeature_VoiceCall_ConfigRecording>RecordingAll owed</CscFeature_VoiceCall_ConfigRecording>
It should be without the blank spcace in "RecordingAll owed", but RecordingAllowed", my friend.
Po properly it should look like this"
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
Do NOT forget after putting these line in the "cscfeature.xml"-file to do these 2 things:
1. Set permissions to the file "others.xml" to 0644
(if you're on Nougat, then the file is "cscfeature.xml" in this folder:
system/omc/"your CSC"/cscfeature.xml
Set permissions (if changed) to your CSC folder (in my case it's "XEO") to 0755.
2. Restart.
Now, good luck.
In my case it worked like hell
Mine model & ROM: N920C with KHONGLOI-NOUGAT ROM ver. 11

Jack_Surfer said:
Well. Watch out.
There is a missmatch in that line:
<CscFeature_VoiceCall_ConfigRecording>RecordingAll owed</CscFeature_VoiceCall_ConfigRecording>
It should be without the blank spcace in "RecordingAll owed", but RecordingAllowed", my friend.
Po properly it should look like this"
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
Now, good luck.
In my case it worked like hell
Mine model & ROM: N920C with KHONGLOI-NOUGAT ROM ver. 11
Click to expand...
Click to collapse
It is a forum Glitch when copy-pasting

No modification required
just update My files App from galaxy store or from apkmirrior.

prabjots07 said:
just update My files App from galaxy store or from apkmirrior.
Click to expand...
Click to collapse
Nope.

Your job
wuau men, you´re are a genius!!! Thanks for this...

<CscFeature_MyFiles_SupportFolderDescription>TRU E</CscFeature_MyFiles_SupportFolderDescription> newer builds like note8 roms it will disable samsung cloud

What am i supposed to be seeing in the screen shots? Only dif i see is Scloud

I already have them without anything

Cant use Gear S2 Classic with lineage OS

So, I've just installed Lineage OS on my phone.
Wanted to try a custom rom.
And when I try to connect to my Gear S2 Classic it states in a pop up.
The operating system on your phone has been modified in an unauthorized way.
and is not compatible with the Samsung Gear app.
Check your operating system and try again.
Any idea how to do it anyways?

Installing the safety net fix could help

Angle784 said:
So, I've just installed Lineage OS on my phone.
Wanted to try a custom rom.
And when I try to connect to my Gear S2 Classic it states in a pop up.
The operating system on your phone has been modified in an unauthorized way.
and is not compatible with the Samsung Gear app.
Check your operating system and try again.
Any idea how to do it anyways?
Click to expand...
Click to collapse
Could you solve it ??? I have the same problem.

Adding in to say that I too have this issue with LineageOS and my Gear S2 Classic. I remember someone on XDA offered some other (maybe older?) apks which allowed it to work for a while but now it seems after updating LineageOS to a newer nightly build, the Gear stopped working again. I'm on a OnePlus3 running the December 15th nightly.

Hey any idea ? I have same problem

I have the same problem

Updating your build.prop, change all "samsung" references to "htc" and you'll be able to open the app... I'm still fighting to get it to see my Gear 2, though.

I have it working on my Samsung Note 3 with Resurrection Remix 5.8.5 which is Lineage 14.1.
I also had to change manufacturer and another build.prop entry from samsung to something else (htc in my case) before I could download it from the playstore (got the same message, probably due to Knox not being there anymore and therefore Samsung thinking I have a modified Samsung phone which is true).
After that I think I also had to download from apkmirror com.samsung.accessory_3.1.73.71102-317371102_minAPI15(arm64-v8a,armeabi)(nodpi)_apkmirror.com.apk and com.samsung.android.gearoplugin_2.2.03.17121551-2117121551_minAPI18(arm64-v8a,armeabi,armeabi-v7a)(nodpi)_apkmirror.com.apk
It's working like on a original Samsung Touchwiz Rom now.
And of course you have to reset your watch to connect to your "new" phone.
Best regards
Amber

Hi, the only solution that helped me to resolve this issue is well explained in this post (more than 48 hours trying different solutions):
https://forum.xda-developers.com/gea...cm-rr-t3743138

My 50cts (or 500 words)
I have used the following to be able to connect my Samsung Gear S2 to my rooted Samsung Galaxy S7 running on lineage-14.1-20180214-nightly-herolte
I use TWRP (twrp-3.2.1-1-herolte.img.tar) as recovery manager to install .zip files onto my S7.
I had rooted my S7 by installing the LineageOS su add-on (addonsu-14.1-arm64), but due to SafetyNet issues which prevented my Gear S2 to connect,
I removed it with addonsu-remove-14.1-arm64.
So I installed Magisk (MagiskManager-v5.6.0.apk) to have Root and to hide Root and (part of) the SafetyNet 'Failing',
so Play Store and other programs will not know it is rooted.
I installed the following Samsung apk files to get my Gear S2 working:
com.samsung.android.gearoplugin_2.2.03.18011941N-2118011941_minAPI19(arm64-v8a,armeabi,armeabi-v7a)(nodpi)_apkmirror.com.apk
com.samsung.android.app.watchmanager_2.2.20.17113061-2117113061_minAPI18(nodpi)_apkmirror.com.apk
com.samsung.accessory_3.1.80.80109-318080109_minAPI15(arm64-v8a,armeabi)(nodpi)_apkmirror.com.apk
Via Magisk Hide option I have hidden root from the Samsung Gear application so it would not abend with the infamous "your device has been tampered with..." error
Finally you need to edit the /system/build.prop file and change all 6 occurrences of samsung into [email protected] (or htc if you prefer that),
so the application does not realize the hardware is in fact a Samsung and therefore not running the stock ROM, the bluetooth connection
to the Gear S2 will fail if build.prop contains samsung.
(I use Total Commander editor to edit the build.prop file but I think any editor will be able to do that if you are rooted.
and last but not least make sure the permissions of the build.prop file are -rw-r--rr or 644 in Linux terms because the Lineage ROM
will not boot if the permissions are not 644).
I installed the Samsung Health application from the play store and that seems to work fine.

MuSzAr said:
Hi, the only solution that helped me to resolve this issue is well explained in this post (more than 48 hours trying different solutions):
https://forum.xda-developers.com/gea...cm-rr-t3743138
Click to expand...
Click to collapse
The link you posted is giving a 404 error (probably because it has "..." in the name instead of the full thread name)--would you please post the full name of the thread so I can search for it?
Thanks

samej71 said:
The link you posted is giving a 404 error (probably because it has "..." in the name instead of the full thread name)--would you please post the full name of the thread so I can search for it?
Thanks
Click to expand...
Click to collapse
Hi,
This is the right link : https://forum.xda-developers.com/gear-s2/help/gear-s2-gear-manager-touchwiz-romscm-rr-t3743138
But you can search it : "Gear S2 (Gear Manager) works on non-TouchWiz Roms(CM, RR, Lineage etc)"

In case anybody has the same problem, this thread solved all of my issues. I have a Nexus 5 with lineage OS, and I could not get google play store to install the app. It didn't show up in play store on my phone, and online it said the app wasn't available for my device.
Fortunately [B @j to the 4n[/B] has made resigned versions of all three necessary apps (gear plugin, samsung health, samsung accessories) - and the Samsung Gear S3 is working flawlessly again.
https://forum.xda-developers.com/an...d-samsung-gear-app-android-n-samsung-t3547035
And a direct link to the drive folder, just in case: https://goo.gl/WjqOhv
Mirror 1, mirror 2
Thank you very much @j to the 4n.

MuSzAr said:
Hi, the only solution that helped me to resolve this issue is well explained in this post (more than 48 hours trying different solutions):
https://forum.xda-developers.com/gea...cm-rr-t3743138
Click to expand...
Click to collapse
Link not work !

SWAT10101 said:
Link not work !
Click to expand...
Click to collapse
The links for the files are in the post right above yours.

[ROM][7.1.2] LineageOS for microG [6/17/18]

Code:
I am not responsible for anything that happens as a result of you using the ROM. Sure, i'm willing to help with bugs, but if you get fired because the Alarm app crashed, gremlins crawl out of your arse, thermonuclear war starts, or if your progress in Clash of Clans gets reset, i'm not the one to blame.
Features
Code:
microG and F-Droid pre-installed
Anything else LineageOS can do
Is not certified cancer-free in California
Stuff you need to actually use this
- Unlocked Bootloader (duh). Seriously, I will ignore you if you mention that you tried to boot this with Safestrap.
- Update TWRP to Android-7.1 builds located here. Please make sure to use the recovery image which is appropriate for your device (Thor or Apollo)
How do I actually install this?
- Backup existing ROM if you want. Or don't. I don't really care, truth be told.
- Wipe /data partition. You can keep media storage if you want, but I prefer to format it to make it SQUEAKY CLEAN
- Flash the .zip
- Do not flash OpenGapps. Or any Gapps. That defeats the purpose of microG.
- Flash any other crap you want. This'll probably Magisk.
- Reboot.
Downloads
AndroidFileHost: Thor, Apollo
Extra junk you might want
Magisk
Yalp Store (play store wrapper)
Flashable Standalone Google Play Store
Sources
I didn't make any of this. I just compiled and signed it. People smarter than me, like hashcode and ggow did, made this work on the HDX. Lots of other people made LineageOS and microG. Thanks to you all.
Phoenix Kernel
HDX-Common device tree
Thor device tree
Apollo device tree
Docker instance that I use to build this
How do I tell the NSA didn't tamper with my download?!
Luckily, I signed the builds with my own key!
Code:
$ keytool -list -printcert -jarfile lineage-14.1-20180613-UNOFFICIAL-thor.zip
Signature:
Owner: [email protected], CN=steamport, OU=steamport, O=steamport, C=US
Issuer: [email protected], CN=steamport, OU=steamport, O=steamport, C=US
Serial number: b1b3cdcf593b5030
Valid from: Tue Jun 12 20:49:48 EDT 2018 until: Sat Oct 28 20:49:48 EDT 2045
Certificate fingerprints:
MD5: 13:E0:38:54:47:CC:FA:B8:24:50:16:6D:41:90:C7:4F
SHA1: 5F:AD:C9:4B:43:D3:1E:C3:6B:5F:86:DE:6A:F6:C7:F8:72:CB:B7:04
SHA256: BB:A1:BB:0F:7B:E1:62:2D:87:27:FE:EC:C5:CA:C6:B7:E3:EA:1A:CB:32:33:7E:F4:2C:D6:BC:BC:6E:46:27:CC
Signature algorithm name: SHA256withRSA
Subject Public Key Algorithm: 2048-bit RSA key
Version: 3
XDA:DevDB Information
LineageOS for microG, ROM for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
steamport
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader, TWRP
Based On: LineageOS
Version Information
Status: Testing
Created 2018-06-13
Last Updated 2018-06-22

so confuse about microg. there are some games we must live with google play or the games can't run.
but micro g are great for user who not play games rely on google play.

locolyric said:
so confuse about microg. there are some games we must live with google play or the games can't run.
but micro g are great for user who not play games rely on google play.
Click to expand...
Click to collapse
What is there to be confused about? Yes, Google Play Games doesn't work with microG yet. Just don't play with games that mine your data. Problem solved. Or just try to lubricate it with cat piss. I don't care.

Stupid Question: does this support LTE?

CCF_100 said:
Stupid Question: does this support LTE?
Click to expand...
Click to collapse
I don't think any Nougat ROM for thor or apollo supports LTE. Sadly, no.

CCF_100 said:
Stupid Question: does this support LTE?
Click to expand...
Click to collapse
steamport said:
I don't think any Nougat ROM for thor or apollo supports LTE. Sadly, no.
Click to expand...
Click to collapse
Correct - only KitKat based custom ROMs support LTE (data only). FireOS 4.5.x is the best choice for voice and mobile data support.

New zips are out. I just updated microG's GMSCore to one I built myself based on master and a fix PR. Also pulled from latest Lineage 14.1 sources.

Bluetooth issue ? I still use kitkat because i can use bluetoooth. But so boring ..

NeverSmile said:
Bluetooth issue ? I still use kitkat because i can use bluetoooth. But so boring ..
Click to expand...
Click to collapse
Likely won't be any different with this ROM as core issue resides at the kernel level. Inconsistent connection behavior leads to erroneous claims based on individual experiences but really not ROM related other than the binary KitKat (Android 4.4.x) or above checkpoint.

Firstly this is an amazing ROM! Well done to you and the team! However, the recent Apollo release is broken. Not sure about the Thor version, i would check but the device I bricked because I was messing around... Anyway it boots successfully but the screen is blank and is still turned on, no boot animation other than the generic grey kindle fire. I can still tap the screen and hear android feedback noises after waiting awhile so it works! Just I cant see anything :laugh: The previous release worked fine, no problems! Maybe you could keep the recent previous releases available for download for backups in case? Thanks again
Edit: Obviously I have the bootloader unlocked etc. Using latest TWRP if that helps at all.

kfhdxuser said:
Firstly this is an amazing ROM! Well done to you and the team! However, the recent Apollo release is broken. Not sure about the Thor version, i would check but the device I bricked because I was messing around... Anyway it boots successfully but the screen is blank and is still turned on, no boot animation other than the generic grey kindle fire. I can still tap the screen and hear android feedback noises after waiting awhile so it works! Just I cant see anything :laugh: The previous release worked fine, no problems! Maybe you could keep the recent previous releases available for download for backups in case? Thanks again
Edit: Obviously I have the bootloader unlocked etc. Using latest TWRP if that helps at all.
Click to expand...
Click to collapse
I don't have an apollo, so can you do some debugging for me? ADB into it. It'll ask for authorization on the screen, just guess where the OK button is til it works. Anyways, when you do get adb auth, run this:
Code:
adb shell
logcat > log.txt
exit
adb pull log.txt
, then put the log.txt on pastebin and give me the link

Been trying for about an hour now all i'm getting is feedback noises, is the confirmation dialog being prevented due to the setup process if there is one? Cant seem to get out of it and ADB keeps saying the device is unauthorized. I'll keep trying on the OS and once i get anything i'll update you as soon as i can.

kfhdxuser said:
Been trying for about an hour now all i'm getting is feedback noises, is the confirmation dialog being prevented due to the setup process if there is one? Cant seem to get out of it and ADB keeps saying the device is unauthorized. I'll keep trying on the OS and once i get anything i'll update you as soon as i can.
Click to expand...
Click to collapse
I've seen the dialog pop up as soon as it finishes booting

Done!
steamport said:
I've seen the dialog pop up as soon as it finishes booting
Click to expand...
Click to collapse
Okay i've got a log file after a few unsuccessful attempts, i'm not sure why the code you gave me did not work but I tried myself using "adb shell adb logcat -d > Lineage14.1.txt" and that seemed to do the trick. (Hopefully this is what you were after).
I tried to upload this to pastebin but it refused so i've uploaded it to an alternative website here: https://paste.ee/p/kL4Ur

kfhdxuser said:
Okay i've got a log file after a few unsuccessful attempts, i'm not sure why the code you gave me did not work but I tried myself using "adb shell adb logcat -d > Lineage14.1.txt" and that seemed to do the trick. (Hopefully this is what you were after).
I tried to upload this to pastebin but it refused so i've uploaded it to an alternative website here: https://paste.ee/p/kL4Ur
Click to expand...
Click to collapse
Thanks.... this is a weird log. It mentions turning the screen on several times? Can you try fully wiping system and reinstalling?

steamport said:
Thanks.... this is a weird log. It mentions turning the screen on several times? Can you try fully wiping system and reinstalling?
Click to expand...
Click to collapse
Yep i'll do that, was it the method that I used to extract the log file that could be the culprit? I should probably mention that you can see the screen when it turns off and on its just a different shade of black indicating that the screen works but it just won't display anything if that makes sense. I'll do a complete wipe and start again to see if its any different this time around.
Edit: Here is the new log: https://paste.ee/p/VK4oS
^^^
I've noticed it is considerably smaller this time around so hopefully this a good sign haha.
It is weird how the previous release worked and this one doesn't, i'd assume it's an application interfering from the latest build but if it works on Thor then it mustn't be right? Maybe something was accidentally changed for the Apollo release somewhere. Sorry if my ramblings aren't useful

Thanks @steamport! What is the security patch level on this build?

NextDroid said:
Thanks @steamport! What is the security patch level on this build?
Click to expand...
Click to collapse
Whatever the latest for 14.1 was as of 6/7/18?

steamport said:
Whatever the latest for 14.1 was as of 6/7/18?
Click to expand...
Click to collapse
Well, that depends, as the last AEX build, for example, was still on May 5.
Tapatalk を使用して私の LG-RS988 から送信

steamport said:
I don't have an apollo, so can you do some debugging for me? ADB into it. It'll ask for authorization on the screen, just guess where the OK button is til it works. Anyways, when you do get adb auth, run this:
Code:
adb shell
logcat > log.txt
exit
adb pull log.txt
, then put the log.txt on pastebin and give me the link
Click to expand...
Click to collapse
I've got the same problem. Loads but no screen and unable to find the "ok" to authorize the device. There must be a better way.
I will revert back to previous version until this is fixed.

General [U1][One UI 5] [STABLE]Android 13 Beta Testing

Upgrade Path
AVF7 -> ZVH4 [Beta 1]
http://fota-secure-dn.ospserver.net/firmware/XAG/SM-S908U1/nspx/fc88e20549314e42a3cf633fe022c5b8.bin?px-time=633d99a3&px-hash=16f77ec1312b710fae2fed054590b947&px-wid=6448401-WSA220806145009&px-wctime=2022-08-06%2014:50:09&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA==
ZVH4 -> ZVHK [Beta 2] - Thanks to Venom0642
OneDrive
onedrive.live.com
ZVHK -> ZVI9 - Thanks to Zacharee1
http://fota-secure-dn.ospserver.net/firmware/TMB/SM-S908U1/nspx/2017d046adba42e3b625b71213e8f249.bin?px-time=637b8846&px-hash=1e0bc1e12e8dc392e662527197b94d64&px-wid=9687435-WSA220922141636&px-wctime=2022-09-22 14:16:36&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA==
ZVI9 -> ZVJ2 [Beta 4]
http://fota-secure-dn.ospserver.net/firmware/XAA/SM-S908U1/nspx/47baffcb1e004202b228670abf2ed3c0.bin?px-time=638dcfd7&px-hash=ab2aa84429b258ac69c96f2f7f181875&px-wid=4811747-WSA221006110246&px-wctime=2022-10-06 11:02:46&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA==
ZVJ2 -> ZVJA [Beta 5]
http://fota-secure-dn.ospserver.net/firmware/XAA/SM-S908U1/nspx/9699aa24258049c6a9fb8e7aecb703ee.bin?px-time=639fc594&px-hash=a237d8cc9f71d4a5ec6e6f29a9dd38f0&px-wid=6510679-WSA221020015946&px-wctime=2022-10-20 01:59:46&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA==
ZVJA ->BVJA [STABLE FINAL]
http://fota-secure-dn.ospserver.net...58:23&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA==
This is the script content
Code:
pushd %~dp0
adb.exe sideload update.zip
pause
Tutorial
1. Backup your data
2. Fully power off your phone
3. Power your phone up while pressing Volume Up and Power at the same time
4. With the volume buttons navigate to "Apply update from ADB"
5. Press power to select that option
6. Decompress ADB folder anywhere and also script in the same folder
7. Download ZIP from Samsung and rename to update.zip or just update if your extensions are hidden
8. Connect phone to PC
9. Run script wait and enjoy

I will be posting all zip files for all the upcoming updates here in this post

There has been some improvements to gaming I play Apex Mobile and I can confirme the performance has improved

Hi brother, is there a firmware for the s908N （oneui5.0）for Korea?

Angerli said:
Hi brother, is there a firmware for the s908N （oneui5.0）for Korea?
Click to expand...
Click to collapse
i dont have N model, but seen this..
Post in thread '[OneUI 5 Beta] (Snapdragon) Galaxy S22/S22+/S22 Ultra OneUI 5.0 Beta Thread' https://forum.xda-developers.com/t/...a-oneui-5-0-beta-thread.4476787/post-87251423

rhystagram said:
i dont have N model, but seen this..
Post in thread '[OneUI 5 Beta] (Snapdragon) Galaxy S22/S22+/S22 Ultra OneUI 5.0 Beta Thread' https://forum.xda-developers.com/t/...a-oneui-5-0-beta-thread.4476787/post-87251423
Click to expand...
Click to collapse
Thank you very much

maxrdlf95 said:
There has been some improvements to gaming I play Apex Mobile and I can confirme the performance has improved
Click to expand...
Click to collapse
Yes. Can confirm better performance. Very shocking for their first beta, Although this can be due to minor changes

Does eye protection work for you?
Not for me

could you maybe upload a video tutorial to make it easier?

oile said:
Does eye protection work for you?
Not for me
Click to expand...
Click to collapse
I noticed after update it was disabled but I went into settings and Enabled it and it is working, we are talking about Eye Comfort right?

maxrdlf95 said:
I noticed after update it was disabled but I went into settings and Enabled it and it is working, we are talking about Eye Comfort right?
Click to expand...
Click to collapse
Yes, eye comfort. To me it worked only after a clear data on its specific app.
I am not fully understand why whatsapp is showing my old notifications style while Telegram shows better looking extending popus at the top. How to make whatsapp do the same?

oile said:
Yes, eye comfort. To me it worked only after a clear data on its specific app.
I am not fully understand why whatsapp is showing my old notifications style while Telegram shows better looking extending popus at the top. How to make whatsapp do the same?
Click to expand...
Click to collapse
Did you clear CACHE on Recovery mode? maybe that helps

OK If you update one5. You must flash AVF7 build. Then sideload beta update.zip.
I have another small question.
beta2 can ota？

Updated with Beta 2 link

maxrdlf95 said:
Updated with Beta 2 link
Click to expand...
Click to collapse
kinda need help with step 6 and 7. could you provide a little more detail please? thanks for the updates!

vvrrare said:
kinda need help with step 6 and 7. could you provide a little more detail please? thanks for the updates!
Click to expand...
Click to collapse
basically you need to download all files and put them together in one folder Zip from samsung on beta 2 it's actually a onedrive link when you download the file it will be called ZVH4-TO-ZVHK.zip basically you need to right click on it and rename it to update.zip because the script it's designed to flash and update file only called update.zip i tried to make it easier this way so people don't need to mess with command line!

thanks for the beta 2 update

maxrdlf95 said:
basically you need to download all files and put them together in one folder Zip from samsung on beta 2 it's actually a onedrive link when you download the file it will be called ZVH4-TO-ZVHK.zip basically you need to right click on it and rename it to update.zip because the script it's designed to flash and update file only called update.zip i tried to make it easier this way so people don't need to mess with command line!
Click to expand...
Click to collapse
thank you !

maxrdlf95 said:
basically you need to download all files and put them together in one folder Zip from samsung on beta 2 it's actually a onedrive link when you download the file it will be called ZVH4-TO-ZVHK.zip basically you need to right click on it and rename it to update.zip because the script it's designed to flash and update file only called update.zip i tried to make it easier this way so people don't need to mess with command line!
Click to expand...
Click to collapse
one more question, will i have to do anything on terminal, or do i just plug in the device and run adb?

Any good souls who captured the S906E?