Custom Rom +Theme = Lost Exchange Support - Verizon Galaxy Note 3 Q&A, Help & Troubleshooting

just hoping for a little help on getting 1 piece solved to my N3 setup with the theme i want and everything working. i am running 4.4.2 custom rom with a Backs Black theme that i had to manipulate a little when flashing to get everything themed just the way i want.
my only feature not working to complete my setup is Exchange Email for work and standard Email works fine but Exchange tells me something is wrong and it always worked perfectly with just name and password before theme stuff
i have tried to replace SeEmail_J, SecExchange, and EnterprisePermissions with the original rom files and permissions for them but this has not helped and still fails.
any thoughts or suggestions on fixing this without having to use a 3rd Party like K9?
thanks for any help

Just curious but did you verify it working prior to flashing the theme? It may be 100% vr theme based, but it does replace .xml files in certain apks.
<Note3>

LeftyGR said:
Just curious but did you verify it working prior to flashing the theme? It may be 100% vr theme based, but it does replace .xml files in certain apks.
<Note3>
Click to expand...
Click to collapse
it did work perfectly on Jasmine 1.1.1 Stock prior to flashing.
thanks

fletch33 said:
it did work perfectly on Jasmine 1.1.1 Stock prior to flashing.
thanks
Click to expand...
Click to collapse
If you try it again from scratch, yank all the .xml's out of the theme before flashing and see if that solves it. If so, guess it's trial and error to se3 which of those are causing it. . .
<Note3>

LeftyGR said:
If you try it again from scratch, yank all the .xml's out of the theme before flashing and see if that solves it. If so, guess it's trial and error to se3 which of those are causing it. . .
<Note3>
Click to expand...
Click to collapse
i never mind starting over and in fact it took some serious trial and error to get Backs Black working on dialer and contacts and had to install KromeX first just to get it to take.
would pulling XML's affect installation of theme? not familiar with this so thanks for clarification

fletch33 said:
i never mind starting over and in fact it took some serious trial and error to get Backs Black working on dialer and contacts and had to install KromeX first just to get it to take.
would pulling XML's affect installation of theme? not familiar with this so thanks for clarification
Click to expand...
Click to collapse
Unsure. It might. But what you can do once you've verified (IF it works) you can use your apps with the theme minus xml, start reflashing the theme with xml's in a few apps at a time. Backing up in between. It may not have too much impact on the theme once you narrow it down. And it's probably just one in framework, settings, or the email app doing it.
<Note3>

LeftyGR said:
Unsure. It might. But what you can do once you've verified (IF it works) you can use your apps with the theme minus xml, start reflashing the theme with xml's in a few apps at a time. Backing up in between. It may not have too much impact on the theme once you narrow it down. And it's probably just one in framework, settings, or the email app doing it.
<Note3>
Click to expand...
Click to collapse
well thanks and go figure i tried replacing the apks again with a fresh data clear on each before and then recovery caches wipe as a last effort to having to start over and all is good and working and very DARK!
thanks for you input

Related

need help replacing Browser.apk

it is possible to replace the stock browser with the one from CM5?
can some one explain the steps..?
thanks
eortizr said:
it is possible to replace the stock browser with the one from CM5?
can some one explain the steps..?
thanks
Click to expand...
Click to collapse
Whats the benefit of CM5?
^ more options.
^^ I have tried to use a few of the system apps from Cyanogen 5.0.8 Stable with success, but others have put me in constant reboots. Be sure you do a nandroid. Grab the .apk, delete the old browser (be certain to make a backup), go to manage applications and delete any remnants (if any), drop the cm version in system/app and reboot.
It will either work, or constant reboot. No promises on any of this as I have not tried... I'm kinda doubting its going to work. Let us know.
What are the options it offers?
I'm really waiting on foldered bookmarks.

[ROM] Captivate-Deodexed-JH7 v 0.2-Stock

The fruits of my deodexing project are now available for everyone to taste. What this ROM has is JH7 fully deodexed and zipaligned, and then tweaked. I have decided to remove the focus off the optimization, as others have made far more advances, and my choices may not be agreeable to someone else. I am not responsible for anything that happens to your phone, but I have tested this on my phone, and other than the issues noted below, I have not run across anything deal breaking. This is just a different way to optimize the files, so risk of any hardware damage is minimal. You'll only run into software that won't work.
How to install:
1. Download the zip file, and place it on the sd card.
2. Fire up ROM manager, and apply from SD card, also recommend doing a nandroid back up at the same time
3. ???
4. Profit
What yout get:
1. Stock JH7 deodexed, and zipaligned
2. AT&T and Samsung bloatware removed
2. Superuser and Busybox preinstalled
3. build.prop preedited to allow you to see all market apps
4. The kernel is untouched during the update, but the user data, and cache are wiped. You will need a Titanium Backup to restore.
Known Issues:
1. This is a stock style ROM, and you have to apply any optimizations or fixes manually, or using something like SRE. The JH7 files are all there (except the odex's of course), so the latest SRE should be compatible in theory, but I have always done all tweaks on the phone myself in the past so I am not 100% sure. I'll let some of you be the guinea pigs and report back.
2. Deodexing, and zipaligning is not some magic bullet for performance increase. I personally see no significant difference between the stock performance and this installation. But this is more flexible down the line to get us nearer to Vanilla Eclair due to having been deodexed.
How to Remove:
Use ROM manager, and restore previous backup.
The ROM can be downloaded Here:
Captivate-Deodexed-JH7_v_0.2-Stock
I hope for this to become a test bed of new ideas I can try out to make things better on our phone. So if you want to test it and guide me, I'd appreciate your input. If someone wants to take this and build upon it further, feel free to do so. I'll look into fixing the two apps force closing, with focus being on the camera, followed by the keyboard. Squashed.
Wow lets see what's to come off this + sre + new kernel + voodoo lag fix + froyo!
BRING ON THE THEMES!
WOw! How long did this take you???
TheTodFather said:
WOw! How long did this take you???
Click to expand...
Click to collapse
Not all that long. The deodexing itself is very automated. Making the ROM took a couple of more days to work out the updating script. I still need to work on the best way to integrate superuser and busybox.
i'll give it a shot!
Dear sirs and/or madams,
What's "deodexed and zipaligned"?
skinien said:
Dear sirs and/or madams,
What's "deodexed and zipaligned"?
Click to expand...
Click to collapse
I've wandered this as well
I would try it but I am too happy with how I've got it. The next time I flash it, it's gonna be to stock so I can get the 2.2 OTA. The work tho, I will say thank you for that.
Quick question..Why is sideloading disabled???
Flashing in just a sec, will update.
Sideloading is controlled by the settings.db file in dbdata. When you flash this ROM, that file gets wiped out and is rebuilt on first boot. I think the original is in the ramdisk packed with the kernel. So on first boot the old crippled file is recreated for you to hack into again.
Sent from my SAMSUNG-SGH-I897 using XDA App
Camera FC all the time, besides that ROM is pretty fast and zippy good job OP.
Will this rom do anything that might break something like SRE? If not, I'll flash it for sure. Got to do a round of it anyway to get the latest goodies
Here's what I've found so far:
-Camera force close
-Log tab in Superuser causes it to force close
-Superuser does work though, aside for the Log tab
-Wifi doesn't work for me
-Mobile Video bloatware isn't uninstalled, just need to be removed from script file and apps folder
Other than that, it's quite zippy and quick. Nice job! I'll take a look at the scripts and files a little later to see if I can fix some of the problems. Keyboard FC should also be an easy fix.
rajendra82, can I suggest that you release the rom as completely vanilla with the deodex and zipalign in place? In theory, everything should work as expected from a vanilla rom and not have things like the Camera app FC.
Users can then apply SRE and you would not have to reinvent the wheel regarding including Superuser, etc. apps.
From what you said about deodex and zipaligning in the other thread, a completely vanilla rom with these optimizations would already be beneficial.
Will installing this ROM negatively affect my phone in any way besides voiding the warranty?
spook said:
rajendra82, can I suggest that you release the rom as completely vanilla with the deodex and zipalign in place? In theory, everything should work as expected from a vanilla rom and not have things like the Camera app FC.
Users can then apply SRE and you would not have to reinvent the wheel regarding including Superuser, etc. apps.
From what you said about deodex and zipaligning in the other thread, a completely vanilla rom with these optimizations would already be beneficial.
Click to expand...
Click to collapse
It will be very easy for me to release the vanilla version, I had actually built that first. Samsung Keyboard still force closed on me when I had flashed that. I didn't know about the force close on camera at the time, but I am sure that it would have behaved the same way. The reason for force closure of these two apps is some bug in deodexing. The apps I removed are the same that SRE does, and I manually removed from my phone before deodexing. That is not the reason for force closes. But if everyone would rather have a stock deodexed ROM that they optimize themselves, I can release it a short time. I will also have to look at tweaking the deodexing process some to get rid of the force closes on the keyboard and camera apps.
+1 on a vanilla Rom..That would be great
rajendra82 said:
It will be very easy for me to release the vnilla version, I had actually built that first. Samsung Keyboard still force closed on me when I had flashed that. I didn't know about the force close on camera at the time, but I am sure that it would have behaved the same way. The reason for force clodure of these two apps is some bug in deodexing. The apps I removed are the same that SRE does, and I manually removed from my phone before deodexing. That is not the reason for force closes. But if everyone would rathe have a stock deodexed ROM that they opimize, I can release it a short time. I will also have to look at tweaking the deodexing process to get rid of the force closes.
Click to expand...
Click to collapse
vanilla would be great my friend...much appreciated
OP updated with stock deodexed ROM linked.
Now I need your help. I know the Camera app that is force closing is Camera.apk, but what app is the Samsung keyboard? On the same lines, when an app force closes, is there a log file generated somewhere to explain what happened.
frenchtoasted said:
Here's what I've found so far:
-Camera force close
-Log tab in Superuser causes it to force close
-Superuser does work though, aside for the Log tab
-Wifi doesn't work for me
-Mobile Video bloatware isn't uninstalled, just need to be removed from script file and apps folder
Other than that, it's quite zippy and quick. Nice job! I'll take a look at the scripts and files a little later to see if I can fix some of the problems. Keyboard FC should also be an easy fix.
Click to expand...
Click to collapse
Camera issue acknowledged. Looking to fix that. The superuser app version I used had that issue anyway on stock ROM before deodexing, later versions seem to have solved it. I have now decided to keep this a stock ROM project to weed out extraneous issues such as these. WiFi worked fine for me at home and work, so I am not sure what's going on at your end.
E_man5112 said:
Will this rom do anything that might break something like SRE? If not, I'll flash it for sure. Got to do a round of it anyway to get the latest goodies
Click to expand...
Click to collapse
Other than the kernel, everything that SRE does will be wiped out, as the whole system, data, and cache partitions will revert back to stock. You can always re flash SRE though.

[Q] Missing Notification Bar

Hey all. I have a Droid X that has been running with Launcher Pro Plus for the past few months.
I rooted my phone the other day and everything was going fine. I downloaded Titanium Backup, ShootMe, and then Metamorph.
I've been checking out droidpirate.com and downloaded a few different notification bar color schemes, which were working fine. Today I downloaded another and decided I wanted to change it, so I switched to a new one through Metamorph, applied it, and rebooted my phone. Upon restart it was still the same color as before, so I applied again and before I could restart it gave me an error message that the status/notification bar (not sure which it said at the time) had crashed.
I restarted it, and ever since then I've had no notification bar. I've tried reapplying the color schemes in Metamorph and restarting after, but nothing has changed.
I've gone to the Launcher Pro settings and toggled on and off the "hide notification bar" setting which hasn't changed anything. I've restored my backup in Titanium Backup and it is still the same. I'm not sure what else to do at this point.
What do you all suggest? It really sucks to not see my battery meter, time, etc. when I open my phone. Any suggestions would be appreciated. Thanks!
I don't know if this is best practice, but I would just re-sbf / reinstall rom.
FluffyMittens said:
I don't know if this is best practice, but I would just re-sbf / reinstall rom.
Click to expand...
Click to collapse
Does that mean flashing the Droid X rom? I am new to all of this, so I'm sorry if these are stupid questions. And what guide would you recommend for going about doing this? Thanks!
Download RSD Lite and flash an SBF. There's a sticky telling you how to do this I'll subscribe to this thread in case you have any questions.
Great, thanks for the info! I'll give this a try tomorrow.
Wait!
Before you do that...
(Which is good advice, and would be my second choice...but you'll be without all of your applications and settings. This will put you on complete stock!)
http://www.chadhaney.com/droidXDefault/4.5.602/
Download the file that this theme was changing.
(system/framework/framework-res.apk I think?)
Download "Root Explorer" from the market...or a free alternative if you can get one to work.
I think "ES file explorer" works, but I've never tried it.
Check the "permissions" on the file you'll be replacing...and change the new file to have the same permissions (prior to moving, just to be safe).
Move and replace the new file into place.
If your phone didn't reboot during that process...
Double check the permissions again...
And reboot.
I knew it was only a matter of time, and that's a good resolve. Thanks for the alternative!
Jubakuba said:
Wait!
Before you do that...
(Which is good advice, and would be my second choice...but you'll be without all of your applications and settings. This will put you on complete stock!)
http://www.chadhaney.com/droidXDefault/4.5.602/
Download the file that this theme was changing.
(system/framework/framework-res.apk I think?)
Click to expand...
Click to collapse
I'm not seeing that file on the website you mentioned. If I ctrl+f framework, all I see is a GoogleServicesFramework.apk file. Would it perhaps be the StatusWidget.apk from that list that I am looking for?
Status widget doesn't sound right, but I have never had to recover my notifications bar before.
http://www.mydroidworld.com/topic/8240-official-gingerbread-update-45602-rooted-and-ready-or-stock/
Sorry man, at work...and can't check...but this should have it.
Or if you've purchased Rom Toolbox or Rom Manager...they have some .zips you can download via your phone and extract with your PC.
Ahh this is all confusing me. I can't find the framework-res.apk on that site either. Would it work to just hard reset my phone then download an app restore app? Then re-root it and restore everything to how it used to be with Titanium?
The framework-res.apk was an attempt to fix your phone without wiping your apps and all that fun stuff. A hard reset wouldn't fix the problem because the file, in theory, is still corrupted or not working. I would sbf your phone. It looks creepy but it's just resetting back to stock.
http://forum.xda-developers.com/showpost.php?p=11118819&postcount=2
Go down to SBF: What is it, and what does it do?!?
If the files are offline because of the SOPAA thing, let me know.
Alright, looks like that's what I'm gonna try. Thanks to both of you for all the help, it is greatly appreciated . Before I go through with it I was just wondering, if I backup all my apps to my SD card with "App Backup and Restore" then reinstall the app after the backup, I'm guessing it should be able to reinstall my apps from the SD afterwards? (I wouldn't use Titanium to restore because I'm assuming that would restore my phone with the flawed system data I have now)
The apps themselves wont be flawed. The phone runs off a whole bunch of apk's. Just the apk that controls the notification bar was messed up. You should be fine with backing up your apps regardless of method. Use what program you're comfortable with.
FluffyMittens said:
The apps themselves wont be flawed. The phone runs off a whole bunch of apk's. Just the apk that controls the notification bar was messed up. You should be fine with backing up your apps regardless of method. Use what program you're comfortable with.
Click to expand...
Click to collapse
Agreed...
But to reiterate...
Titanium won't bork you in any way.
Simply use the option>batch>restore USER apps option and you'll be %100 back to where you were...aside from having to change your settings back to where you had them...
Also...
Facebook and any "Overclocking" applications seem to behave badly when restored.
Not in a negative way...
But I always uninstall them after a restore and install manually through the market...
Facebook won't receive push notifications if you don't.
And Overclock apps simply may not work.
Everything else (game data...whatever) will be exactly as you had it.
Check my sig if you need...
And use the sections about backing up and restoring your data.
Ignore the actual rom flashing part...as it's irrelevant in your situation.
There is also another SBF link in there if the one Fluffy posted is dead.
So I downloaded the latest RSD lite with no problems, but whenever I try to download the "Droid X 4.5.602 SBF Gingerbread 2.3.3" file, it leads me to http://www.multiupload.com/57SX6Q5HJI which lists the file as 602.sbf.zip but downloads as a program called "iLivid", which is a video downloading program.
Any suggestions?
Different Mirror?
http://www.mydroidworld.com/topic/8503-official-45602-sbf-for-droid-x/
Figures, thanks a bunch. I tried the download links from two different forums and both led to that same program download, but it looks like I've got the right one downloading now. Thanks again for all the help, I'm going to try the whole restoration process this weekend when I have more time. I'll let you know how it goes.
ec91199 said:
Figures, thanks a bunch. I tried the download links from two different forums and both led to that same program download, but it looks like I've got the right one downloading now. Thanks again for all the help, I'm going to try the whole restoration process this weekend when I have more time. I'll let you know how it goes.
Click to expand...
Click to collapse
I am totally up sh*t-creek and looking for that .602 SBF - can you point me in the direction. (Damnable SOPA!)
http://www.multiupload.com/ZCEAXVOASG
off of:
https://sites.google.com/site/1kdsdroidx/

[Q] Out of Space??? [SOLVED]

I'm about to destroy my phone and go back to iPhone 5 because that didn't constantly make me want to destroy everything around me.
I wanted to side-load an app. I just unlocked my bootloader and rooted it and was re-installing my apps.
When I go to install an app it says that there is no more space. the file is 4.85mb and I have 12GB of storage left.
I tried:
-Re-booting
-Installing other apps (which works)
-Clearing the cache
-Downloading Trail from PlayStore (I get the same result)
NEW:
-When plugged in via USB to my PC, device doesn't show up under "Computer" [Running Windows 7 x64)
What I did:
I backed up my phone and wiped the whole thing because I was running out of time last night
Thankfully Foxnov1990 and ImbaWind's tips worked. I restored the original backup and it solved my problem. Thanks so much! Love ya guys! :victory:
AFAIK my friend and I don't have this problem with our N4 and my friends don't have this problem with their GNEX.
Btw this is a N4 forum.
ImbaWind said:
AFAIK my friend and I don't have this problem with our N4 and my friends don't have this problem with their GNEX.
Btw this is a N4 forum.
Click to expand...
Click to collapse
I'm talking about the N4... DERP
If you aren't here to answer then don't post... please leave.
Chubby_Skunk said:
I'm talking about the N4... DERP
If you aren't here to answer then don't post... please leave.
Click to expand...
Click to collapse
it's your problem you don't know how to solve, not google's.
if you're here just to unleash this anger then YOU leave.
the guy is right about what he said in the first line.
android wasn't made to piss you off, it was made to stay stock, but you rooted it.
solution? easy: 1) install a stock-like ROM or 2) unroot...
Lol you'll get a lot of constructive answers with your style of posting What have to tried so far to fix the problem? Could we get a screenshot of your storage page?
Chubby_Skunk said:
anyone have a simple answer? rather than sending me to another page where I have to read a 10,000 word essay on how to fix it...
Click to expand...
Click to collapse
That's kinda how it works here - if someone else has fixed it you read their solution! Quite a simple concept really...
However, I've never had that with my old GNex or my current N4 so I can't help you personally
desarenezitic said:
Lol you'll get a lot of constructive answers with your style of posting What have to tried so far to fix the problem? Could we get a screenshot of your storage page?
Click to expand...
Click to collapse
I tried:
-Re-booting
-Installing other apps (which works)
-Clearing the cache
People tend to complain about the OP rather than sticking to the topic at hand.. here's the pic:
Riro Zizo said:
it's your problem you don't know how to solve, not google's.
if you're here just to unleash this anger then YOU leave.
the guy is right about what he said in the first line.
android wasn't made to piss you off, it was made to stay stock, but you rooted it.
solution? easy: 1) install a stock-like ROM or 2) unroot...
Click to expand...
Click to collapse
If you are going to direct that back at me, please send me a PM instead of posting your complaints in the forum. Then we can argue all you want.
Maybe it's the app you're trying to install? Side loading indicates its not quite kosher?
Sent from my Nexus 4 using xda app-developers app
chrisrozon said:
Maybe it's the app you're trying to install? Side loading indicates its not quite kosher?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Not even. I tried to download the Trail from the PlayStore and that says the same thing too... It's like the app is just being a d**k to me lol
I think actually the answer begins on 10,001th word !
And actually I think I know how to fix this problem !
Chubby_Skunk said:
Not even. I tried to download the Trail from the PlayStore and that says the same thing too... It's like the app is just being a d**k to me lol
Click to expand...
Click to collapse
I get the attitute, but you might wanna at least try to be friendlier as we're just here to help.
But On-Topic: have you tried this?
File explorer (app)
Go to /data/app (in System (root))
Del this line
com.maxmpz.audioplayer-1.odex
I've had it before that on stock ROM (aka unlocked bootloader and rooted) which means that it's not DEodexed that some Odex files were left behind. Which means that whatever you try, as long as that file is there, you won't be able to install the app. (shouldn't happen but it's possible in rare occasions)
Hope it helped.
If it didn't help and the Odex file is not there, see if you have Lucky Patcher installed, deinstall it (it sometimes holds on to odex files), and try installing PowerAmp now. Then reinstall Lucky Patcher
Foxnov1990 said:
I get the attitute, but you might wanna at least try to be friendlier as we're just here to help.
But On-Topic: have you tried this?
File explorer (app)
Go to /data/app (in System (root))
Del this line
com.maxmpz.audioplayer-1.odex
I've had it before that on stock ROM (aka unlocked bootloader and rooted) which means that it's not DEodexed that some Odex files were left behind. Which means that whatever you try, as long as that file is there, you won't be able to install the app. (shouldn't happen but it's possible in rare occasions)
Hope it helped.
If it didn't help and the Odex file is not there, see if you have Lucky Patcher installed, deinstall it (it sometimes holds on to odex files), and try installing PowerAmp now. Then reinstall Lucky Patcher
Click to expand...
Click to collapse
Normally just delete the odex file it will works
this problem always occur after uninstalling the app and when you want to install it back, **** thing happens
ImbaWind said:
Normally just delete the odex file it will works
this problem always occur after uninstalling the app and when you want to install it back, **** thing happens
Click to expand...
Click to collapse
Honestly, I have installed and deinstalled the app more than you can possibly imagine... and I've nearly never had issues with reinstalling.
And when I did get issues it was Lucky Patching (having patched the app) that was holding on to the odex and I couldn't delete it till Lucky patcher was deinstalled.
So not sure what **** you mean but there was always an easy solution for me
Foxnov1990 said:
Honestly, I have installed and deinstalled the app more than you can possibly imagine... and I've nearly never had issues with reinstalling.
And when I did get issues it was Lucky Patching (having patched the app) that was holding on to the odex and I couldn't delete it till Lucky patcher was deinstalled.
So not sure what **** you mean but there was always an easy solution for me
Click to expand...
Click to collapse
Oh yep, always happen when I use lucky patcher to removed the app's ads !
I've run into a similar issue before.
I've had similar issues when I've removed an .apk using adb or root explorer without removing its associated .odex file.
Use root explorer and try to find an .odex file that has the same name as the package that you are having trouble installing.
There are some cache cleaning utilities in the Play store that might assist you as well.
https://play.google.com/store/apps/details?id=com.SystemCleanup.Inteks.org&hl=en
Good luck. Also, try to approach asking for help in a more mature manner in the future. You are not entitled to hack a device then complain when something unexpected happens.
-Mike
bunch of winers in here...girls keep your problems to yourself
Sent from my Nexus 4 using xda app-developers app
have you tried to flash userdata.img via msdos?
sometimes my N4 needs to erase everything cause i erase everything and im still seeing rubbish in the memory trough windows explorer!
follow this tutorial!
http://forum.xda-developers.com/showthread.php?t=2010312
Foxnov1990 said:
I get the attitute, but you might wanna at least try to be friendlier as we're just here to help.
But On-Topic: have you tried this?
File explorer (app)
Go to /data/app (in System (root))
Del this line
com.maxmpz.audioplayer-1.odex
I've had it before that on stock ROM (aka unlocked bootloader and rooted) which means that it's not DEodexed that some Odex files were left behind. Which means that whatever you try, as long as that file is there, you won't be able to install the app. (shouldn't happen but it's possible in rare occasions)
Hope it helped.
If it didn't help and the Odex file is not there, see if you have Lucky Patcher installed, deinstall it (it sometimes holds on to odex files), and try installing PowerAmp now. Then reinstall Lucky Patcher
Click to expand...
Click to collapse
Thanks for the tip! I'm going to save this for future reference. I fixed the problem though. ^^^ in OP
ImbaWind said:
Normally just delete the odex file it will works
this problem always occur after uninstalling the app and when you want to install it back, **** thing happens
Click to expand...
Click to collapse
Thanks for the help as well sir. I'm going to save this for future reference if it happens again... I fixed the problem though. ^^^ in OP

Anyone else theme their Axon 7 yet with Substratum yet? Any issues?

I themed my Axon 7 a few days ago using Substratum and the "DarkStock" theme. A few things don't theme and I always leave a few "Google" things out due to when they update, they'll crash (usually Photo's and Calendar).
I discovered today, that if I have "Android System" themed and try to change my input (keyboard) either in Settings or on the pull-down notifications, my phone will reboot. If I remove "Android System" from being themed, it works fine... But, if I'm running a dark theme I need the Android System themed, otherwise I get dark text on dark background and it's near impossible to read.
Luckily, I don't need to change my keyboard.....and I discovered it by accident, but I was wondering if anyone else had experienced this or if it's just my phone?
tele_jas said:
I themed my Axon 7 a few days ago using Substratum and the "DarkStock" theme. A few things don't theme and I always leave a few "Google" things out due to when they update, they'll crash (usually Photo's and Calendar).
I discovered today, that if I have "Android System" themed and try to change my input (keyboard) either in Settings or on the pull-down notifications, my phone will reboot. If I remove "Android System" from being themed, it works fine... But, if I'm running a dark theme I need the Android System themed, otherwise I get dark text on dark background and it's near impossible to read.
Luckily, I don't need to change my keyboard.....and I discovered it by accident, but I was wondering if anyone else had experienced this or if it's just my phone?
Click to expand...
Click to collapse
Huh,didn't know zte didn't have their own keyboard.
Hmmm, I think theres a themed Google Keyboard in TBO. Personally I use SwiftKey as I can't stand the Google keyboard and want the numbers row on top. There's a great (free) SwiftKey in TBO as well with hundreds of (free) themed keyboards.
tdgillihan said:
Huh,didn't know zte didn't have their own keyboard.
Hmmm, I think theres a themed Google Keyboard in TBO. Personally I use SwiftKey as I can't stand the Google keyboard and want the numbers row on top. There's a great (free) SwiftKey in TBO as well with hundreds of (free) themed keyboards.
Click to expand...
Click to collapse
Yeah, they use TouchPal as their "stock" keyboard......But that's not really what I was getting at with my post
I've used SwiftKey for 2 or 3 years now.... I don't plan on changing, but if I wanted to, I can't because my phone will reboot unless I remove the "Android System" part of the theme.
tele_jas said:
Yeah, they use TouchPal as their "stock" keyboard......But that's not really what I was getting at with my post
I've used SwiftKey for 2 or 3 years now.... I don't plan on changing, but if I wanted to, I can't because my phone will reboot unless I remove the "Android System" part of the theme.
Click to expand...
Click to collapse
I understand. It's pretty common for some themes to break things. Actually I was talking to one of guys from Substratum and he was saying that it shouldn't work but that Layers should. I told him that it was the other way round and he thinks it's the legacy part of Substratum. Which doesn't make sense to me, but whatever. I'm just glad we can theme some of it. So if you leave the Android system themed and leave the keyboard alone does it still crash? Maybe if you froze or uninstalled the stock keyboard in titanium it would work?
tdgillihan said:
I understand. It's pretty common for some themes to break things. Actually I was talking to one of guys from Substratum and he was saying that it shouldn't work but that Layers should. I told him that it was the other way round and he thinks it's the legacy part of Substratum. Which doesn't make sense to me, but whatever. I'm just glad we can theme some of it. So if you leave the Android system themed and leave the keyboard alone does it still crash? Maybe if you froze or uninstalled the stock keyboard in titanium it would work?
Click to expand...
Click to collapse
When I applied the theme, I only themed the following:
Android System
Calculator
Google Contacts & Dialer (I did not theme the stock dialer & contacts)
Google App
System UI
Substratum
The rest I left alone, so I never themed the keyboard.
Ok, so as long as you don't try to change the input keyboard it's fine. Sorry for being obtuse.
Always thank those who are helpful...and just ignore those who aren't.
I just tries to apply a Substratum theme and phone got stuck on the Axon boot screen..
What sucked the most was I had just got Project fi working but forgot to make a back up before applying the theme so I had to do that all over again.
I am not able to compile my substratum theme. Did you do anything special like use a different kernel? Or flash anything?
canezila said:
I am not able to compile my substratum theme. Did you do anything special like use a different kernel? Or flash anything?
Click to expand...
Click to collapse
No, I am rooted...You have to be to use Substratum. After some issues with reboots getting stuck on the "Axon" logo, I have not themed anything else (after the last clean flash of B29) other than the PlayStore (made it dark). I'm going to wait until it's fully compatible now.
That just frustrates me. My busy box is updated.... It just won't compile. I am rooted. 2.78. I want to try different themes.... At least Gmail and play store. It really would make the system ui pop.... If the white could be replaced.
canezila said:
That just frustrates me. My busy box is updated.... It just won't compile. I am rooted. 2.78. I want to try different themes.... At least Gmail and play store. It really would make the system ui pop.... If the white could be replaced.
Click to expand...
Click to collapse
I thought that Substratum required "Masquerade" to be built into the ROM for Substratum to work, which this one does not have. Correct?
I think you are correct. But I read others have had it work so I was seeing if I was missing something.
canezila said:
I am not able to compile my substratum theme. Did you do anything special like use a different kernel? Or flash anything?
Click to expand...
Click to collapse
I had that same problem until I disabled write protection, but you said your busy box is up to date I assume you've done that. My busy box not updating was the first clue that it was enable, then trying to modify build.prop and moving apps needed for project to system(I actually ended up just flashing gapps with google dialer, GSC and Project fi).
Once I got mine to compile I themed a lot more things than the Op but still not everything and phone wouldn't boot. I haven't tried again yet with only applying them to a few things but I've heard more recent builds of substratum have been having issues on non Nexus devices so thought that might be what happened with me.
BTW does anyone know if there's a way to remove the theme in recovery like with the old layers themes? I don't recall ever reading anything about it after the switch to substratum and couldn't find anything when phone wouldn't boot so i just flashed an oldish(missing project fi mods) system backup(on my Nexus if something went wrong with layers I'd just reflash vender image-seemed easier than deleting files).
lovemyram4x4 said:
I had that same problem until I disabled write protection, but you said your busy box is up to date I assume you've done that. My busy box not updating was the first clue that it was enable, then trying to modify build.prop and moving apps needed for project to system(I actually ended up just flashing gapps with google dialer, GSC and Project fi).
Once I got mine to compile I themed a lot more things than the Op but still not everything and phone wouldn't boot. I haven't tried again yet with only applying them to a few things but I've heard more recent builds of substratum have been having issues on non Nexus devices so thought that might be what happened with me.
BTW does anyone know if there's a way to remove the theme in recovery like with the old layers themes? I don't recall ever reading anything about it after the switch to substratum and couldn't find anything when phone wouldn't boot so i just flashed an oldish(missing project fi mods) system backup(on my Nexus if something went wrong with layers I'd just reflash vender image-seemed easier than deleting files).
Click to expand...
Click to collapse
I am pretty sure that you nailed it. I think my write protection is enabled. I have a root Explorer that offers to remount the filesystem so it can be r/w except it fails to complete the process. I had to access my filesystem through twrp file manager to actually change anything system level. But I am rooted, twrp and busybox pro says all good. I think I need to investigate how to get r/w access (like root does or should do).
And yes, there is an overlay file you can access through twrp that will save you if you bootloop. But also, in your home folder, there is an easier way to save yourself from a bootloop. The substratum folder is created when installed and inside the folder is 2 flashable zips. One for legacy and other. In case of emergency.
* I just checked and my busybox is 1.18.4. I can install without errors but it does not actually install. When I reload busybox it only shows old busybox...
++ got it. I had to TWRP, terminal: reboot disemmcwp
--- just finished installing Biohazard substratum and the only issue is the Android setting text is dark and almost unreadable. But everything else looks great! BTW I use tbo SwiftKey for my keyboard so I don't know if the keyboard is still causing problems.
amphi66 said:
I thought that Substratum required "Masquerade" to be built into the ROM for Substratum to work, which this one does not have. Correct?
Click to expand...
Click to collapse
That may be why I get stuck at the boot logo when I apply more than the PlayStore....But It does work, other than messing up on the reboot after the theme is applied and working.
I'm currently running my PlayStore with a dark theme.....Was on Stock/rooted B29, now I'm using DrakenFX custom ROM.
I just tried applying Spectrum theme again but only android system, system UI and a few apps, still got stuck on boot.
I guess I'll try a simpler theme like biohazard and wait for a AOSP ROM before trying Spectrum again.
Biohazard rebooted when I opened Google photos. Then I tried Domination. Everything seemed OK. Then I tried spectrum and everything was great EXCEPT when I used my chase bank app and the location /GPS appeared and caused a reboot. Tried it again and same results.
I will keep trying different variations. I love substratum.
canezila said:
Biohazard rebooted when I opened Google photos. Then I tried Domination. Everything seemed OK. Then I tried spectrum and everything was great EXCEPT when I used my chase bank app and the location /GPS appeared and caused a reboot. Tried it again and same results.
I will keep trying different variations. I love substratum.
Click to expand...
Click to collapse
I love it too..... But I don't want to get stuck at the "Axon" boot logo again and have to wipe and start over (again, for the 3rd time). So, I'll wait to theme more until it gets worked out.
I know the keyboard selector crashed it, as well as holding the power button to get the "reboot" menu, but I use a different reboot menu now so that didn't matter.....But sometimes, I'd hold it too long by mistake and it'd reboot on me anyways.
When installing substratum, a folder is created in your home files. Inside the substratum folder is two zip files. Both are a recovery file that removes overlays. I used it to save myself about an hour ago.
After trying lots of good themes, I seem to have found one that is trouble free. Every attempt to cause a reboot fails. All past problems are now uncreatable .... But it might just be that I have not found the problem yet. If I do I will update my story. But..
The theme is called SHARKPIE magpie theme. By setiawanjimmy

Categories

Resources