Related
Hey guys i'm running the current cyanogen mod on my mytouch. I just in the past two days attempted to change the theme. once i did i couldn't download anything from the market, nor could i update any of my apps. each time i do it downloads to 100% (or so it says) and then it asks to force close. I've attempted to reboot my phone and change themes. i'm running the system force theme by prash
any suggestions? i'm a huge tecky but i'm new to this phone so any suggestions would help.
thanks for all your help!
I've had similar problems when I played with the themes. CyanogenMod never caused me problems though. If I remember correctly, I did this for another Rom and it worked. Go into recovery, -> Other -> Fix UID mismatches or something like that. (It might help...? I'm not sure) By the way how did you put on prashes theme? Did you just flash a zip file?
KAwAtA said:
I've had similar problems when I played with the themes. CyanogenMod never caused me problems though. If I remember correctly, I did this for another Rom and it worked. Go into recovery, -> Other -> Fix UID mismatches or something like that. (It might help...? I'm not sure) By the way how did you put on prashes theme? Did you just flash a zip file?
Click to expand...
Click to collapse
Try opening terminal and type:
su
fix_permissions
Then reboot phone.
FYI: Not sure what theme you're using, but sometimes themes break things. I personally don't use them.
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.
Ever since getting my Razr Maxx HD (XT926) three months ago I've been trying to get rid of the Navigation Bar on the bottom of the screen. I use Button Savior so I'm fine with having the NavBar controls disappear.
Among the most reliable remedies seemed to be upgrading to 4.1.2, at which point many people said that you could simply add the line "qemu.hw.mainkeys=1" to the end of your build.prop file in /system, reboot, and *poof* the NavBar would be gone. My phone, which I bought used, was running a leaked 4.1.1 so, once root for OTA 4.1.2 was discovered, I downgraded to 4.0.4, did the updates to that, then took the OTA upgrade to 4.1.1 (no problem), then took the OTA upgrade to 4.1.2 (no problem). So now I had the latest JB version offered for Verizon XT926 in the US. I know that I'd wiped data at least once along the way. The SafeStrap installation that I used to have was gone, as I expected. I assumed that my phone was as stock as it could be and thus ready for the build.prop edit.
I used the new procedure to root my XT926. At that point all I did was to download and install Root Explorer (needed to do the build.prop edit) and Button Savior (needed for navigation once NavBar was gone). In Root Explorer I navigated to /system, made it R/W, opened build.prop in the stock text editor, added qemu.hw.mainkeys=1 at the end, saved (which backed up the older version as expected), and rebooted.
The first thing I get when my phone boots up is the "SystemUI has crashed" error message. My NavBar is gone but so is my System Bar (a/k/a Notification Bar), which I need and want to be visible. I've read a TON about this and I'm pretty sure I've followed the instructions. Why is this not working for me?
I am just not smart enough to decompile and edit my framework-res.apk file (or whatever the name is) so I'm stuck trying to make the build.prop edit work. What could I be doing wrong?
(also, if I use one of the apps like FullScreen or BottomBar they produce the EXACT SAME result -- SystemUI crashes, NavBar disappears but so does System Bar).
cant help
it works for me as experted
Are you positive you entered it correctly?
Sent from my JokerMATRIX HD MAXX
deeje00 said:
Are you positive you entered it correctly?
Sent from my JokerMATRIX HD MAXX
Click to expand...
Click to collapse
He also tried an app which writes the line to the build.prop and got same results.
AFAIK I had crashes on ICS but since I'm on JB 4.1.2 I never had any issues...
Sent from my XT925 using xda app-developers app
Yes, the edit is entered correctly. I've checked that more times than you can imagine. And I've tried nearly every variation that's been suggested anywhere: with spaces before and after the "=", adding the line ending with "0" first then rebooting then changing the end to "1" then rebooting, putting an empty line at the end of build.prop before adding the edit. No change. Is there any history of an app interfering with this edit? I don't have anything exotic installed I don't think but I use a third party launcher (Go Launcher EX) and then a variety of apps, mostly audio/video, social media and a few basic games. I believe that changes to build.prop take place "below" that kind of activity, though, right? And besides, I made the edit before I installed any of that stuff. I may try a hard reset or something like that but if this works for everyone else then I must just be missing something.
I have had the exact same issue and done the same troubleshooting...sucks!
did you happen to check file properties after you saved, i remember back in the early days of Android if you edited a file, you had to change the properties back to the defaults, not sure if that is still the case, but worth a look.
It can't be done on any stock via build.prop only, and framework edits require a deodexed rom.
I recommend you install CM10 or 10.1. If you prefer safestrap over CWM, then you can use CM10, but without a camera. Fullscreen toggle works perfectly, and I'm able to use PDroid : )
I suppose I should be glad that at least *one* other person is having this problem. Means it's slightly less likely that I'm just incompetent.
As for changing file properties, I didn't change any properties to do the edit other than making /system "RW" in order to be able to edit the file. Could someone tell me what the default values are for build.prop? The most recent edit I've made always shows up correctly when I go back into build.prop, by the way, so I know I'm actually changing the file.
If a rooted stock 4.1.2 can't hide the NavBar with a build.prop edit then this is the first I've read about it, and I've read just about everything that I can find on this subject (including translations of non-English discussions, just in case I could get a new lead from them). Not saying that's not true, just not consistent with what I've read so far.
I'd love to install a CM ROM on my XT926. I've admired Cyanogenmod since I first started fiddling with my Nook Color some years ago. Their crew does some spectacular work. But -- no camera? No Bluetooth? Sometimes wifi or phone call problems? That's too much lost functionality for me. If those remaining few obstacles are someday overcome I'll be all over it though.
ONE LAST QUESTION -- I assumed that, if I "scrubbed" my phone down to the lowest level possible (wipe cache, wipe dalvic, wipe data) I would eliminate whatever weird impediment I have to getting the build.prop edit to work. Is there something else I can do to wipe the phone even MORE thoroughly?
The permissions are RW-R-R, I have had the issue with stock and custom roms (running Foot Through the Floor right now). I wasn't surprised when it didn't work with stock (silly Moto) and I was a little surprised when it didn't work with and of the custom roms I tried, I have no doubt it would work in CM.
I tried it out, it works but you need to reboot after edit, I hot booted and nothing changed, full reboot and it works. hope it helps you.
Just in case this makes the difference, can you tell me what distinguishes a "hot boot" from a "full reboot"?
Having issues myself. Have 4.1.2 rooted, RAZR HD. Added the line above to build . prop with "=0" first shutdown, started back up. Then changed to "=1" saved, shutdown and started back up. System UI FC's.
Wonder if it matters what launcher is being used. I am on GO Launcher. I say this since on home screen I see the GO Launcher menu show up just below bottom of my wallpaper but behind it. I can swipe up to bring up full menu but it is weird how it comes up in background on its own.
Anyone get it to work with GO Launcher?
Sent from my DROID RAZR HD using xda app-developers app
---------- Post added at 10:56 AM ---------- Previous post was at 10:54 AM ----------
Oh and does it matter where in build.prop the line goes? I just added to bottom. Thx.
Sent from my DROID RAZR HD using xda app-developers app
---------- Post added at 11:29 AM ---------- Previous post was at 10:56 AM ----------
lesdense said:
Yes, the edit is entered correctly. I've checked that more times than you can imagine. And I've tried nearly every variation that's been suggested anywhere: with spaces before and after the "=", adding the line ending with "0" first then rebooting then changing the end to "1" then rebooting, putting an empty line at the end of build.prop before adding the edit. No change. Is there any history of an app interfering with this edit? I don't have anything exotic installed I don't think but I use a third party launcher (Go Launcher EX) and then a variety of apps, mostly audio/video, social media and a few basic games. I believe that changes to build.prop take place "below" that kind of activity, though, right? And besides, I made the edit before I installed any of that stuff. I may try a hard reset or something like that but if this works for everyone else then I must just be missing something.
Click to expand...
Click to collapse
I just noticed this (missed it first scan through) that you use Go Launcher as well. I do also and am having same issue. I am going to try switching to Apex, Nova or other to see if that is the culprit. If so, I can most likely get used to another custom launcher to gain the extra space.
BUT if anyone doesn't have issues AND is using Go Launcher, please let us know so we can rule that out.
Thanks
I use nova pro and have the issues.
Sent from a non-apple device.
coolloser said:
I use nova pro and have the issues.
Sent from a non-apple device.
Click to expand...
Click to collapse
I just tried Apex Launcher and had same FC issue. So guess it isn't specific to any of the launchers (was a long shot anyway). This is just really weird. Some folks swear they have it running on stock 4.1.2 (OTA update) rooted, but many of us have the same and can't get it to work.
I saw one thread where someone mentioned you needed to make sure everything is stock, meaning using TB to unfreeze anything you had frozen, and then give it a go. Problem is I'll want to refreeze much of that bloatware from VZW so not sure if that helps or not.
So frustrating......
At this stage in the trail and error I wonder what other variables could be the key. It's not the version (4.1.2). It's not launcher (problems with Go, Apex and Nova plus the stock launcher). Making everything stock didn't help me -- I flashed a brand new version of 4.1.2, installed ONLY Button Savior (for navigation) and Root Explorer (to edit build.prop). Same problems as usual. I assume it's not the rooting utility as I believe only one exists.
OK, how about some weirder ideas. Has everyone done the build.prop edit with Root Explorer? Maybe there's a flaw in that tool. I just tried editing the build.prop to put IN the qemu.hw.mainkeys=1 line, then temporarily suspended root with VooDoo, then rebooted to see if it would behave if it thought it wasn't rooted. Same result. Maybe the guy saying you can't make this work on rooted stock ROMs was right Still, I'll keep looking, and sharing.
lesdense said:
At this stage in the trail and error I wonder what other variables could be the key. It's not the version (4.1.2). It's not launcher (problems with Go, Apex and Nova plus the stock launcher). Making everything stock didn't help me -- I flashed a brand new version of 4.1.2, installed ONLY Button Savior (for navigation) and Root Explorer (to edit build.prop). Same problems as usual. I assume it's not the rooting utility as I believe only one exists.
OK, how about some weirder ideas. Has everyone done the build.prop edit with Root Explorer? Maybe there's a flaw in that tool. I just tried editing the build.prop to put IN the qemu.hw.mainkeys=1 line, then temporarily suspended root with VooDoo, then rebooted to see if it would behave if it thought it wasn't rooted. Same result. Maybe the guy saying you can't make this work on rooted stock ROMs was right Still, I'll keep looking, and sharing.
Click to expand...
Click to collapse
Root Explorer is what I used.
For the other guy having trouble, it hasn't been mentioned yet; did you set the owner and group for the file to root? If the file was ever stored on the sdcard or pushed there then moved, those permissions might make a difference as well. Its a good security measure in the case that it isn't relevant in any case... don't want a wild website writing to your build.prop file, for example.
PantsDownJedi said:
Root Explorer is what I used.
For the other guy having trouble, it hasn't been mentioned yet; did you set the owner and group for the file to root? If the file was ever stored on the sdcard or pushed there then moved, those permissions might make a difference as well. Its a good security measure in the case that it isn't relevant in any case... don't want a wild website writing to your build.prop file, for example.
Click to expand...
Click to collapse
I used ES File Explorer (and then you have to use Root Explorer menu option to set r/w prior to opening build.prop).
Regarding the rest of the post above. Not sure what the question is. I never did anything to the build.prop file other than set ES File Explorer to r/w on everything, then edited the build.prop file, saved, checked to ensure it was edited right, then rebooted. So the 'file' has never been anywhere other than in /system. When I check the properties on the build.prop file I see rw- r-- r-- (this the same whether or not /system is set to RW or just RO). I believe these are correct (default) settings, but let me know if that is not correct.
Anyone out there that has this working on Stock 4.1.2 it would be nice to know more (i.e. is 4.1.2 the OTA or leaked version, did they use motochopper root method (only one I thought), persmissions on file, where did they place the qemu line in the file, etc, etc).
---------- Post added at 11:33 AM ---------- Previous post was at 11:21 AM ----------
PantsDownJedi said:
Root Explorer is what I used.
For the other guy having trouble, it hasn't been mentioned yet; did you set the owner and group for the file to root? If the file was ever stored on the sdcard or pushed there then moved, those permissions might make a difference as well. Its a good security measure in the case that it isn't relevant in any case... don't want a wild website writing to your build.prop file, for example.
Click to expand...
Click to collapse
BTW... anyone look into testing the framework-res.apk option? Sounds in-depth and much more work (not to mention chance of screwing things up). It would be new to me to decompile, etc, etc, but am not scared to try, just thought I would ask if anyone else already has. Also, not sure if that option is for the 4.1.2 OTA version (verizon in my case).
Thanks.
surfmly said:
I used ES File Explorer (and then you have to use Root Explorer menu option to set r/w prior to opening build.prop).
Regarding the rest of the post above. Not sure what the question is. I never did anything to the build.prop file other than set ES File Explorer to r/w on everything, then edited the build.prop file, saved, checked to ensure it was edited right, then rebooted. So the 'file' has never been anywhere other than in /system. When I check the properties on the build.prop file I see rw- r-- r-- (this the same whether or not /system is set to RW or just RO). I believe these are correct (default) settings, but let me know if that is not correct.
Anyone out there that has this working on Stock 4.1.2 it would be nice to know more (i.e. is 4.1.2 the OTA or leaked version, did they use motochopper root method (only one I thought), persmissions on file, where did they place the qemu line in the file, etc, etc).
---------- Post added at 11:33 AM ---------- Previous post was at 11:21 AM ----------
BTW... anyone look into testing the framework-res.apk option? Sounds in-depth and much more work (not to mention chance of screwing things up). It would be new to me to decompile, etc, etc, but am not scared to try, just thought I would ask if anyone else already has. Also, not sure if that option is for the 4.1.2 OTA version (verizon in my case).
Thanks.
Click to expand...
Click to collapse
I was kind of just pulling at straws, and trying to answer two posts at the same time, sorry for the confusion. My habit, especially before unlocking the bootloader, is to push things to the sdcard then moving them and setting the right permissions and assingining the correct group and user.
As you've explained things, I don't know why it shouldn't work. Mine is a 4.1.2 OTA. It was originally rooted before upgrading and using Voodoo root keeper but between that and Supersu paid version I was able to reinsert root again after a factory reset, which was a stroke of luck as others lost it. I don't think it would matter which root method is used but I could be wrong; esentially its just allowing us to access the build.prop file to edit at all. I don't remember if I had modified the build.prop before or after the reset. I know that it was working both before and after I unlocked the bootloader though. As for the placement of the line, I put it at the end. I also, out of habit, hit enter for a new line for this type of thing. Afterwards, though, there is now new things that Pimp My Rom has inserted (Some of the tweaks in that package are old and I'd advise people to stick with close to stock as possible when using it unless they know what those lines mean; and there's some build.prop myths still floating around XDA that are not good ones, one of which I know Pimp My Rom uses and looks pretty apealing to select). So, now I have some stuff after it. If there were other things added to your build.prop, then perhaps moving the line to the end of where the default configuration ended... grabbing at straws again with this last sentance but in the lack of information I'm just trying to be helpful
Perhaps if people also with this problem, in addition to answering your question about the root method they used, also posted which carrier branding they had it might reveal something, or rule it out. <-Put that in bold for you
I am VZW with Nova Pro, and I get the systemUI FC as well. After much research, I haven't heard of too many people with PHONES that have been successful in this hack, so I tried it on my GTab 2, and same thing.
After spending entirely too much time looking into this, I purchased Full!Screen+, set the apps that I wanted full screen, and I'm set (oddly enough, this didn't work on my GTab, so I also purchased Hide Bar for that device. I prefer FullScreen+ because the truth is, there's only certain apps that I care about being full screen (Netflix, games, youtube...).
The biggest problem with FS+ is that it hides the notifications. Honestly, I don't really care about that either when I'm doing one of these other activities. After all, we have a notification light.
Bought a new nexus 7 yesterday (after having my old one stolen...) and I decided to root and install AOKP JB MR1 Milestone 1. I'm really impressed with it but I was surprised to find the AOSP browser rather than Chrome and a lack of Performance Control.
I tried to install Chrome as a system app (download from Play, push from /data/app to /system/app and set permissions to rw-r--r--) and rebooted. I was again surprised when I found that "Chrome's installation was incomplete." It worked fine in /data/app but I am now curious as to why it won't work in /system/app. (Sorry if this sounds nooby, I haven't dealt with rooting Nexus devices before, I only rooted my crappy old GT-S5830)
Does anyone have a solution? Missing lib files or something else that I need to transfer over?
And as a sidenote, is Performance Control compatible with the N7 on this build? And does anyone have a working version of it?
why are you trying to force it to be a system app? what benefit do you think its going to give you?
Pirateghost said:
why are you trying to force it to be a system app? what benefit do you think its going to give you?
Click to expand...
Click to collapse
No major benefits, but it does save some space on the data partition (and my system partition is only half full). I'm just curious as to why it won't execute properly when installed and upgraded as a system application. I'm fine with having it in /data/app, I was just curious.
Anyone have an answer?
I found THIS
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