Related
I've looked around and can't seem to find a proper guide of how to make flashables I know newer cwm's use an amend script as opposed to the older edify what ever that may mean xD .... anyways I want to start creating my own shiz I don't want to give details but I think it might be kind of special and could interest some nerds anyways if someone can point me in the direction of a proper guide/ tutorial I will much appreciate it.
Sent from my OG Epic
Someone recently asked a similiar questioon. Maybe their thread will help?
http://forum.xda-developers.com/showthread.php?t=1394328
sent from a phone using an app
Figured it was as easy as modifying someone elses zip but wanted to make sure
Sent from my OG Epic
Biggoron said:
Figured it was as easy as modifying someone elses zip but wanted to make sure
Click to expand...
Click to collapse
Often it's as easy as gutting another flashable .zip that you know works, then replacing the directory structure and files with what you want to install. If you want a neater solution with more customization, adamdelozier found benzyniarz1's UpdateZipCreator utility, which provides much more customization possibilities. It currently has a bug that causes scripts to fail, thus causing the entire flashable .zip to fail, but I've let the developer know what's up so hopefully a fix will be out soon. If you want to learn about the bug and the workaround, see pages 5 and 6 and pay close attention to the "Error 6" and "EOL" related posts.
Customization kind of like what the script shows ex: after flashing rc it says your phone is now legendary?
Sent from my OG Epic
Biggoron said:
Customization kind of like what the script shows ex: after flashing rc it says your phone is now legendary?
Click to expand...
Click to collapse
Yes, you can create a custom script from scratch within the utility, and it has the most used commands available to drop into your script, along with a very brief description of syntax for each. Read the OP for the utility to get an idea of its range of features.
AmericanJedi001 said:
Yes, you can create a custom script from scratch within the utility, and it has the most used commands available to drop into your script, along with a very brief description of syntax for each. Read the OP for the utility to get an idea of its range of features.
Click to expand...
Click to collapse
You are the man jedi. Thanks for updating the op also
sent from a phone using an app
Djinn23 said:
You are the man jedi. Thanks for updating the op also
Click to expand...
Click to collapse
Word! Umm, which OP are you refering to? I've updated a couple different OPs this evening, that's why I'm confused!
Thanks as well this is what I did with the knowlegde gained here.
http://forum.xda-developers.com/showthread.php?t=1404886
Sent from my OG Epic
AmericanJedi001 said:
Word! Umm, which OP are you refering to? I've updated a couple different OPs this evening, that's why I'm confused!
Click to expand...
Click to collapse
Yea I typed that knowing it was misuse n abuse. Sorry. I meant the link above I provided to this thread where the people were struggling to find out why it was broken and you explained the bug you linked to here. Jedi's always pop in, save, then boogie. Not choad chomping or anything but I also read your proposal for documentation formatting and lmmfao at your example.
sent from a phone using an app
Biggoron said:
Thanks as well this is what I did with the knowlegde gained here.
http://forum.xda-developers.com/showthread.php?t=1404886
Sent from my OG Epic
Click to expand...
Click to collapse
Awesome. Not my personal cup of tea but I am sure someone somewhere is thinking you are the motts! Well done.
sent from a phone using an app
Most people aren't picky about their cwm zips, basicly it consists of the items you want to flash, the stuff to flash it with, and an updater-script and updater-binary. I usually just take someones updater-binary and write my script from scratch
sent from my always aosp epic
Biggoron said:
Thanks as well this is what I did with the knowlegde gained here.
http://forum.xda-developers.com/showthread.php?t=1404886
Click to expand...
Click to collapse
Interesting... I'm glad you found what you needed!
Djinn23 said:
Yea I typed that knowing it was misuse n abuse. Sorry. I meant the link above I provided to this thread where the people were struggling to find out why it was broken and you explained the bug you linked to here. Jedi's always pop in, save, then boogie. Not choad chomping or anything but I also read your proposal for documentation formatting and lmmfao at your example.
Click to expand...
Click to collapse
Ah, now I understand, my young padawan. Awww, no choad chomping? But seriously, I'm glad I got a laugh out of you! Unfortunately, I'll have to clean parts of it up to get the Mods to sticky it.
Back on topic, the dev of UpdateZipCreator hit me back and said he'll release a fixed version of his utility soon.
UpdateZipCreator has been updated to use UNIX newline / end-of-line / EOL characters in the script generator / editor, which should eliminate "Error 6" when flashing .zips in CWM Recovery.
UpdateZipCreator
AmericanJedi001 said:
UpdateZipCreator has been updated to use UNIX newline / end-of-line / EOL characters in the script generator / editor, which should eliminate "Error 6" when flashing .zips in CWM Recovery.
UpdateZipCreator
Click to expand...
Click to collapse
Awesome too bad I'm headed to bed thanks ill try it out tomorrow. Is this complex or does this generate script or do I have to? That's over my head but yeah...
Edit nevermind took a look at. Any way to change what the binary script displays ie. What it shows in the script when flashing..." your phone is now legendary"
Sent From My Cyan Samurai
Biggoron said:
Awesome too bad I'm headed to bed thanks ill try it out tomorrow. Is this complex or does this generate script or do I have to? That's over my head but yeah...
Edit nevermind took a look at. Any way to change what the binary script displays ie. What it shows in the script when flashing..." your phone is now legendary"
Click to expand...
Click to collapse
This has example scripts, but I don't remember it dynamically generating scripts based on what you install. You must customize the scripts yourself, to include mounting the partition you wish to install to, install package, and screen output. FYI, IIRC the screen is 48 fixed-width characters wide in CWM Recovery. That should help make pretty output screens!
Well i will share my knowladge to you people, two years of learning stuff about android....
If this guide dont help you (0,01 possibilities) LOGCAT YOUR BUILD!! I WILL TRY TO HELP
Tools needed /by saranhai/:
7zip (alternative to winrar, doesn't matter which you choose to use)
Notepad++ (highly recommend if you're on windows)
Android SDK/ADB (MUST HAVE, for troubleshooting and such)
dsixda kitchen (could come in handy)
First to port an ics rom you need winrar.
This are the steps:
grab an ics rom like cm9 or aokp to take the libs and hw folders
Never unzip the rom.
1-from cm9/aokp copy all outside system, i mean boot.img mtd etc..... and past it over the rom you are porting (nexus s rom)
2-enter system/app and remove torch.apk, crespoparts.apk and replace camera.apk with aokp camera.
3-enter system bin and replace this files with aokp/cm9 ones
*dhcpcd
*bluetoothd
*vold
*wpa_client
*wpa_supplicant
Click to expand...
Click to collapse
4-enter system etc and replace this files with aokp/cm9 ones
*bluetooth folder
*dhcpcd folder
*Apnconf.xml
*wifi
*vold.fstab
*vold.conf
Click to expand...
Click to collapse
5-Then we go to the libs, enter system/lib and replace:
*HW folders
*modules folders
*egl folders
*libril.so
*libsec-ril.so
*libreference-ril.so
*libsec-ril-client.so
*libbluedroid.so
*libbluetooth.so
*libbluetoothhd.so
*lib_cameraclient.so
*libcameraservice.so
*libhardware_legncy.so (very important to wifi to work) hell this caused me problems
*libEGL
*libgles (the 3 files)
Click to expand...
Click to collapse
--------------replace usr and vendor folders-------------------
And last edit build.prop, well first check if it boots then you change this and add this.
edit this:
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ADD THIS TO SIGNAL TO WORK!!
additional build propieties
ro.telephony.ril_class=SamsungRIL
ro.telephony.ril.v3
=icccardstatus,datacall,signalstrength,facilitylock
mobiledata.interfaces=pdp0,eth0,gprs,ppp0
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
Click to expand...
Click to collapse
ADVANCED USERS ONLY (dont ask me how) :
for working external sd (emcc) you need to decompile/recompile framework-res.apk
you need to change this:
xml/storage_xml with other storage xml from aokp or cm9
Click to expand...
Click to collapse
I´m not responsible for bricked devices (this shouldnt brick it) but i dont want anyone crying because i will laugh at you, it works for me..
Libs functions
Lib:
*Libhardware_legancy.so (makes wifi works)
*all libs with ril: DATA and SIGNAL
*LibEGL, modules, hw: hw aceleration, lights,etc...
*Libgles (Gpu and cpu)
Click to expand...
Click to collapse
etc:
*apns-conf.xml (all related to apn and services)
*dchcpd,vold.ftsab,vold.conf: internal sd
*wifi,bluetooth: wifi bluetooth lol
Click to expand...
Click to collapse
someone correct me if im wrong but im preaty sure what im writing...
Thanks for this thread. It should give many new possibilities!
amazing guide thx for sharing
Things i would add:
7zip (alternative to winrar, doesn't matter which you choose to use)
Notepad++ (highly recommend if you're on windows, used to edit build.prop and other text files)
Android SDK/ADB (MUST HAVE, for troubleshooting and such)
dsixda kitchen (could come in handy)
I will add more if i think of any
EDIT: Forgot this...
If you are experiencing issues booting up, here's how to get a logcat so you can figure out what's wrong:
connect phone to computer
open up command prompt
navigate to your android sdk tools folder i.e C:/androidsdk/platform-tools (ADB MUST BE SET UP BEFOREHAND)
type in:
Code:
adb logcat
watch as a whole bunch of text scroll by, don't bother reading it right now, do it later.
If you want to stop the logcat, just disconnect phone from computer.
-Saranhai
saranhai said:
Things i would add:
7zip (alternative to winrar, doesn't matter which you choose to use)
Notepad++ (highly recommend if you're on windows, used to edit build.prop and other text files)
Android SDK/ADB (MUST HAVE, for troubleshooting and such)
dsixda kitchen (could come in handy)
I will add more if i think of any
-Saranhai
Click to expand...
Click to collapse
Okey i added them
Nice guide. Thanks.
Nice guide!!! Thanks!
Will try this out later
Sent from my PG86100 using xda premium
i have a question ... How you can test your own ported rom ? Because i dont want to brick my phone (again) ))
Driv said:
i have a question ... How you can test your own ported rom ? Because i dont want to brick my phone (again) ))
Click to expand...
Click to collapse
oh, haha i dont think there is another way rather than using your device as a lab rat.... lmao
I give you an unbrickeable guide, if you dont forget to swapp the boot.img and hw and modules folder you wont brick it since recovery is on the kernel, so you can restore or do what you want, if you flash a nexus s kernel (as example you forgot to remove it) you will soft brick it
Madflapjack respond to your pm's, I need some help!
EDIT: resurrected a dead thread sorry..
Sent from my GT-I9000 using xda app-developers app
Madflapjack,
Hope you are ok.
Does this guide works with jellybean roms?
malcho said:
Madflapjack,
Hope you are ok.
Does this guide works with jellybean roms?
Click to expand...
Click to collapse
exactly what i want to ask for. since nexus S got the OTA official update.
malcho said:
Madflapjack,
Hope you are ok.
Does this guide works with jellybean roms?
Click to expand...
Click to collapse
im ok thanks for asking !! i moved to the galaxy nexus thats why im not posting much lol, im playing with the baby!
to the point, you should try, it wont harm, but if you do try, dont port aosp, they need special coding in framework or something similar and you will get a nice dark screen on booting, well if its cyanogenmod or aokp then yes it should work..
Madflapjack said:
im ok thanks for asking !! i moved to the galaxy nexus thats why im not posting much lol, im playing with the baby!
to the point, you should try, it wont harm, but if you do try, dont port aosp, they need special coding in framework or something similar and you will get a nice dark screen on booting, well if its cyanogenmod or aokp then yes it should work..
Click to expand...
Click to collapse
Nice to see that you are ok.
My constant struggle with codenameandroid,trying few guides butt none work.
It's ok i will wait till sources are out.
Many regards
malcho said:
Nice to see that you are ok.
My constant struggle with codenameandroid,trying few guides butt none work.
It's ok i will wait till sources are out.
Many regards
Click to expand...
Click to collapse
jb codenameandroid? it should work, worth the try!! but well remember to replace the kernel so you dont lose your recovery and your good to go.
if i dont bad remember my codename android port was booting and all ok, i was talking about pure aosp,
T
Madflapjack said:
jb codenameandroid? it should work, worth the try!! but well remember to replace the kernel so you dont lose your recovery and your good to go.
if i dont bad remember my codename android port was booting and all ok, i was talking about pure aosp,
Click to expand...
Click to collapse
I tried butt it stuck on boot animation.
Trying tommorow again.
malcho said:
T
I tried butt it stuck on boot animation.
Trying tommorow again.
Click to expand...
Click to collapse
so it boots, try watever you know to make it boot, if not logcat. lol
In case anyone is having trouble finding toro as a device target when trying to build from the list of targets from the 'lunch' command... Toro didn't show up in the list but I was able to manually specify it rather than selecting a numeric option.
Devs probably know that works, but amateurs like myself might benefit from that tidbit. Jellybean seems to be building OK for me now.
EDIT: I was asked what I did, more specifically, so I'll put that here in op:
Rather than enter a numeric choice, I entered 'full_toro-userdebug'. Apparently this was a valid response and the build proceeded.
Mind explaining how you manually selected it?
keith.mcintyre26 said:
Mind explaining how you manually selected it?
Click to expand...
Click to collapse
Not at all. Rather than selecting say, 11 or another choice, I entered: full_toro-userdebug. Apparently this was a valid response and the build proceeded.
question... not much into actual developing here but i know my way around the inside of a rom or two... once you compile. will it be a fully capable rom? as in (what the OTA will be like without VZ apps)?
spunks3 said:
question... not much into actual developing here but i know my way around the inside of a rom or two... once you compile. will it be a fully capable rom? as in (what the OTA will be like without VZ apps)?
Click to expand...
Click to collapse
It's not as 'polished'. There are no gapps, the dictionary is not complete (need a version from a factory image/rom), there are extra keyboards (Japanese?), maybe a couple other oddities as compared to a stock ROM. It will certainly be more capable that porting a gsm rom to toro, that's for sure .
mmuzzy said:
Not at all. Rather than selecting say, 11 or another choice, I entered: full_toro-userdebug. Apparently this was a valid response and the build proceeded.
Click to expand...
Click to collapse
I did that right after I asked haha. Building now. Thank you.
Sent from my Galaxy Nexus using xda premium
keith.mcintyre26 said:
I did that right after I asked haha. Building now. Thank you.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You're very welcome. Happy flashing.
I thought you meant the whole system. I was wondering where you got the jellybean source
Sent from my Galaxy Nexus using Tapatalk 2
phydo said:
I thought you meant the whole system. I was wondering where you got the jellybean source
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Google released it into the wild today:
https://groups.google.com/forum/?fromgroups#!topic/android-building/XBYeD-bhk1o
mmuzzy said:
Google released it into the wild today:
https://groups.google.com/forum/?fromgroups#!topic/android-building/XBYeD-bhk1o
Click to expand...
Click to collapse
Haha uhh.. I did realize that about two minutes ago. Thanks.
Sent from my Galaxy Nexus using Tapatalk 2
phydo said:
Haha uhh.. I did realize that about two minutes ago. Thanks.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I was actually trying to pull it before Google was finished so it hasn't been that long.
Hey can you help me out? Is your android version showing as 4.0.9.99.999.9999.99999? Wth?
anton2009 said:
Hey can you help me out? Is your android version showing as 4.0.9.99.999.9999.99999? Wth?
Click to expand...
Click to collapse
Lol!
Sent from my Galaxy Nexus using Tapatalk 2
phydo said:
Lol!
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Well... I figured out why it was showing like that; because I was syncing the master branch and not the 4.1.1 branch. But I'm still confused on this
Not to thread jack, but i have my rom building, but to actually personalize the rom, is there any app like eclipse or is it just editing files in the zip?
cdrshm said:
Not to thread jack, but i have my rom building, but to actually personalize the rom, is there any app like eclipse or is it just editing files in the zip?
Click to expand...
Click to collapse
You edit the source files. The goodies you want are in the res folder of most applications. /packages/apps in the source code. Here's my question, when I boot it gets to the Google screen and then a black screen. I suspect this here. When I start the build I see this:
Code:
find: 'src': No such file or directory.
PRODUCT_COPY_FILES device/generic/goldfish/data/etc/apns-conf.xml:system/etc/apns-conf.xml ignored.
... Many more of these Product copy ignored things...
And then it finishes compiling. What's up here, I'm pretty sure it's missing drivers and stuff!
CPCookieMan said:
You edit the source files. The goodies you want are in the res folder of most applications. /packages/apps in the source code. Here's my question, when I boot it gets to the Google screen and then a black screen. I suspect this here. When I start the build I see this:
Code:
find: 'src': No such file or directory.
PRODUCT_COPY_FILES device/generic/goldfish/data/etc/apns-conf.xml:system/etc/apns-conf.xml ignored.
... Many more of these Product copy ignored things...
And then it finishes compiling. What's up here, I'm pretty sure it's missing drivers and stuff!
Click to expand...
Click to collapse
Did you install the binaries for toro? There is also a script that will pull them from your phone (so a stock rom is best), which may be better because Google can't give you everything you need for a functional rom (GPS for example). I ended up copying those files from a stock image to my compiled rom.
i got my binaries from here https://developers.google.com/android/nexus/drivers#torojro03c
mwalt2 said:
Did you install the binaries for toro? There is also a script that will pull them from your phone (so a stock rom is best), which may be better because Google can't give you everything you need for a functional rom (GPS for example). I ended up copying those files from a stock image to my compiled rom.
Click to expand...
Click to collapse
cdrshm said:
i got my binaries from here https://developers.google.com/android/nexus/drivers#torojro03c
Click to expand...
Click to collapse
For future reference, what he's referring to is the extract-files.sh script included in the CM source. If you cannot find the proprietary binaries for a certain device you wanna build for, plug in the phone via usb, cd to the directory with the script and execute the command.
anton2009 said:
Well... I figured out why it was showing like that; because I was syncing the master branch and not the 4.1.1 branch. But I'm still confused on this
Click to expand...
Click to collapse
I also got version 4.0.9.99.999.9999.99999 when I synced to the master branch. Thanks for mentioning the workaround to sync with 4.1.1_r1 .
Did you figure out if it's a problem to sync 4.1.1 into a directory that's already synced with master (4.0.9.99...)?
--------------------------------
Update: I think I can answer this question based on JBQ's response:
https://groups.google.com/d/msg/android-building/rtH5ZbJC7qU/-N1lr9MqexYJ
"You can also switch in place: just run "repo init -b <new_manifest_branch>; repo sync" in your existing client."
Sounds like syncing to a new branch in the same working directory should work just fine.
***OFFICIAL THREAD FOR THIS ISSUE FOR THE OPTIMUS G PRO E980***
I have the necessary APKs and other files to make a flashable zip, however whenever I try to flash it it succeeds but when I click on quickremote, the app force closes on me and will not load. How can we successfully get this to work on lollipop? I have posted several times in the forums but nobody seems to care about helping get this done.
Here is a the link to my pasted logcat relating to this error. I uploaded it to pastebin.
http://pastebin.com/1GhY8b3T
rjmxtech said:
I have the necessary APKs and other files to make a flashable zip, however whenever I try to flash it it succeeds but when I click on quickremote, the app force closes on me and will not load. How can we successfully get this to work on lollipop? I have posted several times in the forums but nobody seems to care about helping get this done.
Click to expand...
Click to collapse
Take a logcat and see what's in there (use google, to search how to do that. )
Sunandroid said:
Take a logcat and see what's in there (use google, to search how to do that. )
Click to expand...
Click to collapse
I sent you a PM
wow, this is proving to be just as uneventful as it sounds.... dude, if you're going to ask for or write a guide, make its own thread.
berryman13 said:
wow, this is proving to be just as uneventful as it sounds.... dude, if you're going to ask for or write a guide, make its own thread.
Click to expand...
Click to collapse
I replied to one of your posts on another thread. @Snepsts and I are attempting to figure this out at the moment through PM's and such. I will make a thread for it if we get anywhere with it.
I pasted a logcat on pastebin and put the link in the OP
Are you sure, you got all files? Odex file? Another part of the apk? Set the right permissions? Do you use a custom screen density?
Sunandroid said:
Are you sure, you got all files? Odex file? Another part of the apk? Set the right permissions? Do you use a custom screen density?
Click to expand...
Click to collapse
Check your inbox BTW. I just sent you a message.
Code:
03-02 12:34:40.312 E/AndroidRuntime(4334): java.lang.NoClassDefFoundError: Failed resolution
by: java.lang.ClassNotFoundException: Didn't find class "com.lge.systemservice.core.LGContext" on path: DexPathList[[zip file "/system/app/LGQRemote.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
First is why I asked about density. Try it out with stock density of the G3
2nd: Those are the patha I'd go diggin. Maybe gonna explain a bit closer/have a closer look tomorrow. Got to sleep now.^^
Amything new here? Have you already searched in the fokders I "mentioned"?
I'm back and trying to get this working once more. It is so odd that the way they got this working on the G2 and G3 does not work on ours. It makes me think that the stock LG ROM with lollipop for the G Pro is just a bunch of hacks LG threw into a zip file which just makes this even more difficult. I'm not going to give up yet though. If anyone else has any suggestions please PM me. I would gladly appreciate more ideas.
---
rjmxtech said:
---
Click to expand...
Click to collapse
As already asked, what was the results of digging in the directories I mentioned. And better don't take this to PMs...
Sunandroid said:
As already asked, what was the results of digging in the directories I mentioned. And better don't take this to PMs...
Click to expand...
Click to collapse
I'm pretty sure I tried it and it didn't work but I will give it another go
@Sunandroid, how can I get the odex files without installing the ROM myself. Is there a way to accomplish this?
rjmxtech said:
@Sunandroid, how can I get the odex files without installing the ROM myself. Is there a way to accomplish this?
Click to expand...
Click to collapse
Not sure, but it should be doable by unpacking the roms zip.
Sunandroid said:
Not sure, but it should be doable by unpacking the roms zip.
Click to expand...
Click to collapse
I am pretty sure the odex files are generated when the ROM is installed. This means I need to have someone who has the ROM working to get them to me.. The zip only has the files from the system partition.
rjmxtech said:
I am pretty sure the odex files are generated when the ROM is installed. This means I need to have someone who has the ROM working to get them to me.. The zip only has the files from the system partition.
Click to expand...
Click to collapse
Yeah, and the odes files usually are in system partition. Post a link to the ROM, you want to ectract the remote from, please. Gonna dig in there next weekend if O got the time.
Sunandroid said:
Yeah, and the odes files usually are in system partition. Post a link to the ROM, you want to ectract the remote from, please. Gonna dig in there next weekend if O got the time.
Click to expand...
Click to collapse
Here is the link to the ROM's thread. http://forum.xda-developers.com/showthread.php?t=3043779
Just bumping this up. I have had no luck with it at all. Need help from others.
I got bored, so I decided to build the latest TWRP. Big thanks to @negamann303 for his source. I only made minor, mostly theme related, tweaks to it. The only non-theme related tweak that I can remember is that I enabled the flag that enables taking advantage of NEON, so that might result in some speed increases, but I haven't done any tests to confirm that.
Q: Sweet! Does ADB backup work?
A: No. Sorry. If you know how to make it work, please let me know and I will implement it.
Q: Oh. So this is basically the same as the previous version?
A: Pretty much. I imagine it supports a whole bunch of new things that our watch isn't capable of, but who cares. It also features the nag screen that asks if you want to install the official TWRP app, which is useless in this case. You can tell it to stop though.
Q:So why should I bother with this?
A: Because you're a flashaholic that needs to have the latest and greatest thing. Duh.
SOURCE
Device: https://github.com/theSt33v/omni_twrp_device
Kernel: https://github.com/Negamann303/Huawei-W-1.5-2.0
TWRP: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni
Does this work with the android 2.0 on the Huewai? Also, is there an img file to flash in fastboot? Thanks.
jnewberry1 said:
Does this work with the android 2.0 on the Huewai? Also, is there an img file to flash in fastboot? Thanks.
Click to expand...
Click to collapse
It does, and - have you tried downloading the ZIP and checking what's hiding inside?
munky-head said:
It does, and - have you tried downloading the ZIP and checking what's hiding inside?
Click to expand...
Click to collapse
LOL. My bad. I just assumed it was a flashable zip. Thank you.
1st of all: Thank you soo much!!!!
How could I theme this?
(also you only build it with a local manifest or do you also have a git, which I could fork for theme testing?)
BIade said:
1st of all: Thank you soo much!!!!
How could I theme this?
(also you only build it with a local manifest or do you also have a git, which I could fork for theme testing?)
Click to expand...
Click to collapse
Sources are posted in the OP. Help yourself. I don't know much about TWRP theming, but I do know that the files you want to modify are found in device/huawei/sturgeon/watch_mdpi. This is the folder that was modified by @negamann303, and by myself to a lesser extent, to get the theme that you see in the version that I built. There is also a watch_mdpi folder in the TWRP source somewhere that contains the default watch theme. TWRP is also capable of themes that can be applied post-build so you don't have to build a new one every time you want it to look different, but I don't know anything about how to make that happen. Search XDA for flashable TWRP themes for examples, but make sure they're for 3.1.0. The theme template has changed a bit from previous versions. Hope that helps!
TheSt33v said:
Sources are posted in the OP. Help yourself. I don't know much about TWRP theming, but I do know that the files you want to modify are found in device/huawei/sturgeon/watch_mdpi. This is the folder that was modified by @negamann303, and by myself to a lesser extent, to get the theme that you see in the version that I built. There is also a watch_mdpi folder in the TWRP source somewhere that contains the default watch theme. TWRP is also capable of themes that can be applied post-build so you don't have to build a new one every time you want it to look different, but I don't know anything about how to make that happen. Search XDA for flashable TWRP themes for examples, but make sure they're for 3.1.0. The theme template has changed a bit from previous versions. Hope that helps!
Click to expand...
Click to collapse
Worked, thank you very much
Thank you, im really happy now
Cheers
Blade
P.S.: @TheSt33v I changed
Code:
%col1_x_left%
to 50 for some titles, due to the round sceen cutting some header texts in statusbar. (see last screenshot)
BIade said:
Thank you, im really happy now
Cheers
Blade
P.S.: @TheSt33v I changed
Code:
%col1_x_left%
to 50 for some titles, due to the round sceen cutting some header texts in statusbar. (see last screenshot)
Click to expand...
Click to collapse
Sexy. Maybe I'll look into making that an applyable theme for everyone if I find some time. Can you post your watch_mdpi folder?
Looks like 3.1.1 came out today. I'll have to get on that too.
TheSt33v said:
Sexy. Maybe I'll look into making that an applyable theme for everyone if I find some time. Can you post your watch_mdpi folder?
Click to expand...
Click to collapse
I already did ^^
BIade said:
I already did ^^
Click to expand...
Click to collapse
You explained what you did, but I don't see the actual folder uploaded anywhere. It would save me some time if I didn't have to reproduce what you did.
TheSt33v said:
You explained what you did, but I don't see the actual folder uploaded anywhere. It would save me some time if I didn't have to reproduce what you did.
Click to expand...
Click to collapse
Sorry, I meant, I already created a flashable theme-zip. I will share it tonight, when I arrive at home...
BIade said:
Sorry, I meant, I already created a flashable theme-zip. I will share it tonight, when I arrive at home...
Click to expand...
Click to collapse
I hate to nag you, but could you post that theme when you get a chance? I'd like to see it in person.
@TheSt33v Sorry mate, for the late response. As promised here my theme (Just a WIP, I used a template for the filestructure etc.)
This saves me time from having to do it myself, I can look into removing the nag screen if you haven't figured it out yet
Sent from my SM-G935P using Tapatalk
negamann303 said:
This saves me time from having to do it myself, I can look into removing the nag screen if you haven't figured it out yet
Sent from my SM-G935P using Tapatalk
Click to expand...
Click to collapse
I forgot it was even there, so I wasn't looking into it. Once you disable it the first time, it's gone for good unless you wipe the device. Let me know if you figure out how to get rid of it though. I'm surprised there isn't just a flag to enable.
Thx, worked as expected and the good thing is : sideload don't must be fall back to the old protocol
Sorry guys first time flash on android wear however i am familiar with android phone flash. Please tell me how to install this?
long.nguyen said:
Sorry guys first time flash on android wear however i am familiar with android phone flash. Please tell me how to install this?
Click to expand...
Click to collapse
Same as with a phone. Extract the .img file from the zip attached to the post, boot watch in bootloader mode, plug into computer, fastboot flash recovery [path to twrp image file].