Welcome to Part II of the basics of ROM building.
If you have not had a chance yet, please check out this link. This should be followed after all of the "files" are gotten from the first part of this Trilogy of tutorials. Okay enough Lord of the Rings, the true trilogy (nerd reference may be criticized below, I preferred the matrix until the third one lol) I digress.
So, we have the files we downloaded them, Red bull/Rockstar/Monster/Bawls, whatever your legal poison. Let's set up working directories.
Organization is critical to the development process. I mean, I only realized this after I started modifying. I mean wow, it was so much easier once I started to record notes and logs.
To begin, always go to a root of a hard drive
Create a folder called
Rom
Tools and then create a new folder called Smali and APKTOOL
Multimedia and then create a new folder called Pictures and Sounds
So we have created 5 folders, do you need 5? No. Do you need 20? It doesn't matter, do what you are comfortable with. It is about staying organized.
Take the ROM you have selected from the first Basics Rom Tutorial. I assume for (hint hint) simplicities sake you chose a DeOdexed rom version of the Sprint S3 MD4 rom. Freeza Thank you. It will be in a zip file
Called: MD4_update_FULL_DeOdex.zip
Rename it to MD4.zip, feel free to call it whatever you want (remember feel comfortable). I will refer to it as MD4 from now on for simplicities sake.
So you have 7-zip installed right? Uh Oh, check, make sure that is ready to go before we start.
I cannot go into that tutorial because....well come onnnnnnn is it really that hard to press next 10 times or less ?
Extract all the files to MD4_Version_1
Oh yeah, we will be making hundreds of versions if you want. Trust me later down the line, after each mod is good, you can just continue naming them in increments. But version control should always be implemented in case you mess something up. So the logic is:
Make 1 mod or set of mods, try mod, if it works keep using that version as your base version and keep going until you are ready to try it again. Mind you it is time consuming but the only way you truly learn this backwards art of reverse engineering.
So lets look at this disaster. I mean it's overwhelming so do not think you are King of the Hill or Any hill. Maybe a mole hill because this a very complicated system in front of us.
Let's analyze the anatomy, BTW, I do not even know what everything does or is, but by all means, ask questions and we will find out. A forum is meant to voice opinions and feedback to those opinions.
The root folder has 2 folders and 2 files
META-INF
system
boot.img
installbusybox
The META-INF folder is extremely important. It contains useful information about signatures and is very necessary for android to" say its official software" remember the idea of this folder, not its contents. I do not mess with this META-INF but there are so many all over the place down the road that we will need to know it plays an important role.
The system folder has every file that we are going to modify, we will hit this folder harder than a head crab being hit by another "delay" at Valve.
The boot.img is an important file for booting up android. We will not be touching that right now. Can you? Sure but hell, don't bother with it for this tutorial. If you know all about ROM mods like some of our bad-ass developers ( yes Cyanogen all of you are badass), Stop reading get to better pastures.
The installbusybox should be there for tools for ROM modifications. It is basically a set of functions that makes Android have teeth. I will not be using it right now but we can keep going. The best tools collected into one so do not delete or modify
Lets get to the meat, the big shabang, the wholy mole(for my Latin friends), the kabosh(for whoever knows what that is)
System
The sub folders are:
app: Contains all the apps that come with the ROM. Remember android operates by utilizing apps for different functions. Modify the files in here can be good and bad, we can make the best tweaks ever here or ruin everything. Be very careful, I have had boot hangs happen to these files
bin: This folder appears mysterious but it contains important files, the binary files. Complexity gets checked right here. This folder is extremely sensitive, I have not modified this folder just yet but when I feel like bricking my phone like a gravity gun dropping combine soldiers, I will get to this asap.
cameradata: Contains important files for camera raw data to JPEG conversion, I do not mod this folder.
csc: This is a jewel, it contains Consumer Software Customization. It has multiple XML files that can be edited and modified critical settings for various functions. Very nice to start your ROM customization here, but not the easiest, lets ease in with another folder first.
etc: This folder contains critical data storage. It has things like the hosts file which will allows you to block ads(cough cough, youtube) and many other files. This folder can brick your phone. Lets not get crazy here...yet
fonts: Pretty obvious, fonts for the ROM, oh and it requires True Type Fonts so contact your local free repository for those.
framework: This folder is an important folder, almost just as important as the app folder
hdic: Language files they are based off the first 2 initials of the language. Not affecting anyone if we are not trying to pinch each ROM's size down to the bare minimum
lib: Library folder, this has files with extension .SO, they will contain libraries of information for different functions. For example, how to take a "Best Pose" picture mode would have functions in this folder as well as other areas of the rom.
media: Contains the most obvious of sounds and a prime location for android universal sounds and bootimages. The bootimages is a touchy subject, the files are Samsung proprietary which makes them useless to us for modification, but we can make the puppet dance one way or another. The sounds, however, are key as we can isolate sounds when the phone starts up, or mute certain camera functions here, we can even make it sound like all of your favorite games(Yes I did, Mechwarrior boot sounds are acceptable, F.E.A.R. sound effects and some DOOM noises added for ambiance and of course Half life 2 noises for complete nerdgasm)
T9DB: This folder contains T9 predictive text in I believe 3 languages: English, Spanish and Korean, can you get rid of 2 of these sure, but expect problems if you decide later you need them. I mean they are not that large in size but at the same time, everyone has their own way of doing things
tts: This folder houses the Text to Speech programs. They suck. I am sorry but they do, SVOX is better, I love IVONA personally. I always like a british women to wake me up and tell me I am late. But that's me.
usr: This folder is not really meant for us to modify as it has to do with the keyboard layout, grammar recognition and customization. Realistically though, I use Swiftkey and call it a day. So do not hate me if I do not bother with mucking around here. It is useful to some I am sure but nothing I want to dabble in. But by all means, it can be useful for setting well Settings.
vendor: Contains library and binary files for certain features from the vendor, I would say camera related but I do not care for this folder just like people really hated the HEV suit announcing all of its amazing features, are you kidding me that was the best part. Yes I fell 100 feet, please let me know about my fracture and how this suit somehow repaired it. It might have well said "Oww". Nothing wrong with that.
voicebargeindata: From my understanding, Svoice related. No need to bother, that feature is about as useful as a Crowbar in a Gun Fight.
vsc: Version Software Control
wakeupdata: Acoustic and Grammar models contains several languages as well
xbin: Has busy box and Super User, a useful tool to become well super.
build.prop: Very sensitive file that is magical and detrimental. There is a lot of false promises on performance with this one. We will dig through this one carefully.
CSCVersion.txt: Should have the model number of your phone
SW_Configuration.xml XML file with more model number configuration
Please feel free to let me know what is understood or not.
This run down allows us to attack the appropriate folders for the next parts
Before we even begin with the complicated mods, let's attack the basic mods first.
The media Folder then go to audio, there is 4 folders
alarms
notifications
ringtones
ui
The first 3 folders you can place anything you want inside. They each correspond to the default ringtones you would like in the phone. I recommend using .ogg files or .mp3 files, you can use Audacity to modify your sounds. Sometimes the length of the sound plays an important role. Short sounds should be kept short for a reason. If you play a noise and its barely half a second, do not make it 4 seconds long because it will sound ridiculous longer than what is meant to sound. Taking a picture while hearing Puff Daddy's Come with Me can be quite awkward but hey its all about your ROM, your choice, your likes. Who the hell is going to tell you that you cannot have a sound of a crowbar whacking a headcrab while in the middle of a busy subway.....besides the police. This works similarly to the situation of ringtones, keep them full blown songs and I have noticed some lag. Do not be discouraged, but most modern phones end the call after about 30 seconds. This time limit has to do with how long the phone is takes to find the phone and ping it. Of course, I safely recommend 45 seconds of your song to cover yourself.
Take note that there are 3 files in these folders that are set to default (ringtone, alarm and notification). We can change that with the build.prop but that's after we mess with the ui folder that contains the User Interface Sounds.
Alert_on_call.ogg: An Alert when you are on call. This should be subtle noise
Auto_focus.ogg: Tricky one, I modified this, still makes an auto focus noise. Clearly a trick has been devised
Auto_focus_error.ogg: Same as above
Call_Connect.ogg: When the call first connects
Cam_Start.ogg: Video Recorder start noise
Cam_Stop.ogg: Video Recorder stops noise
camera_click.ogg: Camera Click noise
Camera_click_short.ogg: Camera Click noise
Camera_empty.ogg: Camera related
camera_focus.ogg: Tricksie this one is, mute and still makes noise, will discuss where noise is coming from
Camera_Timer.ogg: Timer for camera countdown
Camera_Timer_2sec.ogg: 2 Second timer
Charger_Connection.ogg: When you plug in your phone to charging port
Dialer_new.ogg: Tricky one will get to later
Dock.ogg: When you put the phone on dock, useful to distinguish from charger_connection.ogg
Effect_Tick.ogg: I have heard it whilst changing pictures but not sure
Highlight.ogg: I Silenced it, and "I dont know whhhyyy"( Can you guess which comedian said this line and if you know it say it in his voice)
HoverPointer.ogg: I Silenced it, and "I dont know whhhyyy"( Can you guess which comedian said this line and, if you know it, say it in his voice)
Insert.ogg: Google Voice Noise
KeypressDelete.ogg: Default keyboard, I do not use this
KeypressReturn.ogg: Default keyboard, I do not use this
KeypressSpacebar.ogg: Default keyboard, I do not use this
KeypressStandard.ogg: Default keyboard, I do not use this
Lock.ogg: When you press the power button and it instantly locks. This noise will play. Mechwarrior noise here
LowBattery.ogg: Doom low amm noise here to indicate I should have brought a charger becuase my battery is low
New_chat.ogg: Chat software related, I got rid of that junk but thats for another tutorial
PowerOff.ogg: Most people silence this as it is the noise that powers off the phone, I got creative here but you do not have to.
PowerOn.ogg: Most people silence this as it is the noise that powers on the phone, I got creative here but you do not have to.
S_HW_Touch.ogg: The HW indicates Hardware touch, basically the buttons and any touch screen action
S_SIP_Backspace.ogg: Backspace stuff
Sent_chat.ogg: See New_chat.ogg
Shutter.ogg: Silence this for sure if you do not want noise but really silence everything camera related here and it wont be 100%. So just do it
Shutter_multiple.ogg: Burst shot related
TW_Battery_caution.ogg: Any TW has to do with TouchWiz related actions. This one is for battery
TW_Call_Disconnect.ogg: The tricky thing is, some of these are controlled by another piece of software, this one is one of them
TW_Error.ogg:
TW_Silent_mode_off.ogg:
TW_SIP.ogg: Sounds like the default tapping sound for the rom's built in keyboard
TW_Touch.ogg: The default TouchWiz touch noise. Tricky little one this was as I had to verify there was no other location for the droplet noise, it turns out there is, so stay tuned as we dig into the apps and locate where the rest of the sounds are
TW_Unlock_Glass.ogg: Gallery Noises for file management
TW_Unlock_Puzzle.ogg: Gallery Noises for file management, not sure why I heard these exact noises in the gallery app other than they are linked
TW_Volume_control.ogg: The volume rocker button on the side, i mean logically there is only one choice, the Half Life 1 Medical Bay MedShot sound, okay maybe too annoying sure, but bada$$
Undock.ogg: Removing the phone from the dock that so few of us get because you know it doesn't fit my big case, or expanded battery or whatever. You know what, custom solutions are too expensive but trust me people do make the docks that accommodate bigger cases
Unlock.ogg: When you type in your Pin/Password/Pattern, the sound that it makes to unlock
VideoRecord.ogg: Camera video start recording noise, of course, I silenced this one as well
So this takes care of some of the noises, the problem is, Samsung software actually hides the rest of the noises. They are actually hidden away in the APK files in the system/app folder. Do not worry, in future parts of this Discovery channel special on Black Mesa, we will be investigating why they detonated a nuke in the first place if it didnt do anything to stop the invasion. I mean future parts of this series
So where do we go now? Well modify the sounds you want or add the ringtones you want. But something that I felt was important was that certain noises be set when I reboot my rom by default. No I do not want that stupid Samsung whistle! NO ONE DOES SAMSUNG!.
Lets set the default sounds on ROM start up, we will need to modify the build.prop file
This file contains an amazingly large set of instructions for the start-up of the phone and features in the phone. it is therefore, very sensitive to screw-ups. Hopefully, notepad++ was installed.
Navigate in Windows to the working directory of your ROM in our case MD4/system/ there is a file there that says build.prop
Let's open that up in notepad++, we should see some intimidating pieces of code or more like lines of text that tell the phone what and when to do something.
A caution to all, the build.prop has been synonymous with words like "increase performance", "maximize battery life" and other claims that are unfortunately sometimes not always true, for every mod someone makes to this file, someone traces the code to a Gingerbread rom that is useless on Jelly Bean, or an old reference to ICS(Ice Cream Sandwich),
I would highly suggest we not dabble too much on this. XDA has some great people who have found great information about the build.prop file. This link, user Chris_84 has put a great Wikipedia together on this so I will not try and explain each one. But there are so many other links that can show a post of good tweaks and bad tweaks and useless tweaks that I will not go into. Let's instead focus on our start-up sounds
The build.prop code we will scroll to with the ctrl+f button should be enough for us to get started is
Code:
ro.config.alarm_alert=
ro.config.ringtone=
ro.config.notification_sound=
Each of these do have a word after the equal sign, which means if you configure the correct file in the correct folder(hint hint) alarm, ringtone,notification folders we talked about earlier, all you have to do is add the name of the file exactly as it appears, please only use .ogg files here. MP3 files also work but you know just do it okay. I don't ask Alex why she never made a move on me, I just know she cant have a meaningful relationship with a guy who doesn't even say hi, that's a little creepy but you know and I know she loves Freeman alright.
As an example, just in case my rant did not make any sense,
let's say you put the following sound in the system/media/audio/ringtones folder kick_push_lupe.ogg
you would put in the code the following
Code:
ro.config.alarm_alert=
ro.config.ringtone=
ro.config.notification_sound=[B]kick_push_lupe.ogg[/B]
And that's how simple that is.
So you say you have ranted on too long. Sure I have, but that's not going to be the end here. We will be modifying the rest of this rom business in the more difficult lesson which is part III, that will take the longest because we want to have fun. And I still have some Freduian issues with my role model Gordon Freeman that I need to bring out. Anyway
Also, before I go, you might ask, how do you execute TEST BATCH ALPHA-TRON!.
Go Back to your Home Folder MD4_Version_1/. You should see the folders we discussed earlier
META-INF
system
boot.img
installbusybox
Select all of those files and right click the mouse button to get a context menu from 7-zip or WinRAR and click Add to archive. Make a ZIP FILE ONLY. You can choose to compress the file if you want, I just click fastest compression options available and proceed.
When the zip file is in hand, I take the file and put it on the SD Card root directory. When it transfers(in about 5 minutes), you can open the CWM (clockworkmod) recovery or the TWRP recovery and install the ROM. Sure I did skip some steps here on how you get these recoveries and the like but this tutorial is about ROM modification and the sort not the super basics, you need those to even be reading these. If you need to get those going, let me know in the comments and we can spool that up in part III.
I do not know how many parts this will take, but it is time consuming, i have to research this stuff and recall my notes. I know the spirit of the guide is in the right place but please be patient. I will not fail you Krypton(YES I LIKED MAN OF STEEL, let the downvotes begin, oh wait not imgur).
I appreciate all feedback, do not get me wrong, and I will work whenever I am free to add as many of these parts as I can. I do want to help anyone out who has their own twist on what they want their ROM to do. It is the least I can do to payback this great community and assist one person or inspire one idea. That is all it took for me to get going, the next part will also have a very heavy hand in taking code from other people for examples of mods. I want to say from now, I did not do any of these codes, I used common sense to implement somehow into my own rom mods. They deserve all credit as they are amazing coders/crackers/hackers/whackers/ whatever you name it they truly deserve the praise. I am just compiling their logic into our ROM that we are building together. And has anyone seen the YouTube channel Vsauce, that channel is AWESOME.
Again, thank you. Very, very helpful.
-------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped you!
This is great. Man u really put this down in a way that is really understandable!
Sent from my SPH-L710 using xda app-developers app
Appreciate it
Thanks guys, seems you are tracking my every word, I posted the other ones it seems you hit those up as well. Appreciate it and everyone, please let me know if something did not make sense, we got a great pool of people that can help out.
Related
As the title says, Im a developer but I dont know anything majorly complicated.
I want YOUR ideas for something to make.
Stuff I know:
Things to do with the file system - copy, paste, delete, create etc
Read/write/create text files
Simple or even more complex UIs (nothing too extreme though)
most of the basic stuff
Heres a video of stuff Ive done before:
http://www.youtube.com/watch?v=g3_5xBqf-eQ
If you have any idea for simple apps, please let me know and Ill tell you if I can make them or not
Thanks
Maybe a new app to replace and improve SmileySMS ( development is stopped, and on windows mobile we can't have smileys in sms without this buggy app).
I wish a prog for my HD2, very simple : Use Webradio (with url) as ringtone !
Hi Cris,
I am looking for an app that can do the following:
Disable the touchscreen.
Why?
It's annoying when you watch movies and accidentaly touch the screen (especially with core player).
The app would have to disable the touchscreen after a set time, so you have enough to start the movie (or other application).
A certain area of the screen would have to be defined as touchable, so that you can disable again. Maybe with a gesture? ie. swipe from bottom left hand corner to top right???
just an idea
idea
it would be amazingg if you could make an application that allows the drag down notifications panel like android has
antdawg702 said:
it would be amazingg if you could make an application that allows the drag down notifications panel like android has
Click to expand...
Click to collapse
you know what, im gonna look into this one.
I cant promise anything.
I cant say I have any idea how to do that.
but I can say that im gonna look into it ^_^
wm7
can you make a windosmobile7series for nontouchscreen windowsmobile.need help with it.its just navigaating threw it with the arrow keys
Hi Cris,
Can I suggest a application that can do 2 things which I can't find something similar to this (suggestion).
To create a application for both "Shopping List" + "Inventory".
Let me know if you interested, I can share the idea ..
Hope you can consider it .. thanks
antdawg702 said:
it would be amazingg if you could make an application that allows the drag down notifications panel like android has
Click to expand...
Click to collapse
do you have a screenshot?
how about an application like e-mail and walk for the iphone..........so that wed be able to type and walk at the same time with the background being whats in front of us fed by our camera....
I would like a app that does the following:
All for the Sense music tab!
When NOT in a call:
Long press : Play / pause
Pressed twice : Next song
(If possible:
Pressed three times: previous song
pressed shot : call)
When you are being called:
short press: pickup / hangup
PLUS
The hardware buttons (buttons on the PHONE) MUST be disabled,
But ONLY when the headset is plugged in!
With no headset plugged in everything should be as normal!
Could some developer please make this?
Maybe you can use code from the following:
http://forum.xda-developers.com/showthread.php?t=502881
http://forum.xda-developers.com/showthread.php?t=556801
Great Greet Giblet
I've actually been pitching this one around but no luck yet ... A small GPS toggle cmd app. Here's an OSS project that may have usefull code.
What I would like it to have is:
1- Commands to toggle GPS on or off
2- Stay running and output number of connected satellites and connection status (position fixed/not fixed) as a reg name/value
3- Maybe other stuff (like coordinates, hour/date, update system time... but what I really want is the first point 1 and 2).
Why would I want such an app? To add a GPS connection manager to my today screen HS++ skin (also maybe make a script that will only launch my device navigation software when it has a position fix).
PS:
Other stuff I'd like to see are either other small cmd apps or small updates/fixes of some OSS apps like GSFinder+ or even emulators (small stuff like adding onscreen controls using existing sources, emulate mutli touch or improving controls by mixing the use of oncreen keys with hw ones or minor GUI standardization and fixes related with new devices screen resolution).
cris_rowlands said:
As the title says, Im a developer but I dont know anything majorly complicated.
I want YOUR ideas for something to make.
Stuff I know:
Things to do with the file system - copy, paste, delete, create etc
Read/write/create text files
Simple or even more complex UIs (nothing too extreme though)
most of the basic stuff
Heres a video of stuff Ive done before:
http://www.youtube.com/watch?v=g3_5xBqf-eQ
If you have any idea for simple apps, please let me know and Ill tell you if I can make them or not
Thanks
Click to expand...
Click to collapse
OK here is an idea for a simple but useful application please would you consider making this
http://forum.xda-developers.com/showpost.php?p=5711236&postcount=1
Slide2Action
Hi cris, How about a simple slide to do anything? Just a scrollable list of blank sliders that you can assign a function too, eg launch an app, blank screen, reset, close all, new message, WiFi, bluetooth etc. the list could be endless. Just a scrollable action screen with sliders instead of buttons. Transparency would be a bonus for a nice visual.
well folks, youve given me plenty of ideas.
A few of them ill try to work on, sadly many of your ideas are a little beyond me
Anyway, Ive got some stuff to be doing so I wont be checking out this thread anymore.
If any developers feel they want to take up any of these, please feel free ^_^
zinconnu said:
Maybe a new app to replace and improve SmileySMS ( development is stopped, and on windows mobile we can't have smileys in sms without this buggy app).
Click to expand...
Click to collapse
I was going to make this same suggestion. I hope somebody with the skills stumbles upon this and can continue the development for this.
cris_rowlands said:
well folks, youve given me plenty of ideas.
A few of them ill try to work on, sadly many of your ideas are a little beyond me
Anyway, Ive got some stuff to be doing so I wont be checking out this thread anymore.
If any developers feel they want to take up any of these, please feel free ^_^
Click to expand...
Click to collapse
Hi Cris,
if you can consider my suggestion to develop a "shopping List" + "Inventory" apps I think is not that difficult to develop. It almost similar to like any shopping list app & you be able to keep track of the inventory list maybe with photo or pic is good enough.
pls do consider this apps, as both iPhone & WinMo still do not have such app yet. If you do build up, you will be the 1st to come out with.
Lockscreen Slider
Please try to do a Lockscreen Slider for WM 6.5
http://forum.xda-developers.com/showthread.php?t=638230
Thanks
salo1 said:
Please try to do a Lockscreen Slider for WM 6.5
http://forum.xda-developers.com/showthread.php?t=638230
Thanks
Click to expand...
Click to collapse
yes let's steal some more apple patents!!! The idea is great! Few months ago I already asked this topic in the S2U thread but no response, probably my request got overseen or the guy is just too busy with other stuff.
Hey guys, like the title says, I'm attempting to create an app, but with little success at this point.
What I want to do, didn't sound all that complicated in my head. I want to make an episode guide for a TV show I like. Nothing too fancy, but I do want it to look WP7-authentic.
First off, I don't know or really understanding coding in the slightest. I was hoping to be able to design most of the app through the on-screen WP7 display, which it seems I can do a lot on.
From what I've gathered, here's what I'd like to do:
Use the "Pivots" as the different story arcs or "seasons"
Within each pivot, Episode # and Title
But I'd also like to go one further and have each episode be clickable, which would take the user to a page containing info about the respective episode. Synopsis, International Titles, Airdate, etc.
It's a big project, I just need a little help getting it going.
Thanks!
dbG33K
what you're describing can be done one of two ways.
1. just display images after images
2. input text into the program
from what im gathering, it should be fairly easy for you to do as this is the sort of beginner stuff in most windows phone 7 programming books. id suggest you look into programming because even the slightest pivots and transitions require code.
now if you were on android or webos, thats different. they have full on graphics based programming thats a simple matter of drag and drop and choose function.
Download Expression Blend. You can do pretty much everything without having to write any code. It includes a "Pivot" template which has a pivot all ready for you, then you just add PivotItems using your mouse. Then you can use the Sample Data feature to mock up how your episode data will look.
The only thing you would have to write code for would be to pull the episode information from a datasource. Bind it to your controls and Expression will have the rest done for you.
http://www.microsoft.com/expression/windowsphone/
Sample Data:
http://expression.microsoft.com/en-us/ee426896.aspx
First thing you'll need before you even open Visual Studio or Blend is a data feed.
An rss feed is ideal, And I'm sure theres alot of them out there for TV listings. Without that, theres little you can do (other than screen scraping websites, but people don't look too kindly on that)
If you can find me a Url for the RSS feed you want to use, I'll be more than willing to help you out
xanderkaiber said:
First thing you'll need before you even open Visual Studio or Blend is a data feed.
An rss feed is ideal, And I'm sure theres alot of them out there for TV listings. Without that, theres little you can do (other than screen scraping websites, but people don't look too kindly on that)
If you can find me a Url for the RSS feed you want to use, I'll be more than willing to help you out
Click to expand...
Click to collapse
What he said
I'd be willing to help you out as well. I'm in the process of writing a feed reader to help me make the move WP7 from WPF/Silverlight. The idea I have for the UI is similar to yours and the feed reader (at least in the basic form) will be open source so I've no problem sharing my code...
I appreciate your willingness to help me out, but it's actually a series that has been over for quite a while.
Hey guys, I've gotten much further on my app and have become a little more well-acquainted with coding in the form of using Expression Blend 4. That said, I do have a few questions:
1. After making a few pages, I decided to make a sort of Welcome page for my app. How do I tell it to show that page first instead of "MainPage.xaml"?
2. On that welcome page, I would like to make a button that pulls up the user's E-mail and have it have my e-mail as the recipient.
Thanks a bunch!
This is in the WMAppManifest.xml file within the Properties folder.
for the email look into the email compose task
barryallott said:
This is in the WMAppManifest.xml file within the Properties folder.
for the email look into the email compose task
Click to expand...
Click to collapse
That doesn't really help me too much...
What am I supposed to do in the WMAppManifest.xml?
And where do I find the email compose task, and how do I implement it into the app?
EDIT: Nevermind, I figured out both of those questions. A new question, though: How do I take screen shots of the app? I need at least one to submit it to the marketplace, but I don't know how :/
dbG33K said:
That doesn't really help me too much...
What am I supposed to do in the WMAppManifest.xml?
And where do I find the email compose task, and how do I implement it into the app?
EDIT: Nevermind, I figured out both of those questions. A new question, though: How do I take screen shots of the app? I need at least one to submit it to the marketplace, but I don't know how :/
Click to expand...
Click to collapse
Download this:
http://www.innovativetechguy.com/?p=13
Make sure your emulator is set to 100% size and uncheck the "Show Device" checkbox in the tool. That will give you the necessary 480x800 sized .png
There's a fair lot you can do using the designer panel, but you will definitely need C# code for what happens 'behind the curtains'. Things like pulling the episodes from the internet and such.
I definitely recommend these tutorials:
Windows Phone 7 Development for Absolute Beginners.
It builds up slowly, but definitely gives you the foundation you need to put together basic applications.
Hey guys I found this thread and after reading it I feel I have a lot in common with dbG33K's tasks & questions. I feel I have a lot to offer WP7 apps as I learn more! I started out in January learning and studying as an absolute beginner (even did the 5 day course online). After a lot of studying, I felt confident enough to write my first BIG app.
I'm pretty good at the xaml part and getting real familiar with c# as I go along. Also, I think I have all the pieces I need, just need help putting it all together. I'm using an API for the data source (i have all the dlls and resources in place even all the c# methods for the API).
I have the UI all put together, now working on the c#. I'm just unsure on the binding part. I know my listboxes and other controls should be binded to a method in c#, but what calls that method? When the page loads that listbox, textblock, etc? Also, what kind of coding is generally used inside the {} of the methods that pulls info from the datasource?
As I have learned a lot aver the past couple of months, I find that I've learned it from examples I've found online, but I'm drawing a blank on this one. Any help would be great!
Thanks!
Do any of you can tellme how can I save text from the text box??
Sent from my LG-C900 using XDA Windows Phone 7 App
Hello everybody,
So these days I've been interested in theming MotoBlur since I had PS skills and wanted to put them to use since being 17 and with so much free time I said it might not be THAT hard.
However, **** happened.
Finding out those pesky MotoBlur apps wasn't that hard - found it rather easily after checking up a system backup.But finding out the MotoBlur apps wasn't the problem - the problem were the apps.
This is how a simple .apk file (MotoBlur Phone app) folder looks like:
http://i279.photobucket.com/albums/kk125/secretalex125/untitled.jpg
See that little thing there? Yeah, you're seeing right - that is the Motorola FlipFlop (or how it's named) phone. But God, why?
Don't ask me; ask Motorola. This may be the reason why they ended up making a striped version of their newer phones' skin/OS updates' skin.
Not to mention these images come up with .xml files. Now, as a dumb idiot with relatively limited text editing (.xml / .ini / whatever coding files) knowledge, but still a basic one enough to know not to screw up with the position of some text, I know that checking up ALL these files would be a damn hard task. Not to mention editing them properly. However, I'm in for the images. And I'm somehow sure that some of these files are pretty much useless. So they should be deleted. But then, when you have 2 apps called "BlurContacts" and "BlurPhone" and notice both of them feature pretty much the same images in some folders, you know you're screwed.
But this is only the foreground idea. The background, the immense sea of files is what is annoying. How could someone be able to create an entirely new skin? All that comes in my mind is that he must be a masochist.
So questions pop up:
1. Did anyone else try to skin ALL the files?
2. Did anyone try to remove files?
3. I know that out there is only one more GB skin. One more. But is it any better?
4. Are there replacements? How easy is to replace these files? Would simply removing these Motoblur apps make my life easier and revert me to classic Gingerbread?
4. I think there's more on my mind, but it doesn't come up right now.
All in all, I don't like what I'm seeing.
I was able to theme almost all motoblur apps when I was on ms2ginger rom, so it was the gb version of defy. I didn't remove any of the files, but yeah it takes some time to understand where goes what.
Sent from my ICS Defy
All samsung "touchwiz" based devices contain files in /system/csc that set variables dictating how certain parts of the phone act, what is pre-configured, etc. In the case of the AT&T variants, the contents of these files are often dictated by AT&T.
This post is an attempt to try and catalog some of the more useful values that can be changed (and the result of changing them.) Not all the variables seem to do much, and only by trial and error can we really know what will happen... So far, I've only played around with items I found interesting, but will continue to expand in this and if people reply to this post with actual experience changing other variables, I'll add the information to this thread.
PLEASE TEST THINGS AND CONTRIBUTE TO THIS THREAD.
Please don't reply with guesses as to what things may or may not do or with requests about specific variables. I'm hoping that eventually document every CSC variable available and "requests" won't make it go faster. If you want to know what a not-yet-documented variable does, try it out (and post your results.)
First, in order to play with the csc files, your phone should be rooted. This isn't optional, as you'll need the ability to overwrite files in the phone's /system partition (the firmware - sometimes improperly called the "ROM")
I'd strongly suggest making a nandroid (or backup via CWM Recovery or TWRP) before making changes. It's possible to mess things up badly enough that the phone won't boot properly.
It's possible to edit the CSC files directly on the phone, but I'd strongly suggest not doing that. Therefore, you should have a good text editor on your computer that's able to properly deal with unix/linux style line endings (notepad isn't good enough.) Notepad++ is a very good editor and freely available. Google "notepad++" For a linux box, plain "gedit" is fine.
In order to edit the files, you'll need to be able to mount the /system partition as read-write, and to move files from /system/csc to your PC or other location for editing. You have several options for this including root explorer, ES File Explorer, or just using adb. I prefer adb myself, but I'm a commandline type of person.
I won't be spending time describing how to get the CSC files off your phone to your PC, nor will I tell you how to overwrite the existing ones with your edits. This isn't because I'm elitist, an a**hole, or anything like that. (I _am_ some of those things, but that isn't my reason here.) My purpose for leaving out the information is to force inexperienced users to learn these things before editing system files. If I give you all the information, you become dependent on me for more information, and I don't want that (and trust me - neither do you.) As well, if I spoon-feed this, you won't have any idea what do to when something goes wrong.
Find this post helpful? If so, please make it MORE helpful by testing one of the other CSC features and replying to this thread telling us what result you had.
First up... feature.xml...
feature.xml
The CSC "feature.xml" file is in XML format. This means that everything "variable" has a start and end tag. Both contain the name of the variable,
but the end tag has a slash in it. The value of the variable is between the start and end tags. For example: <VariableName>value</VariableName>. So, if this message describes changing "CscFeature_SamsungSucks" from "false" to "true", you'd search in the xml file for "CscFeature_SamsungSucks" and might find this:
Code:
<CscFeature_SamsungSucks>false</CscFeature_SamsungSucks>
You'd change the "false" to "true" (no quotes!) and be done. In some cases, the entire line can be deleted (as noted.)
This file has a LOT of variables in it and this post will concentrate on that particular file. Almost all tinkering will occur in this file, and it's also the easiest to edit (as there aren't any complex xml structures.)
CscFeature_Common_DisableMenu4GalSearch: setting this to false didn't seem to bring up any new global address list options on my device (I'm connected to an exchange server) in the email app or contacts/dialer app.
CscFeature_Settings_DisableMenuFindMyMobile: (see next line)
CscFeature_Settings_FindMyMobile: setting "DisableMenuFindMyMobile" to false and this entry to true will enable the "find my mobile" entries in the Settings->Security menu. I'm unable to get these items to function properly, however. (They worked with my international note2, so it might be that there are other support files missing on the AT&T variant I'm using now.)
CscFeature_FMRadio*: editing these seem to have no effect (I don't think any of the LTE capable NoteII phones are capable of FM Radio.)
CscFeature_NFC_StatusBarIconType: If you delete this line, it will get rid of the "N" statusbar icon when NFC is turned on.
CscFeature_Message*: Be warned that editing some of these may break SMS/MMS messaging on your device. There appears to be many carrier specific settings in here that have dependencies on the specific carrier. For example, I don't think that AT&T's network supports proper SMS Delivery reports, so even setting the corresponding variable to "true" would be futile.
CscFeature_Email_UseFixedBgColorAsWhite: if changed from true to false, the email app will appear inverted (with a black background and white/gray text.)
CscFeature_Sip_DisableAutoCorrection: doesn't seem to have any impact on the samsung keyboard
CscFeature_Sip_DisableSpaceSuggestion: doesn't seem to have any impact on the samsung keyboard
CscFeature_Sip_DefaultOff4AutoSubstitution: doesn't seem to have any impact on the samsung keyboard
CscFeature_Launcher_*: all these seem to be for setting defaults for the touchwiz launcher, so no sense in changing them.
language.xml
(coming soon)
This appears to control what languages are available to the system. Canadian users might want to play with this file to see if adding en_US to the "Display" and/or "SupportList" tags will allow them to choose US English (and perhaps get google's TTS to talk to them in google now.)
others.xml
(coming soon)
This appears to set some carrier defaults, including the APN information and the carrier built-in dialer contacts (such as "AT&T Customer Care")
customer.xml
(coming soon)
I've only glanced at this file so far, but it appears to be carrier specified network information, some carrier specified settings defaults, and even some carrier specified browser bookmarks. There also appears to be some APN related information in here, but I'm not certain what it's in here for.
Nice how to guide man its very informative, im going to play around with this later when I get home...do you mind if I add it to my reference thread so it doesnt get lost when this thread begins to get bigger?
Sent from my SAMSUNG-SGH-I317 using xda premium
mjwhirly said:
Nice how to guide man its very informative, im going to play around with this later when I get home...do you mind if I add it to my reference thread so it doesnt get lost when this thread begins to get bigger?
Click to expand...
Click to collapse
This isn't mine to control. This "belongs" to the community, and I hope that the community contributes to it in a meaningful way. Please feel free to reference it elsewhere - perhaps with (contributions welcome) noted. My ONLY demand is that no one profits from effort I've given freely.
My secret motive is to nudge people out of the "MyRom" mentality and more into the "lets all work together to learn, develop and share" mentality often seen with kernels and open source projects.
Take care
Gary
Gary, have you seen the CSC feature web, set user agent?
Possibly an option to set "Desktop" as default user agent in browser, I for one despise mobile sites.
antiochasylum said:
Possibly an option to set "Desktop" as default user agent in browser, I for one despise mobile sites.
Click to expand...
Click to collapse
Not sure if this is what you are looking for or not: Start the browser, tap the "menu" button. Turn on the "desktop view" checkbox.
There are some UAgent related entries in the feature.xml file. Please play with them and post your results:
CscFeature_Web_SetUserAgent // currently empty
CscFeature_Web_SetUAProfile
CscFeature_Web_Bool_EnableUAProfile // currently false
Thanks so much for this. Sorry for the noob question but I haven't done much with xml files. What is the character to just comment out a line?
Sent from my SAMSUNG-SGH-I317 using xda premium
Romee74 said:
Thanks so much for this. Sorry for the noob question but I haven't done much with xml files. What is the character to just comment out a line?
Click to expand...
Click to collapse
In XML, in order to comment out a line (instead of completely deleting it), it has to be surrounded by special tags:
On the left of the commented out area, you need "<!--" (no quotes) and on the right, you need "-->"
See the below code block for an example.
Code:
<Is_This_Commented> false </Is_This_Commented>
<!-- <Is_This_Commented> true </Is_This_Commented> -->
Take care
Gary
On my Galaxy S III, the file /system/etc/feature_default.xml appears to contain default settings, and feature.xml can override those defaults. I'm not sure how comprehensive the list of settings in feature_default.xml are, but I would imagine that many of the available ones are covered there.
Thundersnuz said:
On my Galaxy S III, the file /system/etc/feature_default.xml appears to contain default settings, and feature.xml can override those defaults. I'm not sure how comprehensive the list of settings in feature_default.xml are, but I would imagine that many of the available ones are covered there.
Click to expand...
Click to collapse
That's interesting. Which variant of sgs3 do you have? Would you be willing to attach the two files to a reply in this thread (or point me to someplace I can find the firmware your using to investigate?)
Thank you
Gary
It would be amazing if we could somehow enable auto-replace on the samsung keyboard. I ended up switching to swiftkey because of how many mistakes I've been making with the stock keyboard, but now I don't get to take advantage of swipe, stylus writing, or the one-handed features...
UCLAKoolman said:
It would be amazing if we could somehow enable auto-replace on the samsung keyboard. I ended up switching to swiftkey because of how many mistakes I've been making with the stock keyboard, but now I don't get to take advantage of swipe, stylus writing, or the one-handed features...
Click to expand...
Click to collapse
I completely agree, but I wasn't able to get it working when tinkering with the CSC values (as noted in the corresponding post.) Perhaps there's some other combination of values that might get it going.
Please give it a try and let us know how it works out.
Take care
Gary
Removing the NFC icon from the staus bar is awesome but has anyone tried switching this line;
<CscFeature_NFC_DefaultCardModeConfig>DISABLE</CscFeature_NFC_DefaultCardModeConfig>
To enable? Im not sure why att would "block" this feature, especially with google wallet getting more support for non-nfc devices.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
MonsterBandit said:
...but has anyone tried switching this line...
Click to expand...
Click to collapse
I'm not sure why people keep asking if other people have done this, that, or the other thing. TRY IT and let us know what happens.
garyd9 said:
I'm not sure why people keep asking if other people have done this, that, or the other thing. TRY IT and let us know what happens.
Click to expand...
Click to collapse
fair enough...thanks btw...im slowly growing the courage to make changes and explore deeper into these devices...changed the value to "ENABLE" (minus the quotes) and seemingly nothing changed. Google Wallet app still says Not supported. That might be on Google Wallet's end tho. I guess the better question might be has anyone with a Note 2 gotten Google Wallet to work?
When I first got my GN2 running stock, carrier billing worked. I then flashed Jedi 3.3, and it disappeared. I remember that on my HOXL, someone mentioned a fix on the build.prop. Is there anything I can do on the GN2's build.prop to get my carrier billing back?
I'm on AT&T by the way.
silentecho13 said:
When I first got my GN2 running stock, carrier billing worked. I then flashed Jedi 3.3, and it disappeared. I remember that on my HOXL, someone mentioned a fix on the build.prop. Is there anything I can do on the GN2's build.prop to get my carrier billing back?
I'm on AT&T by the way.
Click to expand...
Click to collapse
this is pretty much a how to thread ..
you seem to be having issues with a rom , you should post in there ..
here is how I fixed it in previous roms ..
compare your build.prop form your att rom to the one you are using ..
and add / replace with the att stuff .
Q: Dear beast.in.black,
I bought my M2 with a lot of great expectations, but I am bitterly disappointed by the lack of volume on the phone speakers; a sparrow's fart is louder than the in-call volume even with my volume controls at maximum.
Due to this issue, I am unable to have dirty phone conversations with my significant other while I am in a crowded place because I am unable to hear what's going on even if I enable the speakerphone and set it at max volume.
Also, my heavy metal music playlist has turned into easy listening elevator music because I can't play it loud enough to make my eardrums bleed like I used to on my old phone, and now all the ear bandages I bought are useless.
I am unable to get used to the feeling of nonbleeding ears and this may cause me and me and me to develop another psychiatric disorder before too long.
Please help me.
(Signed: A desperate M2 user)
A: Dear desperate M2 user,
I too feel your pain because I have been in a similar situation with my M2.
Luckily for me (and now for you), I was able to figure out a way to boost the volume on the phone to allow the max possible volume (as far as I currently know) - if you set the volume control to max - for all applications including call volume.
No volume boost apps are required for this technique!
*** DISCLAIMER *** The procedure required to boost the volume on the phone to the max allowable (at max value of the volume control sliders) requires your phone to be rooted, and involves messing with a critical system file called build.prop, so if you're not comfortable with voiding your warranty and the possibility of damaging your phone, walk away now!
If you choose to continue, you will be solely responsible for any and all consequences and outcomes of your actions - I disavow all responsibility and accountability for you, your phone, your actions, your life and your sanity (or potential lack thereof).
No offense meant. Just standard CYA
Short Answer (for those who know what they're doing):
Edit the file /system/build.prop and comment out the line which starts with ro.config.hw.security_volume so that it looks like this (note the # symbol at the beginning of the line - this is what turns it into a comment instead of an active line of configuration info):
Code:
#ro.config.hw.security_volume=6
Note that the number after the equals sign may be different for you; the above value is what I had on my M2-802L.
You can even delete the line entirely if you're feeling particularly brave - it doesn't seem to have affected anything else on my phone.
Long Answer:
Rambling introduction:
OK, we need to go into some history here.
In days of old, phones had decent volumes if they were manufactured with decent hardware (DSPs, speakers etc), and all was well on this green Earth.
However, some idiot (probably at Apple, they love to do idiotic things in the name of "courage") decided that a phone which you could actually hear stuff out of was gauche, proletarian and unrefined, and that it would be oh-so-much-more upmarket, refined and sophisticated (meaning: "Goshdang! We can charge people a boatload more money and become filthier richer!") if people couldn't actually hear anything out of a device whose primary raison d'être is, you know, communication.
So phones (especially the ones from the more pretentious manufacturers) started artificially limiting their volumes in software even if the hardware was perfectly decent and was actually capable of melting your ears. And thus arose the burgeoning plethora of volume boost apps -some good, some indifferent, some downright nasty.
"But beast.in.black," I hear you cry desperately, "what does all this have to do with me? I just want my phone volume to be loudererer! Enough with the Verbal Kint schtick!! Get to it already!!!"
Well, geez!
Ok then!
Here's what you need to do:
Prerequisites:
Your phone needs to be rooted.
If you're not yet rooted but would like to do this, follow the Rooting guide if you are feeling adventurous and really want this (see DISCLAIMER above).
You need to have a good file explorer on your phone.
I can heartily recommend MiXplorer - it's an open source fully-featured file manager (check out the XDA thread in my link), and is developed and maintained by XDA member HootanParsa. It has a bunch of capabilities including native SMB client support to connect to a share on a Windows machine, and has an inbuilt text editor (which will shortly become rather important, as you'll see).
You need to have a text editor on your phone.
If you install the MiXplorer file manager like I recommended above, it comes with an inbuilt text editor which is more than adequate for the job.
Since I use the vim editor in life, I also personally like to use it on Android phones in its VimTouch avatar. If you don't know what vim is, I suggest that you not find out right now; save it for a more leisurely occasion. Install some other text editor from the play store - whichever one grabs your fancy and can get the job done.
Method:
Using your file manager of choice, navigate to your /system directory.
In the /system directory, you should find a file called build.prop. Select this file in your file manager and open it in a text editor (your file manager should give you various options to open the file, one of which should be the appropriate text editor app).
After the text editor has opened the build.prop file and you can see its contents, search for a line which starts with the following text (I have not shown any text on that line which comes after the word security_volume):
Code:
ro.config.hw.security_volume
*** CAUTION *** Many entries in this file look very similar to each other, and it is very possible that you can end up inadvertently choosing a line of text which is not the correct line. Make doubly sure that you are on the correct line by making certain that the line contains the text security_volume.
Changing the wrong line could lead you to soft-brick your phone, and trust me when I say that dealing with a bricked Huawei phone (especially when Huawei, just to make your life more difficult, has pulled the ROM for your particular model from all their support sites) is a gigantic migraine headache that you most definitely don't want to experience if you can possibly avoid it.
After ensuring that you've found the line of text in the build.prop file which starts with ro.config.hw.security_volume, comment it out by placing a # symbol at the beginning of the line so that the start of the line of text looks like this (note the # symbol at the beginning of the line - this is what turns it into a comment instead of an active line of configuration info):
Code:
#ro.config.hw.security_volume
Note that you can even delete this line entirely if you're feeling particularly brave - it doesn't seem to have affected anything else on my phone. However, since you're following this long version of the answer, I would recommend that you just comment it out for now.
After commenting out the above line of text, save the changes you made (I certainly hope that you didn't change anything else) to the build.prop file.
After making sure that your change to the file was saved correctly, exit the text editor app.
Restart your phone.
Enjoy your new face-melting, ear-blood-inducing, heavy-metal-rocking volume levels :highfive:
Extra fun and profit for experts:
I haven't yet experimented with this myself, but I think that it may be possible to set a custom max volume threshold by varying the numeric value of the ro.config.hw.security_volume config parameter.
On my phone it was set to 6, and I think that perhaps the absolute max value it can take is 10 (denoting full hardware phone volume), although that is a guess (albeit a logical guess) and we need to experiment find the actual range of values that this parameter can take.
Once the range of values is determined, then it would be possible to write an app that could set a custom max volume threshold by varying the value of this parameter as requested by the user.
Enjoy! :cyclops:
I had a the same problem with call volume. In the end the problem was Huawei's obscure software. During a call press the speaker button on the button left. It will double the speaker volume. Simple, but hard to find.
beast.in.black said:
Q: Dear beast.in.black,
I bought my M2 with a lot of great expectations, but I am bitterly disappointed by the lack of volume on the phone speakers; a sparrow's fart is louder than the in-call volume even with my volume controls at maximum.
Due to this issue, I am unable to have dirty phone conversations with my significant other while I am in a crowded place because I am unable to hear what's going on even if I enable the speakerphone and set it at max volume.
Also, my heavy metal music playlist has turned into easy listening elevator music because I can't play it loud enough to make my eardrums bleed like I used to on my old phone, and now all the ear bandages I bought are useless.
I am unable to get used to the feeling of nonbleeding ears and this may cause me and me and me to develop another psychiatric disorder before too long.
Please help me.
(Signed: A desperate M2 user)
A: Dear desperate M2 user,
I too feel your pain because I have been in a similar situation with my M2.
Luckily for me (and now for you), I was able to figure out a way to boost the volume on the phone to allow the max possible volume (as far as I currently know) - if you set the volume control to max - for all applications including call volume.
No volume boost apps are required for this technique!
*** DISCLAIMER *** The procedure required to boost the volume on the phone to the max allowable (at max value of the volume control sliders) requires your phone to be rooted, and involves messing with a critical system file called build.prop, so if you're not comfortable with voiding your warranty and the possibility of damaging your phone, walk away now!
If you choose to continue, you will be solely responsible for any and all consequences and outcomes of your actions - I disavow all responsibility and accountability for you, your phone, your actions, your life and your sanity (or potential lack thereof).
No offense meant. Just standard CYA
Short Answer (for those who know what they're doing):
Edit the file /system/build.prop and comment out the line which starts with ro.config.hw.security_volume so that it looks like this (note the # symbol at the beginning of the line - this is what turns it into a comment instead of an active line of configuration info):
Code:
#ro.config.hw.security_volume=6
Note that the number after the equals sign may be different for you; the above value is what I had on my M2-802L.
You can even delete the line entirely if you're feeling particularly brave - it doesn't seem to have affected anything else on my phone.
Long Answer:
Rambling introduction:
OK, we need to go into some history here.
In days of old, phones had decent volumes if they were manufactured with decent hardware (DSPs, speakers etc), and all was well on this green Earth.
However, some idiot (probably at Apple, they love to do idiotic things in the name of "courage") decided that a phone which you could actually hear stuff out of was gauche, proletarian and unrefined, and that it would be oh-so-much-more upmarket, refined and sophisticated (meaning: "Goshdang! We can charge people a boatload more money and become filthier richer!") if people couldn't actually hear anything out of a device whose primary raison d'être is, you know, communication.
So phones (especially the ones from the more pretentious manufacturers) started artificially limiting their volumes in software even if the hardware was perfectly decent and was actually capable of melting your ears. And thus arose the burgeoning plethora of volume boost apps -some good, some indifferent, some downright nasty.
"But beast.in.black," I hear you cry desperately, "what does all this have to do with me? I just want my phone volume to be loudererer! Enough with the Verbal Kint schtick!! Get to it already!!!"
Well, geez!
Ok then!
Here's what you need to do:
Prerequisites:
Your phone needs to be rooted.
If you're not yet rooted but would like to do this, follow the Rooting guide if you are feeling adventurous and really want this (see DISCLAIMER above).
You need to have a good file explorer on your phone.
I can heartily recommend MiXplorer - it's an open source fully-featured file manager (check out the XDA thread in my link), and is developed and maintained by XDA member HootanParsa. It has a bunch of capabilities including native SMB client support to connect to a share on a Windows machine, and has an inbuilt text editor (which will shortly become rather important, as you'll see).
You need to have a text editor on your phone.
If you install the MiXplorer file manager like I recommended above, it comes with an inbuilt text editor which is more than adequate for the job.
Since I use the vim editor in life, I also personally like to use it on Android phones in its VimTouch avatar. If you don't know what vim is, I suggest that you not find out right now; save it for a more leisurely occasion. Install some other text editor from the play store - whichever one grabs your fancy and can get the job done.
Method:
Using your file manager of choice, navigate to your /system directory.
In the /system directory, you should find a file called build.prop. Select this file in your file manager and open it in a text editor (your file manager should give you various options to open the file, one of which should be the appropriate text editor app).
After the text editor has opened the build.prop file and you can see its contents, search for a line which starts with the following text (I have not shown any text on that line which comes after the word security_volume):
Code:
ro.config.hw.security_volume
*** CAUTION *** Many entries in this file look very similar to each other, and it is very possible that you can end up inadvertently choosing a line of text which is not the correct line. Make doubly sure that you are on the correct line by making certain that the line contains the text security_volume.
Changing the wrong line could lead you to soft-brick your phone, and trust me when I say that dealing with a bricked Huawei phone (especially when Huawei, just to make your life more difficult, has pulled the ROM for your particular model from all their support sites) is a gigantic migraine headache that you most definitely don't want to experience if you can possibly avoid it.
After ensuring that you've found the line of text in the build.prop file which starts with ro.config.hw.security_volume, comment it out by placing a # symbol at the beginning of the line so that the start of the line of text looks like this (note the # symbol at the beginning of the line - this is what turns it into a comment instead of an active line of configuration info):
Code:
#ro.config.hw.security_volume
Note that you can even delete this line entirely if you're feeling particularly brave - it doesn't seem to have affected anything else on my phone. However, since you're following this long version of the answer, I would recommend that you just comment it out for now.
After commenting out the above line of text, save the changes you made (I certainly hope that you didn't change anything else) to the build.prop file.
After making sure that your change to the file was saved correctly, exit the text editor app.
Restart your phone.
Enjoy your new face-melting, ear-blood-inducing, heavy-metal-rocking volume levels :highfive:
Extra fun and profit for experts:
I haven't yet experimented with this myself, but I think that it may be possible to set a custom max volume threshold by varying the numeric value of the ro.config.hw.security_volume config parameter.
On my phone it was set to 6, and I think that perhaps the absolute max value it can take is 10 (denoting full hardware phone volume), although that is a guess (albeit a logical guess) and we need to experiment find the actual range of values that this parameter can take.
Once the range of values is determined, then it would be possible to write an app that could set a custom max volume threshold by varying the value of this parameter as requested by the user.
Enjoy! :cyclops:
Click to expand...
Click to collapse
motchamotcha said:
I had a the same problem with call volume. In the end the problem was Huawei's obscure software. During a call press the speaker button on the button left. It will double the speaker volume. Simple, but hard to find.
Click to expand...
Click to collapse
If you mean the button with the speaker icon on it, that's actually the speakerphone function. Yes, it does make the call volume louder, but I've found that on a stock ROM it is unfortunately not loud enough to be used as an actual speakerphone especially if there is the slightest bit of noise in the environment