Hey guys, I was wondering if it's possible to flash the stock Samsung keyboard back onto the phone when using the Blu Kuban rom. I know the SamsungIME.apk is a system app and must be pushed into the system folder along with the odex file I believe. I've tried with both ES and Root Explorer, after copying it to another system folder, changed the permissions, and then copied it to the app folder. However nothing seems to work in allowing me to put it back. Am I missing something? I've even deleted the keyboard that Ruj gives with the rom and no joy.
It wouldn't be such a huge issue if the keyboard that was included didn't censor my words. I tend to have a filthy vocabulary and when swiping it won't allow me to use profanity. Outside of that, I prefer the numbers row on top of the keyboard as well. I know the rom is odexed and even pulled the stock apk out of a stock odexed rom to be sure, and then several other apks I've found around online. Sorry my first post after lurking for so long is really... well long, but I've usually been able to solve everything by thorough searching, but this one is beating me.
Thanks for any help in advance.
Try adding the libjni_latinime.so lib back to the /system/lib folder.
rujelus22 said:
Try adding the libjni_latinime.so lib back to the /system/lib folder.
Click to expand...
Click to collapse
Thanks for the reply, unfortunately that still had no effect. Tried with and without your keyboard still installed.
Alittle off topic, but since I can't yet post under your rom thread, I'd like to thank you now for all the development you've been doing. You were the sole reason I was able to bear with my E4GT up until the other day when my upgrade came into effect so I could get this S4, and ultimately swayed my choice in going with it. I dunno why the keyboards giving me such issues though.
Also, Rujelus, it might be alittle forward of me, but what I'd actually really love would be a themed version of that original Samsung keyboard. If that's out of line or out of the question I apologize, I'm not sure how much demand there really is for that. Honestly my favorite feature on it is the full keyboard with numbers without having to hit the symbol key. But, I'd mostly content with just being able to install the original again lol.
AkiraHunter said:
Thanks for the reply, unfortunately that still had no effect. Tried with and without your keyboard still installed.
Alittle off topic, but since I can't yet post under your rom thread, I'd like to thank you now for all the development you've been doing. You were the sole reason I was able to bear with my E4GT up until the other day when my upgrade came into effect so I could get this S4, and ultimately swayed my choice in going with it. I dunno why the keyboards giving me such issues though.
Also, Rujelus, it might be alittle forward of me, but what I'd actually really love would be a themed version of that original Samsung keyboard. If that's out of line or out of the question I apologize, I'm not sure how much demand there really is for that. Honestly my favorite feature on it is the full keyboard with numbers without having to hit the symbol key. But, I'd mostly content with just being able to install the original again lol.
Click to expand...
Click to collapse
Don't worry. I am going to theme a bunch of stuff that was removed from the ROM. It will all be available through the updater. I will try and get to the keyboard soon. :thumbup:
Sent from my SPH-L720 using Tapatalk 2
Please read forum rules before posting
Questions and help issues go in Q&A and Help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
rujelus22 said:
Don't worry. I am going to theme a bunch of stuff that was removed from the ROM. It will all be available through the updater. I will try and get to the keyboard soon. :thumbup:
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I really appreciate it! When I first saw the updater on my E4GT I thought it was the coolest thing on a rom ever haha.
Also, sorry for the wrong forum section, was late didn't realize I was in the wrong spot.
Related
Hi im a 15 year old noob and i own the HTC Wildfire im living in the UK on the 3 network and my wildfire is currently on 2.1 update 1 and there are many things this has stopped me from doing. And to be honest im really tired of waiting for this so called 2.2 update which i was expecting to arrive in october before i even bought the phone and doing extensive research it seems this update isnt in any rush whatsoever. I currently have a 2 year warranty one i would like to keep . I hear rooting and flashing my phone will void this as the carrier will see i have modified the ROM however if my phone were to break would it be possible for me to put the stock rom back on to hide this? Also do they really check that well? And if an official update does ever arrive is there an option to return to it? I would also like to know what the best method of rooting and flashing along with the best ROM. Thank you very much even you reading this all without replying is much appreciated. But of course if you reply i fkn love you (no homo).
Hey, I doubt they check that well and you can always install a RUU (ROM update utility/Goldcard) off shipped ROMs to restore, which leaves no traces (I think).
As for the best ROM, in my opinion it is CyanogenMod 6.1 RC2, as for me it is the quickest, it has the most tweaks, and everything works really. It has a lot of tweaks and fixes, and suggestions from the CyanogenMod community are being constantly implemented. If you want a "lighter" version you can try OpenFire, but for me CyanogenMod is a lot quicker and better to use. The only thing is, neither of these ROMs have HTC Sense, which you will not miss once you find the alternatives. I'm using LauncherPro Plus with Beautiful Widgets. Sure the HTC stuff looks pretty, but it's so freaking slow! If you really need a Sense ROM I'd suggest WildPuzzleRom 8 as it's Froyo based also.
Hope I helped
NickHu said:
Hey, I doubt they check that well and you can always install a RUU (ROM update utility/Goldcard) off shipped ROMs to restore, which leaves no traces (I think).
As for the best ROM, in my opinion it is CyanogenMod 6.1 RC2, as for me it is the quickest, it has the most tweaks, and everything works really. It has a lot of tweaks and fixes, and suggestions from the CyanogenMod community are being constantly implemented. If you want a "lighter" version you can try OpenFire, but for me CyanogenMod is a lot quicker and better to use. The only thing is, neither of these ROMs have HTC Sense, which you will not miss once you find the alternatives. I'm using LauncherPro Plus with Beautiful Widgets. Sure the HTC stuff looks pretty, but it's so freaking slow! If you really need a Sense ROM I'd suggest WildPuzzleRom 8 as it's Froyo based also.
Hope I helped
Click to expand...
Click to collapse
Ok so going on what youve said i now want to install CyanogenMod 6.1 RC2, what do i do now?
Hello im 19 years old, im from sweden..... and think this thread is completley wrong section of the forum.
To understand what I mean read this: http://www.xda-developers.com/announcements/a-reminder-from-the-xda-moderator-team/
keep your questions in the right section witch in this case is general.
also why would you write you age and so on no one cares! absolutly not under the developement part of the forum!
to add something that isnt offtopic in my post I got a short statement:
If you absolutly want to keep the garantue and to be sure of that the phone wont turn into a useless pice of plastic: DO NOT ROOT OR FLASH ANYTHING FROM THE XDA-FORUM, CLICK THE "X" IN YOUR UPPER RIGHT CORNER! FAST before the phone explode!!!!!
MadManMark said:
Ok so going on what youve said i now want to install CyanogenMod 6.1 RC2, what do i do now?
Click to expand...
Click to collapse
Download CM 6.1 from the relevant thread in this section and then use tur42keys rooting guide, also in this section.
Sorry I can't post the links since the forum restricts new users posting links.
adeadrat said:
Hello im 19 years old, im from sweden..... and think this thread is completley wrong section of the forum.
To understand what I mean read this:
keep your questions in the right section witch in this case is general.
also why would you write you age and so on no one cares! absolutly not under the developement part of the forum!
to add something that isnt offtopic in my post I got a short statement:
If you absolutly want to keep the garantue and to be sure of that the phone wont turn into a useless pice of plastic: DO NOT ROOT OR FLASH ANYTHING FROM THE XDA-FORUM, CLICK THE "X" IN YOUR UPPER RIGHT CORNER! FAST before the phone explode!!!!!
Click to expand...
Click to collapse
I understand where youre coming from i made a mistake seeing as im a noob and idk whos sad enough to read rules and i really dont appreciate your sarcasm so you can stick it.
ChrisPNE said:
Download CM 6.1 from the relevant thread in this section and then use tur42keys rooting guide, also in this section.
Sorry I can't post the links since the forum restricts new users posting links.
Click to expand...
Click to collapse
Thanks very much i think ill be fine without links anyway
MadManMark said:
I understand where youre coming from i made a mistake seeing as im a noob and idk whos sad enough to read rules and i really dont appreciate your sarcasm so you can stick it.
Thanks very much i think ill be fine without links anyway
Click to expand...
Click to collapse
He's only stating the obvious, this kind of post doesn't belong to the WF android Developpement sub-forum =/
Even a noob without reading the rules, one would already know to post this question in the General sub forum.
I was, and am still an android noob, however i learnt to flash, mod apk's and theme up my phone like crazy, just by simply reading and following instructions carefully. It's simple.
kevin2516 said:
Even a noob without reading the rules, one would already know to post this question in the General sub forum.
I was, and am still an android noob, however i learnt to flash, mod apk's and theme up my phone like crazy, just by simply reading and following instructions carefully. It's simple.
Click to expand...
Click to collapse
But you need to have patience and not expect things to 'happen magically'.
Plus you cant call for mommy to fix it for you!
Obviously he doesn't have patience.
I was wondering if anyone could help me port htc sense to my mytouch. I know it has been said that it will not work but I was wondering if anyone would be willing to try it out and see.
IronLionZion said:
I was wondering if anyone could help me port htc sense to my mytouch. I know it has been said that it will not work but I was wondering if anyone would be willing to try it out and see.
Click to expand...
Click to collapse
root the phone, install a custom recovery. Try out the HTC Sense ROM in the G1 section.
Good Day
Wrong section.
Try searching and reading.
Thank you, I will have to check that out. I guess my real question was is it possible to install a .apk of htc sense on top of say, CM 6.1?
IronLionZion said:
Thank you, I will have to check that out. I guess my real question was is it possible to install a .apk of htc sense on top of say, CM 6.1?
Click to expand...
Click to collapse
Most Sense UI rom system apps you cannot.
They would have to be modified for the Google framework.
It can be done but in most cases it's too much work.
It was done with the HTC Music app but I think that was about it.
Binary100100 said:
Wrong section.
Try searching and reading.
Click to expand...
Click to collapse
I was not aware of that, thought this would be the right section since it is development, guess not. I did search and I did not find any thing that answered my question fully, therefore I went ahead and opened a thread.
IronLionZion said:
I was not aware of that, thought this would be the right section since it is development, guess not. I did search and I did not find any thing that answered my question fully, therefore I went ahead and opened a thread.
Click to expand...
Click to collapse
No. Wrong. Unless you are developing or planning on developing then everything pretty much goes in General. 90% of questions posts that have a [Q] in the title belong in General (Q&A).
It works like this:
People with unrooted phones and just want information should go to General.
People with rooted phones but have ideas or suggesions should post in that particular rom thread for the developer... NEVER a new thread in Development! Otherwise, General.
Questions, comments or submitting of or about customizations (themes, wallpapers, etc) should go in Themes
Questions, comments or submitting (as long as it's not warez) of or about individual apps from Market should go in Apps.
Questions, comments about sdcards, cases, shields, batteries, etc should go in Accessories.
Safe rule of thumb is if you don't know... post in General.
If you don't know how to compile a rom then you should think twice before posting in Development (since it's specifically towards those that are developing or at least the members that are contributing useful information, walkthroughs, guides, etc).
Pretty simple really.
But if you DO know how to create roms and apps then use apktool to decompile the htc framework and try porting it over. However HTC doens't like to release a lot of their sources so if apktool doesn't work then it'll probably be easier for a developer to start by making his/her own as an imitation. Just don't blame XDA if you get sued.
Binary100100 said:
No. Wrong. Unless you are developing or planning on developing then everything pretty much goes in General. 90% of questions posts that have a [Q] in the title belong in General (Q&A).
It works like this:
People with unrooted phones and just want information should go to General.
People with rooted phones but have ideas or suggesions should post in that particular rom thread for the developer... NEVER a new thread in Development! Otherwise, General.
Questions, comments or submitting of or about customizations (themes, wallpapers, etc) should go in Themes
Questions, comments or submitting (as long as it's not warez) of or about individual apps from Market should go in Apps.
Questions, comments about sdcards, cases, shields, batteries, etc should go in Accessories.
Safe rule of thumb is if you don't know... post in General.
If you don't know how to compile a rom then you should think twice before posting in Development (since it's specifically towards those that are developing or at least the members that are contributing useful information, walkthroughs, guides, etc).
Pretty simple really.
But if you DO know how to create roms and apps then use apktool to decompile the htc framework and try porting it over. However HTC doens't like to release a lot of their sources so if apktool doesn't work then it'll probably be easier for a developer to start by making his/her own as an imitation. Just don't blame XDA if you get sued.
Click to expand...
Click to collapse
Ok thank you for clearing that up, I will see if I can figure it out and let you know if I sucessfully port it over. BTW I love the community hero mix, I don't think I really even need to try to find a way to make sense work now that I have it, but I am still intrigued Thank you for making it, it is awesome
IronLionZion said:
Ok thank you for clearing that up, I will see if I can figure it out and let you know if I sucessfully port it over. BTW I love the community hero mix, I don't think I really even need to try to find a way to make sense work now that I have it, but I am still intrigued Thank you for making it, it is awesome
Click to expand...
Click to collapse
Thanks! I've been working constantly on it and Im looking forward to CM6.1.0-RC2-DS so I can make my next release. I wonder what's taking so long.
UberMario said:
Try out the HTC Sense ROM in the G1 section.
Click to expand...
Click to collapse
OMG! wont a g1 rom brick a mytouch ?
shreyas1122 said:
OMG! wont a g1 rom brick a mytouch ?
Click to expand...
Click to collapse
Nope. Actually, flashing a ROM using recovery should never brick a phone. Worse case scenario, it'll throw you into a boot loop, but then you just boot back into recovery and flash another ROM.
And most G1 ROM's will work for myTouch 32B owners, since a 32B myTouch is basically a G1 without the physical keyboard.
DonJuan692006 said:
Nope. Actually, flashing a ROM using recovery should never brick a phone. Worse case scenario, it'll throw you into a boot loop, but then you just boot back into recovery and flash another ROM.
And most G1 ROM's will work for myTouch 32B owners, since a 32B myTouch is basically a G1 without the physical keyboard.
Click to expand...
Click to collapse
thats some news news for me..
what have I been doing wid my myTouch 32B? lol..
(n yes I had the misconception that flashing from recoveries could brick)(thanks again)
Sent from my Nexus One
Learn something new everyday. Happy flashing.
What are the rules about posting other peoples work, i.e. ROMS and themes? Im not sure but I see over in other forums, like the EVO for example where 5 people are making ROMS using a base that they give credit to one guy for. I only ask this because over here in the D2 section, there is only 3-4 different groups working on stuff, everyone is tight lipped and not willing to let anyone in on the "secret". I see random posts where it says that the source for the base of ALL these ROMS is open, meaning ANYONE should have access, and ANYONE should be able to do as they please with them. I know that is not the case and it comes down to who you know, just like anywhere else in life, but I think the community is only being held back because we only have those select few working on new stuff....DONT get me wrong, all the devs. are doing amazing work for us D2 users, I just think we are being limited alot. I sent a pm to one dev in particular asking him to release a variant of his themes with the ApeX flip and fly out transition animations added. They are really cool and they compliment his ROMS well. I even got permission from some others to use those. I not only didnt get a response, but when I pm'd him askin why he hadnt responded, he said he never got it, (I still have it in my outbox). I just think it would be cool to have, say, a Fission Blackout ROM with the blackout Swype and android keyboard, and the cool transitions from ApeX, and only have to flash one zip in recovery. Im just sayin. Im not being ungrateful so please dont tear me apart, just puttin it out there
mikeyinid said:
What are the rules about posting other peoples work, i.e. ROMS and themes? Im not sure but I see over in other forums, like the EVO for example where 5 people are making ROMS using a base that they give credit to one guy for. I only ask this because over here in the D2 section, there is only 3-4 different groups working on stuff, everyone is tight lipped and not willing to let anyone in on the "secret". I see random posts where it says that the source for the base of ALL these ROMS is open, meaning ANYONE should have access, and ANYONE should be able to do as they please with them. I know that is not the case and it comes down to who you know, just like anywhere else in life, but I think the community is only being held back because we only have those select few working on new stuff....DONT get me wrong, all the devs. are doing amazing work for us D2 users, I just think we are being limited alot. I sent a pm to one dev in particular asking him to release a variant of his themes with the ApeX flip and fly out transition animations added. They are really cool and they compliment his ROMS well. I even got permission from some others to use those. I not only didnt get a response, but when I pm'd him askin why he hadnt responded, he said he never got it, (I still have it in my oubox). I just think it would be cool to have, say, a Fission Blackout ROM with the blackout Swype and android keyboard, and the cool transitions from ApeX, and only have to flash one zip in recovery. Im just sayin. Im not being ungrateful so please dont tear me apart, just puttin it out there
Click to expand...
Click to collapse
Straight from XDA rules
Forum Rules said:
If you are developing something that is based on the work of another Member, you MUST first seek their permission, and you must give credit to the member whose work you used. If a dispute occurs about who developed / created a piece of work, first try to settle the matter by private message and NOT in open forum. If this fails then you may contact a moderator with clear evidence that the work was created by you.
Convincing evidence will result in copied work being removed. If there is no clear evidence you created the work then in the spirit of sharing all work will remain posted on the forums.
These rules apply to all software posted on XDA unless that software comes with a license that waives these rules.
Click to expand...
Click to collapse
And that is reasonable. Thanks
mikeyinid said:
And that is reasonable. Thanks
Click to expand...
Click to collapse
No problem.... mind if I close this?
theimpaler747 said:
No problem.... mind if I close this?
Click to expand...
Click to collapse
nope. go ahead.
Due to question being answered and consent of the OP, thread closed
Can anyone help me figure out how to change keyboard background?
I have looked through everything and must be missing it somehow...
Well we found the files, edited one to test but now when we reflashed the swype.apk, no virtual keyboard is installed. ADB pushed it, reflashed it, moved it to system/app... no keyboard shows up after only changing one image...
I am confused...
I basically need to figure out how to resign the apk after customizing and I am pretty noob right now..
You'll be better off asking this in the theming subforum.
I figured it out finally. It was me being dumb is all...
jkrough0728 said:
I figured it out finally. It was me being dumb is all...
Click to expand...
Click to collapse
Would you mind contributing to the community and sharing the solution?
Sent from my mind using telepathitalk
Let me get it completely figured out first but then of course!!
To change it, you have to edit swype.apk and I have had to reflash 3 times now because I keep making little errors. It is kind of a painful process!
Well I finally got most of the editing done... I kept it pretty simple as far as the letters and I didn't really try hard with the placements on things because to be honest I wanted to throw the phone after awhile !
But here is a sample of what I did, if there is actually a demand for people wanting to do this then I will write a "how to" but I have to warn you it is painful and you will need experience with photo editing...
I changed the flame color in the background to be different for each mode.
And yes, Swype still works!
Consider this your first demand for a how-to.
Ha.. I will go ahead and get started on it then and post under themes/apps for everyone! I am not taking credit for doing it but I will write the how to for somebody to try.
Maddog and Illinois08 were the biggest help during the process so I will include them in the walk through.
Pointless816 said:
Consider this your first demand for a how-to.
Click to expand...
Click to collapse
I have placed the how to under themes section.
Let me know if you have any questions...
I recently got my hands on a Kindle Fire HD 7" and have been playing around with it a bit. I wasn't a fan of the ads found in the lockscreen and initially set out to modify the smali to remove the ads or at least not display them. While playing around with the build.prop, I decided to change the density to 213 (the same as the Nexus 7) and upon rebooting I was greeted with the standard ICS lockscreen. So I no longer needed to mess with smali since this is much easier and others can do it just as easily.
I have tried this on the 7.2.3 firmware but it may work on older versions just the same. If it does, please post and let others know that it worked.
Prerequisites
Rooted device
ES File Explorer
local.prop - download link
Although I did this via ADB and manually mounted /system as RW and used vi from busybox, I'm going to explain how to do this without any command line usage.
I'm using ES File Explorer but if you are familiar with an alternative which allows you to write a file to /data then please feel free to use that.
Copy the downloaded local.prop file to your device's SD card
Install ES File Explorer if you have not done so. This is available in the Amazon Appstore.
Open ES File Explorer and go to the settings by pressing the menu button in the navbar.
Select Root Settings
Check Root Explorer
Check Up to Root
Press the back button a few times until you are back at the main app
Navigate to the SD card where local.prop is located, long press the local.prop file and select Copy to
Press the Up icon at the top right of the dialog that appears
Select the / folder (should be above SD Card)
Select data folder and press OK
If you'd like, you can navigate to the /data folder and verify that local.prop does exist in there now. If so, then it's time to reboot.
Reboot the device. You'll have to shut down and then power back on since the amazon firmware does not provide a reboot option.
Caveats
Black background on lockscreen.
Auto brightness toggle no longer shows up when adjusting brightness.
For those that would like to see what's in the local.prop file in advance, here you go.
Code:
# override ro.sf.lcd_density found in build.prop
qemu.sf.lcd_density=213
Before I forget, please do not ask how to root or how to accomplish things outside the scope of this thread. This information is intended for those that have already rooted their device and are on stock firmware but don't want the ads and would rather have the ICS lockscreen.
0xD34D said:
Before I forget, please do not ask how to root or how to accomplish things outside the scope of this thread. This information is intended for those that have already rooted their device and are on stock firmware but don't want the ads and would rather have the ICS lockscreen.
Click to expand...
Click to collapse
And the keyboard?
Sent From My Super Modded KFHD
persano said:
And the keyboard?
Sent From My Super Modded KFHD
Click to expand...
Click to collapse
What about it? Works fine at this density if that's what you are getting at.
0xD34D said:
What about it? Works fine at this density if that's what you are getting at.
Click to expand...
Click to collapse
Yes, in landscape and portrait is well?
Sent From My Super Modded KFHD
persano said:
Yes, in landscape and portrait is well?
Sent From My Super Modded KFHD
Click to expand...
Click to collapse
Yep, no problem in either orientation. Been using it with this density setting since last night. I wanted to put it through some normal usage before posting about it. Besides the caveats listed in the OP, I have not noticed anything else.
This works great! Anyway to change background though?
Sent from my KFTT using XDA Premium HD app
ICS Lockscreen the easy way
0xD34D,
Thank you for the post.
This is a nice option.
prokennexusa said:
0xD34D,
Thank you for the post, we had this tweak under Post #2 in http://forum.xda-developers.com/showthread.php?t=2101564 but as you will see we revoked the post since we had over 27 people Brick there Kindle in one week of posting the How To. We plan to add a new post to #2 that allows you to change the lock screen in 5 steps and no chance of Bricking the Kindle. We prefer this idea, it is just a little more dangerous and we did not like the idea of loosing the brightness toggle.
It is still nice to offer people options.
Click to expand...
Click to collapse
Actually if they follow the steps I have outlined, there is very little danger involved. Like many modifications, there is always the chance that something can go wrong. I've made far more sever changes to this device without problems.
I could probably bring this down to 3 steps if I really wanted to but that's no fun. Please don't jack threads so you can promote your own. The Android community is about choices and they deserve to have this information and do with as they please.
prokennexusa said:
0xD34D,
Thank you for the post, we had this tweak under Post #2 in http://forum.xda-developers.com/showthread.php?t=2101564 but as you will see we revoked the post since we had over 27 people Brick there Kindle in one week of posting the How To. We plan to add a new post to #2 that allows you to change the lock screen in 5 steps and no chance of Bricking the Kindle. We prefer this idea, it is just a little more dangerous and we did not like the idea of loosing the brightness toggle.
It is still nice to offer people options.
Click to expand...
Click to collapse
you gon and did it now
meddle70 said:
This works great! Anyway to change background though?
Sent from my KFTT using XDA Premium HD app
Click to expand...
Click to collapse
Right now there does not seem to be an easy way to set the background (wallpaper). Amazon seems to have disabled the WallpaperManager which apps use to set the wallpaper. I was playing with a test app and on the KFHD I get a null value for the manager so an alternative method will need to be found for that.
0xD34D said:
Right now there does not seem to be an easy way to set the background (wallpaper). Amazon seems to have disabled the WallpaperManager which apps use to set the wallpaper. I was playing with a test app and on the KFHD I get a null value for the manager so an alternative method will need to be found for that.
Click to expand...
Click to collapse
Ah. Well ill tell you what doing that mod makes it feel much more responsive. I tried the third party lockscreens, and they were just too slow for my taste. I dont really mind the black screen and i didnt like autobrightness. Gives me a headache when playing solitare lol
0xD34D said:
Actually if they follow the steps I have outlined, there is very little danger involved. Like many modifications, there is always the chance that something can go wrong. I've made far more sever changes to this device without problems.
I could probably bring this down to 3 steps if I really wanted to but that's no fun. Please don't jack threads so you can promote your own. The Android community is about choices and they deserve to have this information and do with as they please.
Click to expand...
Click to collapse
0xD34D,
Very nice tutorial 0xD34D!
prokennexusa said:
0xD34D,
I am sure it was the ways we setup the steps. Anyways options are great for the end user. Very nice tutorial 0xD34D!
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
0xD34D,
Ahhhh, actually there is a way, easy too. Monitor that like I gave you tomorrow AM. We will have the instructions posted.
Click to expand...
Click to collapse
You might want to monitor my OP since I deprecated the original method in favor of a simple local.prop. And once again, let me thank you for jacking this thread to promote your own. Top notch XDA sh!t right there!
To anyone following this thread. I have been following Ox for quite some time now and he has never led me astray. If you follow the instructions as posted in the OP you'll be fine. People brick because of their own stupidity and lack of reading or knowing exactly what they are doing with their device. Not because a developer led them astray.
Sent from my GT-N7105 using Tapatalk 2
Method update
For those that may have already made this modification. I have updated the procedure which does not require any modifications in /system. If you want to use the new method just revert your changes to build.prop so that the density is back at 240 and then follow the steps to get local.prop onto /data
Any screen shots man
Sent from my Nexus 7 using Tapatalk 2
esema1o said:
Any screen shots man
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I've updated the OP with a couple screenshots. As you can see there is no background but it is indeed the standard ICS lockscreen.
0xD34D said:
You might want to monitor my OP since I deprecated the original method in favor of a simple local.prop. And once again, let me thank you for jacking this thread to promote your own. Top notch XDA sh!t right there!
Click to expand...
Click to collapse
0xD34D,
Wow, what was not my intention, I am quite surprised I have never had someone say I was jacking there thread. We do not need to jack threads since our reason for being here is not for personal gratification or kudos, it is to serve people and a community which we love and have been a part of since 1978. If I offended you, I am sorry, that was not my intention. I was just sharing my concern around a build.prop and I came back to since I saw your edit, I was going to say "impressive idea using a local.prop edit" which it is impressive - I also was going to send you a PM on how to inject the code through two keystrokes. Sorry, I will remove the link. Wow..........
prokennexusa said:
0xD34D,
Wow, what was not my intention, I am quite surprised I have never had someone say I was jacking there thread. We do not need to jack threads since our reason for being here is not for personal gratification or kudos, it is to serve people and a community which we love and have been a part of since 1978. If I offended you, I am sorry, that was not my intention. I was just sharing my concern around a build.prop and I came back to since I saw your edit, I was going to say "impressive idea using a local.prop edit" which it is impressive - I also was going to send you a PM on how to inject the code through two keystrokes. Sorry, I will remove the link. Wow..........
Click to expand...
Click to collapse
One thing I found funny was you said you originally had this in your #2 post of the link you provided but the only thing in that #2 post was "Reserved for new tutorial" and that was the original post since it did not show that it was ever edited. If you had people bricking due to a simple build.prop edit then you must have provided some incorrect directions or the users simply did something else that was out of the scope of the tutorial. Commenting on another thread with a link back to your tutorial and then providing FUD is not really good forum etiquette. Whether that was your intention or not, that is how it was perceived by myself and others I showed the comment to.
And on a side note, this particular community has been around for about 4.5 years. I'm not aware of any Android devices from the late 70's.