hi i installed my native language fonts and libs and i got the language working in every thing except the nofication bar and bluetooth names and as far as i know the noficatoin bar connected some how with framework so what should i do to install the fonts there????
h.boushi1987 said:
[Q] is there language or font files in framework.apk???
Click to expand...
Click to collapse
Not that I've seen. And put questions in the Q&A section.
XperiaX10iUser said:
Not that I've seen. And put questions in the Q&A section.
Click to expand...
Click to collapse
sorry about that i thought it's about devlopment things my bad
h.boushi1987 said:
sorry about that i thought it's about devlopment things my bad
Click to expand...
Click to collapse
Unless you're actually developing something then no.
MOD EDIT: BEFORE POSTING ANY THREAD IN THE DEVELOPMENT SECTION, PLEASE READ THE FOLLOWING:
If you have developed a ROM, or are working with others to do so, the development forum is somewhere to discuss and share ideas, post useful feedback and logs or crash dumps, and to discuss a common goal developers are trying to achieve.
It is NOT the place to post your question because it gets higher traffic, or because more experienced users frequent it. Doing this just annoys those who are working on the device, and drives them away. Developers don't want to wade through 20 threads of "Help me urgently" to find their threads for porting and fixing camera issues etc. Similarly, if a thread is designated as discussion for developers say, porting a camera fix, please do not post in there asking "When will it be ready?", "Can I flash this yet?" etc. This is both completely disrespectful to those working on the project (you evidently haven't read the important posts in the thread), and also is making it harder for developers to find comments from other developers or testers when required.
Similarly, don't make loads of "Thanks for your work here" posts in an active development thread. It's just as annoying to developers as asking when something will be ready. If a ROM is complete, then go ahead and thank the developer if you wish, but don't go into threads for devs only, and interrupt it to post "thanks". It's basically spamming, and is treated as such.
If you are posting in development, you should have read every sticky and notice there, and should be actively developing or helping in the development of something. Developing isn't installing a ROM, or using a tweak, it's creating a ROM or other hack or tweak. If you haven't read for several days before starting out on XDA, you are likely about to ask something already solved. I registered on XDA when I first wanted to post, and that was to join in a discussion on something. Sure, join up and ask a question, but read the information available in General and Q&A first, as your question will have been asked before. Search is your friend here, become familiar with it.
Regarding when to post in development if you are not actually developing something, there is one occasion where it's acceptable. If you find a leak of a new ROM, which isn't already posted, and you verify it's legitimacy via either running it, or based on the source you obtained it from, then this is assisting in development, and should be posted in development. If you want to ask when a leak will be available use search first, then if not already in discussion, open a thread in general or Q&A.
If you have a problem flashing a ROM, this is NOT related to development. It's up to you to determine if it is specific to a particular ROM, and post useful information in that developer's existing thread for the ROM. If it happens on more than one ROM, and isn't a known issue (remember you should read several times more words than you post), then find out what you are doing wrong. Check guides written by others, try to repeat the problem and see if it happens every time. Something needs to be reproducible to be fixed effectively.
Once you have identified what you need help with go to the device Q&A forum (general if device lacks one), and make a clear, informative thread that explains the issue, and what you have tried doing to fix it. Did you re-download the ROM? Did you ask a friend to flash it for you, to reduce chance of user error? What steps (exactly) did you follow? What errors did you see (exact wording)? Did you double check all the steps? Did you do a wipe or hard reset?
If you make a clear, concise, yet detailed post, you will find help forthcoming, and should get the problem sorted very quickly. If someone suggests you try something, report back on what happened, did it work etc. Then, next time someone has this issue and searches, they will find this and have a verified and tested solution.
So remember... before you start a thread in development, ask yourself what you are developing. If you can't answer, then stop, step away from the post button, and think about where you are posting. Would it be better in General or Q&A, or is some more time with your best friend, search, required?
Click to expand...
Click to collapse
- http://forum.xda-developers.com/showthread.php?t=769191
Ok, I downloaded a custom kernel via the ROM manager app on the Vibrant's stock rom. Since then, haven't been able to do anything. It still can into recovery mode. I made a back up but that hasn't work.
Plus the boot screen changed. It says the usual Galaxy S logo but along with that, it now says GT-I9000 below that.
Any ideas on what should I do?
Odin back to stock. Tut is in the stickies. Always do your research fist.
Sent from my SGH-T959 using XDA App
Were you running 2.1 when you flashed this new kernel?
I accidently clicked on download vs cancel when I was browsing around the custom kernels section. Oh god I hate Odin.
Yes it was 2.1.
Do remember what the kernel was called? It was probably a 2.2 kernel. Which will wang the phone. Just download a 2.1 kernel and flash it. BOOM.
Thinking of posting a new thread???
Use the search button on the top bar!
This is the Vibrant Android Development Section, DO NOT post questions here...questions belong in the Vibrant Q&A Section​
If you have developed a ROM, or are working with others to do so, the development forum is somewhere to discuss and share ideas, post useful feedback and logs or crash dumps, and to discuss a common goal developers are trying to achieve.
It is NOT the place to post your question because it gets higher traffic, or because more experienced users frequent it. Doing this just annoys those who are working on the device, and drives them away. Developers don't want to wade through 20 threads of "Help me urgently" to find their threads for porting and fixing camera issues etc. Similarly, if a thread is designated as discussion for developers say, porting a camera fix, please do not post in there asking "When will it be ready?", "Can I flash this yet?" etc. This is both completely disrespectful to those working on the project (you evidently haven't read the important posts in the thread), and also is making it harder for developers to find comments from other developers or testers when required.
Similarly, don't make loads of "Thanks for your work here" posts in an active development thread. It's just as annoying to developers as asking when something will be ready. If a ROM is complete, then go ahead and thank the developer if you wish, but don't go into threads for devs only, and interrupt it to post "thanks". It's basically spamming, and is treated as such.
If you are posting in development, you should have read every sticky and notice there, and should be actively developing or helping in the development of something. Developing isn't installing a ROM, or using a tweak, it's creating a ROM or other hack or tweak. If you haven't read for several days before starting out on XDA, you are likely about to ask something already solved. I registered on XDA when I first wanted to post, and that was to join in a discussion on something. Sure, join up and ask a question, but read the information available in General and Q&A first, as your question will have been asked before. Search is your friend here, become familiar with it.
Regarding when to post in development if you are not actually developing something, there is one occasion where it's acceptable. If you find a leak of a new ROM, which isn't already posted, and you verify it's legitimacy via either running it, or based on the source you obtained it from, then this is assisting in development, and should be posted in development. If you want to ask when a leak will be available use search first, then if not already in discussion, open a thread in general or Q&A.
If you have a problem flashing a ROM, this is NOT related to development. It's up to you to determine if it is specific to a particular ROM, and post useful information in that developer's existing thread for the ROM. If it happens on more than one ROM, and isn't a known issue (remember you should read several times more words than you post), then find out what you are doing wrong. Check guides written by others, try to repeat the problem and see if it happens every time. Something needs to be reproducible to be fixed effectively.
Once you have identified what you need help with go to the device Q&A forum (general if device lacks one), and make a clear, informative thread that explains the issue, and what you have tried doing to fix it. Did you re-download the ROM? Did you ask a friend to flash it for you, to reduce chance of user error? What steps (exactly) did you follow? What errors did you see (exact wording)? Did you double check all the steps? Did you do a wipe or hard reset?
If you make a clear, concise, yet detailed post, you will find help forthcoming, and should get the problem sorted very quickly. If someone suggests you try something, report back on what happened, did it work etc. Then, next time someone has this issue and searches, they will find this and have a verified and tested solution.
So remember... before you start a thread in development, ask yourself what you are developing. If you can't answer, then stop, step away from the post button, and think about where you are posting. Would it be better in General or Q&A, or is some more time with your best friend, search, required?
jellette said:
Thinking of posting a new thread???
Use the search button on the top bar!
This is the Vibrant Android Development Section, DO NOT post questions here...questions belong in the Vibrant Q&A Section​
If you have developed a ROM, or are working with others to do so, the development forum is somewhere to discuss and share ideas, post useful feedback and logs or crash dumps, and to discuss a common goal developers are trying to achieve.
It is NOT the place to post your question because it gets higher traffic, or because more experienced users frequent it. Doing this just annoys those who are working on the device, and drives them away. Developers don't want to wade through 20 threads of "Help me urgently" to find their threads for porting and fixing camera issues etc. Similarly, if a thread is designated as discussion for developers say, porting a camera fix, please do not post in there asking "When will it be ready?", "Can I flash this yet?" etc. This is both completely disrespectful to those working on the project (you evidently haven't read the important posts in the thread), and also is making it harder for developers to find comments from other developers or testers when required.
Similarly, don't make loads of "Thanks for your work here" posts in an active development thread. It's just as annoying to developers as asking when something will be ready. If a ROM is complete, then go ahead and thank the developer if you wish, but don't go into threads for devs only, and interrupt it to post "thanks". It's basically spamming, and is treated as such.
If you are posting in development, you should have read every sticky and notice there, and should be actively developing or helping in the development of something. Developing isn't installing a ROM, or using a tweak, it's creating a ROM or other hack or tweak. If you haven't read for several days before starting out on XDA, you are likely about to ask something already solved. I registered on XDA when I first wanted to post, and that was to join in a discussion on something. Sure, join up and ask a question, but read the information available in General and Q&A first, as your question will have been asked before. Search is your friend here, become familiar with it.
Regarding when to post in development if you are not actually developing something, there is one occasion where it's acceptable. If you find a leak of a new ROM, which isn't already posted, and you verify it's legitimacy via either running it, or based on the source you obtained it from, then this is assisting in development, and should be posted in development. If you want to ask when a leak will be available use search first, then if not already in discussion, open a thread in general or Q&A.
If you have a problem flashing a ROM, this is NOT related to development. It's up to you to determine if it is specific to a particular ROM, and post useful information in that developer's existing thread for the ROM. If it happens on more than one ROM, and isn't a known issue (remember you should read several times more words than you post), then find out what you are doing wrong. Check guides written by others, try to repeat the problem and see if it happens every time. Something needs to be reproducible to be fixed effectively.
Once you have identified what you need help with go to the device Q&A forum (general if device lacks one), and make a clear, informative thread that explains the issue, and what you have tried doing to fix it. Did you re-download the ROM? Did you ask a friend to flash it for you, to reduce chance of user error? What steps (exactly) did you follow? What errors did you see (exact wording)? Did you double check all the steps? Did you do a wipe or hard reset?
If you make a clear, concise, yet detailed post, you will find help forthcoming, and should get the problem sorted very quickly. If someone suggests you try something, report back on what happened, did it work etc. Then, next time someone has this issue and searches, they will find this and have a verified and tested solution.
So remember... before you start a thread in development, ask yourself what you are developing. If you can't answer, then stop, step away from the post button, and think about where you are posting. Would it be better in General or Q&A, or is some more time with your best friend, search, required?
Click to expand...
Click to collapse
This. THIS! Lol.
Sent from my Nero v3 Vibrant.
i guess we have people auditioning for moderators now...weird!
menacetwosociety said:
i guess we have people auditioning for moderators now...weird!
Click to expand...
Click to collapse
I sure hope he gets the job ;-)
Sent from my T-Mobile myTouch 3G using XDA App
I did the exact same thing when I tried installing Eugenes Gingerbread rom. I got the I9000 boot screen and then nothing on my phone worked. Many error boxes popped up. I was able to apply my backup I created though and everything worked fine.
Odin is the answer to 90% of all questions posted here
Sent from my SGH-T959 using XDA App
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
Hey guys, first off let me say sorry if this is already on here, If it is please just point me to it as I can't seem to find anything. I have a i605 (verizon) Note 2, just picked it up off CL and its running I605VRUFND7 4.4.2, I really want to unlock the bootloader to rom it but I will run safestrap **If I have to** is there any way to do this at this point or did the monster get it's claws into it and lock it down?
Locked down....mobile tech vids can possibly
moffitt said:
Hey guys, first off let me say sorry if this is already on here, If it is please just point me to it as I can't seem to find anything. I have a i605 (verizon) Note 2, just picked it up off CL and its running I605VRUFND7 4.4.2, I really want to unlock the bootloader to rom it but I will run safestrap **If I have to** is there any way to do this at this point or did the monster get it's claws into it and lock it down?
Click to expand...
Click to collapse
Hi - you posted this in the original development section of the note II forums - this is NOT a development thread so why you thought it was OK to post it there is beyond me. Not only is this not development, it's certainly not original development. There are strict rules about where threads can be created and for what reason. If you didn't "create it," it doesn't belong in development...if you didn't "create it from scratch" it doesn't belong in original.
Please familiarize yourself with the rules link in my signature and post in the correct sections to avoid further moderator interaction. Thank you.
DutchDogg54 said:
Hi - you posted this in the original development section of the note II forums - this is NOT a development thread so why you thought it was OK to post it there is beyond me. Not only is this not development, it's certainly not original development. There are strict rules about where threads can be created and for what reason. If you didn't "create it," it doesn't belong in development...if you didn't "create it from scratch" it doesn't belong in original.
Please familiarize yourself with the rules link in my signature and post in the correct sections to avoid further moderator interaction. Thank you.
Click to expand...
Click to collapse
Hey forgive me here, I did a google search and posted, it was a simple mistake I even made a comment in the op about apologies before hand and if it was in the wrong section to please point me in the right direction im new here. id ask you to in the future to give people a chance when they are new as it came off kinda hateful or rude and stuff like this will make new members not want to reach out or make new posts let alone come back.
moffitt said:
Hey forgive me here, I did a google search and posted, it was a simple mistake I even made a comment in the op about apologies before hand and if it was in the wrong section to please point me in the right direction im new here. id ask you to in the future to give people a chance when they are new as it came off kinda hateful or rude and stuff like this will make new members not want to reach out or make new posts let alone come back.
Click to expand...
Click to collapse
Your "apology" in the OP was not in regards to the placement of your thread, thus is not applicable to my acting on it. I'm sorry you thought my post was "hateful or rude" (which it most certainly was NOT) - I'm simply asking you to follow the rules of the forum you are a member of, which is the minimum requirement for continued membership. Please familiarize yourself with the rules and you'll have a great time here. If you feel the need to talk with me further about how you conduct yourself on these forums a private message is appropriate. Any futher discussion in this thread will be deleted.
Is it impossible to bypass frp on it? Im locked out of my phone
Saddder said:
Is it impossible to bypass frp on it? Im locked out of my phone
Click to expand...
Click to collapse
I don't have this device but, I believe that one of the following threads may be helpful for what you are looking to do. Don't be afraid to ask for some member guidance within one of them too.
https://forum.xda-developers.com/showthread.php?t=3656806
https://forum.xda-developers.com/showthread.php?t=3740062
https://forum.xda-developers.com/showthread.php?t=3762177
If all else fails, and you don't receive any responses from the above threads, you can always try to obtain some member guidance within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3582142
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
I would like to help you about it, please check my signature
/del
itsm3c said:
Model: LG Q6 (M700A). ADB detect device, but fastboot not. In fastboot mode pc detects device as lg modem, its ok?...
Click to expand...
Click to collapse
I don't have this device but, you may find the following threads may be helpful for what you are looking to do. Don't be afraid to ask for some member guidance within one of them too.
https://forum.xda-developers.com/showthread.php?t=3591240
https://forum.xda-developers.com/showthread.php?t=2586472
https://forum.xda-developers.com/showthread.php?t=2277112
https://forum.xda-developers.com/showthread.php?t=2247471
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Ibuprophen said:
I don't have this device but, you may find the following threads may be helpful for what you are looking to do. Don't be afraid to ask for some member guidance within one of them too.
https://forum.xda-developers.com/showthread.php?t=3591240
https://forum.xda-developers.com/showthread.php?t=2586472
https://forum.xda-developers.com/showthread.php?t=2277112
https://forum.xda-developers.com/showthread.php?t=2247471
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
These threads didn't help me
You are in firmware update mode, not in fastboot mode. Unfortunately I'm not aware of any way to go in fastboot mode on LG Q6 plus (M700A). Tried unsuccessfully with several EU firmware versions.
Hey, moderators! Remove this thread please. LG Q6 has locked bootloader.
itsm3c said:
Hey, moderators! Remove this thread please...........
Click to expand...
Click to collapse
Just asking for a Moderator to close a thread on a post is rarely seen but, there's a process that the forum has set up for this specific request.
The following steps are the best way to have a thread closed by a Moderator (and they prefer to be asked by the specific member who opened the thread... that's you).
{FYI... The Moderators prefer not to delete a thread unless it's necessary to do so. Closing a thread keeps the information available for other members to learn from it as well.}
1) On the first post, select the bottom left triangle (reporting a post).
2) When the next page loads, select the reason on drop down section (at the bottom left of the text area), then select the one that states "Thread/post moving or maintenance".
3) If it's because your question was simply answered, then type the reason within the text area. Something simple like "Can you please close this thread because my posted question has been answered." (you can also tell them that "Ibuprophen is awesome" LOL!).
4) Finally, select the "Send report" and you'll then be taken back to the thread. Your all set!
The report is then listed on cue for a Moderator. It typically takes anywhere from 10 min to a day or two. The Moderators are very good and are pretty much on top of things.
Reporting a thread isn't intended as a bad thing. It just elevates having to send call-outs and PM's to a bunch of Moderators till one is available.
You've now graduated from the "Closing a thread 101" course! LMAO!!!
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Tandy TRS-80.
Thread Closed.