yashsingh1/xdaforums huggingface dataset:
[HTC One X] osm0sis:
No need to duplicate, right? ;)

if [ -f /sdcard/TWRP/theme/ui.zip ]; then
zippath=/sdcard/TWRP/theme;
elif [ -f /int_sd/TWRP/theme/ui.zip ]; then
zippath=/int_sd/TWRP/theme;
fi;

mkdir /cache/twrp;
unzip -o $zippath/ui.zip -d /cache/twrp;
chmod 777 /cache/twrp/zip;
cp -r /cache/twrp/%tw_folder%/* /cache/twrp/images;
mv /cache/twrp/ui.xml /cache/twrp/ui_temp.xml;
sed s/%text_highlight%/#%tw_text_color_highlight%/g /cache/twrp/ui_temp.xml > /cache/twrp/ui.xml;
rm -f /cache/twrp/ui_temp.xml;
cd /cache/twrp;
./zip -0 -r -u $zippath/ui.zip *;
cd /;
rm -r /cache/twrp;

Again, if TWRP or the theme already has some sort of path-to-theme variable built-in, then that would be preferred and can just replace $zippath, AND removes the need for the if logic entirely. :)
[HTC One X] :
And this is what makes XDA what it is lol ;). I had considered using variables but to be honest, I was shocked to even learn that you could use scripts in the TWRP ui.xml from the get go haha.

---------- Post added at 10:19 PM ---------- Previous post was at 10:11 PM ----------

[MENTION=2719389]z31s1g[/MENTION], I would replace what you are currently using with the script [MENTION=4544860]osm0sis[/MENTION] just shared. Look forward to your next release lol. Will have them ported in no time.
[HTC One X] Captain_Throwback:
So where do I put what to fix it, lol ;)?
[HTC One X] :
Take what osm0sis shared and search for line 6756-6766. Replace that script with the more up to date one.

Do the same for lines 9557-9567 as well.
[HTC One X] :
[MENTION=4544860]osm0sis[/MENTION] and [MENTION=2719389]z31s1g[/MENTION], seems the revised script of what I originally shared which osm0sis later modified isn't working properly. Some tests with myself and others are finding results to be not so promising. For now, I would suggest using the script I shared since it's confirmed to work like it should.
[HTC One X] osm0sis:
Must be the variables. Probably some way to fix the parsing of them in the XML. :good:

If anybody will know how it's [MENTION=2719389]z31s1g[/MENTION], dude is the master of TWRP's ui.xml. He probably knows a better TWRP variable or something so that the if logic can be removed altogether. :)
[HTC One X] :
I'm gonna suggest using the script I originally shared lol. Seems to work and if there is one thing I have learned in life it is this:

If it isn't broken, don't fix it

Lol
[HTC One X] DSM_:
Sorry, I've been out of touch these days. Migrated to another state for studies :)

I'm happy to known my color changing script works for all devices, with correct path to ui.zip given.

So ui.zip exist on external SD card?

I don't know if we can get ui.zip path from twrp's XML engine..

I have to take a look.
[HTC One X] Captain_Throwback:
As far as I know, the theme always has to be at /sdcard/TWRP/theme.
[HTC One X] :
Mine is located on the internal. On the external the theme won't work.
[HTC One X] z31s1g:
Title

Best hint ever. :highfive:

Result of investigation

According to above finding, I replaced "/sdcard/TWRP/bla..." with "/%theme_path%/TWRP/bla...". Works just fine. Please confirm. :fingers-crossed:
[HTC One X] z31s1g:
I spoke too soon, it doesn't work. Forgot I need to change the path in two places, after doing so I'm back where I started. Sorry.

Any of you have an idea how to address the TWRP variable from within the theme?
[HTC One X] :
I'm not honestly sure if you can specify both locations because each TWRP build is different depending upon what is required of that specified device. Though, it mat be possible. I personally would have to look in to that myself if I get the chance, otherwise, you would have to specify the location specifically like I did in my script previously before osm0sis revised it. His script technically will work however, running scripts from the recovery can be a bit tricky so because of that his revision won't fully work which is why I recommended mine until this investigation has been properly resolved.
[HTC One X] z31s1g:
Could you please have a look at your TWRP settings file (.twrps). Its in the TWRP folder.

Towards the end, there a variable called "tw_zip_internal". What's its value on your device?
[HTC One X] :
You are on to something ;). Here you go:

tw_use_compression 0 tw_use_external_storage 1 tw_zip_external /sdcard tw_zip_internal /emmc tw_zip_location /sdcard

---------- Post added at 08:32 AM ---------- Previous post was at 08:22 AM ----------

Keep in mind, themes don't work if I place them on my external. Only if I place them on my internal.

---------- Post added at 08:35 AM ---------- Previous post was at 08:32 AM ----------

Crap, [MENTION=2719389]z31s1g[/MENTION], my bad. I shared the wrong info haha. Here you go. One more time.

tw_use_compression 0 tw_use_external_storage 1 tw_zip_external /sdcard tw_zip_internal /emmc tw_zip_location /int_sd
[HTC One X] z31s1g:
That's the one needed. Mine reads /sdcard. If we used %tw_zip_location% in the script, we'd both be save.

Problem is though, I manipulate this variable for the bookmark function on file lists. So we actually can't use it unless I remove the bookmak feature alltogether.

I guess it boils down to hardcoding both paths like you suggested...
[HTC One X] :
Would it be possible to use a different variable for your bookmark feature? This way you don't have to manipulate it? Possibly make up a variable? Seems far fetch but if it would help then that would probably be best and so this way you dont have to hard code the zip paths.
[HTC One X] z31s1g:
Not a far fetch but the last resort. Done, works.

How to:

Search and replace tw_zip_location with tw_flash_location.

On page "partsdcard" is a slider. This is the only place where tw_zip_location must not have been replaced, so now you need to change it back.

Add to variables section:

<variable name="tw_flash_location" value="%tw_zip_location%" persist="1" />

Add to pages "dialog_reset" and "dialog_reset_theme":

<action function="set">tw_flash_location=%tw_zip_location%</action>

In the script, replace /sdcard with %tw_zip_location%

(Note the missing "/"! You need to do it in two places of the xml: on page "set_color" and on page "dialog_color".)

Attached the xml (dark), but it contains more changes than required to test the new script (e.g. new font definitions).
[HTC One X] :
Awesome, this ought to do the trick for now until your brainstorming comes up with another plan and solution down the road but for now this will do :). Thanks man.
[HTC One X] z31s1g:
Does this work for you?
[HTC One X] :
I'm at work so I haven't tried it yet. But looking at the changes I'm pretty sure it will. Though, I will confirm and let you know as soon as I can later on today. I will mention you so you are notified.
[HTC One X] :
[MENTION=2719389]z31s1g[/MENTION], still didn't work..... Don't understand why though... And I still can't wrap my brain around why a twrp theme will not work on my external either, but will on my internal... I'm gonna take a look at the device tree and see what the heck is going on. So far, the only method I have found which works, is the method I shared prior to it being revised by osm0sis.

Grr.....

---------- Post added at 11:31 PM ---------- Previous post was at 11:18 PM ----------

Seems themes will only work on internal if you have both internal and external. So, nothing I can really do about that. Though, still not sure what the deal is after making the modifications.

---------- Post added at 11:48 PM ---------- Previous post was at 11:31 PM ----------

[MENTION=2719389]z31s1g[/MENTION]

Update:

I cleared all TWRP folders. I rechecked my .twrp file and now it says /sdcard and not /int_sd. The vold.fstab file on my device basically wraps the two together. Anyways, if I make a copy of your theme and place it on my external and leave another copy in my internal then change colors from within the recovery it will work, but here is the catch....

It still directs itself to the external. So the ui.zip from there will be modified and then leaves for me to have to copy it over to my internal manually. After which I just restart the theme and voila it works.

In other words, I think the only option at this point is to hard code it as a last resort.
[HTC One X] :
Ok, now I don't know what the heck is going on lol. My .twrp file is saying /int_sd again. But the change wasn't made until I used your theme. Not a big to do and completely meaningless to me so I wouldn't even focus on that. However, I noticed that towards the bottom it says, tw_use_external_storage 1. I wonder if that has anything to do with it? I'm gonna change the value to 0 and try your modification to see what happens.

---------- Post added at 08:51 AM ---------- Previous post was at 08:35 AM ----------

[MENTION=2719389]z31s1g[/MENTION] and [MENTION=1162986]Captain_Throwback[/MENTION]

I found my culprit. The BoardConfig.mk file for my device tree has the following:

TW_DEFAULT_EXTERNAL_STORAGE := true

So, even though I am working off of the internal, all zips, etc are expected to be found on my external since it's set to be the default for my TWRP. I could remove this, make a build, and update the recovery with Dees_Troy, however, since this is something that can be done with other devices and not just my own, a solution needs to be found for others experiencing the same complication as I am.
[HTC One X] z31s1g:
tw_zip_location is beeing continuously updated by twrp. This is where the recovery stores the "last visited folder" information, so the file list alway starts with your last used folder.

Another variable that's not addressed by the the at all is tw_zip_internal. Mine says "/sdcard", yours "/emmc".

In case you are still experimenting with my modified xml from yesterday, replace %tw_zip_location% with %tw_zip_internal% and give it a go.

tw_use_external_storage only seems to indicate the presence of an external sd.
[HTC One X] Captain_Throwback:
According to the TWRP build thread, that flag is "largely deprecated" so it shouldn't be needed.

TWRP should still be looking for the theme zip on internal though (i.e. on /sdcard).
[HTC One X] :
Will try it and let you know. May work around the default setting from my device tree.
[HTC One X] z31s1g:
Interesting. This build flag seems to set the value for tw_use external_storage then.

According to TWRP theme refference:

tw_has_dual_storage - indicates if this device has more than one storage location available.

tw_use_external_storage - indicates whether to use internal or external storage for backup, restore, and zip installs
[HTC One X] Captain_Throwback:
Exactly.

And there's really no need for the build flag anymore since that variable can be set by the theme rather than being hardcoded by the build.
[HTC One X] :
Ok, well, [MENTION=2719389]z31s1g[/MENTION], keep your ui the way you have it now with the mod you made. I will make another build and remove that useless flag which is deprecated and try it again. ;). Those still using the deprecated flag will just have to suffer or make another build.
[HTC One X] z31s1g:
I can't leave it the current way, because as I just found out, tw_zip_location is not as static as I thought it would be.

My guess is that we have to use your script version. Regardless of the flag.
[HTC One X] :
[MENTION=2719389]z31s1g[/MENTION], have you tried using tw_storage_path?

I was looking at your Black theme and when you click on backup it displays the storage from which you can select from. In my case, I can select internal or external. It seems this is set automatically by twrp as it is always on internal unless I tell it otherwise. Maybe using that variable instead would resolve it hopefully. I figured if this works then those who do have options based on storage would just need to simply select the storage where the zip is located, I.e. internal or external, then choose the colored theme. This way nothing is hardcoded. We will see shortly. Been studying the TWRP resource as well.

Check out openrecoveryscript.cpp found at the root of the source, line 206 roughly. May bring some clarity on why I'm looking into this idea. Fingers crossed lol.

---------- Post added at 02:18 PM ---------- Previous post was at 01:53 PM ----------

Hey man, if I select my storage to internal sd then type and enter, %tw_storage_path%, it will display int_sd. If I select my external sd and do the same thing it will display ext_sd. Using this variable ought to solve our problems. It would just be recommended to give instructions insuring that users select the proper storage where the theme is initially found on prior to changing the themes color.
[HTC One X] z31s1g:
I really do appreciate all your input on this matter (and others), so I hope you don't get this wrong:

While your initial script might not be elegant or anything, it does the job. Educating the users they have to set the internal storage before swapping themes is a step back imo.

I've already updated the script as per your initial suggestion and intend to leave it as that.

Also, I currently don't want to tinker on holofied any longer, as it keeps me from progressing with metarialised. Still need to add stuff for the upcoming 2720 update, which is likely to drop within the next couple days.
[HTC One X] z31s1g:
All themes updated

10.09.2014

All themes updated for TWRP 2800

Added support for color in console

Added support for backup / restore progress

Sliders for screen / vibration settings now use images (thanks to Tasssadar)

Revised script for color changing mechanism (thanks to Modding.MyMind)

Added "Decrypt Data" button to mount page (was missing since forever...)

Added "enable / disable MTP" buttons to mount page

Added "refreshfilesystem" page

New .dat fonts with latest version of Roboto

Changed font size for rendered labels of main buttons

Fixed some minor quirks
[HTC One X] z31s1g:
TWRP Materialised BETA

Materialised Themes are available for BETA testing.

Consider this theme a beta version. Things are still likely to change here and there.

Please do not port this beta version to any other devices yet.

If you can test it on an other devices than the HOX, please do so - but don't open threads in other devices sections yet.

If you find anything wrong, odd looking or not working, please report it here.

If you find everything working, please also report it here.

If you want to suggest changes, feel free to do so.

Materialised BETA
[HTC One X] z31s1g:
Materialised BETAs updated

Materialised Themes updated:

fix position of floating action buttons

Consider this theme a beta version. Things are still likely to change here and there.

Please do not port this beta version to any other devices yet.

If you can test it on an other devices than the HOX, please do so - but don't open threads in other devices sections yet.

If you find anything wrong, odd looking or not working, please report it here.

If you find everything working, please also report it here.

If you want to suggest changes, feel free to do so.

Materialised BETA
[HTC One X] z31s1g:
Materialised themes are out of beta. :D

Currently only this generic thread is availabe, device specific threads will follow after the weekend.

Versions for TWRP 2810 are also ready to be downloaded.
[Nexus 7 (2013) General] xxa:
No any news about selling Nexus 7 in my country so far. However, I will fly to Korea soon and Google said in the opening event that Nexus 7 (2013) will be available in Korea “in the coming weeks”.

Is it available in Korea yet ? and where ? or Have you guys heard any news about selling in Korea ?
[Nexus 7 (2013) General] aooga:
Its still in the US now. Canada is next...not sure about other countries. I'm guessing late August, early September. You could always import it from someone that you know in the US. (If you do)
[Motorola Droid Bionic] kschang:
I know HashofCodes is a busy guy, and he basically left off dock support off the last bazillion CM10 builds.

But I *do* use the NavDock quite a bit as I do drive a fair bit.

Is there a way to MANUALLY engage car mode? That'll at least work around the problem until HashOfCodes merge the ICS dock codes into CM10...

I mean, it's just an app, right? Albeit hidden app?
[Motorola Droid Bionic] kschang:
Workaround... car dock ultra. 30 day demo in play store. I have it start when it links with my Bluetooth speakerphone
[Motorola Droid Bionic] kschang:
Not an idea workaround as this workaroun doesn't actually say the phone's docked. It's basically "forced" into car mode. That means apps that detects the car dock, like "motorola car finder" still insists that I don't own the dock and thus refuse to work. Phooey.
[About XDA developers] SubZero5:
Hi,

I get every topic notification mail twice. Why?

PS: I receive my Pm notifications only once...

Anyone face with a similar problem?

I can provide logs from my mail server...
[About XDA developers] mtbsoft:
Yep, every notification I receive is duplicated too.
[About XDA developers] SubZero5:
One of them has "To: " and the other mail has "To: Undisclosed-recipients:" or "To: Undisclosed-recipients: ;"
[About XDA developers] mtbsoft:
Yep, same here, I guess there's a bug in the script but noone's looked at fixing it yet.
[About XDA developers] SubZero5:
this is my first mails header:

Received: from [82.94.252.244] (HELO mail.nah6.com)
by subzero5.yi.org (CommuniGate Pro SMTP 4.3.5)
with ESMTPS id 2030507 for [email]em@il.hidd[/email]en; Sun, 26 Jun 2005 20:01:21 +0300
Received: from server.xda-developers.com (server.xda-developers.com [82.94.252.245])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by mail.nah6.com (Postfix) with ESMTP id 755F5C61802;
Sun, 26 Jun 2005 19:00:07 +0200 (CEST)
Received: (from www@localhost)
by server.xda-developers.com (8.13.1/8.13.1/Submit) id j5QH06sT077398;
Sun, 26 Jun 2005 19:00:06 +0200 (CEST)
(envelope-from www)
To:
Subject: Topic Reply Notification - XDA2i o2 Update...when?
Reply-To: [email]webmaster@xda-developers.com[/email]
From: [email]webmaster@xda-developers.com[/email]
Message-ID: <8329ce86a5487fc8a47ef5dc6bf3ace2@xdaforums.com>

this is my second mails header:

Received: from [82.94.252.244] (HELO mail.nah6.com)
by subzero5.yi.org (CommuniGate Pro SMTP 4.3.5)
with ESMTPS id 2030509 for [email]em@il.hidd[/email]en; Sun, 26 Jun 2005 20:14:35 +0300
Received: from server.xda-developers.com (server.xda-developers.com [82.94.252.245])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by mail.nah6.com (Postfix) with ESMTP id 5E4E3C61805;
Sun, 26 Jun 2005 19:13:24 +0200 (CEST)
Received: (from www@localhost)
by server.xda-developers.com (8.13.1/8.13.1/Submit) id j5QH06qI077392;
Sun, 26 Jun 2005 19:00:06 +0200 (CEST)
(envelope-from www)
To: Undisclosed-recipients: ;
Subject: Topic Reply Notification - XDA2i o2 Update...when?
Reply-To: [email]webmaster@xda-developers.com[/email]
From: [email]webmaster@xda-developers.com[/email]
Message-ID: <8329ce86a5487fc8a47ef5dc6bf3ace2@xdaforums.com>

which means the mail is submitted 2 times by the forum software:

PS: Check the first and second message ID's being different.
[About XDA developers] Anton.Valleyman:
Yeah I've been getting two notifications as well...and normally about 10mins apart which seems consistent with the experiences of others.

Ant
[About XDA developers] Rick GM:
Same for me.
[About XDA developers] Sergio_Bandeira:
I have this problem too.

Anyone read this thread???

Any administrator can reply, please?
[About XDA developers] SubZero5:
Any admin reading this topic? I can help you with this problem if you want/need..
[About XDA developers] Sergio_Bandeira:
Sure!

I'm waiting... :wink:
[About XDA developers] Sergio_Bandeira:
Anybody there???

It's frustrating have two times more e-mail notification messages from this forum.

I love this forum, but I don't want to have two identical e-mails.

Please help us... :idea:
[About XDA developers] SubZero5:
I can't really find the problem from here. Both mails have the same Message-ID 's but the Sendmail/Postfix server that receives emails from www@localhost generates different id 's and different timestamps... :( And as it is submitted twice to the MTA, you are getting two copies of the bodies...

The problem is somewhere between the forum software and the outbound part of the MTA
[About XDA developers] mtbsoft:
I appreciate you looking into it, if a solution can be found then great, otherwise it's bearable.
[About XDA developers] Sergio_Bandeira:
ANYONE???

Anyone reading this thread?
[About XDA developers] LumpiStefan:
Re: ANYONE???

Yes. Actuel 202 Views.... ;-)

Stefan
[About XDA developers] Sergio_Bandeira:
Re: ANYONE???

Ya! That I can see.

I don't see any resolutions too.
[About XDA developers] mtbsoft:
Re: ANYONE???

Well if you looked just five posts up you'd see that it has been investigated only a couple of weeks ago and no problem found. So in answer to your original question LumpiStefan was completely correct, it is also plain to see that people have looked into the problem but don't have a solution yet!
[Nexus 10 Original Android Development] fronti90:
This is an alpha build, it's booting up, but i dont know about known issues (yet), so flash at your own risk and expect a few things to be broken.

Known Bugs:

Dont know, you tell me!
[Nexus 10 Original Android Development] fronti90:
one more for me, just to be sure :D
[Nexus 10 Original Android Development] ricco333:
Tried to download but links are down.

Erik

edit: never mind I found it browsing thru Slimroms site.
[Nexus 10 Original Android Development] Ladicx:
Does slim have tablet ui?
[Nexus 10 Original Android Development] Syk69:
For an alpha build its working real nice! :) Android browser missing sync unfortunately. Pretty stable and quick though! Looking forward to future builds.
[Nexus 10 Original Android Development] ricco333:
Which Slim gapps did you install? Slim Gapps 4.4.4 build 8?

Thanks
[Nexus 10 Original Android Development] Syk69:
No. Slim gapps 4.3 alpha3.x

Build 8 gapps is for 4.2.2 build.
[Nexus 10 Original Android Development] rafaelvelasquez2:
Just downloaded the rom and slim gapps just now. Bout to take this puppy for a spin around the block.
[Nexus 10 Original Android Development] halrulez:
Ditto
[Nexus 10 Original Android Development] johno86:
Worked like a charm. Nothing noticeably wrong at the moment. Will run it for a few days and see how it holds up! Thank you for the rom!
[Nexus 10 Original Android Development] halrulez:
Freaking love it. Just wish it had the aosp keyboard with all the long press for numbers and characters. Everything else is super fast and smooth
[Nexus 10 Original Android Development] DroidZombie:
So far I noticed a graphics glitch on the Google loading screen, and I did not have superuser privileges upon initial startup. Yes I did a full wipe and cleared both caches. I installed slimgapps 4.3, photosphere 4.3, and extras 4.3 as well.

Which superuser.zip would you suggest?

Edit: I used chainfire's supersu 1.51 and regained root.

Sync speed seems to be slower. On 4.2.2 my tablet got mail before my phone, now it's the reverse.
[Nexus 10 Original Android Development] fronti90:
Not sure about that but did you flash the full LatinIME keyboard pack?

Afaik you just have to enable us in advanced options

Gesendet von meinem Nexus 4
[Nexus 10 Original Android Development] DroidZombie:
Tried that and there was no option to enable it.
[Nexus 10 Original Android Development] damngood98:
new to slimbean so perhaps i'm just overlooking the option but after adding a custom tile in the quick settings, i'm not seeing a place to set it up. maybe hasn't been implemented yet?

what i'm looking to do is add a tile that can keep the screen timeout off, not just the standard settings...possible at this point yet?

thanks though....looking good and will likely try this on my phone as well when i get the chance later
[Nexus 10 Original Android Development] Syk69:
To enable superuser you have to go into developer options and change root access to apps and adb. That's how I got superuser to work on the ROM.