yashsingh1/xdaforums huggingface dataset:
[Sony Xperia XZ2 Compact Questions & Answers] FcukBloat:
unfortunately on xz2 family unlocking bl is not reversible, so it is easily detectable.. plus unlocking bl you lose drm protected stuff (noise reduction in pictures etc)

so be aware before doing that, and if you need perfect camera performances be sure to buy drmfix (available for oreo only for now), so you'd need to downgrade to O and not update to P.

btw, in P you can still have camera working (without noise reduction) with some tricks if you unlock and apply drmfix while In O
[Sony Xperia XZ2 Compact Questions & Answers] backslashV:
thank you for your response. exactly what things do I lose with bootloader unlocked on this phone?
[Sony Xperia XZ2 Compact Questions & Answers] FcukBloat:
the only big thing I care about is noise reduction system in cam pictures... then you lose other small things like backup feature from sony and other 1-2 minor things I don't even remember...

but in oreo I have everything enabled because I applied drmfix ;)

and many people is using existenze Pie rom as they say cam quality is not so bad and that's another proof also of course the drm stuff is not important at all
[Galaxy Note 4 Q&A, Help & Troubleshooting] pol-der:
Hi All,

I am using LOS 14.1 unofficial (by dl12345 user from XDA) in my N910C. AutoRotate doesn't work and i found a solution which is working partly. What does mean partly?

I added these to my build.prob with adb.

log.tag.launcher_force_rotate=VERBOSE
lockscreen.rot_override=true

And i've set permission of build.prop like this.

chmod 644 build.prop

Then rebooted to System.

I tested AutoRotate and it is working good even if i am in main (lock) screen. 2-3 days later i realized it is not working anymore mysterious. In the meanwhile i rebooted the device 1-2 times within 2-3 days. I started to look for a new fix and found this command.

ro.sf.hwrotation=360

I deleted first two (2) commands and added this command to the build.prop with adb and set the permission like that.

Rebooted to System and tested. It is working good and today i realized it is not working again.

I started to think what is the problem? It is working some and not working anymore. Why? I couldn't find the problem.

I need your ideas and experiences.

P.S: I don't want to use an app always for this.

EDIT: I had edited and pushed build.prop 1 hour ago and had tested, it was working. I looked now and again it is not working :confused: I understood this is not related with 2-3 days, just minutes. I am really confused.

EDIT2: I enabled Auto Rotation with this command, didn't work.

root@kali:~/Downloads/platform-tools# adb shell settings put system accelerometer_rotation 1

I enabled user_rotation with this command, it is working.

root@kali:~/Downloads/platform-tools# adb shell settings put system user_rotation 1

Results of rests:

Disabled Accelerometer, enabled user_rotation=working

Enabled Acceleremoter, configured user_rotation with 0=not working

Enabled Accelerometer, configured user_rotation with 1=not working

As a result when i enabled Auto Rotation, is not working.

EDIT3: I installed this app and tested Accelerometer. I can rotate my phone 360 degree without enabling AutoRotate feature. I had thought my phone's accelerometer is broken, but not.

Thank you so much.

Have a happy day.
[Galaxy Note 4 Q&A, Help & Troubleshooting] CamoGeko:
Dupe.

Duplicate of this thread - https://xdaforums.com/general/help/autorotate-partly-mysterious-please-t3890032

Thread closed.

Camo.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] srgrusso:
AICP

Android Ice Cold Project

AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!

Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.

With the re-brand of CM to LineageOS (LOS) we became LineageOS based with some tweaks from AOSP and we are now based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.

If there are any bugs, either we will sort them out or the GZOSP team, if it concerns their code base. This ROM isn't GZOSP supported, so there is no need to report errors/bugs to them!!

#include <std_disclaimer.h>

/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/

Gapps: Arm64 9

Magisk: current version

Downloads:

SM-T580

SM-T585

Previous Builds:

SM-T580

SM-T585

Sources:

https://github.com/srgrusso/manifests/tree/gtaxl-aicp-14.0

I would like to give a huge thanks to [MENTION=5480152]followmsi[/MENTION] for building the sources and offering me a chance to maintain this rom.

I would also like to give thanks to [MENTION=2047373]Valera1978[/MENTION] for all his work.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] srgrusso:
Changelog

T580

https://drive.google.com/open?id=1HhHMvU4cZfMM1VZo_bjojKxPcErAfKHu

T585

https://drive.google.com/open?id=1-XwxarfXpgtV4auXarGeojoyflbEIapl
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] srgrusso:
Notes

Known issues:

MP4 recording bug after deep sleep.

In [MENTION=5480152]followmsi[/MENTION] RROS he is recommending to use "Footej Camera" to bypass this problem.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
Yesterday I have updated kernel sources (pie-r22) to support ExFAT for external sdcard.

Was missing in new kernel sources.

And finally fixed Magisk SafteNet (new fingerprint).

Pls pull the new changes via GitHub.

Thanks for driving AICP !

EDIT:

Have removed frameworks/av (youtube bug not happen on r22) and added frameworks/native (hwc1 fix) for now.

https://github.com/followmsi/manifests/commit/62e71a14568f4677a06e9005fe793cdd84eaaee0

As well I have updated the kernel again .. to include NFS and CIFS (network filesystems)

https://github.com/followmsi/androi...mmit/e3052fab7d88e9f4c516250f794b59a9dfbe0bda

The kernel should work on all "new" (r22) ROMS .. like 64-bit lineage, cdroid and AICP ..

And soon on RR as well :)

pie-oreo-kernel-gtaxlwifi-20190115.zip

pie-oreo-kernel-gtaxllte-20190115.zip

Cheers
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
I just finished installing this ROM and the kernel from your latest post. I've noticed one problem. Pressing and holding on a icon to move it, only seems to work on the Home page. But I can't move app icons to the Home page or install widgets. I'm using the latest pico gapps
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] mnd123:
Very nice, thanks. Will test it this week, I hope.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] fiddi1973:
installed new kernel, works perfect without any problems. i'm on crdroid 64bit. Thx ??
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] repey6:
CrDroid already have ExFAT support.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] srgrusso:
I don't seem to be having the same problem on my T580. What device do you have? What build number? Are you using the stock launcher? Did you do a clean wipe before swithching to AICP-14? Have you tried rebooting your tablet?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
Clean install of aicp_gtaxlwifi_p-14.0-UNOFFICIAL-20190112 on a T580 and rebooted several time. Using the launcher from the ROM. open_gapps-arm64-9.0-pico-20190115
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] srgrusso:
I'm still in the process of learning. The only repo I pulled was https://github.com/followmsi/android_kernel_samsung_exynos7870 . It was the only repo I noticed changed.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
Just checked your GitHub .. you have forked the repos now.

Good.

The manifest has changed too .. to add frameworks/native.

https://github.com/followmsi/manifests/blob/gtaxl-aicp-14.0/local_manifests/roomservice.xml

All other changes you have already applied ..

Cheers

---------- Post added at 09:32 ---------- Previous post was at 09:20 ----------

ExFAT is not part of the latest published kernel sources, had to add sources code.

https://github.com/followmsi/androi...mmit/5d0597850153023d1a069876549b4219b2433b3f
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] repey6:
I checked LTE build just now.

Mobile data not working. A lot of not translated to russian language. Root rights are constantly disappearing. Very long boot animation. GPS not working. Maybe something else. I am comeback to crDroid.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] mnd123:
If you came back to crDroid - does gps work ok now, no freezing when using it? If yes - how did you come back? :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] repey6:
GPS work also as before AICP test. I simply restore my crDroid backup from TWRP. At first wipes: system, data, cache and dalvik. Then restore system, data, cache, boot, efs.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
And you may change this line too :)

https://github.com/srgrusso/android...i/blob/aicp-14.0_64-bsp/aicp_gtaxlwifi.mk#L37

Cheers

---------- Post added at 17:37 ---------- Previous post was at 16:50 ----------

For mobile data there are additional changes required .. he may did not apply them for his first build.

For gps and for complete 585 device we use latest sources from Valera and do fully rely on him !

As you know, we don't own 585 devices for testing.

And GPS hardware is different on 585.

Either we build and publish for 585 devices (untested) or we need to skip 585 completely.

Other issues like long boot time or menu issues should be checked in detail.

Aicp is still working on Pie .. like all the other teams too.

Just building another (last) Android flavor for 580 .. Pixel Experience is coming soon. :)

Cheers
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] BADA 187:
[MENTION=5480152]followmsi[/MENTION] im willing to test builds for the 585 on my tablet.

I really like AICP. its in my top 3 fav roms together with HavocOS and SyberiaOS
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] srgrusso:
How much of a difference is there between Valera1978:lineage-16.0 gtaxlte and our AICP gtaxlte branch apart from what is necessary to get AICP to build?

Edit: Maybe we should move the T585 to another thread and label it [Testing].
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] srgrusso:
New build for the T580

https://www.androidfilehost.com/?fid=11410963190603902317

20190117

Exfat, NFS and CIFS filesystem support added. Thanks [MENTION=5480152]followmsi[/MENTION]

Fixed Magisk SafteNet (new fingerprint). Thanks [MENTION=5480152]followmsi[/MENTION]

:D
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] followmsi:
Only minor changes on top of his latest branch .. nothing related to GPS nor mobile data.

Have contacted Valera and asked if there are additional patches for 585 gps required.

Not sure when he replies.

Did you apply the fix from pphusson for mobile data ?

Here we need to replace both repos completely and make new build.

https://github.com/phhusson/platform_frameworks_opt_telephony/commits/android-9.0.0_r30-phh

https://github.com/phhusson/platform_packages_services_Telephony/commits/android-9.0.0_r30-phh

As said above we can not test 585 .. but GPS and mobile data are the only differences to 580.

Let's keep in the same thread .. should be solved in one of the next builds.

Thanks your work !

Cheers

---------- Post added at 08:33 ---------- Previous post was at 08:19 ----------

Thanks for your offer.

Pls install 585 version and have a look. :)

Pls check if gps is starting at all .. and if you get 3d fix.

Pls check mobile data too.

Are you able to post logcat ?

Cheers
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] srgrusso:
I like the pico. It's enough to get me Google Play and then I can pick and choose what else I want.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TheArtfulPenguin:
I did the edit and it made enough of a difference that I will probably keep it, however I am still getting some lockup within the app I use when in the camera. However if I exit & close the app and go back it then it works again for a bit. Better than before but not perfect.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
I only use the camera to snap pics of computer stuff I'm selling, so I'm no expert on camera apps. But having followed threads on XDA for several years, I do know that cameras seem to be the bane of just about every custom ROM ever developed. Most people seem to solve the problem by trying different app from the Play Store until they find one that suits their needs. And because everyone's needs are different, there doesn't seem to be any one app that suits everybody.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TheArtfulPenguin:
the different camera works fine except for apps that use the default camera from within the app. If you could replace the default camera then that might help.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] mnd123:
Is this fix for the video recording after deep sleep bug, or for something else regarding the camera?

does it help to save proper video files, that are recorded after the device has been in deep sleep, and they can be played back later without the video stopping and only sound being played back?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cd492:
Can I install the latest rom with twrp 3.1.1.1?

Edit: Nevermind I needed 3.3.+ to get it working.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TheArtfulPenguin:
For me it probably help almost 90% of the time. Still a couple where the video locked when I started. Just exited the app and back in and it was good.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] mnd123:
When you wrote about the video locking - do you mean that the image in the camera app freezes and you can't take the video, or you mean that the video locks while playing back the recorded file?

And what camera app are you using?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TheArtfulPenguin:
My tablet was charging good. Two days ago all of a sudden now it charges vvvvveeeeerrrrryyyyyyy slow. Over night only to 90 % from 30. If I charge it while using it then in an hour it might go up 2 or 3 %.

Thoughts?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TheArtfulPenguin:
The camera app freezes on a single image when starting to taking a video. Only way to get un-frozen is to get out of the app and clear it in the recent apps list.

This is when using the camera within an app that can record video or take a photo WITHIN the app using the Android default camera. Yes I can use an alternate camera like Footef camera fine, but not all apps let me load a video or photo, or I need to send a live photo rather than get out and take another photos because then the time has passed.

The build.prop edit did seem to work for a few days, but now it does not. I did verify the entry is still in the build.prop. Even exiting the app, going into Setting and closing the camera, clearing cache, and stopping the app, clearing that cache, and reopening them doesn't resolve it. Even restarting the tablet doesn't get the camera working within the app.

If there was just a way to specify a 3rd party camera as the Android default camera I think this wouldn't be a problem. I haven't found a way. Build.prop entry? Different way within Android?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Lonnie Reeder:
I have a general question about the ROM. Does is it purposely turn off cores 5-8 to save power consumption? I have been examining the system and no matter options I try I cannot get those cores to fire up.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
That isn't just this ROM. The high speed cores only turn on when needed. When they do turn on, the other 4 turn off. That is a feature of the SoC. With normal CPU demand, it uses the lower speed cores to save battery. Run the Antutu benchmark app and you'll find it does use the high speed cores.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TheArtfulPenguin:
No one has anything thoughts on this? It was like a switch was thrown. So I don't think the battery instantly changed. I've checked the USB port for anything that could be causing a problem. So it seems ROM related.

Could it be the kernel, or TWRP?

Thanks.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Nimueh:
TWRP has nothing to do with charging speed. But you could boot into TWRP and charge the device there, if it charges faster then you know it has something to do with the rom. I don't see how rom or kernel would suddenly change the charging speed though ... have you tried a different charger or cable?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TheArtfulPenguin:
Thanks. Just eliminating things. Yes different charger, different cable. Going to do a full wipe of everything and reload from scratch.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] srgrusso:
Have you cleaned around the USB port with a paper clip or something. You might have some debri keeping you from getting ahold connection. I have that problem with my phones. The get filled with pocket lint
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] BADA 187:
using any device while changing is a big no no to me. it degrades battery much faster.

do a full discharge then boot to twrp and keep it there charging till it reaches 100% then wipe dalvik/cache and boot again to rom. and see how it goes from there
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TheArtfulPenguin:
Yes I did that last night to make sure there wasn't any debris there. Used a bright flashlight to look around, and a plastic fine pick all round in the USB port.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Casper Young:
Charging Issue

I think it's ROM related. Mine won't charge when it's on (and the USB is plugged in). I did notice that in the Developer Settings under USB Configuration that if I tap Charge it doesn't do anything, it remains on MTP. If I turn the device off, then, it charges normally.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] srgrusso:
New builds

SM-T580 https://www.androidfilehost.com/?fid=6006931924117925251

SM-T585 https://www.androidfilehost.com/?fid=6006931924117925258
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Lonnie Reeder:
Ok, Just a quick sanity check here... I have been studying for a huge exam and I don't want to mess anything up, and on top of it, I am on medications that as a side effect can mess short term memory. So for a dirty flash the order is:

+ Boot to TWRP

+ Backup if so desire

+ Apply above build

+ Apply updated GAPPS

+ Apply Magisk

+ Clear Cache

+ Reboot

I know it might a dumb question but thanks in advance for your help.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Casper Young:
A durty flash is when you do not wipe the Data, Cache and the Davlik. You're not wiping the Cache which is from every application on the system, even those that run things like your UI and the options menus, generates cache files. These cache files are more or less unique to the current installation of Android you are using, and are generated dynamically. These cache files help Android load and run faster. When changing ROMs or updating to a new version of a ROM, you should always wipe the cache partition, or you're gonna have force closes, boot loops and slow performance.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Nimueh:
Wayyyy too much for a dirty flash lol.

Nandroid if you want

Flash new build

Wipe Dalvik/cache

reboot

I haven't tried AICP but with all other roms gapps + Magisk don't have to get flashed again, they remain in place :good::)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] MaximalRoot:
is the text to speech working for you with headphones under android 9 and SM-T580

I clean flash mine using only the normal options but ran into problems with the android 9 and SM T580 device.

question about this rom is google text to speech working on SM-T580 for you on this custom rom?

since google play books with read aloud engine option is not working correctly for me since when I tried both LineageOS 16.0 64bit 20190811 and LiquidRemix-10.0.11 rom ,when I tried to use text to speech which failed to work correctly from google play books. but the test voices worked fine from google text to speech options under settings.

I was not able to get the text to speech to playback sound both either my blutooth headphones and my normal plug in headphones, it selected the text but had no playback voice, it got stuck on the first line it hightlighted under google play books app. also one of these roms had the google camera app crash when trying to go to front camera mode, and the panoramic mode was not working either for me in the default google camera app. those where the only problems I had with android 9 versions listed above.

https://xdaforums.com/galaxy-tab-a/development/rom-t3945359/page7
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Casper Young:
Google Play Service
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Casper Young:
Odin3 v3.13.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] sinedoke:
Re-building the source

I'm trying to rebuild the source but keep getting this error

error: hardware/samsung/lineagehw/hidl/touch/Android.bp:15:1: "vendor.lineage.touch@1.0-service.samsung" depends on undefined module "vendor.lineage.touch@1.0"

What am I doing wrong?

Thank you
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Casper Young:
Just a guess

Read this it may help.

https://blog.arrowos.net/posts/compilation-guide
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] srgrusso:
Remove touch from your device.mk file in the device tree.

Edit: Are you using my sources?