So I want to try customizing a rom for my g925, but all the information I can find is outdated and abandoned or specific to a certain device or incomplete. I'm sure it's out there somewhere, but I just don't know what to look for.
I think the best way is using a kitchen based on what I've read so far, so is there one that works for s6 and s6 edge and works on windows? I've never dealt with linux, so I'd rather not have to start there. Cygwin is what I'd need right?
Somewhat related, (my g925f 32gb is gonna be replaced by a g925t 128gb once I figure all this out) there's a bunch of videos on youtube (with links to download the file) to convert a g925t to g925f. These work fine, but still come with bloatware, so I'd like to make it myself. I found only one thread that doesn't work anymore because the basebands don't match or something.
Do I need a ton of space and time to build from source, or can I just modify the tar.md5 contents?
If anyone could help or point me in the right direction, I'd be really grateful!
Mmm. Somehow in all of my searches, I never found chef central. Now I've gotten somewhere. Should be able to narrow down my broad questions now.
Been using ASSAYYED Kitchen with great results. Got the stock MM rom totally debloated and updated some apps to the version I prefer!
Now I need to figure out how to disable the volume warning. I found this thread but it seems to be outdated for MM on the s6 edge. Still might be there hiding in the 1100+ pages of comments.
Also need to figure out how to make bootanimation.qmg's and such now that samsung's theme maker has been turned into a license application. I still have a few alternatives to look into like katkit or themeDIY. Bet I could probably find the old theme designer program floating around archive.org or elsewhere too.
Also need to bundle themes with the rom.
So I figured out how to disable the safe volume warning on 6.0.1 finally. Found this post, so I added
Code:
audio.safemedia.bypass=true
on its own line in build.prop at the end of the ADDITIONAL_BUILD_PROPERTIES section. Nice thing is it still leaves the little red zone in case I ever use the stock earbuds again, heh.
Now off to adding a new kernel and themes and bootanimations.
Related
Hello all!
Well i've used many search tools here on site, and i've also done some cutom searches on my phone, and yet can't find what i KNOW is here somewhere.
So i'm asking for a little help to point me in the right direction! I'm on the Samsung Fascinate (obviously) running 2.3.3 EC09 with Kernel 2.6.35.7
I would love to get my hands on a cutom dialer, and maybe even in addition to some customization onto contacts list look and feel.
Now directing me to themes and apps is not what im looking for, i dont care to add any full phone theme, i make my own custom (yet basic) themes, just wondering if there is any pre-made dialer replacements, and just maybe a contact list to go along??
I'm almost certain someone will call me blind and point me right there, but I really have came to my witz end looking, and have probably looked right over it!
Thanks in advance for the help in where to find what my mind seeks!!!!
Edit- Before someone asks or states " if you built your own theme why not a dialer?" Simply put, I don't want to!!!! I want a quick pre-made to move about my buisness with!!
hello guys just set up dxsidia android kitchen not sure if anyone uses this but i have a few questions and since dxsidia does not support this anymore was hoping someone could answer them for me...
1. is the major obvious one does it work on the photon in the thread it does say unconfirmed for atrix but nothing on photon?
2.after creating the work folder i go into advanced options and start editing? i realize since there is nothing on the photon most of my answers are probably going to be try and see but no harm in asking right...
3.it has a set of pluign scripts labeled sgs2/ sgs these are for samsung galaxy s right so i dont want to use any of them?
4. there is a task killer tweak you can add from it what exactly is this?
5. add data/app functionality??? lets you add or remove apps??? not sure is why im asking
there are more q's but i figured if i can get these answered im doing good
ive read the thread for a few days now and seems simple but confusing at same time seems like its a one click type thing but if you dont know for sure what you are clicking can really screw up and have to start from scratch... anywho trying to do more around here and would appreciate any help anyone has thanks a ton
1) Yes in terms of an apk is an apk. No in terms of the updater script (IIRC)
2) Yes, assuming theres options in the advanced menu you'd like to impliment
3) You don't need the Samsung plugins.
4) Changes minfree settings in the boot image. Be aware the ICS impliments memory handling differently than previous versions.
5) Adds a script and folder for data/app partition so you can include optional apps. Optional apks (things like nascar for example) could be placed in here and would be installed on flash. But because they are in /data, the user has the option to uninstall through manage apps.
Personal Opinion: While the kitchen may be a convienient way to do things, it leaves little (Read: No) room for learning. Assuming you'd like to create a body of work to be publically distributed and not just for personal use, it might be worth the upfront investment in figuring out how to do/script this stuff yourself. That's not me trying to be an elite a-hole, that's me giving solid advice.
Cheers!
Yeah im a trying to learn as much as i can ive been reading and reading and reading have always known about the kitchen just never tried it thanks for the response you didnt come off as elitest is all good i find its easier for me to learn by trying things while reading about it granted i do research in great lengths not just in xda but other forums, blogs, links so on and so on before even downloading these tools but as i said it seems to sink in better when i can go ok i use this option this what it means thats what it did this what its supposed to do/look like
Sent from my MB855 using xda premium
So ive been trying all day to spit out a rom with the kitchen and no matter what i do it doesnt install either get status 7 or 0 says was looking for 4agrs but only found 3 and sometimes says 3args but only found 2 ive tried using a rom i know flashes and just running it through the kitchen and flashing the output... idk what im doing wrong but starting to think it is not photon compatible any insider tips? i know i already asked this but not quite ready to surrender to defeat on this yet and i REALLY dont want to install linux or ubuntu on my computer would have to partition it and just not to keen on doing that to the family computer my kids and wife play on it almost more than i do
Hey guys, I have a few questions. I looked around a bit before posting this, but I may have missed some stuff so if I need to remove this thread just let me know that I should have looked harder(and kindly provide a link please).
First I would like to know how to get into "Themeing". I want to know how to change the colors mostly. I can usually find the file I need to edit in order to change the icon shape, but If I'm not mistaken, the colors are probably controlled in an xml file. They may all look for a "central file" that contains the colors, or I may need to change each one individually. If there is a central file could someone help me find out what it is.
I have only found how to edit apps, so here's where I get a major case of the noobs. Are the system colors controlled by the launcher or the theme or is there a UI that can be edited what do I need to do. I want to be able to change the number styles, the fonts of the keyboard, and all that jazz. The most important thing, though; is that I need to be able to change the colors. I really don't have an issue with the current fonts and don't have a good idea what to replace them with anyway.
---------------------------------------------------------------------------------------------
Now that the above train wreck is over I have some harder questions.
I also want to get into developing. I will probably start by modifying someone else's. (side question, could I re-release theirs with my changes just so that people could test it provided I ask and give them credit. I know this depends on the person, but is it taboo, or just a no for some people) I already read through and followed shrike1978's. It was possibly the best thing that could have happened to me. It showed me that it was actually possible to do for someone with less android experience. (link)
But after I have built it what do I need to do to get started modifying it? I'm not even sure what all I want to do, but is there any suggestions of a starter project, as well as a how to do it?(maybe changing the launcher, or something like that)
Also I have been using xfce linux mint on a second hard drive of 75 gigs. Will this be an ok setup? Should I switch to ubuntu although I don't really like it as much?
Should I be s-off or on (maybe on so that I know that they will be supported)? Also is there any good vm's that run in linux and will run android?
I probably missed a few questions that I intended to ask, so I will edit them in when needed.
I plan to make a how to thread on my findings(hopefully good enough shrike gives me a :highfive: for doing a good job) so everyone who helps (provided I actually learn how and am capable of making the how to) will be thanked in my future famous thread
Also I apologize for any miss-types. I will do my best to correct them, but my keyboard is pretty broken (it took a tumble when I moved home for winter break)
I figured out the fonts(at least for the few roms I checked). They are easy to change and add. They are controlled in a system_fonts.xml in the "\system\etc" folder of the rom. The files that they represent are in the "\system\fonts" folder of the rom. The xml file has a pretty good explanation of how it is read, so adding your own should be pretty easy.
If anyone here has any suggestions even if you dont know for sure let me know please.;
Here's some threads I had bookmarked that may help:
http://forum.xda-developers.com/showthread.php?p=16459009
http://forum.xda-developers.com/showthread.php?t=916814
I had another one that I can't find the bookmark for.
feralicious said:
Here's some threads I had bookmarked that may help:
http://forum.xda-developers.com/showthread.php?p=16459009
http://forum.xda-developers.com/showthread.php?t=916814
I had another one that I can't find the bookmark for.
Click to expand...
Click to collapse
You are my hero.
NOTE: A lot of this info is duplicated from a post i had made on droidrzr a while ago. I'm adding it here because i'm actively looking into getting this working once again and I would love any input/thoughts that other devs have on this topic.
Ok, so i've been poking around trying to get HDMI support working in non moto-based ROMs (basically anything that would be using kexec or an AOSP base like CM). It's not complete but i figure it's better to have more eyes on this than just mine. Apologies ahead of time if this post turns into a big info-dump, but here's what i have so far. Also, this is HDMI only, not webtop related.
Initial research:
My previous phone was a Droid X and there were similar issues relating to HDMI on non-stock roms. So my first inclination was to look into how that was fixed.
Here's the post in question: http://rootzwiki.com...m-audio-solved/
Basically, there are some required framework files that are needed for detecting an HDMI cable, notifying the system that it exists and enabling the output. There were also some permissions files and an APK that needed to be copied as well. The big issue with this is that the APK needed to be signed with a signature that matched the one that the ROM was built with (and since a lot of devs use the default android test/build keys, this wasn't all that difficult).
Now, keep in mind that the HDMI on the droid X wasn't mirror mode and operated VERY differently. However, it gave me a good place to start looking on the razr.
Some digging:
First, after looking through system/app i found this apk: ExtDispService.apk. As with the DX, this file is definitely going to be needed. This was where i started digging. I re-signed it and added it to the CM install zip, and put it on my phone. Now, of course it immediately crashed, but at least i had some logs to help me determine why.
Tools:
As a small note, I was using Virtuous Ten Studio to do a lot of this editing. I can't stress enough how awesome this program is for things like this. I had been doing it all manually at the start and making ONE change to that APK would take me close to 15 minutes. With VTS, i could do it in 5 or less. So from here on out, if you're following along, be sure to have the APK and JAR files mentioned added to a project in VTS and de-compiled so that you can see the smali code.
The roadblocks:
So once i had the logs, i was able to see where the APK was crashing. I knew that I would need to include some items from the framework, but i just wasn't sure what yet.
The first hiccup was in ExtDispService$HandleInitAutoDetectSetting.
Code:
const-string v3, "hdmi_autodetection"
invoke-static {v1, v3}, Lcom/motorola/android/provider/MotorolaSettings;->getInt(Landroid/content/ContentResolver;Ljava/lang/String;)I
So, from looking at this, you can see that it's trying to access a Moto utility that allows programs access to information from the settings menu. In this particular instance, it's the on/off switch for HDMI autodetect. This opened up a whole new can of worms. How would we add these items back to the settings menu? How would we fake the overscan setting?
My first inclination was to look for the MotorolaSettings class and include that into the package. However, this could potentially lead us down a very dark path of dependency hell. Worst case scenario: we have to include a lot of moto's framework to get this working (and isn't the whole point of this to get away from moto's code?!). I attempted to remove the references to the settings menu in the smali code and replace them with hardcoded values. This was EXTREMELY hackey but it was more of a proof of concept at this point anyway. I was able to get the phone to boot and not have ExtDispService crash on me, however there was also no response when I plugged in the HDMI cable (nothing at all in the logs).
List of files needed:
Here are a list of some files that i know are required to get this working:
system/app/ExtDispService.apk
system/framework/framework-ext.jar
system/lib/libextdispjni.so
system/lib/libhdmi.so
system/lib/libhdcp.so
Some final thoughts:
I realize that there isn't too much concrete info here, but I wanted to share what progress I had made so that maybe someone else could either pick up from where i've left off, or make some suggestions on how to proceed.
EDIT: I wasn't sure if this belonged in the Android Development sub-forum or not, but i put it here just to be safe. If a mod sees this and think's thats a better place, please feel free to move it.
HDMI is mostly related to the kernel (for kexec at least). But currently there is a new kernel and a workaround for kexec in development, 3.0.31 / 3.0.88 Kernel. Two of the main goals are Full HD video recoding and HDMI.
The apks only will not work as there are complete different drivers in the kexec kernel. I guess we would have it working already if this could have been fixed by app side.
However, maybe I'm wrong
Hash told me about the current development, you can see it in their repo of course. Maybe we should wait a little more..
Gesendet von meinem XT910 mit Tapatalk 4
Ah, wonderful! I just read through your thread. Thanks for posting here about it. I'll be keeping an eye on the new kernel. If there's anything i can do to help out, be sure to let me know.
djuniah said:
Ah, wonderful! I just read through your thread. Thanks for posting here about it. I'll be keeping an eye on the new kernel. If there's anything i can do to help out, be sure to let me know.
Click to expand...
Click to collapse
Help is always appreciated! Are you familiar with C coding?
Gesendet von meinem XT910 mit Tapatalk 4
Yup, I am quite familiar with C.
djuniah said:
Yup, I am quite familiar with C.
Click to expand...
Click to collapse
Nice! If you would like to join kernel development, let me kow.
This had been one of the first things that never worked with our custom roms. Your reasearch and approach for solving this damned bug make good sense. I hope you can succeed for all of us and solve the DROID RAZR HDMI MYTH. Thank you.
I'm trying to work with a custom build of Android based on KitKat to incorporate a stylus, copying some of the functionality (though not code) from Samsung which sells Android-with-stylus builds for e.g. the Note 3. I'm not including details of the specific device because right now I am working on a custom dev device and my aim is to write code which is generic enough to be usable from any Android (based on KitKat). The build (written by others) already incorporates drivers and sends stylus events correctly as motion events etc. Programming at the app level I can receive onHover, ontouch, onClick etc
The specific functionality I am trying to achieve is to pick up a stylus-button-click while hovering. It's perfectly possible to do this in any app, using an onGenericMotion Listener.
However, I want to make my "stylus-action" have system-wide effect - so that anywhere (in any other app, or in the launcher or whatever) I will pick up the event (prior to any other app) and bring up my custom menu. (just like AirCommand in Samsung Note 3) I guess in my custom Android this would then make that particular action somewhat protected or unusable for other users, but I'm ok with that.
In older Android (prior to ICS) you could try something by putting up a System Overlay (i.e in regular app code, without hacking the ROM at all), but this is no longer possible.
This is not an attempt to tapjack or whatever, I understand why this functionality has been removed from the domain of the regular programmer, and I don't want to regress my ROM back to pre-ICS behaviour by allowing the System Overlay hack. Now I am programming the system (if my change is good enough I'd like to submit it back to AOSP) so I would like to know the best method to address this. Since Samsung have already done this, it must be legal (using legal in the terms of "Android will allow it"), and I want to do it right.
Is it possible to write something similar to the System Overlay when you are running from a system service? Or is there a good choke-point to capture events before they are broadcast to the current running apps?
I was looking at (sorry, not allowed to post links) AndroidXRef /frameworks/base/core/java/android/view/View.java specifically in the function dispatchHoverEvent() which looks like a promising place. My naive idea is that I would place code here checking the MotionEvent to see if the button is pressed and if it is, don't call any listeners and instead call my little menu app (or broadcast a custom message, or something anyway). However, I've never written code on the ROM level before (LOTS of experience writing app code) so I don't know if this is a really bad point or a good point to add in code. Should I be putting things at a higher level or a lower one? Will this capture all events or not? Is it all just trial and error?
If this is the wrong place to ask questions like this, please tell me where on XDA I should be asking it. If it's the right place - please answer
Thanks
Kibi
Crickets....
Is this the wrong forum to ask? Anyone able to clue me in on where i should be asking?
Thanks
Last try
Bumping one more time for good luck.
if this is the wrong forum, please can someone point the way to the right forum for me
Thanks
Kibi
kibi1 said:
Bumping one more time for good luck.
if this is the wrong forum, please can someone point the way to the right forum for me
Thanks
Kibi
Click to expand...
Click to collapse
this is not a wrong section but your post is too long so no one intrested to wasting time to read whole post.even i haven't read the post
kibi1 said:
Bumping one more time for good luck.
if this is the wrong forum, please can someone point the way to the right forum for me
Thanks
Kibi
Click to expand...
Click to collapse
The guy above me is a ****. I stumbled across this post looking for something completely unrelated (title interested me). Five words in I knew this was something completely out of my league, but I still read the entire post. If I may offer you some probably useless advice, I would talk to the devs in the note forums. The only problem I could see is that the AOSP guys don't have this function in their roms because it's locked up Samsung code and the guys modding the stock roms leave it alone for the same reason. I could also be completely wrong. Like I said completely out of my league.