Related
LIke the title says, this rom is built from the 4.4.2_r1 image and binaries from the Google repository (no changes or mods). This is pure AOSP KitKat.
This rom contains AOSP versions of Gallery2 and Camera2 which does not contain Google features such as HDR+ or PhotoSphere.
To install:
-TWRP or CWM recovery
-Factory reset, wipe cache and dalvik...if coming from a rom other than stock, wipe data too.
-Flash Rom
-Optional....flash "Photosphere Camera Addon Module" or other "Gapps packages"...only necessary for HDR+ and Photosphere
-Reboot and let install
-For HDR+ and Photosphere, flash "Photosphere Camera Addon Module" right after flashing rom (make sure its for 4.4.2) *see below for link
Rom Download.
aosp_hammerhead-kot49h MD5=34d9d60a4062d590f92746c977af9167
https://mega.co.nz/#!DJkD2QLB!OvMrzzp023VJYJSu-Y0wplRuL6Qlt3oDKNr6DtshoEw
Photosphere Camera Addon Module and all other Gapps-PA-Google apps
http://forum.xda-developers.com/showthread.php?t=2397942
To root-SuperSU 1.86
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
-Flash rom, let it install, place SuperSu into internal storage, reboot to recovery flash and reboot.
Thanks to Google for images and binaries
Thanks to TKruzze for PA-Google apps
Thanks to Chainfire for SuperSU
first... first time
will give it a shot.. lets go
Nice to have solid stock to fall back on. Thanks
Sent from my Nexus 5 using XDA Premium 4 mobile app
So what has been done with this besides just building from source? It's not clear whether or not gapps are added. How was the installer generated?
Gene Poole said:
So what has been done with this besides just building from source? It's not clear whether or not gapps are added. How was the installer generated?
Click to expand...
Click to collapse
Nothing. No gapps necessary.
What do you mean how was the installer generated???
Loving all this new development. Thanks for this
sent from my Hammerhead Nexus
rsa 329 said:
Nothing. No gapps necessary.
What do you mean how was the installer generated???
Click to expand...
Click to collapse
When I build, I get system.img, recovery.img, etc. No installer zip.
My builds seem to be missing some critical components or binary packages. That's why I asked if you added anything, or if you did like me and just followed build instructions here:
http://source.android.com/source/building.html
Gene Poole said:
When I build, I get system.img, recovery.img, etc. No installer zip.
My builds seem to be missing some critical components or binary packages. That's why I asked if you added anything, or if you did like me and just followed build instructions here:
http://source.android.com/source/building.html
Click to expand...
Click to collapse
There is better instruction than what you have there. Later, when I'm near my PC I will pm you and give you some links to better instruction.
Also, before I make I add the binaries from the repo.
Thanks, RSA, for the info in your PM. I got a compile that works, but only for 10-12 hours. After that, the cell provisioning breaks. "No Service" and nothing I can do short of a reboot brings it back. I thought it might be my build, so I installed yours. Same thing. It very well may be something broken on my part, like APN or something (I'm using the stock APNs from the AOSP source) since neither my build nor yours are working right. I needed my phone so I restored factory before I could dig through logcats.
Any ideas? Anyone else running this build fulltime? I'm AT&T if that matters.
Gene Poole said:
Thanks, RSA, for the info in your PM. I got a compile that works, but only for 10-12 hours. After that, the cell provisioning breaks. "No Service" and nothing I can do short of a reboot brings it back. I thought it might be my build, so I installed yours. Same thing. It very well may be something broken on my part, like APN or something (I'm using the stock APNs from the AOSP source) since neither my build nor yours are working right. I needed my phone so I restored factory before I could dig through logcats.
Any ideas? Anyone else running this build fulltime? I'm AT&T if that matters.
Click to expand...
Click to collapse
Interesting. I've been using a debloated version of my aosp for a while now with no problems. I ran this build for a couple weeks before switching and had no issues. Did you do a full wipe? How about ART, are you using art or dalvik? Have you tried your build after doing a system format? What service provider do you use?
Sorry for all the questions, just trying to get an idea of your situation.
I'm with AT&T. I decided to put this back on and wait for it to act up, then get a logcat and go from there. We'll see how it goes.
I've been running this for 3 days now without issue. The only change I made from my first attempt was to: install only the system partition (no recovery or boot); use my own boot image that has some things I need in it(1); and install the latest PA-GApps over it after installation. None of those changes should have negated the behavior I was seeing earlier, so I'm writing it off as odd coincidence.
1. I have modified the boot image to include stuff for mounting external storage to the USB port. This also includes a modified framework-res.apk and SystemUI.apk compiled on my system and inserted at install time to the system partition.
Gene Poole said:
I've been running this for 3 days now without issue. The only change I made from my first attempt was to: install only the system partition (no recovery or boot); use my own boot image that has some things I need in it(1); and install the latest PA-GApps over it after installation. None of those changes should have negated the behavior I was seeing earlier, so I'm writing it off as odd coincidence.
1. I have modified the boot image to include stuff for mounting external storage to the USB port. This also includes a modified framework-res.apk and SystemUI.apk compiled on my system and inserted at install time to the system partition.
Click to expand...
Click to collapse
Very cool! Glad to hear you got it working.
One issue I've just discovered is that the camera, when in video mode, records video files with a green line at the bottom (only visible on playback). I've researched this and found that AOSP source is missing an update in one of the files that makes up the libmmcamera_interface.so shared object. Copying the same filename from the factory image into the /system/lib directory, overwriting the existing file from AOSP build fixes the problem.
Again, no problem with your build; the problem seems to be that Android hasn't committed all their code the the AOSP tree.
rsa 329 said:
There is better instruction than what you have there. Later, when I'm near my PC I will pm you and give you some links to better instruction.
Also, before I make I add the binaries from the repo.
Click to expand...
Click to collapse
Hi RSA,
can you please share the instructions with me as well ? much appreciate your work..
What is encryption?
Basically, if you lose your phone and someone wipes /data on Recovery mode, the phone boots with NO lock screen, your apps will be gone but YOUR FOLDERS becomes exposed, that means Whatsapp history and media, pictures, downloads, documents. Stuff you wouldn't want in the hands of thieves/strangers.
Does it affect performance?
It does increase memory readings on every phone. But z7 Max doesn't show any lag at all!
Tested ROMs able to ENCRYPT:
- CM13 beta7 by PaoloW8
Tested ROMs able to DECRYPT:
- Ressurection Remix M by pchatzop
(if you wanna try for yourself, please first MAKE FULL BACKUP of your storage folders, files and appdata)
Requirements:
1. External SD Card
2. Crypto footer
3. CM13 beta7
4. Secure screen lock (PIN, Pattern, Password)
5. Pchatzop's Ressurecution Remix 5.7.4 and GApps 6 (IN SD CARD)
Steps:
0. Boot to TWRecoveryP
1. Open Advanced > Terminal
2. Enter
Code:
umount /dev/block/mmcblk0p23
3. Enter
Code:
e2fsck -f /dev/block/mmcblk0p23
4. (this will resize storage LOSING DATA) Enter
Code:
resize2fs -f /dev/block/mmcblk0p23 6896600
5. (second data error check just for safety) Enter
Code:
e2fsck -f /dev/block/mmcblk0p23
6. Back to TWRP home menu > Install > flash CM13 beta7 and the same GApps you're going to use on RR ROM. (let's avoid future FCs). Wipe Dalvik/Cache then reboot to system.
7. Wait for system bootup
8. Head to Settings > Lock Screen
9. Set a secure screen lock
10. Head back to Settings > Security > Encrypt phone > Encrypt
11. Enter password > Encrypt
12. Wait for a while depending on the size of your used storage.
13. Screen lock input shows upon boot then decrypt successfully THIS TIME ONLY, so head back to TWRP.
14. Have your SD card inserted with your RR ROM and GApps. As of November 24, TWRP builds for the Z7 Max CAN'T decrypt storage so ignore screen lock input and head straight to TWRP main screen > Wipe > Advanced Wipe > Check CACHE and SYSTEM only!!!
15. TWRP main menu > Install > flash your ROM and GApps > Reboot and decryption input should show and decrypt on every restart, even if you change your password.
NOTE: To Decrypt Data you have to head to TWRP > Wipe > Format Data > Type "yes", meaning you will LOSE ALL DATA TO DECRYPT so BACKUP first.
3njoy!
bump
Can not get this to work, in order to try my modified twrp. I have tried beta 2 and Rel V9,still stuck at bootscreen. Done the resize2fs, and got past the overlap error, but still stuck at the bad magic error. Will try the beta7 and see if something changes. Do you have the /data original block size in order to revert the resizing? Didn't occur to me to save it Well, there is always nubia updater tool if i get too OCD .
pchatzop said:
Can not get this to work, in order to try my modified twrp. I have tried beta 2 and Rel V9,still stuck at bootscreen. Done the resize2fs, and got past the overlap error, but still stuck at the bad magic error. Will try the beta7 and see if something changes. Do you have the /data original block size in order to revert the resizing? Didn't occur to me to save it Well, there is always nubia updater tool if i get too OCD .
Click to expand...
Click to collapse
Sorry about the delay, final exams.
My original block size is 6896635. This thread is outdated, my new reports makes some info here invalid
Keep up the good work
Thank for the report, i made some STUPID mistake and mixed the fstab.qcom arguments with the twrp fstab argument, which resulted at data being mounted at failsafe mode, thefore not using any of the footer arguments i used,resulting at the recovery not finding the footer. I revert the twrp fstab to the twrptest2 level while keeping the decryption libs intact. New build is up, give it a spin .
pchatzop said:
Thank for the report, i made some STUPID mistake and mixed the fstab.qcom arguments with the twrp fstab argument, which resulted at data being mounted at failsafe mode, thefore not using any of the footer arguments i used,resulting at the recovery not finding the footer. I revert the twrp fstab to the twrptest2 level while keeping the decryption libs intact. New build is up, give it a spin .
Click to expand...
Click to collapse
OK Twrptest4 formats and resizes correctly but doesn't decrypt yet
Kerneltest1 was better than kerneltest2. Flashed both after CM13 beta7, both kernels enabled f2fs support for Paolo's CM13, kernel1 encryption works on first tries on both ext4 and f2fs (on cm13, not RR), kernel2 always give bad superblock. I guess it is not something just in kernel at all but on RR or CM recent builds :?
As a Senior Member, you have more chance of getting response from @luca020400, @luk133, @Vidhanth, @Vatsal (they all contributed for moto G 2014 encryption on ROMs and TWRP) or @golden-guy, @Android-Andi (for s3 mini's)!
Keep up the good work!!
That is a great report, thank you so much! I will check the diffs between kernel 1 and 2, and will get you a twrp with the configuration of kernel 1 with decryption libs. F2fs encryption working is a great step forward. You are right about the second part, kernel does work, but seems like cyanogen source broke the encryption on later builds. I want to get this to work, and even incorporate it in my nougat builds, but twrp needs to work first! Does twrp find the footer but fail to decrypt, or does not find it at all?
---------- Post added 3rd December 2016 at 12:06 AM ---------- Previous post was 2nd December 2016 at 11:17 PM ----------
Just made a new test kernel, together with a new recovery with the above changes. Hope something changes now(at least the kernel should encrypt fine). I also have the qseecomd blob from cm13 beta7 in the folder, i have a feeling that if we replace that blob in the latest RR with a kernel that can encrypt in beta 7, encryption should work there too. Hope you can test and report back. Feeling we are closer to cracking(pun intended) this!
pchatzop said:
That is a great report, thank you so much! I will check the diffs between kernel 1 and 2, and will get you a twrp with the configuration of kernel 1 with decryption libs. F2fs encryption working is a great step forward. You are right about the second part, kernel does work, but seems like cyanogen source broke the encryption on later builds. I want to get this to work, and even incorporate it in my nougat builds, but twrp needs to work first! Does twrp find the footer but fail to decrypt, or does not find it at all?
---------- Post added 3rd December 2016 at 12:06 AM ---------- Previous post was 2nd December 2016 at 11:17 PM ----------
Just made a new test kernel, together with a new recovery with the above changes. Hope something changes now(at least the kernel should encrypt fine). I also have the qseecomd blob from cm13 beta7 in the folder, i have a feeling that if we replace that blob in the latest RR with a kernel that can encrypt in beta 7, encryption should work there too. Hope you can test and report back. Feeling we are closer to cracking(pun intended) this!
Click to expand...
Click to collapse
twrp does find the footer but fail to decrypt, even the Default Android password dont decrypt, I have the TWRP log at home if you want.
When I get home I'll download your new tries.
Thanks again, regards
Good, that means that either the service does not start, or that the zuk decryption libs are incompatible with z7max encryption model. The logs would be great. Meanwhile, im getting a new recovery with all decryption libs replaced with nubia counterparts, so that you can test both variants and see what is really stopping it from decrypting. Its in the folder too.
pchatzop said:
Good, that means that either the service does not start, or that the zuk decryption libs are incompatible with z7max encryption model. The logs would be great. Meanwhile, im getting a new recovery with all decryption libs replaced with nubia counterparts, so that you can test both variants and see what is really stopping it from decrypting. Its in the folder too.
Click to expand...
Click to collapse
Oh, I tested your RR N, it shows decryption screen lock input but after decryption it bootloops, mostly because the /data has Marshmallow stuff, so we need to fix TWRP first to wipe /data without wiping /media along :highfive:
Got a new twrp in the folder, plenty more testing for you! Is beta7 the last build encryption works? Because i can check the github diffs between beta7 and beta8 and see what i can revert to try getting it working again in the latest builds. That is if it is positively the last build that encryption works.
pchatzop said:
Got a new twrp in the folder, plenty more testing for you! Is beta7 the last build encryption works? Because i can check the github diffs between beta7 and beta8 and see what i can revert to try getting it working again in the latest builds. That is if it is positively the last build that encryption works.
Click to expand...
Click to collapse
Yes it is beta7! I tried beta8, V1.... with your boot.img3, encryption starts but gives the same unsuccessful screen from RR. Only beta7 reboots to decryption input.
Also, I have suspicions: as your TWRP set data partition to 6896631 which was originally 6896635, the password MUST BE OF 4 characters (6896631 - 6896635 = -4) for encryption to work?
Unfortunately, no TWRPtest could decrypt yet, it finds the crypto footer but fails. Attaching twrp log and encryption success logcat:
So boot3 works with beta7? I will sift through the logs, think this is a selinux issue introduced in beta8, i will get a new build and try it on my phone, maybe it will work this time.
I got a new twrp in the folder. Spend 5 hours trying to get RR-M to encrypt, tried selinux changes, test builds, replacing blobs with some from beta7, still not there. I could get it to begin encrypting sometimes by rebooting in safe mode with root disabled, but got the encryption unsuccessful screen. There is something that does not allow /data to get unmounted properly during the soft reboot for the encryption, and even when it does, it gets stuck in another point. Hopefully the new twrp will decrypt an already encrypted system.
Got a new twrp in the folder, my attempts at encrypting have failed so far, most i could get was here: "Cryptfs : Error writing crypto_blkdev /dev/block/dm-0 for f2fs inplace encrypt" where "12-31 13:32:09.246 237 306 I Cryptfs : Encrypting from block 0" wuld be on your log. I will attach it , and hopefully you can try to help me, since you have more exprerience with encryption. Hopefully something changes at the recovery front.
pchatzop said:
I got a new twrp in the folder. Spend 5 hours trying to get RR-M to encrypt, tried selinux changes, test builds, replacing blobs with some from beta7, still not there. I could get it to begin encrypting sometimes by rebooting in safe mode with root disabled, but got the encryption unsuccessful screen. There is something that does not allow /data to get unmounted properly during the soft reboot for the encryption, and even when it does, it gets stuck in another point. Hopefully the new twrp will decrypt an already encrypted system.
Click to expand...
Click to collapse
pchatzop said:
Got a new twrp in the folder, my attempts at encrypting have failed so far, most i could get was here: "Cryptfs : Error writing crypto_blkdev /dev/block/dm-0 for f2fs inplace encrypt" where "12-31 13:32:09.246 237 306 I Cryptfs : Encrypting from block 0" wuld be on your log. I will attach it , and hopefully you can try to help me, since you have more exprerience with encryption. Hopefully something changes at the recovery front.
Click to expand...
Click to collapse
Hey, thanks and sorry for taking your time! Did you try a password/PIN/Pattern 4-character/digits/dots long?
TWRPtest8 doesn't decrypt yet
Could you please make your TWRP "Copy Log to SD" save the log in the external SD when available? It is always trying to save in /data/media, but as it is encrypted, the file goes nowhere. So I always have to format, save the log and re-encrypt :highfive:
Keep up the good work!:highfive:
OFFICAL TWRP RELEASED, this thread is no longer active. 3-30-2018
https://twrp.me/motorola/motorolamotox4.html
---
UNOFFICIAL BUILDS -- USE AT YOUR OWN RISK AND KNOW HOW TO GET YOURSELF OUT OF TROUBLE IF IT ARISES. I ASSUME NO RESPONSIBILITY FOR YOUR BROKEN THINGS.
UPDATED 01-11-2018
There are now 7.1 based and 8.0 based builds. Obviously, be careful to select the proper download. While I don't think flashing/booting the wrong one would permanently brick the device, let's not find out
For now I will not be attempting to make data decryption work. It is REQUIRED that you unencrypt your device by formatting userdata, so back up your stuff first.
IMPORTANT NOTES: TWRP for OREO is a bit of a pain as it currently requires manually editing your fstab. I have tried to automate this process, but it breaks stuff. So just be aware before you begin that it is a rather time consuming process.
If you make any change to your boot partition after flashing SuperSU, you will need to reflash it or you will get a bootloop.
8.0 OREO TWRP INSTALLATION:
OREO SEEMS VERY FINICKY AND DOES NOT LIKE CHANGES TO ITS FILESYSTEM -- BE PREPARED TO REFLASH STOCK.
0. FLASH OREO FACTORY IMAGE (may work otherwise, but we should be starting from fresh stock here)
1. Download FASTBOOT BOOTABLE TWRP for 8.0/OREO below
2. Download SuperSU 2.82 SR5 below
3. Move SuperSU to external SD or USB OTG
4. From bootloader, fasboot BOOT TWRP
5. Flash SuperSU (note: do not format /data now... not necessary and will cause errors on boot)
6. Reboot system
7. With any root file editor/text editor (Amaze, Total Commander, etc) open /system/vendor/etc/fstab.qcom as a text file for editing.
8. At the end of the /data partition entry, delete "fileencryption=ice" and replace it with "encryptable=footer".
9. Save fstab.qcom (and make sure it is actually saved properly!)
10. Reboot to bootloader and fasboot BOOT TWRP
11. Go to Wipe, hit the FORMAT DATA button, and type "yes" to format /data. This will erase your data, obviously:silly:
12. Reboot system (should now be unencrypted, verify in Settings>Security or by booting TWRP and checking /data with File Manager.
If you later choose to flash TWRP (not the bootable we used here!), you may need to flash SuperSU again to avoid bootloops.
7.1.1 NOUGAT TWRP INSTALLATION:
1. Download current TWRP for 7.1.1 build below
2. Download SuperSU 2.85 SR5 (https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
3. Move SuperSU to your external Micro SD card.
4. Fastboot flash the TWRP image.
5. Reboot to TWRP.
6. FORMAT data (not wipe...use the "FORMAT DATA" button and type "yes". OBVIOUSLY THIS WILL ERASE YOUR DATA)
7. Install SuperSU 2.85 SR5
8. Reboot to system (it WILL bootloop a couple times...don't panic!) and confirm that device is unencrypted by checking that SETTINGS>SECURITY>ENCRYPTION now prompts "encrypt" (don't do it).
DOWNLOADS:
TWRP FOR 7.1.1 (Nougat) DOWNLOAD: https://drive.google.com/open?id=1Et-AQgCNx7WDAwzihlI51euUa2ixKHEP
TWRP FOR 8.0 (Oreo) DOWNLOAD: https://drive.google.com/open?id=1WcVS_3rloF7jxPulj_jKxfsp3zy5pB5N
FASTBOOT BOOTABLE TWRP IMAGE (OREO BASED): https://drive.google.com/open?id=12ClviqtEjtflB63UQ1CZQNKEqkprBO0u **For temporary TWRP boot using "fastboot boot". Do not flash or you will be stuck in recovery!**
DEVICE TREE: https://github.com/mightysween/android_device_motorola_payton (NEEDS TO BE UPDATED WITH OREO BRANCH)
changelog:
BETA4
-reverted to 3.2.0 for current build (release candidate rebased to 3.2.1).
-fixed "format data" button
-finalized fstab for OTG/SD/INTERNAL mounting
-target is now UNENCRYPTED devices only (/data decrypt will not be fixed)
BETA3
-Rebased to TWRP 3.2.1
-USB OTG working
-all partitions mounting correctly
-considered working except for decrypt and MTP/ADB
BETA2
-fixed internal storage mount
BETA1
- updated source to TWRP 3.2.0
ALPHA3
- Fixed USB mounting (adb/mtp still nonfunctional) BROKEN IN BETA1
ALPHA2
- SD Card fixed
ALPHA1
- /system is now properly mounted.
- now plays nice with our working root method.
- ramdisk is patched to prevent first boot encryption once /data is decrypted (now requires flashable ZIP)
NOT WORKING:
adb/mtp/sideload
/data decryption (abandoned -- /data access requires unencryption)
CREDITS: @kraatus90 for kernel fix, @Chainfire for SuperSU, @jcadduono for no-verity-opt-encrypt scripts.
---
Thanks so much for all your work!
hi,
you said this is really unstable and could brick the device easily. however, you seem to be testing and experimenting with your device a lot, so i'd like to ask if you have any particual unbrick method that you use when something goes wrong.. like, a via fastboot flashable image or something simmilar...?
thanks for your work!
Thanks for you work. If you have any unbrick methods pls tell.appreciated your work ?
I am not going to provide step by step "unbrick" methods, because until the partitioning is properly set up, TWRP has potential access to things that can not be fixed.
Again, this is still highly experimental.
All that said, my entire process to protect any device remains the same: Have a backup for every partition you will be testing, make as few changes as possible at a time, test boot images before flashing (fastboot boot), and test restore methods frequently (flashing back to stock or backups), and don't do anything unless you are highly certain of the outcome.
By those standards, there is nothing to gain by installing TWRP right now, as its basic function (install/backup/restore) is not set up yet.
Found the BoardConfig flag to enable FBE (TW_INCLUDE_CRYPTO_FBE := true) but do not have the lib it is dependent on (libe4crypt) and I don't see it anywhere yet...
For reference (not sure this is most current, but it demonstrates the process)
https://github.com/nijel8/TWRP/commit/bd7492de28963b7e74e8e5d3f17ec9a5a287d9c3
I have confirmed that FBE support is present in the source, dependent on this missing module... so need to figure out where/how to enable it.
It is possible that this entire process is specific to only certain devices (i.e. Pixel, Nexus). If this is the case, we may be stuck at this point for awhile.
Obvious workaround is to not be encrypted to begin with -- but that isn't a "solution".
mightysween said:
It is possible that this entire process is specific to only certain devices (i.e. Pixel, Nexus). If this is the case, we may be stuck at this point for awhile.
Click to expand...
Click to collapse
This appears to be the case, unfortunately. Seems that the TWRP FBE support was built specifically for the Google implementation of FBE which was merged into kernel sources for Nexus and Pixel. Not even using the qseecomd I assumed it was... will remove on next build.
Info on FBE:
https://source.android.com/security/encryption/file-based
Will be testing options to disable forced encryption, and if necessary dm-verity...
Anyone who wants to dig through kernel for related flags and props, it would be greatly appreciated!
Hey, where did the big "format data" button go in TWRP? Is that optional on compile... can't find a flag for it...
Making good progress this morning.
Seem to have a build with properly decrypted /system, and working SD Card. I also have patched the boot.img to disable forced encryption on the first boot. But now, I can not find a safe way to fully format (not "wipe") the /data partition. As mentioned in the previous post, the "FORMAT DATA" button is missing. The fastboot command "fastboot format userdata" returns an error that it does not support RAW format.
Need to figure out why this is happening... and once I do, I believe I can reformat /data without encryption and then will have an almost fully working TWRP build. Obviously, the ideal solution would be to have TWRP work out of the gate with an encrypted /data, but until then this is going to be our best option.
Will post an updated test build in the OP soon.... needs further testing before I would recommend non-expert users to try it.
Getting very close now!
UPDATE: ADDED NEW BUILD TO OP
---
Also, just occurred to me that the ramdisk will need to be patched every time, so now that I have SD card support will be testing some of the existing flashable ZIPs out there that are designed specificially to prevent first-boot encryption and/or disable dm-verity.
---
mightysween said:
Hey, where did the big "format data" button go in TWRP? Is that optional on compile... can't find a flag for it...
Click to expand...
Click to collapse
This is really the only hold up... I changed the partition from 'Advanced Wipe", but as expected, it was still encrypted on boot as it doesn't actually format the footer where encryption is stored. I can't figure out where that darn "FORMAT DATA" button ran off to, and that is exactly what we need here.
mightysween said:
This is really the only hold up... I changed the partition from 'Advanced Wipe", but as expected, it was still encrypted on boot as it doesn't actually format the footer where encryption is stored. I can't figure out where that darn "FORMAT DATA" button ran off to, and that is exactly what we need here.
Click to expand...
Click to collapse
I don't know how to help except to say that using TWRP 3.1.0-MOD_1 with my XT1254 (DROID Turbo), when you go to wipe it has two buttons --- one on the left for Advanced Wipe and Format Data on the right.
johnjingle said:
I don't know how to help except to say that using TWRP 3.1.0-MOD_1 with my XT1254 (DROID Turbo), when you go to wipe it has two buttons --- one on the left for Advanced Wipe and Format Data on the right.
Click to expand...
Click to collapse
I have 3.1.1-0 (same version I am building here) on several other devices, and the button is there. It has to be triggered by something during compile, but I can't figure it out. Driving me nuts
Looking through TWRP source, and can find actions for every other button (wipe, backup, restore, install, etc) but not for format. Hmm.
I posted over on an old but semi-active TWRP flags thread, maybe someone will have some insight.
Wondering if I make a stock boot image without the encryption tag in fstab, and then wipe data and reboot... then flash my image. That may make it so the data partition is never encrypted in the first place and allow TWRP to work.
But that is an ugly, non-user friendly fix. Why can't we just format /data?
---
Final update for today... this seems to be a compile issue, which is a good thing. I tried to manually decrypt /data from the TWRP command line, and got this:
No crypto support was compiled into this build.
Click to expand...
Click to collapse
So, I must be missing something in boardconfig still... and maybe need to set up a small proprietary vendor folder with the necessary libs
mightysween said:
Final update for today... this seems to be a compile issue, which is a good thing. I tried to manually decrypt /data from the TWRP command line, and got this:
So, I must be missing something in boardconfig still... and maybe need to set up a small proprietary vendor folder with the necessary libs
Click to expand...
Click to collapse
Thanks for doing all of this! I wish I had the time and knowledge to help.
Had a few PM's checking on TWRP status, so an update.
The good news is that the X4 is using Qualcomm based decryption for /data... the bad news is that most if it seems to be closed source. This will take some time for me to figure out, but I have already made some progress by sifting through logs.
Right now, I am trying to find a device with similar decrypt scheme to have some more guidance on the process.
mightysween said:
Had a few PM's checking on TWRP status, so an update.
The good news is that the X4 is using Qualcomm based decryption for /data... the bad news is that most if it seems to be closed source. This will take some time for me to figure out, but I have already made some progress by sifting through logs.
Right now, I am trying to find a device with similar decrypt scheme to have some more guidance on the process.
Click to expand...
Click to collapse
dont know all about these things but maybe xiaomi mi a1 twrp can help as it is also using same a/b partition. and twrp is already there for it
vivek638 said:
dont know all about these things but maybe xiaomi mi a1 twrp can help as it is also using same a/b partition. and twrp is already there for it
Click to expand...
Click to collapse
Thanks, the Mi A1 is one of the devices I have been comparing to, and has been quite helpful.
mightysween said:
Thanks, the Mi A1 is one of the devices I have been comparing to, and has been quite helpful.
Click to expand...
Click to collapse
Keep searching. wish i could have helped but dont know anything about compiling n all..
I'm not much of a programmer, but I can look through the files. Is there anything in particular we're searching for?
LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
/ * Your warranty is now void. Knox 0x1.
/* We are not responsible for bricked devices, dead SD cards, lost data due to failed backups, etc, etc. flash at your own risk
*/
How to flash this ROM:
1. Download the zip file.
2. Make sure this zip file is saved to your device (I prefer transferring to sd card to allow for full wipe of data on tablet).
3. If you want Google Play functionality, download OpenGApps (link below). (optional)
4. Reboot into TWRP (Volume Up + Home + Power or Advanced Restart).
5. Make a backup (optional).
6. Wipe System, Data, Cache, and Dalvik Cache partitions with Advanced Wipe. (I like wiping internal data too, do NOT wipe SD Card!)
7. Flash the ROM you just downloaded.
8. Flash OpenGApps ARM for Android 9.0 if you want Google services (optional).
9. If you want root, flash Magisk.
10. Reboot and proceed normally with installation.
11. ????
12. Profit!
Download links:
SM-T350
OpenGApps ARM 9.0 (I use pico)
Source code:
LineageOS
iesous-kurios (forked from LineageOS, and rest of the developers mentioned in the following Credits) on Github
Galaxy MSM-8916
Credits:
The LineageOS Team (and specifically haggertk )
elginsk8r
VirsysElectron
Nubianprince
And awesome tester : retiredtab (saved me sooo much time and has been huge asset in getting bugs fixed)
And of course the Galaxy MSM-8916 team for all of their hard work on our device specific code.
Version Information:
ROM OS Version: Android 9.0 Pie
Known Bugs:
Static while playing mp3s with stock music player (download vlc player to play mp3 files)
Overwhelming sense to brag that your old tablet has newer version of Android on it than a lot of people's expensive phones.
All other functions seem to be working fine. Please report bugs with logcat. I am just starting out on being able to troubleshoot bugs and make edits to code to fix problems, so a majority of bugs will be fixed by the official devs and maintainers of Lineage but I'm trying to learn how to help out too and you have to start somewhere, right?
1st
2nd
3rd
Looking forward to this, thank you!
Thanks for the nice ROM, older bugs are gone! Runs very smoothly with frequent lock-ups.
Issues:
Some apps from Google Play Store are not available saying "not compatible" when you can install their APKs (i.e. Instagram...etc.)
Lockups are annoying
Jfuginay,
Thanks for compiling this ROM. Your work is appreciated.
On my SM-T350, I get the following message when trying to install the 16.0 ROM
updater process ended with error: 7
error installing zip file /sdcard/Download/lineage-16.0-20190221-UNOFFICIAL-gt58wifi.zip
I will check tomorrow to see if there is a newer TWRP that can work with the updater script. I saw in another thread that the SM-T550 updater script is failing because TWRP can't report the model number.
I do need external audio working. I see that SM-T550 which is the bigger version of this A tablet does have audio working as per
https://forum.xda-developers.com/showpost.php?p=78720468&postcount=22
Perhaps there is something in that SM-T550 code that we can use to help with the SM-T350.
retiredtab said:
On my SM-T350, I get the following message when trying to install the 16.0 ROM
updater process ended with error: 7
error installing zip file /sdcard/Download/lineage-16.0-20190221-UNOFFICIAL-gt58wifi.zip
Click to expand...
Click to collapse
Okay the above error was due to TWRP version 3.1.0. I upgraded to 3.2.1 and now the updater-script installs 16.0 onto my SM-T350.
I found TWRP 3.2.1 at
https://androidfilehost.com/?fid=962339331458992706
TWRP-3.2.1-lineage-15.1_j1_20180418_gt58wifi.tar
for the Samsung Galaxy Tab A 8.0, by Austcool Walker
MD5 = 6455c0cfa01b9f71cf575c553df18733
---------- Post added at 11:55 AM ---------- Previous post was at 11:52 AM ----------
I also noticed a newer build today (dated 20190223).
External audio still doesn't work. Headphone jack works.
---------- Post added at 12:11 PM ---------- Previous post was at 11:55 AM ----------
Here is the SM-T550 thread where virsys got external audio working.
https://forum.xda-developers.com/showpost.php?p=78972270&postcount=70
I'm looking through the SM-T550 commits, but unsure what might be needed for the SM-T350?
The most obvious difference between
https://github.com/Galaxy-MSM8916/android_device_samsung_gt510wifi/tree/lineage-16.0
and
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/tree/lineage-16.0
is the entire configs folder in the SM-T350 code.
I also found
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/tree/lineage-16.0
retiredtab said:
Okay the above error was due to TWRP version 3.1.0. I upgraded to 3.2.1 and now the updater-script installs 16.0 onto my SM-T350.
I found TWRP 3.2.1 at
https://androidfilehost.com/?fid=962339331458992706
TWRP-3.2.1-lineage-15.1_j1_20180418_gt58wifi.tar
for the Samsung Galaxy Tab A 8.0, by Austcool Walker
MD5 = 6455c0cfa01b9f71cf575c553df18733
---------- Post added at 11:55 AM ---------- Previous post was at 11:52 AM ----------
I also noticed a newer build today (dated 20190223).
External audio still doesn't work. Headphone jack works.
---------- Post added at 12:11 PM ---------- Previous post was at 11:55 AM ----------
Here is the SM-T550 thread where virsys got external audio working.
https://forum.xda-developers.com/showpost.php?p=78972270&postcount=70
I'm looking through the SM-T550 commits, but unsure what might be needed for the SM-T350?
The most obvious difference between
https://github.com/Galaxy-MSM8916/android_device_samsung_gt510wifi/tree/lineage-16.0
and
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/tree/lineage-16.0
is the entire configs folder in the SM-T350 code.
I also found
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/tree/lineage-16.0
Click to expand...
Click to collapse
Glad you got it to boot.
I noticed that missing config folder too, so I just added that to my build directory and am compiling that now to test it out. I didn't add the camera files, since it is only bluetooth and speaker I'm trying to troubleshoot. Don't think the camera is having problems, but honestly haven't tried it out yet.
I noticed the missing config folder when checking out the device.mk file for each device. I added the links to the config folder in the device.mk file and added the bluetooth and sound folders from config file to my build directory, so I'm hoping once that compiles it will fix our problems.
Will do a dirty flash first, then if it still isn't working, I'll do full wipe and test it out. If it boots up and fixes anything I'll upload it for people do download, if the same problems persist I won't bother uploading the new build.
One of my links that I found got messed up.
https://github.com/VirsysElectron/android_vendor_samsung_gt510wifi
In the above, virsys does some OSS-audio cleanup for 16.0
---------- Post added at 04:25 PM ---------- Previous post was at 04:24 PM ----------
Regarding the stock 16.0 camera, I get the following error message
Camera error
Can't connect to the camera
If I download open camera from play store, the back camera gives an error message
"failed to start camera preview"
However, the front facing camera shows a preview, but can't save the picture/photo
---------- Post added at 04:29 PM ---------- Previous post was at 04:25 PM ----------
Also had a complete reboot while using Clash Royale game. I hit the news tab and the tablet completely rebooted.
I will try to reproduce, if I can, and get a logcat.
Playing Clash Royale seems okay, but I have to use the headphone jack vs external audio to get sound.
My SM-T350 is a completely fresh install with only gapps pico. Nothing else.
---------- Post added at 04:59 PM ---------- Previous post was at 04:29 PM ----------
Looking at the commit history between the SM-T350 and SM-T550, it looks like deadman96385 didn't add the config/audio files for the SM-T350, but did for the SM-T550 on April 18, 2018
SM-T350
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/commits/lineage-16.0
SM-T550
https://github.com/Galaxy-MSM8916/android_device_samsung_gt510wifi/commits/lineage-16.0
I wonder if the non working external audio is due to missing config folder?
retiredtab said:
One of my links that I found got messed up.
https://github.com/VirsysElectron/android_vendor_samsung_gt510wifi
In the above, virsys does some OSS-audio cleanup for 16.0
---------- Post added at 04:25 PM ---------- Previous post was at 04:24 PM ----------
Regarding the stock 16.0 camera, I get the following error message
Camera error
Can't connect to the camera
If I download open camera from play store, the back camera gives an error message
"failed to start camera preview"
However, the front facing camera shows a preview, but can't save the picture/photo
---------- Post added at 04:29 PM ---------- Previous post was at 04:25 PM ----------
Also had a complete reboot while using Clash Royale game. I hit the news tab and the tablet completely rebooted.
I will try to reproduce, if I can, and get a logcat.
Playing Clash Royale seems okay, but I have to use the headphone jack vs external audio to get sound.
My SM-T350 is a completely fresh install with only gapps pico. Nothing else.
---------- Post added at 04:59 PM ---------- Previous post was at 04:29 PM ----------
Looking at the commit history between the SM-T350 and SM-T550, it looks like deadman96385 didn't add the config/audio files for the SM-T350, but did for the SM-T550 on April 18, 2018
SM-T350
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/commits/lineage-16.0
SM-T550
https://github.com/Galaxy-MSM8916/android_device_samsung_gt510wifi/commits/lineage-16.0
I wonder if the non working external audio is due to missing config folder?
Click to expand...
Click to collapse
I'm hoping it's those config files. I did a build with them in but I'm not sure they were included because of my ccache being enabled. I'm not 100 percent convinced that ccache can tell the difference between slightly modified files well enough to know to include the changed files in new build, so I cleared out my ccache files and ran make clobber and am building fresh right now with those config files in there.
Will do full wipe and flash this and report back if it made any difference.
Adding those config files didn't fix anything. Found several differences in some proprietary.mk files so attempting to see if any of those do the trick. New build compiling now. Will probably need to disable ccache and do make clobber to clear directory so I'll probably let it build over night while I sleep.
Let's hope I wake up to a fixed ROM !
Jfuginay said:
Adding those config files didn't fix anything.
Click to expand...
Click to collapse
Darn, I was hoping the config would fix it.
I left a message in the SM-T550 thread asking virsys what was done to fix the external audio because it's not obvious to me where the commit is that fixed it.
In this post
https://forum.xda-developers.com/showpost.php?p=78170903&postcount=9
dated Nov 15, 2018 virsys says "Audio is working now".
At github
https://github.com/VirsysElectron/android_vendor_samsung_gt510wifi/commits/lineage-16.0
there is a commit for Nov 16, 2018 entitled
Cleanup for OSS-audio and improved lineage-16.0 compatibility
I wonder if this commit fixed the external audio?
Just out of curiousity, how are you building this ROM? Locally or on some clould computer?
Another idea/suggestion?
At
https://github.com/Galaxy-MSM8916/a...8wifi/blob/lineage-16.0/proprietary-files.txt
it says the proprietary files are from (line 1)
# Samsung Package Version T550XXU1CQL5_T550OJV1CQK3_TUR (unless otherwise specified and/or tagged)
The SM-T550 has 2 external speakers while the SM-T350 only has 1. I wonder if we have to grab the proprietary files from a SM-T350. Maybe the drivers from the SM-T350 know how to work with just 1 speaker?
retiredtab said:
Another idea/suggestion?
At
https://github.com/Galaxy-MSM8916/a...8wifi/blob/lineage-16.0/proprietary-files.txt
it says the proprietary files are from (line 1)
# Samsung Package Version T550XXU1CQL5_T550OJV1CQK3_TUR (unless otherwise specified and/or tagged)
The SM-T550 has 2 external speakers while the SM-T350 only has 1. I wonder if we have to grab the proprietary files from a SM-T350. Maybe the drivers from the SM-T350 know how to work with just 1 speaker?
Click to expand...
Click to collapse
I'll check out a working 14.1 ROM and see if it has specific proprietary files there which differ from what we are using now.
Virsys responded back on how he/she got the SM-T550 external audio working. See
https://forum.xda-developers.com/showpost.php?p=78978788&postcount=74
"I've fixed the whole audio framework by editing and importing my own mixer_paths.xml to /system/etc"
I wonder if we can download his SM-T550 ROM image, extract that mixer_paths.xml file to see what changed?
So I downloaded the SM-T550 code and looked at the
/system/vendor/etc
directory.
There are 28 files there. In the SM-T350 /system/vendor/etc, there are only 27 files.
The additional file in SM-T550 is called audio_platform_info.xml.
It has definitions for speaker out. I'm not sure of all the definitions or how it's linked yet? I don't know if this file has to be part of the actual rom compilation process or it gets read at boot/runtime.
In addition, there have been additional entries put into the mixer_paths.xml file in the 550 that virsys referred to.
In the SM-T550 /system/etc directory, there 3 additional XML files named
A05QF_sr544_module_info.xml, B05QF_sr544_module_info.xml and C05QF_sr544_module_info.xml.
Not sure if these files are needed or not?
retiredtab said:
So I downloaded the SM-T550 code and looked at the
/system/vendor/etc
directory.
There are 28 files there. In the SM-T350 /system/vendor/etc, there are only 27 files.
The additional file in SM-T550 is called audio_platform_info.xml.
It has definitions for speaker out. I'm not sure of all the definitions or how it's linked yet? I don't know if this file has to be part of the actual rom compilation process or it gets read at boot/runtime.
In addition, there have been additional entries put into the mixer_paths.xml file in the 550 that virsys referred to.
In the SM-T550 /system/etc directory, there 3 additional XML files named
A05QF_sr544_module_info.xml, B05QF_sr544_module_info.xml and C05QF_sr544_module_info.xml.
Not sure if these files are needed or not?
Click to expand...
Click to collapse
Thanks for all the ground work, gives me a good place to look into tonight when I get home from a meeting and have some time to tinker with the code.
K, I looked through a lot of proprietary code for both the gt58 and 511, and hopefully found all the discrepancies. Added over 20 files and lines of code to gt58 proprietary folders and renamed one file to match the dependency in another file.
Compiling now, so cross your fingers that it fixes our sound!
Are your changes up on github?
https://github.com/jfuginay
I'm newish to github and just learning how to navigate and look around.
What I find confusing is the seemingly incredible amount of layers of abstraction in defining the speakers. That is, A->B, B->C, C->D, D->E, E->F, F->G. Anything missing is enough to break it.
I understand why the layers are required, but without a flow chart or visualization of how these things work, it's difficult to follow all the necessary definitions and files needed.
I also have noticed some of the people using github have no documentation on why the code change was required. The changes are there, but why? Was it because something was broken? Was it because it wasn't defined properly in the first place? Was it because there was a potential security problem?
If you have any URL resources that would help explain some of this, I would appreciate some pointers.
crDroid 6.2 ROM 15-01-2020
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA before!
Make sure you have a custom recovery installed (TWRP is the preferred recovery. [I'm not using Fox recovery, I'm not going to give you advice.])
Boot into recovery
Wipe data, cache partitions to clean install. Wipe dalvik, cache to update previous crDroid.
(If your /data partition secured, maybe need format /data if you want to use this ROM.)
Flash Rom in TWRP (sideload or copy any storage)
Flash OpenGapps (Optional) [I'm not using GAPPS, I'm not going to give you advice.]
Flash Magisk Root (Optional) [I'm not using Magisk, I'm not going to give you advice.]
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 1 minute.
DOWNLOAD SF
DOWNLOAD AD​
All ROMs here: LINK
Known issues: don't know
*
Screenshots: LINK
OS source: LINK Many thanks to adi153!
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.18.140 (not my work)
ROM info: Q10 Lineage-17.1, system_root partition, Android quota removed (easier to go back to earlier 7.x-9.x ROMs).
If you have previously used Android 9.x or 10.x ROM which has a quota set on the data partition, you can remove the quota in TWRP, and not need format the data partition (this method tested, working was for me, but no guarantee for by all means)
commands:
Code:
tune2fs -O ^quota /dev/block/bootdevice/by-name/userdata
tune2fs -Q ^usrquota,^grpquota /dev/block/bootdevice/by-name/userdata
If you then use a ROM that configures quota (fstab.qcom), you can start over, if do not want quota. Or cleaning from fstab: "quota".
Created 24-12-2019 6.0 version
Last Updated 15-01-2020 6.2 (build3)
I am not aware that it contains malicious code in the ROM, I have never put it in. This is a ported ROM, all its elements come from the Internet.
You're welcome.
New build 15.01.2020, & many changes to the system. I'd like to get feedback on whether VOLTE is working? Thanks.
SYS update V1 out: 14-01-2020
Something wrong with the system updates, I moved it to the test directory.
Nice
Wow, a new rom... Thanks szanalmas, will give feedback after testing it
@szanalmas
Edit: Already tested your rom, so stable and smooth...
But found some small bug (doesn't really matter anyway but you may need know):
-At first boot/crdroid setup wizard, email exchange request permission but when i grant it permission manager crash (but back normal after that)
-When i change the hardware button function to screenshot... The Setting app will crash and back to main menu
Just that, still looking for other
Big thanks again for this nice rom
(Sorry for my bad english :v)
@szanalmas thanks ...for stable ROM.
---------- Post added at 04:18 AM ---------- Previous post was at 04:00 AM ----------
From long time i was waiting for stable ROM. Thanks for your hard work.
@szanalmas thanks for make stable ROM :good:
while there are no bugs,
if there are bugs
I'll tell you later
thanks man i like crdroid
rom stable smooth did not find any bug after 2 hours use
Fadly357 said:
But found some small bug (doesn't really matter anyway but you may need know):
-At first boot/crdroid setup wizard, email exchange request permission but when i grant it permission manager crash (but back normal after that)
-When i change the hardware button function to screenshot... The Setting app will crash and back to main menu
Click to expand...
Click to collapse
Thanks for the feedback!
I didn't know about the first bug, probably because I have always denied email permissions in the wizard. I have bad habits!
I knew about the second bug, some of the function settings on the buttons don't work.
Unfortunately, these bugs are in the official ROM, but I think they will be fixed over time.
And of course, the SD card camera and gallery permission bugs have remained, but the solution is to use internal storage for the time being.
szanalmas said:
Thanks for the feedback!
I didn't know about the first bug, probably because I have always denied email permissions in the wizard. I have bad habits!
I knew about the second bug, some of the function settings on the buttons don't work.
Unfortunately, these bugs are in the official ROM, but I think they will be fixed over time.
And of course, the SD card camera and gallery permission bugs have remained, but the solution is to use internal storage for the time being.
Click to expand...
Click to collapse
Okay, will tell you as soon as possible if i found other
could you teach me rom build? i wanna learn and help
@szanalmas
About your ported TWRP, can you install magisk? When i use your TWRP to install magisk, the magisk installation failed, says it can mount vendor which is same as cust, right?
viethoang18 said:
could you teach me rom build? i wanna learn and help
Click to expand...
Click to collapse
Sorry I can't give you guidance. I'm not building ROM, I'm just porting. If you really want to build ROM, I recommend the ViperOS developers, this was the only Official build for this phone (7.1.2). Building a ROM requires 3 things, the kernel, vendor, and AOSP. Since phone manufacturers largely do not make their source code public, their construction is tremendously laborious and time consuming.
If you want to port, it is highly recommended that you know Linux, which is quite a bit of time and energy. Actually, you need to learn the basics of linux for Android, but at least to the point where you can already interpret log error messages.
I don't know if you use linux, if you don't and you want to start with it, install linux, configure it well, and compile a linux kernel for ugglite, which starts with ROM 10. If you want to go hard, thoroughly, and deeper, do it all without installing a linux graphical interface. I don't really know how much time it takes to easily manage Linux. How to port Android 10 on windows I don't know, but I think it's not easy.
And on top of that, Android has some specific changes that are different from the Linux system, so you also have to get to know Android so.
And now we're just about to boot on Linux based Android, on the DalvikVM running applications is another world with lots of Java code.
For all this, there is no guide to doing this or that, you need to apply knowledge in a complex way.
I only do this on a hobby level.
Fadly357 said:
@szanalmas
About your ported TWRP, can you install magisk? When i use your TWRP to install magisk, the magisk installation failed, says it can mount vendor which is same as cust, right?
Click to expand...
Click to collapse
I once used the magisk in TWRP but not this ROM. It worked for some.
But I didn't write in my post on my TWRP either now.
(I don't use magisk now.)
Use Canary: LINK
Or whatever.
szanalmas said:
Sorry I can't give you guidance. I'm not building ROM, I'm just porting. If you really want to build ROM, I recommend the ViperOS developers, this was the only Official build for this phone (7.1.2). Building a ROM requires 3 things, the kernel, vendor, and AOSP. Since phone manufacturers largely do not make their source code public, their construction is tremendously laborious and time consuming.
If you want to port, it is highly recommended that you know Linux, which is quite a bit of time and energy. Actually, you need to learn the basics of linux for Android, but at least to the point where you can already interpret log error messages.
I don't know if you use linux, if you don't and you want to start with it, install linux, configure it well, and compile a linux kernel for ugglite, which starts with ROM 10. If you want to go hard, thoroughly, and deeper, do it all without installing a linux graphical interface. I don't really know how much time it takes to easily manage Linux. How to port Android 10 on windows I don't know, but I think it's not easy.
And on top of that, Android has some specific changes that are different from the Linux system, so you also have to get to know Android so.
And now we're just about to boot on Linux based Android, on the DalvikVM running applications is another world with lots of Java code.
For all this, there is no guide to doing this or that, you need to apply knowledge in a complex way.
I only do this on a hobby level.
Click to expand...
Click to collapse
can i use Unbutu wls on windows ?
@szanalmas I flashed this ROM.
ULTRA SMOOTH... NO SERIOUS BUG, SOMETIMES AUTO BRIGHTNESS RESPONSE SLOWLY. Suddenly high brightness automatically. Another issue with attached sd card asking for format.
"Issue with sandisk SD Card"
Its for daily use is ok.
bug, when enabling ambient display d2tw stopped not wroking after disable ambient dt2w work again
Thank you very much feedbacks and thanks to everyone! :good:
Call volume on speaker is very high by default
@szanalmas Call volume on speaker is very high by default. Please set lower level by default. I hope in new build it willbe resolve.
Thanks...
ahmedhelmy71 said:
bug, when enabling ambient display d2tw stopped not wroking after disable ambient dt2w work again
Click to expand...
Click to collapse
This is what LINK is all about, and I still hold that the double-tap feature cannot be used for two things at once. What's interesting is that I can't find the ambient display double-tap menu option, and there's a separate one in Havoc ambient settings.
This is also an Official bug unfortunately.
*
cpglbitm said:
@szanalmas I flashed this ROM.
ULTRA SMOOTH... NO SERIOUS BUG, SOMETIMES AUTO BRIGHTNESS RESPONSE SLOWLY. Suddenly high brightness automatically. Another issue with attached sd card asking for format.
"Issue with sandisk SD Card"
Its for daily use is ok.
Click to expand...
Click to collapse
The SD card problem is very-very interesting.
What filesystem is in sd card?
Could you send us a logcat digest right after the phone is started?
Code:
adb logcat | grep vold > sdcardproblem.txt
viethoang18 said:
can i use Unbutu wls on windows ?
Click to expand...
Click to collapse
I don't know. I haven't used Windows for years, sorry.