[MOD] Quickpanel Sound Toggle for UCKH3 - Captivate Android Development

I modified the stock SystemUI.apk for UCKH3 to remove the Flight Mode toggle and replace it with Sound toggle. This works with unthemed stock UCKH3 rom. I have added a straight zipped copy of the modified SystemUI.apk, a CWM version, and the original stock SystemUI, in case you need to revert back. These are all deodexed and zipaligned.
I had to wipe data/cache to see the changes so its possible you may have to do the same, or a simple restart may suffice.
Use at your own risk and remember to backup if necessary.
Thanks to elfie who created UCKF1 version which is what I used to remake the 2.3.4 version.

Got force close on modified one...

How about data toggle next?

momulah said:
How about data toggle next?
Click to expand...
Click to collapse
+1 remove BT or GPS and replace with data, i use airplain
Sent from my Stock KH3/4 2.3.4 Captivate using the XDA Premium App!

Restart
steveo314 said:
Got force close on modified one...
Click to expand...
Click to collapse
Steveo, I had the same thing happen, along with disappearing panel, when I replaced the apk. A quick restart should fix the problem. Only other thing I could suggest is to make sure you are on UCKH3.
I haven't gotten to test the CWM that I made yet, have been to busy working on this and AOSP lock screen, so if the cwm version is giving you fits try replacing the apk manually and restart.

Thanks for the mod.
KH3 is getting better and better. Its stable to be a daily driver. With CWM kernel I was able to get number battery. Now the sound toggle. All I need now is an AOSP lockscreen and I will be a happy camper.
sent from my Captivate running some ROM i flashed just a minute ago.

Works good on VictoryRomv1

Thanks. Anyone know if we can get BLN on KH3?

Worked first shot on FastyII 1.5.

shadvich said:
Thanks. Anyone know if we can get BLN on KH3?
Click to expand...
Click to collapse
Only if we get source

I am on KH3, I've installed via cwm, I've installed via root explorer. It doesn't show up and I keep getting force closes on it. I clear the cache each time also via cwm while I reboot
The original works though.....

AOSP Lockscreen
enaybee said:
Thanks for the mod.
KH3 is getting better and better. Its stable to be a daily driver. With CWM kernel I was able to get number battery. Now the sound toggle. All I need now is an AOSP lockscreen and I will be a happy camper.
sent from my Captivate running some ROM i flashed just a minute ago.
Click to expand...
Click to collapse
You're in luck, I just finished reposting a fixed AOSP lockscreen for KH3. Get it here.
http://forum.xda-developers.com/showthread.php?t=1244194

Wipe Dalvik Cache and Reload.
steveo314 said:
I am on KH3, I've installed via cwm, I've installed via root explorer. It doesn't show up and I keep getting force closes on it. I clear the cache each time also via cwm while I reboot
The original works though.....
Click to expand...
Click to collapse
Steveo, I'm not sure why its not working for you. I just loaded the cwm kernel for kh3 and tried both the modded and orig cwm zip files to make sure there was nothing screwy there. They both installed and ran fine, no FCs. The only other thing I could say to try off the top of my head is to reboot in to cwm and clear Dalvik cache under advanced, reload the modded systemui.apk and restart. Hopefully that'll fix it for you. If you still have problems let me know.

Ill try it again later tonight and let you know what I get. I bet I need to clear the d.c.

blitz76 said:
You're in luck, I just finished reposting a fixed AOSP lockscreen for KH3. Get it here.
http://forum.xda-developers.com/showthread.php?t=1244194
Click to expand...
Click to collapse
Thank you thank you thank you ... for your great work.
Looks like I can just leave my captivate alone for alittle bit (I know I am lying ... lol) ... but in all seriousness ... not to say that I don't like custom themes but I also like stock theme. Obviously with number battery, CWM and AOSP lockscreen ...

steveo314 said:
Ill try it again later tonight and let you know what I get. I bet I need to clear the d.c.
Click to expand...
Click to collapse
Also fix permissions! In CWM
Sent from my Stock KH3/4 2.3.4 Captivate using the XDA Premium App!

Related

Help with restoring from cwm

I'm on dk28 with bonsai rom installed w/ gingerbread theme. I deleted an app. That I needed so I did a backup and then restored another backup thru cwm cause I just did a backup yesterday. I booted into cwm and did the restore and the rom loaded and as soon as I typed my passcode in a **** load of force closes started happening. Wouldn't stop doing it. Itvwas hard to open anything up. So I then rebooted back to cwm and restored the backup I just did and still the same thing. I've done restores many times before and I've never had this happen. Anybody know what's going on? Could it be the gingerbread theme doing it??? Well I had to go back to the last one I did before I put the gingerbread theme on. That has to be it. Any way to stop the force closes? I'm so far behind now.
So I restored the bonsai rom right before I flashed the gingerbread theme. I then wanted to get my theme back so I bootefpd back into cwm and wiped cache and dalvik 3 times and flashed the theme and I got all the force closes when it rebooted. WTF? I wish I wouldn't even of restored o begin cause it was fine. Anyone can help me ad o why the force closes with the theme all of a sudden? It was working fine. Thanks
Themes can't be restored without your issue occuring. If you made a backup of the the rom before adding the theme, use that and you should be ok.
Sent from my SPH-D700 using XDA App
Yeah thats where im at now but everytime I.try to add the theme again I get all the force closes again. I dont kniw why. I worked fine the first time I did it.
Are you on a odex or deodexed rom?
Also as stated above if you backed up with a theme on, you will constantly get force closes. Just Reflash the rom make sure its deodexed and try flashing the theme. Only restore the back up of data.
Does the bonsai rom com with a preinstalled theme? That is probaly your dilema, try restoring only data and let me know.
Update: THe bonsai rom comes with a battery mod that is the source of your problem... You cant restore a back up with any theming including the battery mod, i recommend a reflash and restore data only.
im getting the bonsai rom to restore just fine without the gingerbread theme but as soon as i flash the theme i get the fcs again. im just gonna start over and reflash both the rom and theme.
musclehead84 said:
oh ok yeah it workede fine the first time i did it wqith bonsai so ill backup back to stock froyo and then reflash bonsai and then the theme. that should work right?
Click to expand...
Click to collapse
yes back up with no battery mod or theme installed and u shouldnt have any issues restoring..
What i do since i forgot to do this i keep all the stock d118 2.1 flashables on my card, so if i need to restore everything i just flash the stock rom, then start flashing my themes and what not.
But yes backingup with out themes or battery mods will let you restore no problem
davidrules7778 said:
Just Reflash the rom make sure its deodexed and try flashing the theme. Only restore the back up of data.
Click to expand...
Click to collapse
This method generally works best for me when restoring. Wipe and reflash the rom, do any special things that need to be done, then restore data. The cache will catch up on its own.
I am not able to use the gingerbread theme either. Look in the thread for the gingerbread theme and you will see other ppl are having the same issue. I even odined back to stock, rooted my phone, flashed the recommended ROM for that theme, then flashed the theme and I still get a bunch of FCs. I gave up on the flashable zip for the them and took some files from the themes zip file and manually copied them to my phone and that seemed to work just fine.
i got it working now. i restored back to stock dk28 and just reflashed the bonsai rom and then the gingerbread theme. thanks for all your help and i got to learn something new. thats a good idea to keep all the stock flashable zips on yoyur sd card.
musclehead84 said:
i got it working now. i restored back to stock dk28 and just reflashed the bonsai rom and then the gingerbread theme. thanks for all your help and i got to learn something new. thats a good idea to keep all the stock flashable zips on yoyur sd card.
Click to expand...
Click to collapse
Yep very good idead, i keep the stock d118 rom, the stock flashable to get rid of clockwork as well as one click root files and drivers files on my phone so i can do any of that on the go on any computer. Plus its nice to avoid going through the mess of odin.
yeah odin can be a pita. hey quick question i saw the bonsai rom has an update to it. could i flash the update over my theme? if i cant (which i probably cant)im not even worried about it.
musclehead84 said:
yeah odin can be a pita. hey quick question i saw the bonsai rom has an update to it. could i flash the update over my theme? if i cant (which i probably cant)im not even worried about it.
Click to expand...
Click to collapse
ya you can flash it over however im pretty sure it will remove your theme again, but then u just have to flash the theme again..

[HELP] Need help getting my Tab backup and running [verizon]

I have a Verizon Tab and to tell the truth I seem to be having more problems than its worth.
After rooting, installing CwM, installing a Kernel and running KhasMek's K-leanMod v2.
I keep running in to problems, wifi problems, market problems, and now it just wont get booted up.
So I would like a start from scratch list.
Also, I am not able to do much from the CwM recovery. I am not able to wipe any thing or clear any thing.
Thanks for the help, this is my 3rd weekend with the Tab and it seems every friday I break the thing and spend the weekend fixing it.
Maybe a stock rom will help you back on track. I've been on stock for 2 months now. Only change I've done is wpa_supplicant and root.
msg on mobile
Mfloresg said:
Maybe a stock rom will help you back on track. I've been on stock for 2 months now. Only change I've done is wpa_supplicant and root.
msg on mobile
Click to expand...
Click to collapse
Where is a pure stock room? I only see 2 roms for the VGT and both dont seem to be stock, also wont I need a stock kernel?
Here
Check this link out should be the answer to your issues...
http://www.droidforums.net/forum/sa...84-how-restore-vzw-galaxy-tab-stock-dj11.html
jschmid698 said:
Check this link out should be the answer to your issues...
http://www.droidforums.net/forum/sa...84-how-restore-vzw-galaxy-tab-stock-dj11.html
Click to expand...
Click to collapse
Thanks, latter tonight when I have time I will try this out and if it works I will take screen shots and post a how to with the files on here so others can use it.
Good luck my friend hope all works out
Sent from my GT-P1000 using XDA App
Once you start over i found when switching to boushh's kernel and rom do a full wipe, wipe cache and dalvik cache. Install the v3 kernel do a full wipe all over again, install rom do one more full wipe as stated above. Then boot normally this seemed to fix all my issues.
Sent from my SCH-I800 using Tapatalk
That was worked for me, I was able to get my Tab back to Stock.
I fallowed the steps and it worked for me so I downloaded the files and copied steps fro, the droid form so we cah have it here as well.
So if you are looking to get your Tab back to stock this should do it.
http://forum.xda-developers.com/showthread.php?p=11601647#post11601647

Is my phone near death?

I've been flashing this thing left and right since November (when I got it, teehee). It's been through over 10 Odins and 100 custom rom/kernel flashes. Even so, Odin has never failed me, nor has the ROMs. But lately, my phone has been freezing non stop, I thought I flashed Syndicate Frozen wrong so I reflashed after wiping and it still froze. I changed the kernel prefixes to 1000/200 instead of 1000/100 to see if it's the 100 scale being stupid, but no dice. I decided to flash MidNIGHT rom to see if that would fix the problem and it worked fine, but now another problem arose. My recovery can't find internal or SD storage anymore...I fixed the problem before by booting the phone up, then going into settings > Privacy > factory reset (although that froze the phone and I had to manually pull the battery) but once I rebooted, all was good...but I Odined back to DI18, automatically updated to EC05, then ran the EXT 4 one click root and it was fine, then I flashed Syndicate 1.1 again, froze on me, restored my working version of midNIGHT rom, now it's giving me that internal storage problem again in recovery.
Is my phone about to die??? I took a picture of the recovery error with my brother's phone.
Those aren't big-deal errors - but I've seen them before when I flashed CWM3 and entered it early (I can't tell you exactly what I did). Just Odin again, flash CWM3, let it convert, and restore the backup. You should be fine. But no, your phone is fine.
And, see the SRF thread. The freeze fix has been posted many times.
Perhaps you should try something other than Syndicate for a while...maybe try an RFS based ROM. Sounds like all your problems start with flashing Syndicate.
Stock EC05 RFS with Genocide 0.5a kernel has been rock solid for me and unbelievable battery life.
I'll give it a try, thanks!
I get those same errors when I use reboot recovery to get to CWM3, but when i use the 3 finger method it works fine.
What method did you use to boot to cwm?
Tortel1210 said:
I get those same errors when I use reboot recovery to get to CWM3, but when i use the 3 finger method it works fine.
What method did you use to boot to cwm?
Click to expand...
Click to collapse
It was Quick Boot app.
Overstew said:
It was Quick Boot app.
Click to expand...
Click to collapse
There's your issue.
k0nane said:
There's your issue.
Click to expand...
Click to collapse
Why would that be the issue? It makes that app obsolete then.
Overstew said:
Why would that be the issue? It makes that app obsolete then.
Click to expand...
Click to collapse
Quick boot is a hard reset. Cause of this it causes data corruption. Use the reboot option built into the rom.
If you wanna reboot into recovery after hitting the reboot 3 finger death grip. It will reboot into recovery
Sent from my SPH-D700 using Tapatalk
Overstew said:
Why would that be the issue? It makes that app obsolete then.
Click to expand...
Click to collapse
MysteryEmotionz said:
Quick boot is a hard reset. Cause of this it causes data corruption. Use the reboot option built into the rom.
If you wanna reboot into recovery after hitting the reboot 3 finger death grip. It will reboot into recovery
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Not only that, but something just doesn't set right when you do it - I can't tell you exactly what, but that's definitely the cause right there.
Had both of these same issues as well on SFR 1.1 and also thought my phone was in trouble. Quickboot caused problems in CWM3 and data corruptions, so had to wipe and reflash. Then, like a number of others, I started having the freezing problems on SFR. Unfortunately, hadn't made it through all the pages of issues in the thread (and freezing issue wasn't yet noted in 2nd post when I downloaded the rom), so ended having to do several battery pulls, which caused more data corruption that required wiping and formatting sd card. Since the posted fix is to flash a kernel that is said to break the camcorder, which I use, I decided to flash back to midnight and all is working again.
I don't want this post to be seen as me knocking SFR. The team at ACS does great work and I'm sure the kernel works for most users. Once the freezing issue is resolved, I'll probably try SFR again, because I like their roms. Just wanted to let you know others are having the same issues.
mis3 said:
I don't want this post to be seen as me knocking SFR. The team at ACS does great work and I'm sure the kernel works for most users. Once the freezing issue is resolved, I'll probably try SFR again, because I like their roms. Just wanted to let you know others are having the same issues.
Click to expand...
Click to collapse
It is resolved. Search the thread. Use the posted kernel.
k0nane said:
It is resolved. Search the thread. Use the posted kernel.
Click to expand...
Click to collapse
I'd totally use that fix if my camera worked with it. :S
any kind of quick reset (quickboot or pulling battery with power on) is bad news on a non-journaled ROM.
Overstew said:
I'd totally use that fix if my camera worked with it. :S
Click to expand...
Click to collapse
Try the camera APK from EB13. The camera works, too - only the camcorder doesn't.
k0nane said:
Try the camera APK from EB13. The camera works, too - only the camcorder doesn't.
Click to expand...
Click to collapse
No camcorder is a deal breaker for me (have a 6 year old that loves home movies). Hoping for a new kernel soon.
Sent from my SPH-D700 using XDA App
mis3 said:
No camcorder is a deal breaker for me (have a 6 year old that loves home movies). Hoping for a new kernel soon.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Try the APK from EB13 before you say that.
I thought everyone knew not to use quickboot that's why the roms have reboot in the power options but I'm scared to even use that and never have.
Sent from my SPH-D700 using XDA App
jbadboy2007 said:
I thought everyone knew not to use quickboot that's why the roms have reboot in the power options but I'm scared to even use that and never have.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
midNIGHT rom came with Quickboot.apk, so I assumed it's okay. I'll ditch it right away, though.
not meaning to hijack the thread butttt
is adb reboot acceptable to use on a non journal rom?

Is there a way to access Apps on a soft-bricked phone?

I'm stuck at the boot-screen of Deck's 1.2 rom, however, I can still access HBOOT and Clockwork Mod Recovery.
I don't see an explicit option, but is there a way I could access Apps or other data to save as a back-up?
I foolishly deleted my rom back-up, and last time I used Titanium Backup was a few weeks ago, so it's not a good option. Thanks!
Android 17 said:
I'm stuck at the boot-screen of Deck's 1.2 rom, however, I can still access HBOOT and Clockwork Mod Recovery.
I don't see an explicit option, but is there a way I could access Apps or other data to save as a back-up?
I foolishly deleted my rom back-up, and last time I used Titanium Backup was a few weeks ago, so it's not a good option. Thanks!
Click to expand...
Click to collapse
As long as the .zip for the ROM doesn't wipe /data, you could reflash "Deck's 1.2 ROM hopefully fixing your issue and not losing your apps.
mattykinsx said:
As long as the .zip for the ROM doesn't wipe /data, you could reflash "Deck's 1.2 ROM hopefully fixing your issue and not losing your apps.
Click to expand...
Click to collapse
I already tried wiping cache and dalvik, reflashing the rom, and I still get stuck in a boot-loop =/
Thanks for the suggestion though.
Android 17 said:
I already tried wiping cache and dalvik, reflashing the rom, and I still get stuck in a boot-loop =/
Thanks for the suggestion though.
Click to expand...
Click to collapse
You could wipe /boot and /system as well and reflash and see if that fixes it.
mattykinsx said:
You could wipe /boot and /system as well and reflash and see if that fixes it.
Click to expand...
Click to collapse
I just tried that and it didn't work either. This is maddening.
The last thing I remember doing was tinkering with the lockscreen settings in the advanced settings. I set up a rotary revamped lockscreen with Dolphin Browser HD as my custom application. I have Dolphin saved to SD too, but I don't see why such a small thing would cause constant bootloops.
It ran fine before 1.2 stable and messing with the lockscreen.
Android 17 said:
I just tried that and it didn't work either. This is maddening.
The last thing I remember doing was tinkering with the lockscreen settings in the advanced settings. I set up a rotary revamped lockscreen with Dolphin Browser HD as my custom application. I have Dolphin saved to SD too, but I don't see why such a small thing would cause constant bootloops.
It ran fine before 1.2 stable and messing with the lockscreen.
Click to expand...
Click to collapse
I have titanium backup run every night along with my call log back up app and go sms to back up texts.
Prevents this kind of thing.
Nothing you've said you have done explains a boot loop.
mattykinsx said:
I have titanium backup run every night along with my call log back up app and go sms to back up texts.
Prevents this kind of thing.
Nothing you've said you have done explains a boot loop.
Click to expand...
Click to collapse
That's a good idea. I usually just use Titanium backup when I'm doing a full wipe or flashing a ROM with significant updates, but since I'd been using Deck's for a while and having no issues whatsoever really and just updating incrementally, I didn't think to backup in a while.
I had actually backed-up the ROM prior to flashing 1.2 stable, but I needed to delete it to make room to back up the newer version, and I didn't think it'd be a big deal since it was stable for a few boots. I guess I got too comfortable.
This is ridiculous, I didn't make any changes to the ROM or flash any new radios or anything of the sort that should cause a bootloop.
I do also use the Theme Manager MattedBlues theme but I've been using that for over a week or so with no issues, so I doubt that's the cause.
Oh well, thanks for the ideas though.
Android 17 said:
That's a good idea. I usually just use Titanium backup when I'm doing a full wipe or flashing a ROM with significant updates, but since I'd been using Deck's for a while and having no issues whatsoever really and just updating incrementally, I didn't think to backup in a while.
I had actually backed-up the ROM prior to flashing 1.2 stable, but I needed to delete it to make room to back up the newer version, and I didn't think it'd be a big deal since it was stable for a few boots. I guess I got too comfortable.
This is ridiculous, I didn't make any changes to the ROM or flash any new radios or anything of the sort that should cause a bootloop.
I do also use the Theme Manager MattedBlues theme but I've been using that for over a week or so with no issues, so I doubt that's the cause.
Oh well, thanks for the ideas though.
Click to expand...
Click to collapse
Sorry I took my Xanax to sleep or else I'd likely be able to think of some kind of solution.
Hopefully someone else can help you out.
I think in CWM if you mount System&Data /apps you could utilize adb pull..... Also did you set up any custom partitions, a2sd, data2ext, ect... ?
Sent from my HERO200 using XDA App
Actually thanks for the suggestions guys, I managed to dig up an older version of the rom saved on my downloads folder and flashed it and booted.
For some odd reason, an older release labeled as experimental works better than the 1.2 stable...
It's strange too because I looked around Deck's thread and no one else reported any problems similar to what I was having at all.
For all intents and purposes it appears to be very stable and functional for everyone BUT me
Thanks for the suggestions though. I guess I'll hold off on flashing any roms for a while or wait for a newer version and try flashing with a full wipe.
Cool glad you got her going.
Kaaameeehameeehaaaaaa!

[ROM] LG V10 H901-10c Debranded, Debloated, Deodexed ROM - Clean & Stable

Debranded, Debloated, Deodexed H901-10c ROM for T-Mobile LG V10 (LG-H901) - Clean & Stable
Thanks go to @Rydah805 for deodexing the stock ROM and being my guinea pig while I was fixing all the broken features.
Thanks also go to @KOLIOXDA for being my guinea pig while troubleshooting installation issues.
Features:
WiFi Calling works with Xposed (even in Airplane Mode)
Second screen works with Xposed (no more force-closes during calls)
No spyware (Adapt Client and Carrier IQ removed)
No T-Mobile apps
No Google apps (except Play Store, Search, Text-to-Speech, and Google Play Services)
Stock LG boot and shutdown animations
No boot sound (boots silently)
No Chrome customizations (Chrome homepage no longer forced to t-mobile.com)
Stock recovery restore disabled (does not overwrite TWRP on reboot)
External storage permissions fix (all apps can write to MicroSD card)
WiFi connectivity fix by @ZDeuce2
AOSP Emoji font
Over 100 additional alarm, ringtone, and notification sounds from Nexus and Samsung phones
Busybox 1.24.1
SuperSU v2.65 stable
Stock 10c kernel and boot image
Download (built Feb. 08, 2016): https://onedrive.live.com/redir?resid=FE4478E2ABDFD5FC!1082&authkey=!AMAKMBsK8gCEhH0&ithint=file,zip
Changes in this build: Updated SuperSU to 2.65 stable.
Before you install, read below:
Safe to install over stock ROM (odexed or deodexed), no need to factory-reset, unless you're compelled to do so by your inner demons.
Compatible with Xposed v79-sdk22-arm64 and later (sdk22-arm64 ONLY). Do NOT install any earlier versions or other variants of the Framework. You must use Xposed Installer 3.0 alpha 4.
Compatible with P_Toti's G4TweaksBox.
Compatible with the LG Apps Theme Engine.
The T-Mobile Device Unlock app does not work on this ROM and is not included. The Play Store version does not work, either. To SIM-unlock your phone, flash the stock ROM, unlock (SIM-unlock is forever and not ROM-dependent), then flash my ROM.
To get back Google and T-Mobile (except Device Unlock) apps, install them from the Play Store. They all work. They were removed because system apps are not Greenifiable, plus they were causing problems when deodexed.
If you use an ad blocker that modifies your hosts file (such as AdAway), you must reapply your ad-blocking filters as this ROM overwrites your customized hosts file with a stock hosts file.
Do NOT install the "Second Screen Fix" ZIP, second screen works fine in this ROM with and without Xposed. The "Second Screen Fix" is only for odexed ROMs and will break the second screen in this ROM.
This ROM removes any mods you have installed. If you want to reinstall them, they MUST be made for a deodexed stock ROM. Mods for odexed or non-stock ROMs may cause force-closes or a bootloop (flash them at your own risk).
If you're still seeing My T-Mobile, Lookout, or the other apps in your app drawer after installing my ROM, those are updates that have been installed from the Play Store - uninstall them manually like any other user app.
DO NOT USE "FIX PERMISSIONS" IN TWRP. TWRP has no idea what permissions are correct for your phone and will screw them up, resulting in random force-closes in various apps. If you did it, you will need to wipe the entire /data partition (not just factory reset) and reflash the ROM.
If Hangouts crashes when you receive a message or call, it's because it can't find one or more notification or ringtone audio files. Go into your phone's Sound settings and re-select your notification and ringtone sounds, then go into Hangouts settings and re-select the ringtone and notification sound for each type of notification (Hangouts call, Hangouts message, Google Voice call, Google Voice message, and so on).
DO NOT INSTALL PowerNap/WakeLockManager. You will get random reboots and corrupt internal storage, since WakeLockManager randomly hard-crashes the entire ART virtual machine.
To disable the OTA notification: http://forum.xda-developers.com/showpost.php?p=66304926&postcount=1002
Installation:
WARNING: Do NOT install over a custom ROM. You will get a bootloop/force-close loop.
Copy ZIP file to phone.
Boot into TWRP.
If clean-installing, factory-reset the phone. The installer wipes the system partition automatically.
Install the ZIP.
If you want Xposed, install it now (use only v79-sdk22-arm64 or later).
Reboot.
WARNING: Do NOT install mods for other ROMs on this ROM. You will get a bootloop/force-close loop.
Do not reuse this ROM without my permission - ask first and give credit where it's due!
Enjoy!
PS. I will begin work on the Marshmallow version of my ROM once we have an official way of flashing TWRP on the Marshmallow bootloader. I want the upgrade process to be "Flash the MM KDZ, install TWRP, flash my ROM." Until then, sit tight!
So we don't factory reset or wipe anything? What if we have mods flashed as well?
baySF said:
So we don't factory reset or wipe anything? What if we have mods flashed as well?
Click to expand...
Click to collapse
No Factory Reset OR Wipe,just flash over what you have ATM.
Make a backup of your present set-up before flashing though,just in case something else pops up.
EDIT:
Removed my previous statement regarding mods/add-ons,they'll need to be re-flashed & only de-odexed mods will work per siraltus (ROM OP)
baySF said:
So we don't factory reset or wipe anything? What if we have mods flashed as well?
Click to expand...
Click to collapse
If you have mods flashed, this will remove them, so you will have to reflash them - but only if they're made for a deodexed stock ROM. If they're made for an odexed or custom ROM, they will likely not work, so flash at your own risk.
KOLIOXDA said:
No Factory Reset OR Wipe,just flash over what you have ATM.
Make a backup of your present set-up before flashing though,just in case something else pops up.
EDIT:
A flash over a factory reset would probably work,I don't see why it wouldn't,but,it's probably not necessary.
I didn't reset or wipe anything & I'm doing just fine.
I don't have Xposed or any sound mods installed,but,my bet is you shouldn't have any problem flashing over a set-up with Xposed or any other mods.
Click to expand...
Click to collapse
The ZIP wipes the /system partition automatically so there is no need to wipe it manually.
In fact, if you wipe it manually, the ZIP will fail because TWRP will lock the /system partition for an unspecified amount of time and you will need to reboot TWRP before installing the ZIP.
If you want to clean-install this, then do a factory reset, reboot TWRP, then install this ZIP. I updated instructions in OP to reflect this.
Thanks!! I'll be checking this out shortly!! :highfive:
so we need to flash a stock rom first?
Just making sure, because I'm currently on black hole... Sorry, replied earlier, but son got sick again so I didn't see the other replies...
Sent from my LG-H901 using Tapatalk
ZDeuce2 said:
so we need to flash a stock rom first?
Just making sure, because I'm currently on black hole...
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
No, read the instructions under "To clean-flash".
siraltus said:
No, read the instructions under "To clean-flash".
Click to expand...
Click to collapse
Sorry, first read it right after you posted op... Then my son got sick again, so I didn't hit send for a while... Lol.
Sent from my LG-H901 using Tapatalk
ZDeuce2 said:
Sorry, first read it right after you posted op... Then my son got sick again, so I didn't hit send for a while... Lol.
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Oh, sorry, yeah I rewrote most of OP in the past hour, LOL
Is it possible to change the DPI of the ROM without all the stock apps going crazy? I'm not sure of the status of xposed so I'm assuming thats outta the picture right now
_-..zKiLLA..-_ said:
Is it possible to change the DPI of the ROM without all the stock apps going crazy? I'm not sure of the status of xposed so I'm assuming thats outta the picture right now
Click to expand...
Click to collapse
The ROM is fully compatible with Xposed v79 SDK22 arm64.
No idea about changing the DPI. I don't recommend it as it seems to break things on this phone.
Dear Sir. Altus,
Thank you for the clean upload, and directions. Currently I am running Rydah805's deodexed rom that you were kind enough to work on fixing wifi calling, etc.
My question is: Is this rom different from Rydah805's V. 1.2.2 as stability and features goes? Would you recommend dirty flashing it over his rom?
Thank you all for your hard work and Happy Holidays
Best,
Bob
bobobobicsek said:
Dear Sir. Altus,
Thank you for the clean upload, and directions. Currently I am running Rydah805's deodexed rom that you were kind enough to work on fixing wifi calling, etc.
My question is: Is this rom different from Rydah805's V. 1.2.2 as stability and features goes? Would you recommend dirty flashing it over his rom?
Thank you all for your hard work and Happy Holidays
Best,
Bob
Click to expand...
Click to collapse
You're welcome. Yes, you should flash this over his ROM. I took his deodexed base and fixed everything that was broken in it (WiFi, Hotspot, power management, other stuff), and rather than cluttering the old thread, I started a new thread with a 100% tested build and clear instructions. I debloated and debranded it, added a few useful modifications, plus I made about 30ish corrections to broken permissions and SELinux contexts that were likely causing problems in his ROM that we had yet not discovered (the power management stuff was likely not functioning properly due to being denied proper privileges). Read the OP for a list of features and modifications.
siraltus said:
You're welcome. Yes, you should flash this over his ROM. I took his deodexed base and fixed everything that was broken in it (WiFi, Hotspot, power management, other stuff), and rather than cluttering the old thread, I and started a new thread with a 100% tested build and clear instructions. I debloated and debranded it, added a few useful modifications, plus I made about 30ish corrections to broken permissions and SELinux contexts that were likely causing problems in his ROM that we had yet not discovered (the power management stuff was likely not functioning properly due to being denied proper privileges). Read the OP for a list of features and modifications.
Click to expand...
Click to collapse
Thank you again! Dirty Flashing now
Xposed
Will this Rom have the second screen fix once I install Xposed?
Thanks for your hard work.
mkrunk12 said:
Will this Rom have the second screen fix once I install Xposed?
Thanks for your hard work.
Click to expand...
Click to collapse
You're welcome. There is no need for that, second screen works fine in this ROM with Xposed and without. The "second screen fix" is only required on odexed ROMs. Updated OP to reflect this.
I'm having this weird issue where the screen will become tinted, almost like there's a pop-up or the notification bar is pulled down. It'll usually go away after a second or if I tap somewhere on the screen, but it's kinda frustrating.
Sent from my LG-H901 using Tapatalk
TheJesus said:
I'm having this weird issue where the screen will become tinted, almost like there's a pop-up or the notification bar is pulled down. It'll usually go away after a second or if I tap somewhere on the screen, but it's kinda frustrating.
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
I think you posted in the wrong thread. You want to post in the Troubleshooting forum.
siraltus said:
I think you posted in the wrong thread. You want to post in the Troubleshooting forum.
Click to expand...
Click to collapse
No, I was the second one to install it over in the original thread and I didn't have the issue with the actual stock ROM.

Categories

Resources