As a fan of Deus Ex Human Revolution game I was trying to theme my Nexus 10 for some time. Using combination of UCCW, live wallpaper (by Makomako) and android theme by Ramazor I’ve almost reached my goal – last thing that wasn’t themed was recovery. Lucky for me TWRP comes with fantastic theming system.
I’ve made theme based on Deus Ex HR game interface for TWPR 2.6.3.0.
It probably won’t work with older versions! I do not recommend using it with any older version than 2.6.3.0!
Features of landscape version (2560x1600):
Menu:
This theme has live main menu on left, which means it is slightly different from stock “page by page” display. In my theme it is possible to jump between different active pages – it will cancel all selected actions and reset variables, though. So, basically it is equal to pressing “Home” and “page” button in stock theme.
Keyboard layout:
Added numeric keyboard
Terminal Command – keyboard shortcuts:
e2fsck - As I’ve had few times problems with restoring backups and my tablet basically froze in recovery mode, I thought it will save me connecting to PC and doing it via ADB. After performing e2fsck on all partitions (usually DATA was most affected) I could restore backups or flash new roms.
It is important to unmount partitions first, otherwise e2fsck will report mounted partition and exit. It could be done either from \Mount menu or another “shortcut” in \Advanced\Terminal command\e2fsck. These “shortcuts” require pressing “ENTER” button on keyboard.
This theme was designed to use on Google Nexus 10 and as such I’ve added only mmcblk0p7, mmcblk0p8, mmcblk0p9 to umount and e2fsck “shortcuts”.
If any one will ever use this theme on any other device, those commands might not work!
CLS button:
If anyone do not like “swipe left to clean” feature, I’ve added CLS button, which cleans typed characters in command line. (CLS is available only in Terminal command window!)
Remove theme:
If one will have any problems with this theme or will get bored with it, it could be removed and recovery will reload stock theme without rebooting recovery. (File will be renamed to “ui_DeusEx.zip” but TWRP won’t load it anyway – to restore it simply rename it back to “ui.zip” and reload theme).
Portrait version (768x1280, 720x1280, 1200x1920):
Remove theme option (as above).
It was tested by me on Google Nexus 4 phone and Google Nexus 10 tablet. It should work on any device with the same screen resolution.
Theme comes in 2 color variants: orange (Deus Ex) and holo (I rather should say: “holo-ish”).
As files are quite big, please verify checksum after download.
Installation:
Download selected version, verify checksum, rename file to ui.zip, copy via file manager or adb push to /sdcard/TWRP/theme/
Disclaimer
Theme was tested only by me as far as I could and I didn't have any problems with it but I do not take any responsibility for any data loss or other damage. Use it on your own risk!
I will appreciate feedback. I can respond to questions\queries on evenings as I’m working and do not have too much spare time.
UPDATE 1:
Theme now supports TWRP 2.6.0.0.
UPDATE 2:
Removed confirmation windows from Power Menu actions (restored stock function: "No OS installed!" warning message in case of no data on /system partition) - thanks to Nezorflame for pointing it out
Added "(sort of) Holo colors" variant - thanks to halrulez for suggestion
Holo colors: basically only orange color has been replaced with light blue plus new background image to match it.
UPDATE 3:
It's actually a small correction on both themes. I left mount USB storage with disabled condition and it was shown even on devices without that function (i.e. Nexus 10), I'm sorry!
UPDATE 4:
Another detail that I missed previously was corrected (one of consoles windows was slightly adjusted) , added "Inject TWRP" and "Re-inject TWRP" options (it will be visible on supported devices, I can't see it on my both Nexuses). Added phone (portrait) versions.
UPDATE 5:
- Added 1200x1980 pix version (portrait), file has upscaled bitmaps and that bloated it up to 10MB. I do not want to re-make any of the images because it would take a lot of time (which I do not have right now), sorry.
- 1200x1980 version has different keyboard (removed keyboard background, highlighted buttons)
- All portrait themes were updated to TWRP 2.6.3.0. Landscape is still for TWRP 2.6.0.0, I was too focused on fixing portrait versions and completely forgot to update it, sorry! I'll do it ASAP.
- All portrait files can be found on my dropbox folder, link below.
UPDATE 6:
- All themes (lanscape and portrait) are now compatible with TWRP 2.3.6.0.
- In landscape theme Settings menu items were slightly rearranged.
UPDATE 7:
- Fixed "Copy" button position in 768x1280 themes (both variants)
- Fixed "File" icon not showing up in 768x1280 themes (both variants)
UPDATE 8:
- Added MultiROM support for 768p themes (Nexus 4)
- Added "restoreDeusEx.zip" file for restoring theme after use /ADVANCED/Theme tools/Rename theme file option: file can be flashed from stock theme (or any other) but will overwrite any existing ui.zip in Theme folder.
- Added batch "ADB_DE_push.bat" file for simpler theme install: just copy whole selected folder on your PC and run ADB_DE_push.bat file. Along with "ui.zip", "restoreDeusEx.zip" will be copied to /sdcard/TWRP/theme (folder will be created if there isn't one already).
UPDATE 9:
Themes for 768p, 720p, 1080p (portrait) devices as well as Nexus 10 (landscape) are now updated to TWRP 2.7.0.0 (that includes small changes to Settings page). MultiROM version will follow soon.
(I do not have Nexus 7 (flo) on me at the moment, so I wasn't able to test it properly)
Important!
Sorry guys, look's like it will gonna take some more time to fix phone themes - I'm removing them for time being.
I hope I'll be able to make it work.
Please stop use it for your devices safety!
Files were fixed as far as I could - no one reported any problems, neither I had any, so I can assume, that everything is fine.
If anyone will have any problems with theme, please post details and I'll try to fix it.
There are some issues with TWRP 2.6.3.1 on Nexus 10 at least with ROMs based on CM (partition problems, freezes).
These are not theme related and I can't fix it. I recommend not to upgrade TWRP now, please wait for at least 2.3.6.2 version.
I do not intend to produce any other versions for different devices.
But feel free to do it yourself, just keep my nick in xml.file
Information:
There is no chance I'll be able to make updates to MultiROM version or any other version of theme. I simply do not have time and I need to focus on other things right now Sorry!
I'd like to thank all of you for support and all help that you've given me!
If anyone wants to take over please let me know - I can share source files in PSD format.
Below you can find link to all the PSD files, feel free to use them. Please read info.txt. Good luck!
https://www.dropbox.com/sh/1b3kqiijornl95o/AAClEBfnw2Ky8gTvGsmScgsha
I do not take responsibility for any moded/updated theme!
Download:
All files could be found on my dropbox folder:
https://www.dropbox.com/sh/hemfcd28oz1qtaq/0Xe8ZQUxwb
Checksums for all files can be found in checksums.txt file.
Please always verify checksums after downloading theme files!
Wow.
Beautiful theme.
Will give it a try. Thx!
Even though I don't follow the Deus Ex franchise, I can say that this looks absolutely cracking!
Will try this on the first thing when I get some free time with my N10 tomorrow.
Thanks! I forgot to mention that there are two sliders - one you can see on lockscreen preview in first post, other is bigger and thing that should be touched/swiped is that light blue cube on the left. It sounds a bit cryptic but you'll get it when you'll see it.
I removed a prior theme I had from the TWRP theme folder and replaced with this theme. Upon reboot recovery all I get is reboots to the TWRP loading screen. The loading screen is the prior theme though so it seems like its still trying to load the older theme that I removed and replaced with this theme.Any help or do I need to reflash. Not a big deal since I want to try the new 4.3 Factory anyway. Since I cant get into TWRP Recovery it seems I'll have to go back to stock and start over.
Dude I totally love this theme. Took TWRP to a whole new level. Wish the was a good theme for smart launcher to match it.
Sent from my Nexus 10 using Tapatalk 2
Great Theme, e2fsck shortcuts are really handy too :thumbup:
Sent from my Nexus 10 using Tapatalk HD
NICE! I love the Deus Ex HR interface style. Makes me dream of a world where you are just as technological as your computer...
You did a marvellous job there, the theme makes perfect use of the screen!
Could you give me a hint on how I can also get an android framework with solid xhdpi theming?
momulah said:
I removed a prior theme I had from the TWRP theme folder and replaced with this theme. Upon reboot recovery all I get is reboots to the TWRP loading screen. The loading screen is the prior theme though so it seems like its still trying to load the older theme that I removed and replaced with this theme.Any help or do I need to reflash. Not a big deal since I want to try the new 4.3 Factory anyway. Since I cant get into TWRP Recovery it seems I'll have to go back to stock and start over.
Click to expand...
Click to collapse
Sorry to hear that but I'm afraid I can't really help you - it didn't happen to me. You can try to push ui.zip via adb again as adb should be working even with TWRP curtain image stuck on screen. Maybe file was corrupted or something...
halrulez said:
Dude I totally love this theme. Took TWRP to a whole new level. Wish the was a good theme for smart launcher to match it.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Thanks
I'm using these:
theme - https://play.google.com/store/apps/details?id=com.ramazor.theme.freedeax
icons - https://play.google.com/store/apps/details?id=com.badwolf.grey.deus.ex
live wallpaper - https://play.google.com/store/apps/details?id=com.mako.goldlite
plus few widgets that I've made for UCCW and it's almost perfect :laugh:
Still, I'd like to see a proper skin for android that would use similar interface...
pingguo said:
NICE! I love the Deus Ex HR interface style. Makes me dream of a world where you are just as technological as your computer...
You did a marvellous job there, the theme makes perfect use of the screen!
Could you give me a hint on how I can also get an android framework with solid xhdpi theming?
Click to expand...
Click to collapse
Not really I was able to make TWRP theme as it was quite easy (xml there is simple and hardest thing was creating images). Things you're looking for are way out of my league.
Awesome theme. Now you should make a CM 10 theme using the same theme
Sent from my Nexus 10 using Tapatalk 4 Beta
Im using TWRP latest and I cant get it to boot with the theme. ui.zip placed in themes folder but it just boots to the TWRP load screen and stays there.
Sorry to hear that, I can't really help you with that. I do not have any problems with it and nobody else reported any problems.
Does it boot normally without it? Does it work with any other theme for 2.5.0.0? Can you run e2fsck on your sdcard via adb (make backup of your data on other storage before that!)? I've added shortcuts for e2fsck because I had problems with restoring backups but other people reported similar problems with their data or partitions on TWRP 2.5.0.0 (some of them went back to older versions). Can you repack ui.zip and try with it? Last one is a long shot... Otherwise, I do not know what else could be done, sorry.
Hatman41 said:
Awesome theme. Now you should make a CM 10 theme using the same theme
Sent from my Nexus 10 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Have you seen this one: http://forum.xda-developers.com/showthread.php?t=1673652
Making proper CM theme is beyond my skill, I'm afraid.
Kraliz said:
Sorry to hear that, I can't really help you with that. I do not have any problems with it and nobody else reported any problems.
Does it boot normally without it? Does it work with any other theme for 2.5.0.0? Can you run e2fsck on your sdcard via adb (make backup of your data on other storage before that!)? I've added shortcuts for e2fsck because I had problems with restoring backups but other people reported similar problems with their data or partitions on TWRP 2.5.0.0 (some of them went back to older versions). Can you repack ui.zip and try with it? Last one is a long shot... Otherwise, I do not know what else could be done, sorry.
Click to expand...
Click to collapse
Neva mind for some reason it didn't download the whole theme. I re downloaded and it worked. Looks really nice but seems slower...best theme i'm seen so far though. Thanks.
momulah said:
Neva mind for some reason it didn't download the whole theme. I re downloaded and it worked. Looks really nice but seems slower...best theme i'm seen so far though. Thanks.
Click to expand...
Click to collapse
Great! :good:
Kraliz said:
Great! :good:
Click to expand...
Click to collapse
It even works fine with 2.6 guys
Sent from my Nexus 10 using Tapatalk 2
halrulez said:
It even works fine with 2.6 guys
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, good to know. I've updated TWRP on my tablet and I'll check for any changes in stock theme later.
Kraliz said:
Thanks, good to know. I've updated TWRP on my tablet and I'll check for any changes in stock theme later.
Click to expand...
Click to collapse
Would this be awesome if it had the holo colors instead on the orange. I love it the way it is don't get me wrong. Any chance for different colors?
Sent from my Nexus 10 using Tapatalk 2
Related
Hey everybody!
***New APK editor added! Set the keys to whatever you want, see below!***
****I will not be held responsible if your Nook Color starts eating babies!!****
****Or if it breaks either!!****
****Added a revert, for those who may have issues returning the keylayout to stock (like 1.1 users who can't run the keylayout app)****
****As an added request, if anyone knows how to reload the keylayouts sans reboot, please let me know, as that is really the only thing missing from this little thing. I would love to be able to quickly reload these as needed.****
So after creating the flashable zip file for the keylayouts, and receiving some feedback that implied it would be nice to have more options, I decided to brush up on the coding skills and write a nice little app that can re-write the keylayout files without having to flash anything. This is actually my first android app, so please provide me with any feedback you may have, the more the better. The way I see it, the more I know, the better things I can make.
The keylayout app currently supports mapping the volume keys to these items:
Volume Up
Volume Down
Menu
Back
Search
D-pad Center
and can additionally support wake on press, if desired. Once written, you will need to reboot your device for the keylayout to be effective, but it's still easier than manual edits or multiple flashes.
***Note that using the app requires su access, and also at this point requires that you first flash one of my v5 keylayout zip files***
***I have received notice that the application does not run on stock rooted 1.1.0 I will be looking into this and posting an update, and most likely a revert to stock zip in case anyone needs it.***
Thanks go to whoever first suggested this, I'll be damned if I can't remember who I got this from, but thank you, whoever you are, I'll be sure to give you props when I figure out who you are.
History over, now for the details:
To install: Simply flash either zip file in CWM after flashing your CM7 or Honeycomb build to your eMMC. Once you do this, you can install and use the apk file to make changes to the keylayouts to your heart's content.
The CWM zips have been confirmed to work on most all versions of android for the nook, and in theory, the APK should work as well, however YMMV. If it works, or if it doesn't, please please post your version or build info, and let us all know what works and what doesn't.
Feedback and/or critiques accepted, may be subject to rebuttal. Hope this helps someone else, and thanks to everyone on this forum for all the hard work you do!
FYI: For those who still want an easy way to change the volume when these keys are no longer volume keys, try replacing the longpress home app with Recent Plus, by local forum contributor timoskrempel, which I first found HERE and works very well as a replacement.
Version History
-----------------------
apkv0.1b - Initial version of the keylayout app. Feedback appreciated.
v5: added files that apparently weren't as useless as I assumed. Also created inverted keys zip, use INV zip to switch the buttons.
v4: removed useless files from update zip, cause I'm being a bit too perfectionist.
V3: added files to improve compatibility (HC v4 tested, should work on Froyo, maybe stock)
V2: removed wake on press (thanks jasoraso)
V1: First Version
I definitely prefer hard keys, even with the modifications in CM7. I'll give your zip a try next time I flash a rom (I've already changed my qwerty.kl on this rom).
One other thing - I also prefer to remove the "wake" for those 2 keys, I found that the NC was accidentally waking up from inadvertent keypresses on the volume keys ...
jasoraso said:
One other thing - I also prefer to remove the "wake" for those 2 keys, I found that the NC was accidentally waking up from inadvertent keypresses on the volume keys ...
Click to expand...
Click to collapse
An excellent point. Editing my zip and attaching v2. thanks to you!
success! just flashed this along with nightly#4 and it works like a charm.
I love this. always get stuck in pics in Facebook and can't get back.
Question though, what do you all use for a good alternative to adjust the volume on the fly?
Is there a preferred widget? Right now i just have a ADW shortcut to the sound settings on the home screen.
digitalslacker said:
I love this. always get stuck in pics in Facebook and can't get back.
Question though, what do you all use for a good alternative to adjust the volume on the fly?
Is there a preferred widget? Right now i just have a ADW shortcut to the sound settings on the home screen.
Click to expand...
Click to collapse
Widgetsoid has a volume adjuster that I use, though more often I just use headphones with volume sliders built in, so I skip using the software entirely. Ideally, I would love to be able to mod the framework to add a quick volume adjust button to the status bar like the softkeys, however that involves code editing that I just haven't dug into yet. If I do make the edit, I'll be sure to post what i make though.
EpicFail236 said:
Widgetsoid has a volume adjuster that I use, though more often I just use headphones with volume sliders built in, so I skip using the software entirely. Ideally, I would love to be able to mod the framework to add a quick volume adjust button to the status bar like the softkeys, however that involves code editing that I just haven't dug into yet. If I do make the edit, I'll be sure to post what i make though.
Click to expand...
Click to collapse
thanks, i'll check it out.
What would be really cool and I'm not sure it's possible and I know it's not in the scope of this thread; but a way to change functionality of the buttons per app. So for example when in Pandora (or music app of choice) buttons behave as volume buttons, but under other various apps like gallery it could be home+back button set.
Seems like you'd have to have an app running as a service and monitor the currently running focused app (not in sleep mode) and depending on what has focus do a live update to the qwerty.kl file to change buttons to expected functionality, not sure if a reboot is required after an update to the kl file though?
How can you revert back to stock?
Also is there a way to swap the keys? It seems more natural to have the back key as the +
Thanks for your work, installed without a hitch..
spikey911 said:
How can you revert back to stock?
Also is there a way to swap the keys? It seems more natural to have the back key as the +
Thanks for your work, installed without a hitch..
Click to expand...
Click to collapse
change mapping in step 4 from here:
http://nookdevs.com/NookColor_Remap_volume_buttons_for_back_and_menu
adb pull /system/usr/keylayout/TWL4030_Keypad.kl
adb pull /system/usr/keylayout/omap_twl4030keypad.kl
edit 'TWL4030_Keypad.kl' and 'omap_twl4030keypad.kl' with a unix line ending aware text editor (Notepad++, gedit, vi)
replace 'VOLUME_DOWN' with 'BACK' and replace 'VOLUME_UP' with 'MENU' in each (or vice-versa)
adb shell
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
exit
adb push TWL4030_Keypad.kl /system/usr/keylayout/TWL4030_Keypad.kl
adb push omap_twl4030keypad.kl /system/usr/keylayout/omap_twl4030keypad.kl
adb shell
cd /system/usr/keylayout
chmod 644 omap_twl4030keypad.kl
chmod 644 TWL4030_Keypad.kl
exit
adb reboot
Click to expand...
Click to collapse
not working with
[ZIP][DEV][ROM] HC v4 eMMC 2nd ed. - Flashable ZIP {02/21/11}
buttons still remain in their normal functionality...
fattymcdirty said:
not working with
[ZIP][DEV][ROM] HC v4 eMMC 2nd ed. - Flashable ZIP {02/21/11}
buttons still remain in their normal functionality...
Click to expand...
Click to collapse
Thanks for the heads up, will review and post v5 sometime today.
my status bar always shows with HoneyComb, so I always have the back menu buttons. are there apps where this is not the case?
Anyone try this on froyo yet?
fattymcdirty said:
not working with
[ZIP][DEV][ROM] HC v4 eMMC 2nd ed. - Flashable ZIP {02/21/11}
buttons still remain in their normal functionality...
Click to expand...
Click to collapse
Yeah, I totally deleted an extra file, added to v5 and it should now work with this eMMC build. oops.
spikey911 said:
How can you revert back to stock?
Also is there a way to swap the keys? It seems more natural to have the back key as the +
Click to expand...
Click to collapse
I will have to put together a stock zip and put it up sometime in the near future. Your swap keys is not easily done directly, but I have posted a new flashable zip that will swap the keys, flash INV-v5 to have the volup function as back and voldown to work as menu. This one I haven't tested, as I don't actually have my nook with me here now, but in theory it should be OK, as all I did was swap the mappings in the kl files.
After setting up CM7 Nightly 4 last night I replaced the SDcard with CWM 3.0.0.6 used to install CM7 with a fat32 8gb for storage.
Afterwards I installed ROM Manager and the latest Recovery included - 3.0.0.5.
I am able to flash Dalingrin's latest kernel through here but when I went to flash todays Nightly CM7 it did not work (probably because of the 3.0.0.5 i figured). I plugged back in the 1GB SD with 3.0.0.6 and successfully flashed todays nightly.
I then tried to flash the Hard Key Mod file using the emmc recovery and it did not work so I copied it to my 1GB SD and that worked.
Anyways...I wrote this just in case someone was having the same problem I had flashing the Hard Key Mod file and to see if there is any method to set up 3.0.0.6 on the emmc so that I don't have to insert the 1GB SD every time I wanna flash CM7 nightlies.
rickpref said:
After setting up CM7 Nightly 4 last night I replaced the SDcard with CWM 3.0.0.6 used to install CM7 with a fat32 8gb for storage.
Afterwards I installed ROM Manager and the latest Recovery included - 3.0.0.5.
I am able to flash Dalingrin's latest kernel through here but when I went to flash todays Nightly CM7 it did not work (probably because of the 3.0.0.5 i figured). I plugged back in the 1GB SD with 3.0.0.6 and successfully flashed todays nightly.
I then tried to flash the Hard Key Mod file using the emmc recovery and it did not work so I copied it to my 1GB SD and that worked.
Anyways...I wrote this just in case someone was having the same problem I had flashing the Hard Key Mod file and to see if there is any method to set up 3.0.0.6 on the emmc so that I don't have to insert the 1GB SD every time I wanna flash CM7 nightlies.
Click to expand...
Click to collapse
My assumption (it may be wrong, as I do not have my nook present with me to confirm) is that the system partition on the CM7 builds is ext4, and as a result, 3.0.0.5 would not be able to access it to flash any data. flashing either the cm7 nightlies or my additions, both of which write to this ext4 partition, needs to be done via 3.0.0.6.
That being said. I personally managed to get 3.0.0.6 to work on my emmc by taking the uImage and uRamdisk from the SD card version, renaming them uRecRam and uRecImg, and copying them to the eMMC boot parition. I would not recommend doing this without knowing *Exactly* what you are doing, as overriding these files with other files could cause bad things to happen, and as I said above, bad things are bad.
EpicFail236 said:
My assumption (it may be wrong, as I do not have my nook present with me to confirm) is that the system partition on the CM7 builds is ext4, and as a result, 3.0.0.5 would not be able to access it to flash any data. flashing either the cm7 nightlies or my additions, both of which write to this ext4 partition, needs to be done via 3.0.0.6.
That being said. I personally managed to get 3.0.0.6 to work on my emmc by taking the uImage and uRamdisk from the SD card version, renaming them uRecRam and uRecImg, and copying them to the eMMC boot parition. I would not recommend doing this without knowing *Exactly* what you are doing, as overriding these files with other files could cause bad things to happen, and as I said above, bad things are bad.
Click to expand...
Click to collapse
Yeah, I figured it had to be that EXT4 partitions are not compatible with 3.0.0.5 but it took me a while to get it. So I take it you need to use ADB in order to rename and copy to boot those files?
rickpref said:
Yeah, I figured it had to be that EXT4 partitions are not compatible with 3.0.0.5 but it took me a while to get it. So I take it you need to use ADB in order to rename and copy to boot those files?
Click to expand...
Click to collapse
My ADB machine was down and out at the time, so I had to do it via ES file manager and the terminal on the nook itself, but yeah, manual replacement was the way to go. sometimes a bit of command-fu is just easier than the alternative.
digitalslacker said:
Question though, what do you all use for a good alternative to adjust the volume on the fly?
Is there a preferred widget? Right now i just have a ADW shortcut to the sound settings on the home screen.
Click to expand...
Click to collapse
I use Volume Widget by Futon Redemption. It gives you two little onscreen +/- buttons to adjust the volume.
Has anyone else started theming TWRP? We need some love for the Touchpad.
This one comes from the boys on the Kindle thread. Props to the theme Dev.
http://forum.xda-developers.com/showthread.php?t=1423960
Download ui.zip
Mount your SDCARD
Navigate to X:\TWRP\
Make a new folder called “theme”
Move ui.zip into “theme”
Boot into recovery and this will be your default skin.
Trust me, its WAAAAAY better than working without it.
nvm, guess I should test before I speak.
No worries. I was hesitant to try it too. But the basic screen reminded me of my Commodore 64. Your themes are tight by the way.
Confirm, It works
jamesissocool said:
I saw that too. But, I set it up and it works like a champ on mine.
And another. Made for kindle but looks sweet.
http://forum.xda-developers.com/showthread.php?t=1423960
Click to expand...
Click to collapse
Thanks, it works and looks great on the tp.
Background
I have received a few PMs for information about TWRP and I just figured I would post here.
Basically TWRP is a recovery utility like CWM, but it uses a touchscreen interface instead of the volume rocker, home & power button controls. For more information please refer to the dev thread:
http://forum.xda-developers.com/showthread.php?t=1400649
Personally, I like the TWRP method better overall, but I still use CWM for more complex flashes where devs recommend a specific install process using clockwork. However, rumor has it that CWM may be coming out with a touchscreen UI as well.
The point of this thread was to find out if anyone had created a TWRP theme specifically for the Touchpad. It does not appear that anyone has tried to make art out of the blank canvas yet.
Please read this carefully :
- BASE ROM by Kibuuka AOSP ICS 4.0.4
- PORT ROM from Mazda Team Dirt PARANOIDANDROID v0.2.1 for Supersonic aka HTC Evo 4G and Xylograph ParanoidAndroid for HD2
All the Credit and Donate go to :
1. Mazda [Team Dirt] (http://forum.xda-developers.com/showthread.php?t=1714415)
2. Molesarecoming aka PARANOIDANDROID (http://forum.xda-developers.com/showthread.php?t=1717079)
3. Xylograph
3. Kibuuka (you know where to find him)
4. Nop (you know where to find him)
5. TheManii (you know where to find him)
Please do me a favour, hit the THANKS button at least for above name list.
As usually, I take no credit at all for this rom because this is not my work, I'm not build this from the source, all I do is take the 2 rom, combine it, then try to make it boot on my device.
The rom from Mazda was made for running on HTC Supersonic, if running on DS5 sure it will have much problem and bugs.
All I can do just fix as much as I can, I'm not have experience in build rom, so do not expect too much on this rom.
I just want to share, not intend anything by making this, just have fun and feel excited when others ICS rom can running on my old device.
So lets have fun.
Not work
camera
Temporary work
wifi tether (use barnacle wifi tether from playstore)
headphone (use toggle headset2 from playstore, thanks to machbe 1984)
How to
Nandroid back up before flash.
Wipe cache and dalvik cache, factory reset from streakmod recovery
Flash rom
Factory reset from dell recovery
Be patience, phone need longer time to boot up, if it stuck on boot animation, press and hold power button untill phone shutdown and reboot again. This time will boot up.
Download link
http://www.mediafire.com/download/7eq27tblav0qdjt/ParanoidAndroid_Streak.zip
How to have tablet ui
HOW TO MAKE ANY ICS ROM HAVE TABLET UI
Thanks to Veisen for his awesome work, you can follow his thread
http://forum.xda-developers.com/showthread.php?t=1767955
Tools
- Winrar or 7zip
- dex2jar
- hex workshop
- services.jar from ICS rom
How to
- extract services.jar from ICS rom (system/framework)
- use winrar to extract classes.dex from services.jar
- use dex2jar to compile classes.dex [ d2j-dex2jar classes.dex ]
- the result "classes_dex2jar.jar", use winrar to open and extract WindowManagerService.class form classes_dex2jar.jar\com\android\server\wm
- open WindowsManagerService.class in hex workshop, choose replace icon from menu bar, fill the pop up with
Find : 8E0009000A000000821B9900781D36061C36072A2A2A2A1506
Replace : 930009000A000000871B99007D1D36061C36072A2A2A2A1506 8617046E8B
click ok, then choose replace all, after that choose replace icon from menu bar again, fill the pop up with
Find : B11C36061D3607A7FF8B
Replace : B11C36061D3607A7FF86
click ok, then choose replace all
- save WindowManagerService.class
- replace WindowManagerService.class by winrar in classes_dex2jar.jar without compression
- use jar2dex and create new dex file [ d2j-jar2dex classes-dex2jar.jar ]
- rename it to classes.dex
- use 7zip to replace your classes.dex in services.jar
- copy the mod service.jar back to your rom or phone
- in build.prop change density to 128 and reboot.
Now you have tablet phone
I have tested it and the result are
- dpi 128 [phone not work, data and wifi work well]
- dpi 240 [everythings work well]
Feel free to try use other phone.apk and post the result here.
Intriguing concept!
... too bad I cannot flash it. (using ClockworkMod 6.0.1.0)
tried redownloading 3x
Crinos512 said:
Intriguing concept!
... too bad I cannot flash it. (using ClockworkMod 6.0.1.0)
tried redownloading 3x
Click to expand...
Click to collapse
Try use streakmod?
Sent from my Dell Streak using Tapatalk 2
Anybody success flash it ? I'm afraid there is bad upload.
Sent from my PC36100 using Tapatalk 2
Crinos512 said:
Intriguing concept!
... too bad I cannot flash it. (using ClockworkMod 6.0.1.0)
tried redownloading 3x
Click to expand...
Click to collapse
i have flashed it successfully by both StreakMod 0.3.2.8 and ClockworkMod 5.0.2.7
it has some interesting changes
i hope it will be better and better (such as camera and languages)
Yep, was able to flash it too. Preferred the CM9 ROM though! To each his own, I guess!
i always thought that this rom is nice... and ... it is nice..
My friend not believe that my old device can run paranoid android, same like his galaxy note untill I show him. He always laugh at me, said my ds5 is old enough and I should replace it with something new. Ha....this time I beat him
Sent from my PC36100 using Tapatalk 2
nom051205 said:
My friend not believe that my old device can run paranoid android, same like his galaxy note untill I show him. He always laugh at me, said my ds5 is old enough and I should replace it with something new. Ha....this time I beat him
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
streak 5 maybe old but it is still competitive hardware... and its large screen always beat others ( <5inch of course)
though i find it nowadays large screen is standard among south koreans...
Crinos512 said:
Intriguing concept!
... too bad I cannot flash it. (using ClockworkMod 6.0.1.0)
tried redownloading 3x
Click to expand...
Click to collapse
Unless OP silently updated, I cannot confirm this.
What I mean is that it installed fine for me with CWM 6.0, though the way it mounts isnt the preferred way long term.
If anything it shouldnt be compatable with streakmod as it's using the newer format/mount syntax (it's rather complicated in how recoveries read the update scripts).
GApps is also included in it, perhaps you should remove it and point users to a Gapps package, either mine or the 'official' CM one.
ParanoidAndroid is a source based rom isnt it?
We do (preferrably) need a source port instead of a hackport as the rom still thinks it's an EVO
Perhaps when Kibuuka gets AOSP more closer to working 100%, we'll have more people building from source instead of hackports.
Unlike the S7/S10 CM9 ports (and this port of paranoidandroid), all the ICS based ones are currently hackports.
The S5 is terribly slow compared to the S7, it has the ram and nand space to run the newest roms, but the cpu is simply overwhelmed by new apps/stuff.
It's still plenty usable, but 1st gen snapdragons simply cant compare to 3rd/4th gen snapdragons (and their equivilent Exynos/Tegra chips).
It doesnt make it useless though, I still use my S5 ocasionally even though my S7 is pretty much better in every way (except size)
Edit: after reviewing this rom with Quadrant, it seems that the IO score is unusually low. This might explain why my S5 seems so slow with it installed, if it really is IO bottlenecked it could be bottlenecking the entire system.
The other scores are comparable with AOSP/ICS, but PA is signifigantly slower even though I did a fac reset before installing.
Hmm.. it seem that baseband ignorance patch is not working.. it gives blink to the light panel... lol... i am using 366bb to see how the call quality goes and it seems fine.. is there anyway to make the ignorance patch work? I pretty much like this rom and the lags is almost gone too..
TheManii said:
Unless OP silently updated, I cannot confirm this.
What I mean is that it installed fine for me with CWM 6.0, though the way it mounts isnt the preferred way long term.
If anything it shouldnt be compatable with streakmod as it's using the newer format/mount syntax (it's rather complicated in how recoveries read the update scripts).
GApps is also included in it, perhaps you should remove it and point users to a Gapps package, either mine or the 'official' CM one.
ParanoidAndroid is a source based rom isnt it?
We do (preferrably) need a source port instead of a hackport as the rom still thinks it's an EVO
Perhaps when Kibuuka gets AOSP more closer to working 100%, we'll have more people building from source instead of hackports.
Unlike the S7/S10 CM9 ports (and this port of paranoidandroid), all the ICS based ones are currently hackports.
The S5 is terribly slow compared to the S7, it has the ram and nand space to run the newest roms, but the cpu is simply overwhelmed by new apps/stuff.
It's still plenty usable, but 1st gen snapdragons simply cant compare to 3rd/4th gen snapdragons (and their equivilent Exynos/Tegra chips).
It doesnt make it useless though, I still use my S5 ocasionally even though my S7 is pretty much better in every way (except size)
Edit: after reviewing this rom with Quadrant, it seems that the IO score is unusually low. This might explain why my S5 seems so slow with it installed, if it really is IO bottlenecked it could be bottlenecking the entire system.
The other scores are comparable with AOSP/ICS, but PA is signifigantly slower even though I did a fac reset before installing.
Click to expand...
Click to collapse
You named it hackport was exactly what I did, honestly this is the first step of porting rom (make it can boot up then see how stable it run) after that there are others step more, I skipped it
I think when the base rom hit something like beta stage, there should be a lot of changes, on that time better to port from the beginning again to hv a better result
On supersonic, we used to put Papasmurfs script (found in HTC supersonic forum) then should hv good result, I hv tried it and rom show much better performance, but browser and gmail fc. (I choose I/O scheduler = SIO).
Sorry for the "Evo" things show up
I hv changed the strings.xml on values folder but always stuck when compile framework-res.apk.
Tried every method and apktool (apktool1.4.2/apktool1.4.3/apktool1.4.3.1/apkmanagers for ics/new aapt from android sdk) found on google still no go.
Sent from my PC36100 using Tapatalk 2
If you simply use pull the our AOSP build's drivers, I'd imagine that rebuilding shouldnt be too difficult as all the hard work is making the drivers work.
It would be similar to a hackport in that you dont build everything, but it means you dont have to worry about missing those strings
We'd lose device specific stuff like dock detection, but those dont work in the first place.
Kibuuka already has the device tree up on his git repo, you could prob just use that and it'd work with a couple changes at most (hopefully, and under the assumption that you can compile android in general)
AFAIK the 'official' apktool doesnt work on API15 apks, it only supports up to API14 (4.0.1-4.0.2).
Someone's supposedly made a mod to support API15, but I havnt tried it.
Hi good work i flashed the rom and it works perfect on my ds5 but just one problem the lights for the 3 softkeys on the ds5 stays on even when you turn the screen off did i do something wrong? Please advice thanks
That's problem on every ics rom for dell streak
SULEY1 said:
Hi good work i flashed the rom and it works perfect on my ds5 but just one problem the lights for the 3 softkeys on the ds5 stays on even when you turn the screen off did i do something wrong? Please advice thanks
Click to expand...
Click to collapse
use rootdim and select night mode #1 or #2 or #3 :good:
How to change at 160dpi?
ikimradio said:
How to change at 160dpi?
Click to expand...
Click to collapse
Use LCD modder. But the dial stops working for me after sometime on that.
ikimradio said:
How to change at 160dpi?
Click to expand...
Click to collapse
goto..
settings > paranoid settings > hybrid settings > global density
and change it to your preferrence...
disable hybrid mode in case the homescreen look big...
i am currently on 120dpi and i have no problem with the dial not working... all works so far...
---------- Post added at 11:36 AM ---------- Previous post was at 11:34 AM ----------
ncik said:
Use LCD modder. But the dial stops working for me after sometime on that.
Click to expand...
Click to collapse
if you really use this rom.. dont use lcd modder.. use the built in dpi changer..
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Dees_Troy said:
Thanks to Dr_Drache for testing for me!
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.3.2.0:
-Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
-Fixed a bug with deleting a backup with a space in the name
-Added highlights on keyboard key presses
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
Sweet thanks.
Sent from my CM9 HTC Thunderbolt from Tapatalk 2.4
Note, I forgot to have Dr_Drache test off-mode charging. Can someone install this, turn the device completely off, then plug it into a charger. The charge light should come on, maybe blink once or twice, but after about 2 minutes, the charge light should stay on without blinking anymore. Please let me know!
jonah1234 said:
Sweet thanks.
Sent from my CM9 HTC Thunderbolt from Tapatalk 2.4
Click to expand...
Click to collapse
THANK YOU
Dees_Troy said:
Note, I forgot to have Dr_Drache test off-mode charging. Can someone install this, turn the device completely off, then plug it into a charger. The charge light should come on, maybe blink once or twice, but after about 2 minutes, the charge light should stay on without blinking anymore. Please let me know!
Click to expand...
Click to collapse
Off mode charging is fine
Sent from my ADR6425LVW using Tapatalk 2
vinylfreak89 said:
Off mode charging is fine
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Good deal, thanks for checking it and confirming.
I've ran into some trouble with mine. I have created three backups, each with slight differences to system, trying some things out on the ROM. The lase edit was the build.prop. It wouldn't boot so I went to Recovery to restore one of my backups. When it is a good 10 seconds into restoring system, the progress bar stops turning and it reboots. Each time I try this it seems to stop at a slightly different point into the system restore. Most of the time it wont go far enough to allow boot, just the splash screen and then it automatically boots into TWRP.
All of that is ok, and I could get around it, but now my phone is dead! Any suggestions?
*Edit* Got it guys. I was able to use the USB charger from my TPrime and it charged in TWRP. After it charged a bit I was able to fastboot flash TWRP again and restore one of the backups. I'm not sure how it became corrupted, but its all good now!
When will the size be fixed?
Sent from my HTC Droid DNA
jonah1234 said:
When will the size be fixed?
Sent from my HTC Droid DNA
Click to expand...
Click to collapse
I don't have a DNA or any other 1080 * 1920 device that uses a portrait layout (no rotation in recovery). I am unable to do the upscale myself. There's a theme guide on our website if someone wants to to do it.
Dees_Troy said:
I don't have a DNA or any other 1080 * 1920 device that uses a portrait layout (no rotation in recovery). I am unable to do the upscale myself. There's a theme guide on our website if someone wants to to do it.
Click to expand...
Click to collapse
Alright I will give that a try later today.
Sent from my HTC Droid DNA
For some reason I can't make backups anymore. It gets about a quarter way, then reboots. I tried cwm..and same issue. Anyone have any ideas?
it has rebooted on me during a backup as well. i tried again and was successful, but there definitely seems to be a bug somewhere
Hello,
Definitely a bug, seems that after the first successful backup unit will no longer get past the system file.
UPDATE, your backups will complete if you do not change the name. Leave it as the date or default name If this does not work for you the only other thing I have done since it was rebooting was to install/update busybox. This may also work for those who are restoring backups and getting the reboot...did you change the file name? Whatever I am sure it is just a temp bug that will be fixed soon as well as the layout.
Cheers
Has anyone got a fix for the screen size yet?
starscream86 said:
Has anyone got a fix for the screen size yet?
Click to expand...
Click to collapse
I was looking into it ealier today. I haven't gotten it just yet tho.
Sent from my HTC Droid DNA
jschill31 said:
Hello,
Definitely a bug, seems that after the first successful backup unit will no longer get past the system file.
UPDATE, your backups will complete if you do not change the name. Leave it as the date or default name If this does not work for you the only other thing I have done since it was rebooting was to install/update busybox. This may also work for those who are restoring backups and getting the reboot...did you change the file name? Whatever I am sure it is just a temp bug that will be fixed soon as well as the layout.
Cheers
Click to expand...
Click to collapse
I have backups failing when not changing the name as well. Bug happens either way.
After several attempts I am eventually able to get a good backup, but it fails more often than it completes.
Deuces said:
I have backups failing when not changing the name as well. Bug happens either way.
After several attempts I am eventually able to get a good backup, but it fails more often than it completes.
Click to expand...
Click to collapse
Interesting, obviously this needs a bit of work. I have not tried to make another one, I have been spending time modding the factory shipped rom. There are so many features hidden by Verizon. Also there is something running in the background that eats our batteries. Hard to start cranking on a rom without a reliable recovery. I sent a note over on the TWRP website, hopefully someone will have some ideas. On the size issue has anyone tried using a TWRP skin from one of the 1080p tablets?
Cheers
Have you looked into using one of the 1080p tablet themes? I plan on doing that tonight.
Sent from my HTC6435LVW using Tapatalk 2
jschill31 said:
Have you looked into using one of the 1080p tablet themes? I plan on doing that tonight.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
Any luck with that?
starscream86 said:
Any luck with that?
Click to expand...
Click to collapse
Hello,
Actually a big NO on that...this recovery isn't even recognizing the THEME folder? It seems this has a few bugs to iron out. I looked at pulling the resource the other day and building a new one but I can't seem to find a reliable git for the DNA? If anyone knows of one please let me know and I will pull the files late tonight. I am not a DEV by all means but have been building for multiple devices for over two years and have a smoking build machine. I am not comfortable working on any roms until we have a solid recovery. Don't get me wrong, this does backup after a few tries but what I am worried about is a fail when trying to restore. I have read where Clockwork it the same way, seems to have something to do with the partitions?
Cheers
oZoP Development Projects are on the way!!!
ONE ZIP ONE PLACE
System Transition Animations mod
By flashing this zip you will be given a bunch of choices for different system animation style for screen/window transitions, keyboard/toast views and many others. You will get an additional option to tweak a little for unique styles!!
So I give you this, UNIVERSAL for MOST devices Aroma installer to give users the option for different choices!
This zip will work for MOST device running ANY Rom with ANY version Android 5.0+!
How to use the ozop-restore.zip to revert/recovery quickly without the need to restore or reinstall the whole Rom:
And just to be safe, I have included in my scripts and files a method that will create a flashable restore zip of your files before the mods does its thing!
The restore zip will be inside the new "ozop" folder that has been created and the zip is named "ozop-restore.zip"
If something doesn't play nice, just flash the zip and you'll be back to the way it was before you flashed the mod
NOTE: the script will delete any existing restore zips EVERY TIME you flash a new option, meaning that if you flash the mod again, your original system files will be replace with the file you flash previously!
If you want to have a permanent back up of the original file, you will need to rename the zip inside the ozop folder to whatever, just can't have the same name or it gets replaces everything you flash the mod
BUG REPORT:
Code:
MIUI choice causing boot issues for some users (works fine for me), so be prepared to you the restore.zip if needed. Will look into a fix for future releases
Report bug properly to get my support
Of course there are many way to properly report bugs and ALL of these ways have one thing in common, THEY ALL REQUIRE VERY DETAILED NOTES of the issue!
I'm not going to go deep into how detailed you could get because lets face it, most people that report improperly are the ones who don't read and probably are going to read this! HaHaHa...
To get support from me I only ask for some simple things
1. What device, and rom you are running
2. What is the issue (no boot, fc everywhere, fc only certain app etc...)
3. Which option did you select
4. Did you get the install log
5. Did you use the restore.zip option to get back running
6. Do other choices share the same effect
That looks like a lot, but it really is the minimum amount of info need to troubleshoot!
Provide me that and I'll do my best to fix things and make this fun for everyone.
If you post things like
"Doesn't work", "bootloop" or anyone other similar post that have no value and help development is no way, actually these kinds of post only put development behind and slow progress die the fact that anyone who cam help has to waste their time reading it!
If these kind of post ever come up, its best to ignore the lazy person and not clog the thread with flaming replies as that too slows development!
Anyway, I don't expect there to be many if any bugs! Been tested by myself and confirmed with users of this device!
Now grab the download and enjoy!
DOWNLOAD v1.1 HERE
SYSTEM ANIMATIONS PREVIEW PAGE:
Note: the animation have unique motions and some may look better with some minor adjustments to animations speeds. Some are better set to quick speed, others set slow. You will have to decide as per your needs.
You can access these adjustments via developer options in settings (activate if not shown by clicking about device/software version/build number 7 times)
List of the current animation:
COMPLETE SYSTEM ANIMATIONS
"oZoP Custom Missing Link Animations",
"Nexus 7 Ported Animations",
"Blur Animations"
"iOS Animations",
"Flyne OS Animations",
"Stock Animations",
"Google Pixel Animations",
"MIUI Animations"
ANIMATION ADJUSTMENT ADD-ON FOR POP-U AND DIALOG ANIMATIONS
"Bounce Style Dialog Animations",
"Drop In Style Dialog Animations",
"Flip in Flip mix Style Dialog Animations",
"Fold Style Dialog Animations",
"Slide Style Dialog Animations",
DEVICE COMPATIBILITY
Confirmed compatible devices for this version:
LG
OnePlus
Confirmed NOT compatible with the version:
?Samsung
PREVIEWS:
Credits:
spanna for the original vrtheme script
changelog:
v1.1
*added support for OnePlus and possibly more devices..
*cleaned up Aroma code
*added ext sdcard calculation to device info and mount info
v1a
*removed incompatible Samsung styles
*changed text style in Aroma UI
*fixed mounting
*fixed install log recording
v1
*initial release
XDA:DevDB Information
oZoP Development - System Animations, Theme for the OnePlus 3T
Contributors
stangdriver44
Version Information
Status: Stable
Stable Release Date: 2017-07-30
Created 2017-07-30
Last Updated 2017-08-06
Cool mod
Great... All in one place... Missing link is my favourite... Many thanks dev
Missing link animation is great.... Will try more animation on oos 4.1.6
Welcome
@stangdriver44, great to see you here! your amazing work for the Galaxy S6 was the only reason I kept it for as long as I did. Ultimately touchwiz killed me and I switched to the 1+3T.
Miui animation giving bootloop...
Does it provide Miui recent apps horizontal thumbnails style?
Sent from my LG-H870DS using XDA-Developers Legacy app
Does it require root and trwp?
PashaF said:
Does it require root and trwp?
Click to expand...
Click to collapse
Yes
---------- Post added at 08:41 PM ---------- Previous post was at 08:41 PM ----------
EMJI79 said:
Does it provide Miui recent apps horizontal thumbnails style?
Click to expand...
Click to collapse
No
Whoever wish to use this theme first pls make sure that u took a original backup of system animation as said by OP otherwise you can stuck on bootloop. However most of the animation is working on my oos 4.1.6
It broke most of my apps running 7.1.2 resurrection remix CAF version with stock kernel (whatsapp, contacts, playstore, GMS) , i had to revert back using the restore zip and waiting for it to boot up. thanks anyway.
OP updated with the Preview page
SYSTEM ANIMATIONS PREVIEW PAGE:
I am also looking at the MIUI animations that some users are having trouble with.
Hopefully a fix and possibly more animation options coming soon...
stangdriver44 said:
OP updated with the Preview page
SYSTEM ANIMATIONS PREVIEW PAGE:
I am also looking at the MIUI animations that some users are having trouble with.
Hopefully a fix and possibly more animation options coming soon...
Click to expand...
Click to collapse
hope you can make this more modular, i like missing link keyboard animation, and like ios transition
so for now i use missing link + drop down transition
hope more option coming on next release
Missing link and iOS animations worked fine for me on RR . Using missing link right now. Missing link working on my son's nexus 6 running RR as well
Now my smartphone looks much better.
I use the Nexus 7 Style.
Thank you for your work .
Can you add the OxygenOS animations? The fading etc that they add is very nice.
I can't flash the zip through TWRP, when i try it says that it cannont be installed and it gives me error 255.
Model: Asus Zenfone 2 Z00A
ROM: LineageOS 14.1
I tried mutiple times and also tried moving the zip from the SD to internal storage but it gave me the same error again.
I really hope you can help me because i really want those iOS animations since LOS ones suck.
OBS: This is the only info i can give to you since i can't even see the Aroma GUI, the error happens as soon as i try to flash the zip.
Edit: Through a little research i now think is because me phone is x86 and not arm, would you kindly make it x86 compatible? Please?
Edit 2: Here's the recovery log i copied right after the error appeared: https://pastebin.com/6q1cwdeA (the flashing process starts at line 1022)
Edit 3: Managed to fix the 255 error by replacing the "update binary" file with one compatible with x86 (from lineageOS). But now i get another error, this time error 6, which apparently has something to do with the "updater script" file i think.
lucassilvas1 said:
I can't flash the zip through TWRP, when i try it says that it cannont be installed and it gives me error 255.
Model: Asus Zenfone 2 Z00A
ROM: LineageOS 14.1
I tried mutiple times and also tried moving the zip from the SD to internal storage but it gave me the same error again.
I really hope you can help me because i really want those iOS animations since LOS ones suck.
OBS: This is the only info i can give to you since i can't even see the Aroma GUI, the error happens as soon as i try to flash the zip.
Edit: Through a little research i now think is because me phone is x86 and not arm, would you kindly make it x86 compatible? Please?
Edit 2: Here's the recovery log i copied right after the error appeared: https://pastebin.com/6q1cwdeA (the flashing process starts at line 1022)
Edit 3: Managed to fix the 255 error by replacing the "update binary" file with one compatible with x86 (from lineageOS). But now i get another error, this time error 6, which apparently has something to do with the "updater script" file i think.
Click to expand...
Click to collapse
This mod is made keeping the OnePlus 3T in mind, buddy. You should have expected it to not work on the ASUS Zenfone. Moreover, ARM - x64 v/s Intel - x86 (32 bit). It was bound to fail.
No updates??
Will it work on one plus 3t 5.1 oxygen os