Related
I have gone through several applications from the MR release and optimized the images inside in an attempt to free up memory and/or speed things up a bit.
Some things benefited more than others, for example, Rosie.apk has lost around 7MB.
This will only work on software version 1.56.651.2. Don't know what version you have? Go into your settings -> About and scroll down to Software Version
Anyways, here's a list of things that have been optimized:
Code:
Folder: /system/app/
Browser.apk
com.htc.WeatherWidget.apk
htcContacts.apk
HTC_IME.apk
Maps.apk
Phone.apk
Rosie.apk
Settings.apk
Weather.apk
Folder: /system/framework/
com.htc.rersources.apk
Also included in the zip are the animations and boot screen from the Gutted rom
The zip is signed and can be flashed from recovery
This has been tested on the following:
Fresh 0.4b, 0.5d, 0.6
Unofficial MoDaCo 1.2
Disclaimer: I am not responsible for what you do with you device. If you break it, it is solely your responsibility.
Always remember to do a nandroid backup before flashing anything
Downloads
11.24.09 New with zipalign
11.23.19 (Old - non zipaligned)
Installing now... Will let you know how it goes...
Edit.... Wow this really made a noticeable difference. Running really nice on a stock rooted phone. No errors as well...
Installed on Fresh Rom. Works good no errors!
Wow! Just flashed this and it's great. Apps seem to load quicker. thanks for the work!
How are your optimizing these? Just the graphics inside them? have you tried to use zipalign from the SDK on anything?
ekinnee said:
How are your optimizing these? Just the graphics inside them? have you tried to use zipalign from the SDK on anything?
Click to expand...
Click to collapse
You are correct, just the graphics, I haven't looked into any other methods yet
I just flashed this over my stock/rooted image. It does indeed load and run very fast. I was wondering what changes you made to the Settings.apk? I also did notice that the transition effects changed to a fade-in effect. Was this also the result of graphic optimizations? Either way, great work!
excellent mod. really enjoy the fading in and out and works alot quicker!
Spunkzz said:
excellent mod. really enjoy the fading in and out and works alot quicker!
Click to expand...
Click to collapse
Has this been tested on the Gutted ROM?
For further optimization use zipalign on the apks. This allows dalvik to mmap the files for further speed improvements.
I like it alot but I get a ton of force close errors cant even really do anything. Installing from the orignal modaco rom.
Ok I don't know if it was this update or the 1.2 unofficial but my dialer now vibrats and I can't figure out how to shut it off.
My dialer vibrates as well, running Fresh .5d, would also like to disable it.
Looking forward to giving this a shot
QuiQNeZZ said:
Ok I don't know if it was this update or the 1.2 unofficial but my dialer now vibrats and I can't figure out how to shut it off.
Click to expand...
Click to collapse
The dialer started vibrating after the official firmware update from Sprint/HTC. I don't see any option under settings that allows us to disable it.
thanksa bunch I was really hoping someone would slim Rosie down a bit
i keep getting the application touch input process com.htc.android.htciem) has stopped unexpectedly. Please try again
EDIT
aparently i cant text anymore?! help!
To those people who are having errors, are you using this on a rom that has been updated with the Sprint Maintnance Release?
no but i never had a problem XD
By optimizing the images is there a downgrade in quality? Or is there no downside to this mod?
Thanks man. the animations are awesome. and it faster, i didnt notice a change in available memory, but i dont really care.
Thanks again!
i had removed the Browser, so this reinstalled the .apk. just had to go in and remove it again, JIC anyone has removed one of the files, just go in and remove it again.
Originally this was going to be something I would do for Kyorarom v0.2.0, but I will also let the general public in on my works.
I am currently going through every single file in CM6.2 and seeing if it will work on Froyo with little to no effort. Why? Well think of it as a poor mans alternative to a fully functioning CM6.2. I respect marcellusbes work 100% but there are so many people who are being impatient about the non-existant ETA of CM6.2 and CM7 (BECAUSE IT SAYS THERE IS NO ETA AND THERE SHOULD NOT NEED TO BE AN ETA), I decided to give the people half of what the want: the performance and open sourceness of CM6.2 while still retaining 100% functionality of the Samsung firmware.
Current Status
99% of the bins are working
A few CM apps are working
Some of the libs are working (but they are more just sitting in there)
--- CONSIDER THIS VERY MUCH IN BETA - THIS WILL HAVE A FEW BUGS HERE AND THERE SO PLEASE REPORT ALL OF THEM SO I CAN FIX THEM ---
Now remember, this is by no means an alternative to CM6.2, it is more of a stopgap for people who really want our phone to have CM6.2 on it.
I have been working on this all day today and haven't been able to actually test it properly, but it appears to be stable with the files I have added, and it also appears to be quicker. Not by much, but it feels a little smoother.
Why would I need this?
As I said, it's a poor mans CM6.2. It will give you 90% of the performance of CM6.2 while still giving you 100% functionality (provided I haven't broken anything) from Samsung firmware. Programs run quicker, the system responds faster, and the system just feels smoother in general. It's not like FuguTweaks or V6 Supercharger which gives you a tiny change, the goal of this is to give you a HUGE change.
What is noticably quicker?
Well I need people to tell me that, but what I have noticed is quicker is:
Screen rotate happens quicker
Scrolling through menus
Swiping around websites
System boot time
What do I need to use this?
Well I have only tested this on Kyorarom v0.2.0 alpha (unreleased), so I don't know how your results may go, but it SHOULD work on all JPS based SAMSUNG ROMS.
THIS IS NOT A PATCH FOR CM6.2! THIS IS A PATCH FOR SAMSUNG!
You will also need CWM with update.zip signing disabled. This is provided as an update.zip as there are SO MANY permissions that need to be set in the bins/xbins/libs that it would be ridiculous to tell people to run an ugly script which will probably not work on 99% of peoples computers, so an update.zip without signing is how I will do this. Why no signing? Because every guide I have followed to tell me how to sign a zip or an APK has done nothing useful. SOMEONE TELL ME HOW PLEASE!
How do I install this?
Just put this on your SD Card, go into CWM and tell it to update from an update.zip. Pretty simple. I highly recommend doing a system.img backup first though to be on the safe side in case something goes terribly wrong. Format your /system before restoring the system.img.
What should I do if I get a bug such as a force close or a random reboot
Get your phone right to just before the crash happens
Plug your phone into ADB
Go into ADB SHELL
Type logcat > /sdcard/crashlog.txt
Reproduce the crash
Wait until it has rebooted/force closed
Press Ctrl-C on ADB SHELL
Get the crashlog.txt off your SDcard and paste the last about 20-30 lines in a code box here telling me what you did to cause the crash.
Links
Patch 0.3.1 (requires Samsung firmware, recommended to be on JPS)
CMapps 0.3.0 (should work on Samsung firmware without CMbins)
CMbins Remover (will only replace the bins with the original Samsung bins)
Patch v0.2.0 (requires Samsung firmware, recommended to be on JPS)
Busybox Fix (for in case you installed any of the patches v0.0.3 and below - NOT AN UPDATE.ZIP: THIS IS A BUNCH OF FILES WITH A README)
Please note that this may play up with some custom themes, especially large ones such as MIUI as this replaces a lot of files which these themes may be using or rely upon.
Credits
marcellusbe for his incredibly hard work on CM6.2 and CM7 which sadly seems to not be appreciated as much as it should by some of this community. Please go over to both the CM6.2 and CM7 threads and thank him for his hard work, even if you have already done so.
Change Log
v0.3.1
Removed more pointless stuff such as the etc and libs as they won't provide a performance boost. They were more decoratio.
Fixed install script which removed TW apps but didn't replace them from v0.3.0.
v0.3.0
Removed pointless bins which don't provide any performance boost, such as ping and stuff.
Fixed force close lag bug.
v0.2.0
Added the last few bins that were missing. Only bins missing are the ones that cause the system to break.
Added a few more things from etc from CM. They shouldn't cause any difference.
v0.1.1
Fixed dalvik-cache building.
v0.1.0
Removed xbin. It was causing too many problems
Added a few libs (ones that aren't in Samsung)
Added a few items from etc
Replaced a few stock Samsung apps in order to clean the system up before I remove twframework.
v0.0.3
Fixed the missing meta-inf folder in the update.zip. Sorry guys!
v0.0.2
Fixed the busybox issue. the patch removed the old busybox and replaced it with a broken one. If this doesn't fix it then 'mount -o rw,remount /dev/block/stl6 /system' and 'chmod 755 /system/xbin/*'
I was doing something like this , cm framework on jps
But you did more
np
i didnt have the time to complete it fully(exams)
Best of luck!
cdesai said:
I was doing something like this , cm framework on jps
But you did more
np
i didnt have the time to complete it fully(exams)
Best of luck!
Click to expand...
Click to collapse
If you wish to help me then by all means I'll be grateful. I am nowhere near finished as there are a few files in /system/bin that still need checked to see if they cause issues. I just went through the alphabet and if a file such as 'dexopt' caused problems then I left out all of D. However that's just an example. Dexopt is left out, but I left in the rest of D as I found it causing problems later down the track. I know I am missing Q and S. I'm gonna go through them all tomorrow.
EDIT: Not to mention I want to go through frameworks and libs and the etc folder too.
I am not sure if this is helpfull or not... I instaled the update in my phone. At the moment, only issue is that busybox installer is not working after it get superuser permisions, and then i cannot open any other app. I need to reboot my system. If i find any other issue, i will let you know.
Sergiales said:
I am not sure if this is helpfull or not... I instaled the update in my phone. At the moment, only issue is that busybox installer is not working after it get superuser permisions, and then i cannot open any other app. I need to reboot my system. If i find any other issue, i will let you know.
Click to expand...
Click to collapse
Hmm, I might have done somethign weird with xbin. Try going into adb shell and run 'chmod 755 /system/xbin/*'. I might have to get it to set permissions in the update.zip for that folder.
EDIT: Try restore your system back to how it was prior the install of the update, and then try the other zip I just put in the first post. I think it'll be the xbin folder doing it.
@hillbeast
you also plan to port the framework of cm6?
ale_bot said:
@hillbeast
you also plan to port the framework of cm6?
Click to expand...
Click to collapse
I hope I can. The plan is to get everything that will work from CM6.2 in Samsung firmwares to work.
New version uploaded. See first post for details.
I fixed the busybox issue. I thought I fixed it earlier but aparently not. It was CM6.2s Busybox being in there that killed it. I put the Samsung one into v0.0.2 so it'll fix the grief it caused with version 0.0.1.
If it still causes issues then go into adb shell (or Terminal Emulator) and run this code:
Code:
mount -o rw,remount /dev/block/stl6 /system
chmod 755 /system/xbin/*
Donate and get rewarded
Good work, hillbeast.
I wish you would work more togother, i mean most of the main developers in g3.
you know the names.
And some more support from the community with donating and thanks or appriciation.
You (just caught you user reading this), could donate a little bit, so that your galaxy 3 is got tuned with great software, so it worth allmost double the price then you paid for it, because it expands with possibillities and powers.
Just click someones (dharamg3, marcelubes.. and some of all the other great programmers) donate button, type the number: 5 or 10 or 20 or 100 +++ etc, log in to paypal and DONATE!
(•.•) said:
Gut work, hillbeast.
I wish you would work more togother, i mean most of the main developers in g3.
you know the names.
And some more support from the community with donating and thanks or appriciation.
Yes You, could donate a little bit, so that your galaxy 3 is got tuned with great software, so it worth allmost double the price then you paid for it, because it expands with possibillities and powers.
Just click someones donate button, type the number: 5 or 10 or 20 or 100 +++ etc, log in to paypal and DONATE!
Click to expand...
Click to collapse
I actually work with dharamg3 on occasion and have given him ideas for G3Mod. I just don't take credit for anything because my contributions have been very minor at best and my credit isn't deserved considering how much more he and marcell have done for our phone.
hillbeast said:
I actually work with dharamg3 on occasion and have given him ideas for G3Mod. I just don't take credit for anything because my contributions have been very minor at best and my credit isn't deserved considering how much more he and marcell have done for our phone.
Click to expand...
Click to collapse
Yeah, i mean it for all developers, but you included of course. so why not.
Just for every user to remind if he reads my post.
(•.•) said:
Yeah, i mean it for all developers, but you included of course. so why not.
Just for every user to remind if he reads my post.
Click to expand...
Click to collapse
Yeah that is the entire point of the XDA: developers helping developers to make our phones incredible and help them reach their true potential.
People bash the Galaxy 3 but undreneith it's actually a really good phone with really good hardware. It's no dual-core Cortex-A9 with 1GB of DDR2 RAM or anything, but it's certainly a very good mid-range phone. It was just held back by Samsung not programming it right.
Nice vision man...best of luck
To make things easier i guess you can consult marcellusbe about what all stuff is not working in CM6.2...then u'll need to replace only those files instead of going through evry file !!
niteshtak said:
Nice vision man...best of luck
To make things easier i guess you can consult marcellusbe about what all stuff is not working in CM6.2...then u'll need to replace only those files instead of going through evry file !!
Click to expand...
Click to collapse
Yes however I also need to find what is compatible with the rest of Samsungs firmware.
hillbeast said:
Hmm, I might have done somethign weird with xbin. Try going into adb shell and run 'chmod 755 /system/xbin/*'. I might have to get it to set permissions in the update.zip for that folder.
EDIT: Try restore your system back to how it was prior the install of the update, and then try the other zip I just put in the first post. I think it'll be the xbin folder doing it.
Click to expand...
Click to collapse
I have just installed that 0.1 you told me and now is working good. I am gonna try the 0.2 and tell you if all is ok.
Guys I totally forgot the meta-inf folder in v0.0.2. You can just use the one from v0.0.1 as there is no signing or anything. I'll see if I can get the link on my phone for v1
Sent from my GT-I5800 using XDA App
But why using cyanogenmod files in samsung firmware ?
You know that CM 6.2 is the most awesome rom for froyo ! I've almost never had any lags and the rom is fast even after installing a tons of app's !
Darius_AWS said:
But why using cyanogenmod files in samsung firmware ?
You know that CM 6.2 is the most awesome rom for froyo ! I've almost never had any lags and the rom is fast even after installing a tons of app's !
Click to expand...
Click to collapse
Well its just a try to get the CM6.2 speed and smoothness on the samsung ROM..without having the bugs of CM6.2 which arent solved yet...
Sergiales said:
I have just installed that 0.1 you told me and now is working good. I am gonna try the 0.2 and tell you if all is ok.
Click to expand...
Click to collapse
Same problem in 0.2 with busybox installer, even trying to fix it with adb.
Darius_AWS said:
But why using cyanogenmod files in samsung firmware ?
You know that CM 6.2 is the most awesome rom for froyo ! I've almost never had any lags and the rom is fast even after installing a tons of app's !
Click to expand...
Click to collapse
As I stated in the OP, Cyanogenmod is incomplete and is buggy. The camera doesn't work, the FM radio doesn't work, no Bluetooth, and some things are buggy. By working in the opposite direction of moving to Cyanogenmod with small steps by using the working components from it, we get a balance.of speed and functionality which is what a lot of people have been moaning about all this time since CM went alpha.
Again, huge respect to marcell for getting it this far. This is a huge achievement from him.
Also here is the mediafire link for v1 so people can grab meta-inf and insert it into the v2. I will fix this in v3 later today.
Sent from my hybrid Kyorarom + Cyanogenmod Galaxy 3
I Welcome to the first custom ROM for the note 5 it is light fast with great battery life and a few minor modifications in due time I will add things I appreciate you for coming and trying out my work.. You can flash whatever kernel you enjoy the best. as I see everyone has different preferences.
2 versions.so please mind the instructions for each
You can choose between stock deodex or live on the edge and go with ThrashRom lite.. Your choice... Happy flashing.
The old AOGE downloads will be at the bottom if you need.
Developers-I do not mind if you use this as a base just please give credit.
9-11-2015 THRASHROM 3.4 clean flash
https://www.androidfilehost.com/?fid=24052804347813339
9-8-2015 ThrashRom 2.4 https://www.androidfilehost.com/?fid=24052804347811318
Boh6 modem- https://www.androidfilehost.com/?fid=24052804347812657
BOH4 modem only if you need - https://www.androidfilehost.com/?fid=24052804347809079
Arter kernel http://forum.xda-developers.com/showthread.php?t=3189907
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Features for lite
-rooted
-deodexed
-busybox
-3minit battery mod
-zip aligned
-over 200 fonts
-debloated
-private mode working
-SuperSU built in
-Knox removed
-boot sound removed
-international samsung boot animation
-ext read/write fix - thanks @TEKHD
-Netflix fix
-Removed volume warning
-block messages
-disable sms to mms threshold
-Removed Knox version in settings
-removed input method switcher in statusbar
-27 quick settings toggles
-5 way reboot thanks @foreverloco
-ram fix
-custom boot animation
-save restore messages
-enable camera during call
-increased volume throughout
Working V4A- http://forum.xda-developers.com/showthread.php?p=62783064
-more I'll post later when I get home
donations are not required or expected but if you feel like it.. It will give me more red bull to motivate me! ... paypal.me/JThrasher47
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Instructions - erase all registered fingerprints!BEFORE FLASHING! After you can put back in.
For THRASHROM LITE
Boot into recovery (TWRP OR PHILZ) NOT FLASHFIRE
-1. Make a backup
2. Perform a full wipe
3. Flash rom
( I recommend arter kernel but that is optional)
4.flash xposed (optional)
5.reboot. sometimes can take up to 10 minutes to boot first time.
6.thanks button goes a long way.
Uodated 3minit https://www.androidfilehost.com/?fid=24052804347810304
If you do not like 3 minit remove it with this-https://www.androidfilehost.com/?fid=24052804347809789
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
ADD ONS-
Custom boot animation push to system /media and fix permissions
https://mega.nz/#!zN1ARSBA!3IOtVjsJbZH_f-Mz-v3cZ6BkioSThWNynIlsQjrvPas
-3minit for BOH4 ONLY - https://www.androidfilehost.com/?fid=24052804347810304 THANKS @foreverloco
3minit battery mod for AOGE ONLY https://www.androidfilehost.com/?fid=24052804347802688
Xposed framework-http://forum.xda-developers.com/xpo...samsung-lollipop-t3180960/page59#post62556222
noble kernel rebuild 2in case you have reboots with rebuild 3
https://www.androidfilehost.com/?fid=24052804347803877 @drbveb88 thanks for the link I lost lol
Xposed running great!
Old downloada-
Old V2-download- https://www.androidfilehost.com/?fid=24052804347803738
Still dirty flash and flash SuperSU
Old Debloated version- https://www.androidfilehost.com/?f...ww.androidfilehost.com/?fid=24052804347807578
ThrashRom Lite BOH4 with some mods- --please perform a full wipe on this one - https://www.androidfilehost.com/?fid=24052804347808630
list of apps removed--View attachment 3463572
Thanks to @Manh_IT for root and the kernel.
Thanks to @TEKHD for helping behind the scenes.
Thanks to @Chainfire for supersu
Thanks @-viperboy- for the updater script and all the help
Big Thanks to @markbencze for the banner!
Changelog:
V2- removed drive and lookout.. So you don't need to disable
Included kernel and su in rom
9-3-2015- Updated to new base
9-7-2015-removed volume warning
-removed input method switcher
-call/message block In settings
-Netflix fix
-removed Knox version in settings
-removed 3 minit.. Optional to flash
-disable sms to MMS threshhold
9-8-2015- added 27 toggles at boot
fixed private mode
Thanks to @daxgirl and @foreverloco for pointing me in the right direction
9-11-2015
-updated to boh6
-custom boot animation
-ram fix
-5 way reboot thanks @ foreverloco b/c I was being lazy
Thanks for getting things rolling!
dandroid7 said:
Thanks for getting things rolling!
Click to expand...
Click to collapse
No worries.. I'm just as ready as everyone else.. Too bad I don't have kernel knowledge
Misterjunky said:
I found this N920T (note 5) STOCK kernel posted in this forum earlier today but
forgot who posted the link. It's an Odin flash TAR file, perhaps you can use it.
Here is the download link in case you can use it:
https://www.androidfilehost.com/?fid=24052804347800814
Good luck,
Have a great day!
Click to expand...
Click to collapse
Thanks but no stock kernel will not work unless it has been modified.. There's a reason I left it out lol
Misterjunky said:
I found this N920T (note 5) STOCK kernel posted in this forum earlier today but
forgot who posted the link. It's an Odin flash TAR file, perhaps you can use it.
Here is the download link in case you can use it:
https://www.androidfilehost.com/?fid=24052804347800814
Good luck,
Have a great day!
Click to expand...
Click to collapse
I posted that earlier and that is not the stock kernel that is the stock recovery you should give credit where credit's due man not upload that to your own file host..
re: ok
jthrasher47 said:
I posted that earlier and that is not the stock kernel that is the stock recovery you should give credit where credit's due man not upload that to your own file host..
Click to expand...
Click to collapse
I just edited my post and also removed it from the file hosting.
Thanks for letting me know!
Have great day!
Misterjunky said:
I just edited my post and also removed it from the file hosting.
Thanks for letting me know!
Have great day!
Click to expand...
Click to collapse
I will put together a stock boot tar.. And if you send me one for your device I will put together one for your device too. But it's just not cool to take peoples stuff they put together for the community and upload to your host and share it around..
No harm no foul..
Will that stock boot tar be compatible with my s6 edge+ too?
Perhaps since the Note 5 and the s6 edge+ are almost identical
the roms, recovery and the kernel might be interchangeable. ..
Maybe that's just a lot of wishful thinking on my part.
Have a great day, and good luck with the rom.
Sent from my SM-G928T using Tapatalk
Misterjunky said:
Will that stock boot tar be compatible with my s6 edge+ too?
Perhaps since the Note 5 and the s6 edge+ are almost identical
the roms, recovery and the kernel might be interchangeable. ..
Maybe that's just a lot of wishful thinking on my part.
Have a great day, and good luck with the rom.
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
I'm not sure. If it has any similarities to the s6 and s6 edge then it might boot but stiff gets broke like screen gets twisted on x Axis and whatnot so I kind of doubt it.. But recovery I'm sure would be fine.
In the build.prop issues like the screen might be an easy fix by renaming
the model numbers or the versions.
To me it looks like the actual rom has parts in it for more than one phone
model and certain files like the build.prop tell the rom which parts to use
depending on the phone's model.
Or am I completely wrong?
Sent from my SM-G928T using Tapatalk
Misterjunky said:
In the build.prop issues like the screen might be an easy fix by renaming
the model numbers or the versions.
To me it looks like the actual rom has parts in it for more than one phone
model and certain files like the build.prop tell the rom which parts to use
depending on the phone's model.
Or am I completely wrong?
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
Yeah I don't mean to sound rude but yea you're wrong the build.prop won't do anything if you make the changes I mean if you flash it and your axis gets inverted you just put in the dialer code *#2663# and press ftp firmware upgrade and it will fix it it..
The kernel modules is what tells it what to do
re: screen issue
jthrasher47 said:
Yeah I don't mean to sound rude but yea you're wrong the build.prop won't do anything if you make the changes I mean if you flash it and your axis gets inverted you just put in the dialer code *#2663# and press ftp firmware upgrade and it will fix it it..
The kernel modules is what tells it what to do
Click to expand...
Click to collapse
Yea, I know about that *#2663#, it saved my bacon when my touchscreen on my
Note 4 went crazy, it was the right resolution and size but none of the touches
corresponded with what was on the screen, however the s-pen did work properly.
After punching in that code and doing the upgrade the phone worked perfectly.
Before finding that code I was about to flush the phone down the toilet. LOL
The problem was all my fault, I by error odin flashed the wrong version of twrp.
Zip failed to flash on my Note5. Restoring my backup, I'll get you the error log when I'm back in Android.
EDIT: Literally nothing helpful...
Code:
Installing '/sdcard/Deodexed-N920TUVU1AOGE.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/sdcard/Deodexed-N920TUVU1AOGE.zip'
Updating partition details...
Let me take a look inside the zip and see what's up.
EDIT2: Yeah, you don't have a META-INF folder. No updater-script or anything. No wonder this won't flash. You'll need to fix that before this will flash.
-viperboy- said:
Zip failed to flash on my Note5. Restoring my backup, I'll get you the error log when I'm back in Android.
EDIT: Literally nothing helpful...
Code:
Installing '/sdcard/Deodexed-N920TUVU1AOGE.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/sdcard/Deodexed-N920TUVU1AOGE.zip'
Updating partition details...
Let me take a look inside the zip and see what's up.
EDIT2: Yeah, you don't have a META-INF folder. No updater-script or anything. No wonder this won't flash. You'll need to fix that before this will flash.
Click to expand...
Click to collapse
It says the zip is uploading on the OP lol.. I had a bad connection at work and had to stop uploading I'm about to be back and I'm going to start uploading to flashable
jthrasher47 said:
It says the zip is uploading on the OP lol.. I had a bad connection at work and had to stop uploading I'm about to be back and I'm going to start uploading to flashable
Click to expand...
Click to collapse
The ROM I downloaded was complete, not corrupted. It's just missing essential files needed to flash the ROM.
What you're going to upload next, you've tested and it flashes? I can help you if you need.
EDIT: Oh, the link you put up was a system download lol gotcha, missed that part.
-viperboy- said:
The ROM I downloaded was complete, not corrupted. It's just missing essential files needed to flash the ROM.
What you're going to upload next, you've tested and it flashes? I can help you if you need.
Click to expand...
Click to collapse
That is not the ROM that you downloaded that is just the system files that I put there for anyone to use as a base if they need I have to run it through archikitchen to get the updater script unless you have one lying around that will flash on our phones lol
I'm just getting home so I'm about to start running that it should not be long
jthrasher47 said:
That is not the ROM that you downloaded that is just the system files that I put there for anyone to use as a base if they need I have to run it through archikitchen to get the updater script unless you have one lying around that will flash on our phones lol
I'm just getting home so I'm about to start running that it should not be long
Click to expand...
Click to collapse
Yeah, I missed that lol I quickly threw one into the system download, it just successfully flashed, but it's bootlooping after hitting the T-Mobile logo haha I'm at work, so I'll look at it later.
-viperboy- said:
Yeah, I missed that lol I quickly threw one into the system download, it just successfully flashed, but it's bootlooping after hitting the T-Mobile logo haha I'm at work, so I'll look at it later.
Click to expand...
Click to collapse
The lollipop updater scripts are different from jelly bean they have to find the block and mount it that's why I have to run it through the kitchen real fast I just threw this up there the other day for any better qualified people to use as a base.
Now that we have root I'm about to get the updater script and throw it in there and upload
jthrasher47 said:
The lollipop updater scripts are different from jelly bean they have to find the block and mount it that's why I have to run it through the kitchen real fast I just threw this up there the other day for any better qualified people to use as a base.
Now that we have root I'm about to get the updater script and throw it in there and upload
Click to expand...
Click to collapse
No, you can do something like this:
Code:
run_program("/sbin/mount", "-t", "auto", "/system");
and that'll work just fine.
I have a feeling mine bootlooped because of permissions or symlinks, but it wasn't booting far enough for me to get a logcat of it.
-viperboy- said:
No, you can do something like this:
Code:
run_program("/sbin/mount", "-t", "auto", "/system");
and that'll work just fine.
I have a feeling mine bootlooped because of exactly permissions or symlinks, but it wasn't booting far enough for me to get a logcat of it.
Click to expand...
Click to collapse
Exactly.. Archikitchen does all the sym links in the updater script.. I'll admit I'm not that skilled lol I can just build a simple ROM. It seems like you know what you're doing if you can help in any way that would be appreciated other than that the only way I know how to do it is through the kitchen
Hello, i bring to you the QuickRemote app for your AOSP Marshmallow rom, CM13 or any rom based on CM13 (Resurrection Remix, Bliss, AICP), you may ask, "Why would i want QuickRemote on my AOSP rom if MM has native IR support and Peel or Anymote works without all this mambo jambo?
Well, even though what i just said is true, no remote controller app has the learning method enabled, even on a stock rom, only QuickRemote can enable the IR receiver to learn a controller that does not appear on the device/manufacturers list.
So, that's the reason we want QuickRemote to work on our AOSP rom.
So, before anything, i would like to thank @hikarisei23 because in a comment of his post HERE i found the files for QuickRemote to work on MM wich leads to the second person i want to thank wich is @syndre who on said comment, posted the files that worked on MM, also @KronicSkillz who helped a lot to troubleshoot and also confirmed that the method i'm posting here works.
Well, this is it, after personally testing with: Resurrection Remix, AICP and Bliss, all of them MM amd CM13 based, all of them with the stock kernel and Lambda Kernel i'm confident enough to post it here, days of testing and troubleshooting and 3 different roms later.
So first, the mandatory disclaimer, im not responsible for any problem that may result from using my method and the files i'm providing you, either with your phone or your self-esteem, it's your responsibility to read, re-read and only do what you are comfortable with.
What you will need:
1. - The phone, this only has been tested with Lg G2 and Lg G3, this may or may not work on another LG phone with IR, you can try, but at your own risk.
2. - The Rom, this only have been tested with AOSP roms either CM13 or CM13 based roms, again, you can try in another rom but at your own risk.
3. - Obviously a Custom Recovery (twrp, cwm, philz)
4. - The three zips im leaving at the end of the post, QRemote_AOSP_MM.zip Fix_Part1.zip and Fix_Part2.zip.
5. - Maybe necessary or not, depending on your rom, Universal init.d from Playstore HERE and Selinux Mode Changer from HERE.
6. - Root Access.
Ok, once you checked and have everything needed, we have to make a little prep on your Rom before starting to flash the zips.
Rom Preparation 100% Needed
You need to set Selinux to permissive, here is where you may or may not need Selinux Mode Changer, First go into "About Device" on your phone settings and in the bottom you will find an indicator for Selinux state, if its "Permissive" you are good to go, some Roms and Kernels have this set to Permissive by default, if it's Enforcing, search in your Rom or Kernel settings, some of them have an option to set it to Permissive, if your rom does not have any option to change it, you will need Selinux Mode Changer, you install it and set Selinux to permissive, after reboot you can check in About Device again to see if it succeded, if it does not work, try again and check the original post, most of the answers are there, i cant give support for this app, also, this app needs root rights, and preferably two reboots after setting Selinux to Permissive.
Next you need to have init.d support, again, some roms have it, but at least for the test that me and the other users did, even though you are pretty sure init.d is enabled it's better to just install Universal init.d from the Play Store and enable init.d manually after doing so, reboot the system at least two times and grant Root access.
Installation!
Now we are ready to start flashing, reboot into recovery and RECOMMENDED, do a Nandroid Backup just in case, but at the moment no boot loops or any other problems had raised from flashing this, but again, just in case. After that, flash the first file: QRemote_AOSP_MM.zip, reboot your system and let it settle for a bit, 1 minute at least.
Now is the part where almost everyone has problems, you have to check in your Sdcard root for a log file named Qremote.log, if the file is there, it means init.d is enabled and in the file it will say if Selinux is Ok, if you don't have the file, check back the first two prep steps and try again.
Now if everything is going ok, is time for the second file, Fix_Part1.zip, reboot and let the system settle again, you may have some force close errors from QuickRemote or QuicksetSDK, its ok, you can try and check if QuickRemote is working, in allmost every case it will not work just yet, but you may have some luck.
Now, is the time to flash the third file, Fix_Part2.zip, again, reboot and let the system settle, now, you should have a working QuickRemote app on you AOSP MM Rom.
This are the steps, if you need more information about what all of this is doing and why you need Selinux and init.d, also why you need to flash 3 files, you can read the troubleshooting section where i explain what i understand about it.
TROUBLESHOOTING
Well, if you are here, it means that this didn't work as planned, so lets make this like a FAQ so you just search your problem and get the answer for it.
P.- I can't see QuickRemote on my app drawer. A: be sure that QuickRemote.apk is not showing as "com.lge...." and has the default green Android icon on your app drawer, sometimes and for reasons unknown to me, this happens for the first day or so, it will automatically change to QuickRemote and it will have the correct icon at least 5 hours after you installed it, it can take more time. A2: Maybe the flashing proccess was not successful, re-flash the file, it will automatically delete previously flashed files and install a new copy of them.
P. - I get force close messages for QuickRemote or QuicksetSDK after completing the proccess. A: try to run QuickRemote after the system settled, most of the times is 1 minute, in some roms and for reasons unknown to me, this messages will appear at boot but after the system settled, you will be able to run QuickRemote without any problem.
P. - QuickRemote opens up but no manufacturers are showing and it also gets really slow. A: this problem shows when either QuicksetSDK is not correctly installed or Selinux is not set to permissive, the solution for the first problem is in my 2 part fix, the version of Selinux included in the first zip, works great with MM but for some reason it will not work out of the box, i dont know if it's missing some files but it may or may not even show under system apps list on your settings menu, what my 2 part fix does is that, deletes the version of QuicksetSDK that the first flash installs and installs a temporary copy of QuicksetSDK wich i believe, writes information needed for QuicksetSDK to work properly, but this newer temporary QuicksetSDK apk, will allmost never work on MM, you can try but allmost every time it will not work, it will constantly force close, so the second fix zip, will delete this temporary QuicksetSDK and the folder it creates in your Sdcard root and install the previous version of QuicksetSDK again, and now, if everything went well, it will work as it's supposed to, i really dont know why exactly, but it works.
A2: the first thing you will notice when you switch to MM is that allmost every app will ask for permission to your Sdcard or camera or microphone wich in LP was not doing, since 4.3 Google is taking extra steps to ensure that you and your information are better protected one of this steps is Selinux (Security Enhanced Linux) wich, for putting it in simple terms, is like a sandbox for your system, only some trust-signed apps can get out of that sandbox and copy files etc... Into your system, those not-so privileged apps cant output anything outside the sanbox and thats why you need to disable or "set to permissive" Selinux, so QuicksetSDK can make the changes necessary for QuickRemote to do its work, it's true that now your system is in a degree "more vulnerable" but if you are a user of this forum, the odds to install something that will damage your system or jeopardize your information are minimal, you need to be really silly to fall for those "your system has problems" or "your battery is gonna explode if you don't install this app" ads that appear on your phone on the daily basis, so, dont worry, but at the same time, just be carefull and have some common sense, if there is a way for this to work with Selinux set to Enforcing, i will update it in the same second.
P. - QuickRemote force closes whenever i try to open it. A: this is caused by either a bad zip flash, or problems with Selinux or init.d, follow the previous answer and the first installation steps again.
P. - I can see QuickRemote and QuicksetSDK on my apps list, no force closes but still no manufacturers. A: Be sure init.d is enabled, i had problems with Roms that had "native init.d support" and emulated init.d will not work, the only way i got no problems with this was with Universal init.d, install that even though you are "pretty sure" your rom supports init.d, the 10QuickRemote.sh script on your init.d tries to get your country to see if you will use the app in, either Korean or any other supported language, it will also give some permissions to a file and it will check if Selinux is Permissive and finally, it will log this to a file called Qremote.log on the root of your Sd, if you have problems and you cant see the file, the problem is 99% most of the time, init.d.
P.- I don't want to flash three files, isn't there a simpler way? A: Unfortunately no, at this moment and after A LOT of testing etc... This is the only effective way i found.
P. - I'm afraid to set Selinux to permissive and leave the door open for all kind of bad ju ju and stuff to invade my sacred Android system, what can i do? A: Skip this hole thing, at the moment, the only way to make this work on AOSP MM is by doing the previous, just be careful, get some common sense and everything will be just fine.
Well, thats all i can think of right now, if you have suggestions, problems or a better way to make this work, please tell me in the comments or PM me, i'm glad to help as far as i can, i hope this helps, i leave you with the needed files and proof that it works.
QRemote_AOSP_MM.zip - MEGA - DRIVE
nice you started a new thread!
Ive been messing around with this a lot the last few days and I have been seeing the same fix you were talking about by swapping the quickset apks back and forth. Ive put together a zip for flashing that I think would make things as easy as possible for people to get the list to show up.
The script in this one sets the correct permissions for everything on flash. It will instal;l the L version of Quickset, which doesnt show the manufactures list. The M quickset apk also gets flashed but i just put it in /system, so its there and can be moved easily. When you boot the first time after flashing, the the ROM uses the L version. All you should have to do then is use a file manager app to move the QuicksetSDK.apk from /system to /system/app/QuicksertAPK/ replacing the one thats there already. Set perms to 644 if necessary. Now wipe tjhe app data for quickset app, forcing the new one to restart, you dont even have to reboot.
Last thing is you have to delete the Quickset Settings folder made by the lollipop quickset. The Marshmallow version will make a working folder of its own the first time you start Quick Remote.
I like your idea to make fixes in separate flashes, that is probably easier
link to my 01262016.AOSP-6.x.x-M_LGQuickRemote_v4.50.19.zip on MEGA
it's working great!
tnx!
i just ran a nightly update on mokee6 which is cm13 similar and i had to reflash the fixes to get it working again and strange thing is i noticed lib folder is gone from quickset sdk folder but it's working
another thing i noticed is quickset sdk is not in my apps list so don't use that as a way to test if it's working either see if manufactures show up after waiting a bit or try the learning feature to test app functionality
im using d852 with stock mokee6 kernel btw of anyone's wondering and yes i have all apps selected
The mult-zip installation also worked out here on BrokenOS. Remote is working fine.
Originally I used "init.d scripts support" app to handle the init.d file. Worked just fine, BTW. Reason for that is I wasn't sure what would happen if I used Universal Init.d with Broken as it has a directory full of tweaks.
On later examination I see that each script needs to be enabled before it will run (via Settings. True/false values are then looked up in a cfg file).
So I reckon I can safely use Universal Init.d.
LG G3 D851, BrokenOS MM ROM, Tapatalk 4.9.5
can i delete universal init.d after enabling it?
@syndre well yes, i think that flashing zip it's pretty straight forward, your new method is simpler but i think that just flashing and not having to deal with system folders and permissions is better for the less tech savvy, but a little more hideous because of the various reboots
smolchy said:
it's working great!
tnx!
Click to expand...
Click to collapse
You're welcome
@marcdw yes, the thing with Universal init.d is that it really enables init.d at boot, Resurrection Remix and AICP also have their individual init.d scripts and they run, i don't know why the QuickRemote script does not run, and Universal init.d does not mess with the existing scripts, so it's not harmful for the system and runs the script at boot and thats what we want
@KronicSkillz well, I'm glad it works, i used the QuicksetSDK thingy because it seemed like it was the only consistent thing, sometimes the Quickset Setup folder would not show, or it will show with the first QuicksetSDK but at least at first QuicksetSDK would not show in the apps list, after the first fix it would and it would show again, i will put it in the post, thanks for the feedback
Roi007leaf said:
can i delete universal init.d after enabling it?
Click to expand...
Click to collapse
I think you can i but i have not tested that, if you do, tell me what that did to update the post, i keep Universal init.d for other scripts that i have installed so i need it, if you only use it for QuickRemote i dont think you'll have a problem
ok checked.. safe to uninstall...
---------- Post added at 04:56 PM ---------- Previous post was at 04:19 PM ----------
btw.. i did all the steps and i can see manufactures but the IR itself doesnt work.. the devices wont react to it..any solution?
Roi007leaf said:
ok checked.. safe to uninstall...
---------- Post added at 04:56 PM ---------- Previous post was at 04:19 PM ----------
btw.. i did all the steps and i can see manufactures but the IR itself doesnt work.. the devices wont react to it..any solution?
Click to expand...
Click to collapse
What variant/rom you have?
Jc_master said:
What variant/rom you have?
Click to expand...
Click to collapse
LG d855 32GB 3GBRAM RR 5.6.2 android 6.0.1
Roi007leaf said:
LG d855 32GB 3GBRAM RR 5.6.2 android 6.0.1
Click to expand...
Click to collapse
Try force closing QuicksetSDK and delete its data, re-flash the fix part 2 and see in that helps, also i think that you need Universal init.d again, the Qremote.log updates at every boot and it wont update if Universal init.d is not installed
Thanks for creating a new thread, I've been busy for a while and won't be able to do much androidy stuff for now.
I have seen an interesting changelog in cyanogenmod that creates selinux policies for QuicksetSDK, but they haven't merged it yet. So fingers crossed that it'll be merged ASAP so things will be easier for us
link: http://review.cyanogenmod.org/#/c/127449/
hikarisei23 said:
Thanks for creating a new thread, I've been busy for a while and won't be able to do much androidy stuff for now.
I have seen an interesting changelog in cyanogenmod that creates selinux policies for QuicksetSDK, but they haven't merged it yet. So fingers crossed that it'll be merged ASAP so things will be easier for us
link: http://review.cyanogenmod.org/#/c/127449/
Click to expand...
Click to collapse
I hop they do, and thank you for your work also
No quicksetsdk in apps but I saw its library in systrm/app and the permissions are correct.. Any idea ?
Roi007leaf said:
No quicksetsdk in apps but I saw its library in systrm/app and the permissions are correct.. Any idea ?
Click to expand...
Click to collapse
Did you flash both fix zips? The need for those 2 fix zips is because the QuicksetSDK that comes in the Qremote_AOSP_MM.zip works with Marshmallow but by itself it will not create some required files in the system and it will most likely not show in the apps list, the QuicksetSDK that comes in fix part1 most of the times wont work on Marshmallow but it will create some necessary files on the system it will show in the apps list but it force closes, and the QuicksetSDK in the fix part 2 is the same as in Qremote_AOSP_MM.zip but this time it has everything needed to work properly and it now should show in apps list allmost every time, so you need to follow the steps again closely and i recommend that before you flash the fix part 2, you go into your apps list and force close QuicksetSDK and delete its data, also report if you get Qremote.log on the root of your Sd and what this shows if its there
Jc_master said:
@KronicSkillz well, I'm glad it works, i used the QuicksetSDK thingy because it seemed like it was the only consistent thing, sometimes the Quickset Setup folder would not show, or it will show with the first QuicksetSDK but at least at first QuicksetSDK would not show in the apps list, after the first fix it would and it would show again, i will put it in the post, thanks for the feedback
Click to expand...
Click to collapse
ya i was using quickset sdk check (apps list) to see if it was working too until i realized it's working without showing up this time
October release is available with or without root
Made a few changes as far as adding in some apk's to hopefully make it stable for everyone.
Besides that, the usual with normal default font BUT lots more choices in the font section.
Enjoy!
*if anyone has solid reasons to remove any apk files i've put back please let me know as some I should not have been removing and others... not so sure
I will no longer be able to provide new copies of this after the October security patch. I no longer own an A8 2018 and without a device to test the work, I do not feel it is appropriate to continue the project. I'd like to thank everyone that participated and I hope you enjoyed using it! If anything changes in the future that will allow me to provide the latest edited firmware, I will definitely be providing it here for you. I am using an S7 now so if you own one and like this work, there shall be downloads available there similar to this one. (Already testing).
Anyone that would like to continue on their own or have access to files used in making it I will try to include as much as possible from the link provided below by the end of October. There is currently a slightly outdated set of files and instructions (from June I believe) on how I made it already available.
Thanks Again!
Oct Security patch zip ready for download
Available with or without root AND with or without exo font - also an attempt to allow printing feature version. "Attempt" meaning I've placed a set of apk files into a separate and clearly labelled zip on the main download page that may allow proper use of the feature which has not been validated as operational by me or any other user. The "print fix" zip is rooted with exo font
This was made ONLY for the SM-A530W! Please do not use if not W (Canadian) variant. Check your phone info before attempting to flash
All ROMS/extras here:
https://drive.google.com/drive/folders/12Vwzn1CxNdT-ISsrOnSL4D353Nr14iRb?usp=sharing
The ROM will function very well and does not require any special patches, kernels, etc except obviously TWRP
Any additional issues you face with added mods most likely will need to be addressed with the creator
*Built by Superr's Kitchen*
Over 100 apps removed
***Find my mobile and pop-up asking to store lockscreen info removed- BE AWARE reduced ability to locate lost device!***
retro shutdown qmg
Overloaded notifications and ringtones
Oreo Weather (pie weather is a serious downgrade)
August Security release
FM tuner and App Lock (Next Radio may now be used starting from July 2019). Gee, THANKS SAMMY! What took you so long? Was it the polar bears?
Goofy selfie stickers that are funny... and creepy *big thanks to hadesRom genius Corsicanu for the find*
Other typical CSC changes
If your plan has wifi calling, turn it on/off once in phone settings to "break in" the qs tile
Dedicated Screen Recorder access in launcher with no shortcut style appearance (if deleted may be re-enabled with activity launcher as shortcut)
Chrome can be safely disabled at any time if desired and auto replaced with system webview
dm-verity + force encrypt already removed
Magisk rooted
Installation is easy as pie
BACK UP FIRST!
Wipe caches, data, system. Internal may be safely wiped and give the "freshest" install but is optional. Then flash away.
Once flash completes, just reboot.
-*Usage*-
You are free to use any ideas/changes included in the zip. In fact, I encourage you to do so. I've mostly pieced together work from other very difficult projects to create this. Nobody has asked me to add, remove or alter anything contained within this page or in shared downloads. Their work is everywhere and it's what made this possible.
Built with Superr's Kitchen
Some screens to sample below. yay
nobody home
empty
I followed your instructions. I was already updated to pie previous to flashing your rom. I am not able to get root. Any ideas why. I also have the Canadian version. Good job on the Rom, I like it. I wish I could get root.
Ok. I can't really suggest anything other than the obvious.
But you've let it boot once before trying, and are adding the apk as well after flashing magisk in twrp?
Hard to figure that one out. If you're using Magisk, i am assuming.
burnt_31 said:
I followed your instructions. I was already updated to pie previous to flashing your rom. I am not able to get root. Any ideas why. I also have the Canadian version. Good job on the Rom, I like it. I wish I could get root.
Click to expand...
Click to collapse
Have you tried 19.1 you may need to flash twice.
I used magisk 19.1. First I used supersu and magisk uninstaller first. I have root now. Thanks for your help. It amazes me that sometime we over look the simplest thing.
burnt_31 said:
I used magisk 19.1. First I used supersu and magisk uninstaller first. I have root now. Thanks for your help. It amazes me that sometime we over look the simplest thing.
Click to expand...
Click to collapse
I know exactly what you mean. I do it all the time.
Nice you got it going. It's pretty lame if you don't root this. I just cut it up and added a couple things and they can be taken out, except radio and the recorder.
Curious if i got it right. If you're on anything other than VMC, is call recording and other micro features working? All the cscfeature xml files are decrypted so you can see what was done.
Everything seems to be working. I appreciate the work, Canadians are usually the last to get Roms. Most are made for the sm-a530f model. I was using the wrong method. One post said about waiting 166 hrs to reboot your phone after zipping RMM_State Bypass etc. etc.. Your way is simple. Once I get a chance I wlll have a look at what you have done, I work long hours. And as you said, what is the point if you cant root. Thanks again.
burnt_31 said:
Everything seems to be working. I appreciate the work, Canadians are usually the last to get Roms. Most are made for the sm-a530f model. I was using the wrong method. One post said about waiting 166 hrs to reboot your phone after zipping RMM_State Bypass etc. etc.. Your way is simple. Once I get a chance I wlll have a look at what you have done, I work long hours. And as you said, what is the point if you cant root. Thanks again.
Click to expand...
Click to collapse
It is 168 hours no reboots and rmm did work that rmm was for Oreo.
I think his would be fine but no guarantees.
Custom kernel 2.0 flash twice.
Light rom works without issue make sure you flash magisk.
Hello I have a530f model with lastest pie version for Russia. I would like to install native screen recorder. Can yo help me ? Please. My email is [email protected]. thanks
fabian_barrios said:
Hello I have a530f model with lastest pie version for Russia. I would like to install native screen recorder. Can yo help me ? Please. My email is [email protected]. thanks
Click to expand...
Click to collapse
Yeah bud. If you unzip the attached file, you can place it in /system/priv-app/ and make sure the permissions are set correctly for the folder and apk. Compare with other apps in the directoty and make it the same.
Then get the activity launcher app from the play store. Use that to make a link for it.
Getting random freezes sometimes, have to reboot phone using hardware buttons. Using Freedom A8
boominboodhoo said:
Getting random freezes sometimes, have to reboot phone using hardware buttons. Using Freedom A8
Click to expand...
Click to collapse
okay thanks for that. It is probably from my csc edits. I can adjust for freedom and hope it makes a difference.
Anything else to mention about it? What you did before flashing, are you using latest twrp, root or non root.... anything at all
no-verity... favourite snack... p.i.n. number(s)... oops sorry not the last two. My mistake. TOO MUCH info. Disregard.
Do a search on xda for rooting your model for the correct version of twrp. U will need no verify no encript. I used the latest Magisk to root. Supersu did not work. I used twrp for the A8 plus and had problems. Get the right one. It's a great rom. https://www.google.com/amp/s/forum....ery-twrp-3-2-2-0-galaxy-a8-2018-t3818201/amp/
I am looking at the csc for FMC and it appears i have doubled an entry. I need to go over all of them to see if i've done it elsewhere. I will have 2 updated ones hopefully late tonight. (Takes forever to upload).
Not sure if that is the cause but i will definitely adjust it.
Quick question in regards to your Rom. I been using it for a while now. Its the best one I can find, I did post a few times at the start. By any chance, did u get adoptable storage working? I know Samsung removed it in Pie. I tried root essentials but still no luck. Thus is not my first time rooting or installing roms. I started with the HTC 1. Lol. So far, u have the best rom for the A8 2018. Its nice and clean. Almost compares with lineage in my opinion. Thanks again. And by the way, I am Canadian.
Thanks
Hey i appreciate the gesture but even though i "made" this, i did it because of other people. SuperR is an invaluable tool. Then you got magisk, the twrp recovery and heck even give ol' Sammy some credit, haha. All i did was spend time learning everything from this site. I can't stress that enough. I still have not paid for superR and i am going to see how i can right after this.
ANYWAY!
Your question. I've never attempted it but i am very certain there's a magisk module that'll do it.
It involved formatting sd to ext 4 or 3. So i will get on it. Got a few 64 gig cards to spare. If you have a computer, grab the superR linux distro. I've run it on 32 bit machines. K... pay superr... adopt a card heheh.
I will look again in the magisk module section. And I give everybody right now credit for all their hard work and sharing it amongst all of us. Thank you. Thank you. I love modding my phones and I could not do it without everybody's help. All my PC's are 64bit.
Nice. If you need any help just ask. Just bought the kitchen.
I'll have something very soon. Mexico's pie has the classic csc folder of old. I think we should unify with some fiesta pie zip ui sorta thingy... um rom.