Database Users

[MMS][MOD] Softbank Japan HTC Sense & Stock Mms app (updated 7 Nov)

These are confirmed working ONLY on the Android version listed below on the SOFTBANK network in JAPAN and requires ROOT ACCESS unless you are already on stock Android
SMS's and MMS's in Japan are called S'Mail. The main difference is this: You can either enter the phone number or the email of your recipient and any length of text or attachments can be sent (Works like emails, but it also uses phone numbers as an address). The problem is that unless your Rom or phone comes from Japan, you will be limited to SMS functionality only, if you are lucky.
The main problem is that the company requires a specific useragent to be specidied by the messaging app. I use Softbank here in Tokyo so I have made some tweaks get the apps to work for a few versions of Android that I have been using. I thought I would share them in the hopes of helping others out too.
ICE CREAM SANDWICH - Android 4.0.x
Stock / AOSP Android
View attachment Mms-ICS-4.0.4.apk - From stock Android 4.0.4 with only the user-agent changed. (Updated 20 Aug 2012)
View attachment Mms-ICS+Emoji.apk - Styled work from here, and useragent changed by Kremlin987(Updated 3 June 2012)
HTC Sense Instructions
I have finally found a way to get the stock Sense messaging app to work. It actually works much better than the stock android once you get it going. There is no app to install. Sense copies the UserAgent information from a default file into it's internal database the first time you boot your phone after a factory reset or new installation (data wiped). The Stock app reads the database to get the UserAgent. I created a recovery flash-able file to make it easier.
Flash View attachment SoftbankSenseUserAgent.zip (Taken from ARHD 4.1.1) or View attachment SoftbankSenseJBUserAgent31.zip (Taken from ARHD 31-4.2.2) after a full data wipe or after fresh install (FLASH BEFORE FIRST BOOT) - (Updated 4 Sep 2012)
After flash, boot device for first time.
Don't forget to add your Softbank APN details.
DONE
You can do this on your phone before you do a factory reset or edit a ROM.zip before you flash it. The IMPORTANT thing is that it's a factory reset or completely fresh (data-wipe) install. Once booted and your APN is entered the stock app should work nicely.
USEFUL TIP: Once you get this working once. Use Titanium Backup App to backup "Customization Settings Provider". Restore this on any sense ROM after this and your messages will work. This is handy if flash often and don't have time to unzip each new ROM.
JELLY BEAN - Android 4.1.x
Stock / AOSP Android
View attachment 1265527 - From stock Android 4.1.1 with only the user-agent changed. (Updated 20 Aug 2012)
HTC Sense Instructions
Exactly the same instructions as the above Sense Ice Cream Sandwich instructions, except please use this file: View attachment 1458044
INSTRUCTIONS FOR INSTALLING THE APPS:
Try this first - just download and install the apk. If the install has no errors this is the easiest way. Your good to go.
If you get an error message - (Your phone MUST have root access from here)
1. Delete the Message app from your /system/app folder (Could be Mms.apk or something different with other providers)
2. Copy and paste the downloaded MMS.apk into the system/app folder and change permissions to match the other apps in that folder
OR
2. Restart your phone and install the downloaded app as usual.

OMG, I have tried so many times with adb and apktool but just couldn't get it done!
Thanks!
Sent from my Galaxy Nexus using Tapatalk 2

Yeah it took many tries, but it worked when I changed the URL in the res/xml/config as well as the useragent.
Sent from my HTC Desire using XDA

thanks for the help..
i was using Softbank mail client before but it wont work in ICS..
this works..

i have an issue. I am not able to download attachments. if the mail dont have attachments, i can get it.. but if it have some images attached, it says downloading failed.. anything i should do?

fake_japanese_guy said:
i have an issue. I am not able to download attachments. if the mail dont have attachments, i can get it.. but if it have some images attached, it says downloading failed.. anything i should do?
Click to expand...
Click to collapse
Do you have a silver or black sim card? Which APN are you using? I can only vouch for the silver sim card with the "open.softbank.ne.jp" APN. This downloads pictures.
I don't think the MMS app was designed to be able to download other types of attachments like gmail. I'll look into it though.
Edit: looked into it. Only pictures as far as I can tell.

Here's my Mms.apk for ICS - I modified one that has Emoji support (and changed the UserAgent and URL for Softbank compatibility). Have tested receiving and sending MMS and it works fine.
It is styled after Sense and so has avatars and speech bubbles:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Brilliant thanks! I was going to do this for my new One X that arrives tomorrow. I'll put it into the first post with credits to you. Just let me know if this isn't ok.

That's fine by me. I can't take the credit for actually making the app, I got it from here, and modified the config files to use the correct user agent strings. I hope people find it useful.

I have unlocked and rooted the HTC One X (International) by All-in-One Root Tool. Still with stock ROM/Kernel, SuperSU v0.90 and CWM recovery v5.8.4.0.
But would you mind providing an instruction how to install the MmsEmoji.apk?
First rename it into Mms.apk, then use ES file explorer to install the downloaded apk, it says "an existing package by the same name with a conflicting signature is already installed".
Then try to mount system/app into R/W with the mount/system app from Google Play. Still cant copy the mms.apk into system/app folder.
PS. Watching Thunder vs Heat in the same time is not very productive
Kremlin987 said:
That's fine by me. I can't take the credit for actually making the app, I got it from here, and modified the config files to use the correct user agent strings. I hope people find it useful.
Click to expand...
Click to collapse

Changes?
What changes did you make to the source code?
I'd like to keep building this myself when versions get changed.
I did change the User Agent to iPhoneOS, but you are talking about some URL as well. What file is this, and what do i change it to?
Thanks!

@BrianInfo,
Sure. Your phone does need to be rooted, so you can remount /system/app read/write. I always do it from the bootloader, where my desire's system partition security is off. Then you can just
adb push EmojiMms.apk /system/app/Mms.apk and reboot.
You can probably do it from Android if your system partition is not security protected (S-OFF), by going to a shell, remount /system rw, and then deleting Mms.apk and putting the modified one in its place. You will need to reboot after that, though.
@viddy,
I used apktool to unpack the source code. The file you need to edit is res/xml/mms_config.xml.
Change the userAgent entry to
Code:
<string name="userAgent">iPhoneOS/3.0 (7A341)</string>
and then change the uaProfUrl to
Code:
<string name="uaProfUrl">http://www.google.com/oha/rdf/ua-profile-kila.xml</string>
I also had a problem where I could receive but not send due to the maxMessageSize being set too high. It's currently set at 307200, which is working fine. maxImageHeight is 768 and maxImageWidth is 1024, but you could probably play around with those if you wanted to see what the maximum allowed image dimensions/message size is according to Softbank. I pinched those values from dombayo's Mms.apk, and they work fine.
Then just rebuild it using apktool, and sign using jarsigner, after doing a zipalign. You're good to go!

With this it let's you be able to see emojis from iPhones? Or just allows you to send
Sent from my MB855 using XDA

Jaemo, it does both. You can also use emoji in your messages.

BrianInfo said:
I have unlocked and rooted the HTC One X (International) by All-in-One Root Tool. Still with stock ROM/Kernel, SuperSU v0.90 and CWM recovery v5.8.4.0.
But would you mind providing an instruction how to install the MmsEmoji.apk?
First rename it into Mms.apk, then use ES file explorer to install the downloaded apk, it says "an existing package by the same name with a conflicting signature is already installed".
Then try to mount system/app into R/W with the mount/system app from Google Play. Still cant copy the mms.apk into system/app folder.
PS. Watching Thunder vs Heat in the same time is not very productive
Click to expand...
Click to collapse
Go to the HTC MMS app with you root explorer. Rename to MMS.bak or delete the file. Then do either of these 2 steps:
Copy and paste the new MMS.apk into the system/app folder and change permissions to match the others in that folder OR
Restart your phone. After this just click MMS.apk and it should install normally.

will this work for Sprint?

none of these are working for me?!

Jaemo, what specifically isn't working? Emoji? Sending mms? These apks are made specifically for Softbank's network, and while they may work on sprint, we can't test that. You're probably better off getting one of the emoji-enabled mms.apk files linked from one of my posts on the first page, which is not modified to work with Softbank. But we'll need more info if we are to help you effectively. What have you tried?

Kremlin987 said:
Jaemo, what specifically isn't working? Emoji? Sending mms? These apks are made specifically for Softbank's network, and while they may work on sprint, we can't test that. You're probably better off getting one of the emoji-enabled mms.apk files linked from one of my posts on the first page, which is not modified to work with Softbank. But we'll need more info if we are to help you effectively. What have you tried?
Click to expand...
Click to collapse
it seems as if iPhone users still can't see the emoji i've sent.. I'm using jokersax's ics rom cm9 and i was able to send emoji but iPhone users still can't see it they say it gives them the box symbol.

it seems as if iPhone users still can't see the emoji i've sent.. I'm using jokersax's ics rom cm9 and i was able to send emoji but iPhone users still can't see it they say it gives them the box symbol.
Click to expand...
Click to collapse
Are you in Japan? Are you using Softbank? If yes, please write down the steps you took.
This won't work on sprint in the USA. Its only for Japan.

[B][Guide]Noob Guide To Set File Permission's[/B]

Hey Guys i have often seen lot of Question regarding the same "How to set the file permission,sorry i am a noob please explain?"
well this we come across on all threads, at some given point of time.
Reason being simple that we suggest some people to do as said below:
Hey,
1) copy the file XXXX to your Internal or External sd-card.
2) push the file XXXX to sytem/xxxx folder.
3) set permissions to rw-r--r-- blah blah blah.
4) reboot your phone and see.
Then comes the question again from the same people as below:
Hey,
1) I have done accordingly, but really confused regarding File permission though please explain?
2) How to set File Permission?
3) what is rw-r--r-- blah blah i cannot get it? etc.
So this Simple Guide will defenetly help the people with the same.
In order to set the file permission all you need is to have Root explore/Browser or similar type of File manager app been installed on your phone, with Root access.
when you open the File manager you see all your files and folder listed there, thats not our main concern, but something below each one of those file's or folder's, what we are really interested in like:
under say Data folder you see something like 'rwxrwx--x' which is of real concern here.
when you long press on the same Data Folder a pop appears as below
Fig 1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and when you select Permissions in that pop up menu it appears as below.
Fig 2
as you can see in the pic above the permission is set to 'rwxrwx--x' (771 according to Table below)
So in order to set the right Permission for a file, after you have copied the file to the relavent folder, all you have to follow is the below steps and also the Table guide below it.
1)Any File Manager app like Root Explorer/Browser,Es-file explorer installed with root access.
2)Find the File which you have copied to the appropriate Folder for which you have to set Permissions with the above installed file manager app.
3) Long press on the file to open a pop up menu as shown in Fig 1 above.
4)Set Permission accordingly ( been suggested by people for you) using the table guide below as reference.
5) Then reboot your phone for the same (Permission set) to take effect.
Table Guide for Reference
----------------------------------
No- Box is Unchecked, Yes- Box Checked
So, for example:
777 is the same as rwxrwxrwx
755 is the same as rwxr-xr-x
666 is the same as rw-rw-rw- and so on.
I do hope this Guide will come in handy to all those people who want to set filepermission, but need some clarity upon the same.
All Credit to Sun90 for his Excellent Tutorial on 'Understanding File Permissions' which being an inspiration for me to make this Guide in Galaxy S3 section.
Sun90 original thread here http://forum.xda-developers.com/showthread.php?t=1857648
And also like to Thank the XDA for this wonderfull Knowledge based Site.
All constructive Comments to improve the same by my fellow Member's are Welcome

Hey Nishu a good begining ma8:good:
PS- send a request PM to ur galaxy S3 FSM(Forum Specific Moderator) to make this thread 'Sticky' else it will be lost in no time

Sun90 said:
Hey Nishu a good begining ma8:good:
PS- send a request PM to ur galaxy S3 FSM(Forum Specific Moderator) to make this thread 'Sticky' else it will be lost in no time
Click to expand...
Click to collapse
Thanks for suggestion...I thought they will automatically make it sticky now i will send them a PM about this.
And again a big thanks to your Sir because without you this thread not possible :good:

Good work mate..but the real concern is to make people read it..

zoot1 said:
Good work mate..but the real concern is to make people read it..
Click to expand...
Click to collapse
Lol, that very True, they even create a new thread below this very same one saying 'Please Help how to set File permission i am a noob and new here'!!!!!!!

zoot1 said:
Good work mate..but the real concern is to make people read it..
Click to expand...
Click to collapse
Sun90 said:
Lol, that very True, they even create a new thread below this very same one saying 'Please Help how to set File permission i am a noob and new here'!!!!!!!
Click to expand...
Click to collapse
yeah That is why This type of tutorial thread must be sticky :angel:

Maybe u can also add the value for each permission in the OP....ie
Read (r) has value 4..
Write (w) has value 2..
Execute (x) has value 1..
This wud make it easier to understand n corelate between the numerical and alphabetical permission values...
Eg. rwxrwxrw- = 776 bcoz of above.
Sent from my GT-I9300 using xda app-developers app

Manually "fixing permissions" is better left to more experienced and advanced users. Most CWM recoveries have "fix permissions" under "advanced" item in the menu that does a fine job. This is not to take any credit from you for a useful thread you have started but just adding a word of caution.
Sent from my GT-I9300 using xda app-developers app

sathkartha said:
Manually "fixing permissions" is better left to more experienced and advanced users. Most CWM recoveries have "fix permissions" under "advanced" item in the menu that does a fine job. This is not to take any credit from you for a useful thread you have started but just adding a word of caution.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Pal CWM file permission and this file permission are different
Suppose u have to replace any system app. Can u tell me what steps u follow ??

Nishu_gamer said:
Pal CWM file permission and this file permission are different
Suppose u have to replace any system app. Can u tell me what steps u follow ??
Click to expand...
Click to collapse
All I am saying is this is serious business,certainly not for 'noobs'.Besides,you have discussed only data apps and not system apps.I have been on Android since the donut days and am personally comfortable with tinkering around.
Now to your question,if you have to replace any system app,you begin by getting into the system apps folder to rename the old app(as against deleting it,just in case),fix the permissions of the replacement app outside the system app folder and then copy that into the system folder.
Someone skips a step and gets into FCs!
Which is why something like ROM Manager is used efffectively for fixing permissions.
Like I mentioned before,this is not to challenge your post in anyway but only to advocate caution...any guide for noobs must anticipate pitfalls and give a work around...
Best wishes.

sathkartha said:
All I am saying is this is serious business,certainly not for 'noobs'.Besides,you have discussed only data apps and not system apps.I have been on Android since the donut days and am personally comfortable with tinkering around.
Now to your question,if you have to replace any system app,you begin by getting into the system apps folder to rename the old app(as against deleting it,just in case),fix the permissions of the replacement app outside the system app folder and then copy that into the system folder.
Someone skips a step and gets into FCs!
Which is why something like ROM Manager is used efffectively for fixing permissions.
Like I mentioned before,this is not to challenge your post in anyway but only to advocate caution...any guide for noobs must anticipate pitfalls and give a work around...
Best wishes.
Click to expand...
Click to collapse
OK

nice start manoj.. btw what happened to your fingers in your profile pic

No WR premision for entire External SD card
Hi Guys, could someone help me with write permission for external sd card? I'm not sure how and when I made this problem but currently I cannot write to external sd card. I noticed issue when I tried to take picture and I got info that picture cannot be saved on external SD card as I don't have permission...

Useful
Sent from my GT-I9300 using xda app-developers app

bala_gamer said:
nice start manoj.. btw what happened to your fingers in your profile pic
Click to expand...
Click to collapse
Nothing lol

Nishu_gamer said:
Nothing lol
Click to expand...
Click to collapse
nice one manoj....

OTA update could not verified

hi
i m in 14?4.A.0.108 second edition on z1 compact and root and cwm and xposed instaled
j ever do my update with ota but at this time after update my phone says " could not verified" and the new firmware 14.4.A.0.157 is not installed
my bootlooder is locked and j didnt understant what is the propleme !!!!!
can you please help
thank you

You need to go back to stock before the OTA will install.. That means no xposed and any apps that you've uninstalled that came with the ROM need to be installed again..
A factory reset could do it, but if you do that then you will lose all your user data.. So make backups of everything you want to save before you do that.
If that doesn't work then you'll have to completely reflash the stock ROM, then try to download the OTA.. But that would be senseless as you'd be saving yourself time and downloads by just flashing the updated stock ROM

did you deodexed your rom? i have xposed, SU, recovery installed, but got no problem update to 157 via OTA...

I had the same problem, just install the new update via PC companion, you won't loose any data. One thing you'll loose is root
Sent from my D5503 using XDA Free mobile app

My room is bot deodexed i understant nothing ????

Nobody know what is thé probleme with this update could not verified message.?

Hey i have the same problem! I just dont have high speed internett to figure out what it is. Or download ftf.

I have the same problem, some one with one solution, of any one knows if it worth it?
Sent from my D5503 using XDA Free mobile app

PC Companion is the Solution?
I recently had drama of a similar nature - used PC companion successfully as a workaround.

If is here someone, who still has this problem, look into /cache/recovery/fota/ and open "report" file. If you are not able to open this - it ends with error, just copy it into internal storage or SD Card.
First of all, you need to find a lines which looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The important part is rb_file_open[4]. If this line ends with "could not stat file" or someting like this, you need to download this zip https://drive.google.com/file/d/0B-79RLdvfasJMV9ZM2dfVEZtRnM/view?usp=sharing and copy/paste the missing file into your system. Don't forget to change permissions RW+R+R
If this won't help, you probably also have installed 4k mod and your "report" file looks exactly the same like the what I post above.
So, if yes, than download this zip https://mega.co.nz/#!QZYkGZZR!BL9dkTpPzPcClEz8our776jpXpia827mYEd5lCM3OvI and replace all files in your system with the files in this zip. Again, don't forget to change permissions RW+R+R and reboot your phone.
Now you should be able to update your phone with/over OTA. Thanks pcpepik from xperia.cz

Thanks play3man.
just by going through your post i was directed in the right way for resolve this issue. Though i did not follow the exact steps that you mentioned, but, the "rb_file_open[4]" really helped. Here is what i did:
1. Using ES File Explorer i navigated to /cache/recovery/fota/ and opened "report" file
2. Went all the way down (actually somewhere almost 3/4th down) and located the line rb_file_open[4]
3. This line actually said it is trying to open the Build.Prop file and mentions the size of that file in the end of that line.
4. I suddenly remembered that i had edited my Build.Prop file a few weeks back for some testing (ro.ril.enable.dtm=1) Like i said i was doing some testing. Though this setting does not work with my Mobile Service Provider (Airtel) here in India for 2G Networks. But I had kept the setting as it is and never bothered reverting it.
5. So what i did was, edited my build.prop file again and reverted that setting by deleting this line which i had added a few days back.
6. Rebooted my phone
7. Downloaded the OTA again, and tried installing it.
8. And it was a great success . LOL It Worked!!!!
So basically, this error, "Could not verify", could also simply mean that the System files are missing/corrupt or as simple as modified by the user and hence the verification could not complete. So people who have their Build.Prop file modified by one means or other (Manually, Scripted, or by Xposed) You may face this issue and may want to try this method and then make all those settings in build.prop file after installing the update. You could also temporarily revert the old build.prop file which you may have backed up somewhere before modifying it.
Hope this helps!!!

adarpatel said:
Thanks play3man.
just by going through your post i was directed in the right way for resolve this issue. Though i did not follow the exact steps that you mentioned, but, the "rb_file_open[4]" really helped. Here is what i did:
1. Using ES File Explorer i navigated to /cache/recovery/fota/ and opened "report" file
2. Went all the way down (actually somewhere almost 3/4th down) and located the line rb_file_open[4]
3. This line actually said it is trying to open the Build.Prop file and mentions the size of that file in the end of that line.
4. I suddenly remembered that i had edited my Build.Prop file a few weeks back for some testing (ro.ril.enable.dtm=1) Like i said i was doing some testing. Though this setting does not work with my Mobile Service Provider (Airtel) here in India for 2G Networks. But I had kept the setting as it is and never bothered reverting it.
5. So what i did was, edited my build.prop file again and reverted that setting by deleting this line which i had added a few days back.
6. Rebooted my phone
7. Downloaded the OTA again, and tried installing it.
8. And it was a great success . LOL It Worked!!!!
So basically, this error, "Could not verify", could also simply mean that the System files are missing/corrupt or as simple as modified by the user and hence the verification could not complete. So people who have their Build.Prop file modified by one means or other (Manually, Scripted, or by Xposed) You may face this issue and may want to try this method and then make all those settings in build.prop file after installing the update. You could also temporarily revert the old build.prop file which you may have backed up somewhere before modifying it.
Hope this helps!!!
Click to expand...
Click to collapse
Yes, if you have done some more changes in your system, you may have different "error"

play3man said:
If is here someone, who still has this problem, look into /cache/recovery/fota/ and open "report" file. If you are not able to open this - it ends with error, just copy it into internal storage or SD Card.
First of all, you need to find a lines which looks like this:
The important part is rb_file_open[4]. If this line ends with "could not stat file" or someting like this, you need to download this zip https://drive.google.com/file/d/0B-79RLdvfasJMV9ZM2dfVEZtRnM/view?usp=sharing and copy/paste the missing file into your system. Don't forget to change permissions RW+R+R
If this won't help, you probably also have installed 4k mod and your "report" file looks exactly the same like the what I post above.
So, if yes, than download this zip https://mega.co.nz/#!QZYkGZZR!BL9dkTpPzPcClEz8our776jpXpia827mYEd5lCM3OvI and replace all files in your system with the files in this zip. Again, don't forget to change permissions RW+R+R and reboot your phone.
Now you should be able to update your phone with/over OTA. Thanks pcpepik from xperia.cz
Click to expand...
Click to collapse
Thank you for your help
I didnt find this .....rb_file_open[4] in the report file
I have just rb_file_open[0] and [1]
Im rooted locked bootloader deoxd cwm
I have 4k and timeshift video
Sorry for my bad english

BASHARAWAD said:
Thank you for your help
I didnt find this .....rb_file_open[4] in the report file
I have just rb_file_open[0] and [1]
Im rooted locked bootloader deoxd cwm
I have 4k and timeshift video
Sorry for my bad english
Click to expand...
Click to collapse
The second line ([1]) ends with could not state file? If yes, continue from that line with steps from my original post
You have deodexed rom, so the phone is probably missing way more original files, so that's why it ends already on second line

For me OTA updater complains about
rb_file_open[4]: //system/priv-app/psmselfupdater.odex
and apk, but the system dump you provided doesn't have it.

kentaurest said:
For me OTA updater complains about
rb_file_open[4]: //system/priv-app/psmselfupdater.odex
and apk, but the system dump you provided doesn't have it.
Click to expand...
Click to collapse
I have the same error on a stock Z1C, only rooted. I think if we could get the file from somewhere we could drop it on and the OTA would complete, and we'd probably keep root ?

Thank you for the /cache/recovery/fota/report trick. It seems my phone was missing /system/app/SonyEntrance.odex and .apk - I am not sure how this happened or what those files are for.
Edit: Seems it's because I removed 'What's New' :cyclops:

[GUIDE] Using TortoiseSVN and WinRAR to build Leedroid Rom

I have seen a lot of questions and issues with successfully building LeeDroid Rom using SVN. Here is a short guide for building and syncing using Tortoise SVN and zipping up a flashable zip with WinRAR on Win 10. This should work equally well on any other Win version. Mac users are on their own. This guide will aim to get you started, it is by no means comprehensive. Follow the guide carefully. It will take a few hours to complete it the first time through, mostly because of the time it takes for an initial sync, but the following syncs and builds should only take about five minutes from sync to flashable zip.
1. Download the latest TortoiseSVN and install it - I encourage you to read the website when you have the opportunity, especially reading the PDF for your language in the Support/Docs section.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Create a folder for syncing to. I create a folder in the root of my C: drive and just name it "LeeBuilds". Feel free to name it how you please. Inside the LeeBuilds folder, create two folders. One for syncing to and one for output. So I made two folders, "Sync" and "Output".
3. Go to the LeeDroid website and select your device. In this case the U11, so click on U11.
4. After clicking on U11, a pop-up window will appear with an SVN address. Highlight the URL and right-click to copy it. DO NOT include the "[email protected]:~$" portion, only the part beginning with "svn..." and ending with "...trunk". *Remember to check the URL closely after copying to TortoiseSVN to be sure you sync the correct device*
5. Go back to the sync folder you created and right click on it and hit "SVN Checkout".
Since you copied the SVN URL from the LeeDroid site, the URL to sync with will be automatically populated. *BE SURE to closely double check the URL and make sure it points to the U11. You don't want to sync for the wrong device!* Simply tap ok and you will begin to sync. You can always go back to the Leedroid site to copy the URL again if needed. Again, be sure to not include the "[email protected]:~$" portion. Depending on internet speed, an initial sync can take 15 minutes to a couple hours to complete.
----a standard SVN sync in progress window looks like this
6. After syncing is complete, you will see the LeeDroid rom version number you are synced to.
7. You can now close the SVN sync window and right-click on the Sync folder again. Move the cursor over "Tortoise SVN" and click on "Export".
-----There are hidden files and folders in your sync folder. You MUST use the "Export" function to include only files and folders needed for making a flashable zip.
8. Select your Output folder to export to and tap "Select Folder". Your export will begin.
9. After the export finishes, you're done with the syncing part! Download and install the latest WinRAR.
10. Go to your output folder and select all the files including the boot.img in the folder, right-click on your selection, move the cursor to WinRar and select "add to archive".
11. In the pop-up, be sure to hit the "zip" radio button and rename your zip to whatever you like and then hit "ok".
You're finished! Transfer the zip to your phone and flash in recovery like normal. For following updates, right-click the sync folder and an "SVN update" option will appear in the context menu. Click the update button, delete the files that were in your output folder, export to the output folder and then zip and flash. You can always refer to the steps above if you encounter an error somewhere or need to start over. Hope this helps.

Thank you for the guidance! It's very detailed and easy to use!

DroidIt! said:
I have seen a lot of questions and issues with successfully building LeeDroid Rom using SVN. Here is a short guide for building and syncing
You're finished! Transfer the zip to your phone and flash in recovery like normal. For following updates, right-click the sync folder and an "SVN update" option will appear in the context menu. Click the update button, delete the files that were in your output folder, export to the output folder and then zip and flash. You can always refer to the steps above if you encounter an error somewhere or need to start over. Hope this helps.
Click to expand...
Click to collapse
Thank you for the guide, I have tried per your instructions but I get a error (see Attach) when I try the initial download. Is it not working or am I messing up? Thanks

dioooi said:
Thank you for the guidance! It's very detailed and easy to use!
Click to expand...
Click to collapse
Great to hear.
hammered58 said:
Thank you for the guide, I have tried per your instructions but I get a error (see Attach) when I try the initial download. Is it not working or am I messing up? Thanks
Click to expand...
Click to collapse
I have seen that before. Sometimes, maybe one in twenty, the connection with the server will time out for whatever reason. What I'd do is just delete your sync folder to make sure it's clean, make a new one and try another sync. You should get a good sync. It CAN depend on your internet connection too.

DroidIt! said:
Great to hear.
I have seen that before. Sometimes, maybe one in twenty, the connection with the server will time out for whatever reason. What I'd do is just delete your sync folder to make sure it's clean, make a new one and try another sync. You should get a good sync. It CAN depend on your internet connection too.
Click to expand...
Click to collapse
Ok thanks will try!

hammered58 said:
Thank you for the guide, I have tried per your instructions but I get a error (see Attach) when I try the initial download. Is it not working or am I messing up? Thanks
Click to expand...
Click to collapse
IT looks like the URLin the pic may be incorrect. It should be:
http://www.renovate-ice.com/svn/leedroid-11/trunk
Try starting again.

jhill110 said:
IT looks like the URLin the pic may be incorrect. It should be:
http://www.renovate-ice.com/svn/leedroid-11/trunk
Try starting again.
Click to expand...
Click to collapse
Uhoh, I was afraid of that. Yeap, you need to CLOSELY check the SVN URL as I say in the guide. I saw the same thing yesterday when I went to copy/paste the URL. It seems for whatever reason it wants to default to the 10. I actually let Lee know about it. I added to check the URL in the guide after I discovered that. Easy fix though, you can just change the "10" in the URL to "11" and you'll be just fine. :good:

DroidIt! said:
Uhoh, I was afraid of that. Yeap, you need to CLOSELY check the SVN URL as I say in the guide. I saw the same thing yesterday when I went to copy/paste the URL. It seems for whatever reason it wants to default to the 10. I actually let Lee know about it. I added to check the URL in the guide after I discovered that. Easy fix though, you can just change the "10" in the URL to "11" and you'll be just fine. :good:
Click to expand...
Click to collapse
Well, it looks correct until after "trunk". There's extra characters. It's fine until then.
Great guide. I'm leaning towards user error on the copy somehow.

jhill110 said:
Well, it looks correct until after "trunk". There's extra characters. It's fine until then.
Great guide. I'm leaning towards user error on the copy somehow.
Click to expand...
Click to collapse
The only thing I see in the pic after "trunk" is a "I". That's just the cursor animation from the website. Do you see more characters after "trunk"?

DroidIt! said:
The only thing I see in the pic after "trunk" is a "I". That's just the cursor animation from the website. Do you see more characters after "trunk"?
Click to expand...
Click to collapse
Yes, /%7c after trunk, then doesn't exist.

jhill110 said:
Yes, %7c after trunk, then doesn't exist.
Click to expand...
Click to collapse
That's really weird. I just tried Lee's site on both Chrome and Edge and didn't see that. I'll let him know. Thanks a ton for the report. :good:

DroidIt! said:
That's really weird. I just tried Lee's site on both Chrome and Edge and didn't see that. I'll let him know. Thanks a ton for the report. :good:
Click to expand...
Click to collapse
It worked perfectly fine for me. First time using tortoise and no problem.

jhill110 said:
It worked perfectly fine for me.
Click to expand...
Click to collapse
Lol, now I'm confused. Worked good with or without the %7c?

Ok, to clinch it all I heard from THE MAN. Either copy/paste and make sure it looks like it does in the pic, or just type it out in the URL field. Any strange characters you might see are PHP used for the cursor animation. Soooo, lol just follow the guide and check the URL when you come to that part. Simple solution.

DroidIt! said:
Lol, now I'm confused. Worked good with or without the %7c?
Click to expand...
Click to collapse
No worries, I'm probably not explaining properly.
I copied "http://www.renovate-ice.com/svn/leedroid-11/trunk"
And it worked great for me.
Looking at the error line in his pic it's :
http://www.renovate-ice.com/svn/leedroid-11/trunk/|.
It appears to be looking for /%7c in the url and not being correct it throws the error.
Like I mentioned it sounds like the url copy got messed up some how for him.

jhill110 said:
No worries, I'm probably not explaining properly.
I copied "http://www.renovate-ice.com/svn/leedroid-11/trunk"
And it worked great for me.
Looking at the error line in his pic it's :
http://www.renovate-ice.com/svn/leedroid-11/trunk/|.
It appears to be looking for /%7c in the url and not being correct it throws the error.
Like I mentioned it sounds like the url copy got messed up some how for him.
Click to expand...
Click to collapse
Ahhh, gotcha. Yeap, should end with the "trunk". Maybe I should add that in the guide. Thanks for the catch.
Edit: fixed on #4 in the guide. :good:

for what do I need the output folder for? if I export, then exactly the same files are included as in the sync folder.
and the data folder is not available for me.

4ntagonist said:
for what do I need the output folder for? if I export, then exactly the same files are included as in the sync folder.
and the data folder is not available for me.
Click to expand...
Click to collapse
There's hidden files and folders in the Sync folder. If you zip up from there you'll likely not have a bootable rom...or it'll be borked. So, that's the propose for the second folder. Not sure what you mean about the data folder though.

DroidIt! said:
There's hidden files and folders in the Sync folder. If you zip up from there you'll likely not have a bootable rom...or it'll be borked. So, that's the propose for the second folder. Not sure what you mean about the data folder though.
Click to expand...
Click to collapse
I have activated hidden files & folders in explorer. You are right, here is the comparison. But I have always packed the files from my one sync folder. If I do not pack the hidden folder .svn, it is exactly the same data. The ROMs have always worked. But I am doing it now according to your instructions. And I meant the folder from your screenshot that you named data, seen in step 11. I do not have it.

4ntagonist said:
I have activated hidden files & folders in explorer. You are right, here is the comparison. But I have always packed the files from my one sync folder. If I do not pack the hidden folder .svn, it is exactly the same data. The ROMs have always worked. But I am doing it now according to your instructions. And I meant the folder from your screenshot that you named data, seen in step 11. I do not have it.
Click to expand...
Click to collapse
Lol, honestly don't know where it came from. I just checked my SVN folders for the 10 and the 11, I don't have it either. Some little buggers to fix up in the pics.
FYI, I figured out that if you copy/paste the URL's from Lee's site to SVN, the URL's are backwards, meaning that if you copy the 11 link, it'll paste the 10 URL into Tortoise and vice-versa. Soooo, statement still stands. Double-check your pasted URL when you do your init sync. If the URL says "10" simply chance it to "11" or whatever you desire and all's good. :good:

[GUIDE] How To Modify Framework-res for WHITE NOTIFICATION TEXT - Noob Version

White Notification Text and YOU
~
How to...
Decompile - Modify - Recompile - Sign
Your Framework-res.apk
~
GET WHAT YOU WANT IN LIFE​
Disclaimer: This is how I went about getting white notification text on my sprint s8+ running @partcyborg's latest U2 Rom. Whatever you do to your device is your business and if you brick your device it is also your fault! I do not take responsibility for your actions. That being said, enjoy! ...at your own risk. MUAHAAHA! ...sry
So basically I followed the instructions @envy~ laid out in his bodhisattva_V3 theme. I'm not a dev by any means so I figured I would record the steps I took when modifying my framework-res to share for us fellow noobs. There's a bunch of color values that can be changed, most of which i'm too lazy to test. Together we may be able to find all the values we need for the perfect white notification text arrangement. Once you get the process down pat, its really quick and easy to crank out zips to test for yourself. word.
Tested on galaxy s8/s8+ with snapdragon. Should work on all kinds of devices, long as you change the right values.
Prerequisites:
-- Need root.
-- download/install apktool and TickleMyAndroid (TMA) and take note of their installed folder locations. Make sure you have latest versions, update apktool by downloading the latest .jar file from their thread and put it in your "apktool" folder. I renamed it from apktool2.0.3.jar to just apktool.jar and that seemed to work nicely.
-- I put TMA and apktool in same parent folder for convenience.
-- Install notepad++ because its pimp, and we use it later.
-- Use a root file explorer to grab your "framework-res.apk" located in (root)/system/framework, copy and paste it to your PC.
-- Make a backup of your framework-res.apk by copy/pasting the file somewhere and add ".bak" to the end of the full filename.
!!!!!!!!!!!!!!!MAKE!!!!!BACKUPS!!!!!!!!!!!!!!!!
If you mess up and get a boot-loop, I believe the(an) easy way out is to just boot into stock recovery and factory reset(then restore). Factory reset wipes your internal SD along with whatever else. So BEFORE FLASHING YOUR MODDED FRAMEWORK-RES, go ahead and backup EVERYTHING. Use TiBu, use flashfire to do a FULL BACKUP. Copy paste your entire internal SD onto your external SD card or on your PC. If you are backed up then you should have no problems moving forward. In fact, if it comes down to it, your phone will be thanking you for the factory reset.
Anyways, If you have a better way to recover from a boot-loop in this scenario please share if you want. If your not familiar with backing up/restoring data (without custom recovery) please reconsider this... "Do I really need white notification text?" If the answer is "yes!" then lets go!
The good thing about this method and using TickleMyAndroid is that TMA will just error out if you messed up somewhere along the process. If it doesn't error out, then you did everything right and the zip should flash fine and boot successfully.
!!!!!!!!!!!!!!!MAKE!!!!!BACKUPS!!!!!!!!!!!!!!!!
Thanks and credit go out to:
@envy~ for his framework fix
@iBotPeaches for apktool
@Ticklefish for TickleMyAndroid
@partcyborg for his incredible GalaxyS8 and GalaxyS8+ Roms
-----------------------------------------------------------------------​
1. Put original framework-res.apk in TMA workarea folder - "C://.../TickleMyAndroid/_workareaX/_in"
2. Open "Tickle My Android.exe" from inside your TickleMyAndroid folder.
Enter 5 - setting menu.
Enter 1 - Change active work area. Enter (#) - Of the Workspace "_in" folder you chose before.
Enter y - for yeah.
Enter x - to go back (twice).
Enter 3 - theming menu.
3. (I DN IF THIS IS NECESSARY, BUT IT MAY BE CRUCIAL, SO DO IT)
Enter 3 - Install Framework on PC.
Enter 1 - (should be your framework-res.apk from inside the ".../_in" folder)
Enter y - for YES FOOL! Press any key...
4. Enter x - to back up to the theming menu.
5. Enter 5 - Decompile files.
Enter 1 - Decompile Files (again).
Enter 1 - framework-res.apk. THEN behold, "...[This Will Overwrite Any Existing blah blee blee]"
Enter y - for YUSSS
6. Decompiling in progress (in second window) If you were too busy to watch this elegant automated miracle of technology happen, and the second window is gone, THIS IS OK, so press any key to continue....
7. Enter x - to back dat azz up, to the theming menu...
8. Enter 1 - Explore "_working" Folder, to explore the decompiled framework-res.apk
9. Navigate to framework-res.apk\res\values, locate "colors.xml" and left click right click to choose "Edit with Notepad++"
10. Here (as recommended by @envy~ in his thread) you can change these three values for a good look. But If you wanna go further to change more text/icon color values that remain unaffected you are going to have to look around, change some other color values and see what happens ya know, trial and error!
Example: If you wanna know what color say "ff669900" is, just google #669900. There's a good site where u can easily grab darker or lighter shades of a certain color value to suit your theming needs. Cool!
11. Ok these are the three values mentioned by @envy~ you can change. I decided to just go all white ("#ffffffff") everywhere I could:
Code:
<color name="notification_title_color">#ff252525</color>
<color name="notification_info_color">#ff8c8c8c</color>
<color name="notification_text_color">#ff515151</color>
Changed to...
Code:
<color name="notification_title_color">#ffffffff</color>
<color name="notification_info_color">#ffffffff</color>
<color name="notification_text_color">#ffffffff</color>
In an attempt to make more stuff white I edited these values too with success...
Code:
<color name="notification_icon_default_color">@color/notification_default_color</color>
<color name="system_notification_accent_color">#ff607d8b</color>
Changed to...
Code:
<color name="notification_icon_default_color">#ffffffff</color>
<color name="system_notification_accent_color">#ffffffff</color>
12. Ok once you are done making history, SAVE it.
13. Enter 9 - Recompile Files.
Enter 2 - Recompile App with Original Signature.
Enter 1 - framework-res.apk
14. To keep any changes to "AndroidManifest.xml" OR NOT TO Keep Any Changes To "AndroidManifest.xml"?... THAT, is the question.
Enter n - FOR NO!
15. Add Recompiled File To ZIP Workspace?
Enter y - for YUP.
16. Enter 4 - Add "system/framework/" File To Project.
Enter 3 - Create Standard Zip File.
Enter y - Creating Standard Flashable ZIP File From Files In Existing Project To Destination Folder: "c:\ticklemyandroid".
Just hit ENTER - to use given filename... or not.
Enter y - Overwrite dat shiii.
17. Recompiling in another window. If it's successful... press any key to continue...
18. Go to C://Ticklemyandroid and grab the latest flashable zip u made, rename if u want (good idea to rename it regarding the colors you chose). Put flashable .zip on Phone and flash via flashfire (choose "flash zip or OTA", select "Mount /system read/write", disable everroot, then flash)
19. and 20. PROFIT
-----------------------------------------------------------------------​
If you guys notice any black text on black background or similar situations... sometimes its the app's theme and sometimes its a sammy theme thing from what I can tell. If yall have little problems/solutions like this and wanna share maybe we can help/learn from each other. Its def not a perfect solution but its better than nothing. I freaking love my white text, amoled black all day son!
I'll Post some screenshots of my results so far in just a sec... this post took forever.... need a break.

Screenshots... yay.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

monroe0328 said:
Screenshots... yay.
View attachment 4438752
Click to expand...
Click to collapse
i use rom control

kin201303 said:
i use rom control
Click to expand...
Click to collapse
Care to be more specific? What rom control are you talking about. Those screenshots look great!

monroe0328 said:
Care to be more specific? What rom control are you talking about. Those screenshots look great!
Click to expand...
Click to collapse
i edit framework.jar + SystemUI.apk
i use rom control to change the colour

kin201303 said:
i edit framework.jar + SystemUI.apk
i use rom control to change the colour
Click to expand...
Click to collapse
Ok, so care to share which values you have changed in either of those? Also still not clear on which "rom control" you are talking about. Is this a rom control included with a custom rom? Is it a play store app?

monroe0328 said:
Ok, so care to share which values you have changed in either of those? Also still not clear on which "rom control" you are talking about. Is this a rom control included with a custom rom? Is it a play store app?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=62296264&postcount=2741
[Guide] Custom Notification Background TEXT Color Android L
edit
framework_yes\smali\android\app
Notification$BigTextStyle.smali
Notification$Builder.smali
Notification$InboxStyle.smali
Notification$MessagingStyle.smali
https://forum.xda-developers.com/android/general/source-code-6thgear-romcontrol-v2-devs-t3411916
[SOURCE CODE][DEV TOOL][SDK 21+]6thGear RomControl v2.+ for Devs

@kin201303
Man tdunham and rompnit are freaking beasts... I was lucky enough to experience their greatness from beginning to end on the s5 MOAR project. In fact my dad still uses my s5, has MOAR rom and ktoons amazing kernel. Still runs great. Haha he doesn't know how lucky he is!
Ahh I remember the good days, real time theming. Literally every bug was annihilated and improved upon. Those guys are great. The most all inclusive rom ever made.
I'll have to spend some time on your recommendation here. May be a bit of a learning curve but I'll figure it out. Good stuff.
My guide was meant for noobs like me. But I welcome more advanced and thorough solutions like this. Thank you so much!

monroe0328 said:
@kin201303
Man tdunham and rompnit are freaking beasts... I was lucky enough to experience their greatness from beginning to end on the s5 MOAR project. In fact my dad still uses my s5, has MOAR rom and ktoons amazing kernel. Still runs great. Haha he doesn't know how lucky he is!
Ahh I remember the good days, real time theming. Literally every bug was annihilated and improved upon. Those guys are great. The most all inclusive rom ever made.
I'll have to spend some time on your recommendation here. May be a bit of a learning curve but I'll figure it out. Good stuff.
My guide was meant for noobs like me. But I welcome more advanced and thorough solutions like this. Thank you so much!
Click to expand...
Click to collapse
this is my guide see the gif

What is this .gif telling me.
Are you saying this tdunham guide for android L is applicable for Andoid N on our s8's?

monroe0328 said:
What is this .gif telling me.
Are you saying this tdunham guide for android L is applicable for Andoid N on our s8's?
Click to expand...
Click to collapse
lockscreen AnalogClock add AnimatingImage

kin201303 said:
lockscreen AnalogClock add AnimatingImage
Click to expand...
Click to collapse
That's cool. I can dig it. I'm more interested in figuring out how to use this rom control. I want ALLL WHITE notification text.

monroe0328 said:
That's cool. I can dig it. I'm more interested in figuring out how to use this rom control. I want ALLL WHITE notification text.
Click to expand...
Click to collapse
example
SystemUI.apk\res\layout
notification_stack_bottom_bar_for_block.xml
<com.android.colayaya.rz.Text android:textSize="@dimen/bottom_bar_button_text_size" android:textStyle="bold" android:textColor="@color/bottom_bar_button_text_color" android:gravity="center_vertical" android:id="@id/block_button" android:background="@drawable/notification_bottom_bar_button_ripple_bg" android:focusable="true" android:clickable="true" android:layout_width="wrap_content" android:layout_height="@dimen/bottom_bar_button_height" android:text="@string/block_notification_text" android:singleLine="true" android:includeFontPadding="false" android:textAllCaps="true" android:fontFamily="sec-roboto-condensed" android:layout_marginEnd="18.0dip" key="colayaya_block_notification_text_color" />
C:\TickleMyAndroid\_WorkArea1\_working\UnclControl_For_S8.apk\res\xml
notification_panel_prefs.xml
add
<com.wubydax.romcontrol.v2.prefs.ColorPickerPreference android:title="block_notification_text_color" android:key="colayaya_block_notification_text_color" android:summary="choose the color
" android:defaultValue="\#ff505050" />
SystemUI.apk have key
romcontrol have key
you want any color
my english is bad

kin201303 said:
example
SystemUI.apk\res\layout
notification_stack_bottom_bar_for_block.xml
<com.android.colayaya.rz.Text android:textSize="@dimen/bottom_bar_button_text_size" android:textStyle="bold" android:textColor="@color/bottom_bar_button_text_color" android:gravity="center_vertical" android:id="@id/block_button" android:background="@drawable/notification_bottom_bar_button_ripple_bg" android:focusable="true" android:clickable="true" android:layout_width="wrap_content" android:layout_height="@dimen/bottom_bar_button_height" android:text="@string/block_notification_text" android:singleLine="true" android:includeFontPadding="false" android:textAllCaps="true" android:fontFamily="sec-roboto-condensed" android:layout_marginEnd="18.0dip" key="colayaya_block_notification_text_color" />
C:\TickleMyAndroid\_WorkArea1\_working\UnclControl_For_S8.apk\res\xml
notification_panel_prefs.xml
add
<com.wubydax.romcontrol.v2.prefs.ColorPickerPreference android:title="block_notification_text_color" android:key="colayaya_block_notification_text_color" android:summary="choose the color
" android:defaultValue="\#ff505050" />
Click to expand...
Click to collapse
This is great and all, but if you really want to help people like me, your gonna have to give some general context of use.
How do you take advantage of rom control specifically for notification text color? Set up process? Forgive me if that's asking to much, but pretend your doing this for your first time. Even if it's a broad step by step summary, that would help put people on track with what you are advising.
Your English is fine tho, thanks!
Is there a gui for rom control, or an apk? Maybe that's what I'm missing here.

monroe0328 said:
This is great and all, but if you really want to help people like me, your gonna have to give some general context of use.
How do you take advantage of rom control specifically for notification text color? Set up process? Forgive me if that's asking to much, but pretend your doing this for your first time. Even if it's a broad step by step summary, that would help put people on track with what you are advising.
Your English is fine tho, thanks!
Is there a gui for rom control, or an apk?
Click to expand...
Click to collapse
you goto download a rom use his rom control
i edit for you
you must understand

kin201303 said:
you goto download a rom use his rom control
i edit for you
you must understand
Click to expand...
Click to collapse
Ahhh I see...
This is NOT anapplication. This is a SOURCE CODE
So you import the ROM somehow and use rom.control to make the changes.
You say you can make the changes for me? All white notification text. If yes what do you need from me?

monroe0328 said:
Ahhh I see...
This is NOT an
Click to expand...
Click to collapse
<TextView android:textSize="@dimen/bottom_bar_button_text_size"
change to
<com.android.colayaya.rz.Text key="colayaya_block_notification_text_color" android:textSize="@dimen/bottom_bar_button_text_size"
file Credits RZ

kin201303 said:
<TextView android:textSize="@dimen/bottom_bar_button_text_size"
change to
<com.android.colayaya.rz.Text key="colayaya_block_notification_text_color" android:textSize="@dimen/bottom_bar_button_text_size"
file thank RZ
Click to expand...
Click to collapse
Is this a flashable with edits for white text? Ok nvm. Like I said, a little over my head. I got buddy who can help me with your advice.

Rom Control?
Hey @kin201303 i was trying to use rom control but keep getting this error " Project with path ':6thgeardebloater' could not be found in project ':app'. "before i can do anything with it at all any ideas?

RealGroot said:
Hey @kin201303 i was trying to use rom control but keep getting this error " Project with path ':6thgeardebloater' could not be found in project ':app'. "before i can do anything with it at all any ideas?
Click to expand...
Click to collapse
Same.