settings>about phone>model number>t-mobile G1
the problem.... i have a rogers htc dream
it's not really that big of a deal but it is really irritating to have the tmobile bootscreen and have my model number set as tmobile is there anyway to change this? preferably w/o bricking my phone
I'm not 100% sure but I think you can fix this by editing your build.prop file. I remember a while back when CM ROMs had your Dream labeled as the ADP1 and all the T-Mobile users couldn't use the T-Mobile apps someone found a way to edit your build.prop and fixed that.
it will say tmobile g1 based on what rom you are using.
I was ebi1 and went to ebi0.
There is absolutely no reason for you to go back to ebi1, it will only provide more of a hassle when flashing roms and ect.
If you are still interested in switching back to ebi1 pm me (although i dont know why you would )
no thank you i do not wish to go back, it's much easier this way i just want to get rid of any hints to tmobile as i have never used their service in my life.
ps. if it was the rom i flashed how come it changed my splash1 ?
I'm pretty sure that the G1 bootscreen was flashed when you flashed the DRC83_Base_Defrangled rom. If you want to change it, use the bootscreenflasher 3000 tool from these forums (I think its on the G1 themes section). Also, to make it say rogers under the settings menu, just change the build.prop. (or build.trout.prop, I forget which). Open it with notepad and everytime you see Tmobile G1 just change it to HTC Dream (or whatever you want...). Also, while your there, you can change the android version number it displayes, so if you want you can make it show your on android 3.0 gingerbread lol.
themapleboy said:
settings>about phone>model number>t-mobile G1
the problem.... i have a rogers htc dream
it's not really that big of a deal but it is really irritating to have the tmobile bootscreen and have my model number set as tmobile is there anyway to change this? preferably w/o bricking my phone
Click to expand...
Click to collapse
/system/build.prop (or could have a "trout" in there...)
Your phone was broken by someone who doesn't understand that there is NO SUCH THING as a "tmobile g1" -- they are ALL "HTC DREAM".
so i looked into my DRC83_Base_Defrangled rom and it said nothing about a g1 tried reflashing it to no avail. is there anyway to see the file's inside my phone? maybe that way i can adb in a new prop file if that one is messed up.
EDIT: nevermind i found out u can see the files with linda and it was build.trout.prop ........ anyone know what the command is to push that with
$ /ANDROID/android-sdk-mac_86/tools/adb push /ANDROID/build.trout.prop /system/build.trout.prop
failed to copy '/ANDROID/build.trout.prop' to '/system/build.trout.prop': Read-only file system <-- because apparently i don't
EDIT:EDIT: yh i forgot to remount lol it worked now and my phone is now a htc dream again........to bad splash 1 is still the same
You can change the first boot screen using this tool. Its easy to use.
And some quick adb commands for you to know
adb remount (always do first)
adb push C: (location) /system (install/push files to phone)
adb shell rm -r /system/app(apk name) (removes unwanted apps)
Related
tested on JACxHEROSki2.2 A.B.RMX & Drizzy's last HERO rom. Maxisma1.6.1
If your on HERO rom but hate the ARC lockscreen here's how to change it.
get the attached file, unzip *.apk and extract it to the root of your sdcard, then perfrom the following:
adb remount
adb shell rm /system/framework/com.htc.resources.apk
adb shell cp /sdcard/com.htc.resources.apk /system/framework/
adb shell reboot
or console
mount /system/
rm /system/framework/com.htc.resources.apk
cp /sdcard/com.htc.resources.apk /system/framework/
reboot
UPLOAD KEEPS TIMING OUT CHECK BACK LATER - IF ANYONE WOULD LIKE TO HOST THE FILE PLEASE LET ME KNOW...if you want the file please send me a PM
this should be the same for the hero build you are on, but since the last hero build i downloaded was new vision revision 2 for a friends phone, i don't have a more current hero. with that said
it was in data/app_s/HtcLockScreen.apk/res in that folder there are 4 drawables. each of them contains parts to it. i would imagine you could just drop that .apk into another hero rom, sign it, and flash it.
though i would definitely make a nandroid first
david1171 said:
this should be the same for the hero build you are on, but since the last hero build i downloaded was new vision revision 2 for a friends phone, i don't have a more current hero. with that said
it was in data/app_s/HtcLockScreen.apk/res in that folder there are 4 drawables. each of them contains parts to it. i would imagine you could just drop that .apk into another hero rom, sign it, and flash it.
though i would definitely make a nandroid first
Click to expand...
Click to collapse
thanks, what i actually ended up doing since both lockscreen.apk were the same i figured the "difference" i wanted laid somewhere else so through trial and error i figured it out.
it was the .com.htc.resources.apk from drizzy's rom that made the difference from an ARC lockscreen to a FULL lockcreen.
adb shell rm /system/framework/com.htc.resources.apk
adb shell cp /sdcard/com.htc.resources.apk /system/framework/
adb shell reboot
i should post a [how to] lol
UPDATED OP MADE MY FIRST HOW TO WOOT WOOT!!
wrong thread.
screenshots of this please?
johnnylicious said:
screenshots of this please?
Click to expand...
Click to collapse
a bit pointless to show screenshots of something that is not there. the lockscreen just shows the info that is normally on the arc, but no arc (the png files have been replaced with transparent versions)
Big thanks to the OP. I was doing this myself but didn't know enough adb to get my revised graphics back on to the phone.
Baldyman1966 said:
a bit pointless to show screenshots of something that is not there. the lockscreen just shows the info that is normally on the arc, but no arc (the png files have been replaced with transparent versions)
Big thanks to the OP. I was doing this myself but didn't know enough adb to get my revised graphics back on to the phone.
Click to expand...
Click to collapse
AGREED, this just removes the arc from your lockscreen and shows the complete image - leaving just date and time.
I'll post a screenshot later, I guess.
haha oooh i got cha i didnt undestand exactly what you changed or modifited to the lockscreen =D
i have the transparent lockscreen also on mine hero rom
thanks!
console commands
So i unziped it to my sd card, but I can't remember if i put it in the root of my sdcard or if its in /sdcard/downloads, but I don't know the console command to list the directories or files in that folder, i know on ADB/terminal emulator its 'ls'
NVM i figured it out, had to also type mount /sdcard because it kept saying no such file, but mount /sdcard did the trick
Has anyone got this to work on 1.7r2?
djunio said:
Has anyone got this to work on 1.7r2?
Click to expand...
Click to collapse
nope feel free to try it out.. just make a nandroid backup first using the recovery console if you have CM's new recovery image. if it doesnt work you can always just do a restore..
post back results
cest hero 2
My results on "cest hero 2" were well..take a look.
Kidd_Hanma said:
nope feel free to try it out.. just make a nandroid backup first using the recovery console if you have CM's new recovery image. if it doesnt work you can always just do a restore..
post back results
Click to expand...
Click to collapse
I did it seems like it worked but it gets stuck on the htc screen, I also tried to modify the file in 1.7r2 and that put me in a bootloop
does anyone know what hero built this resourse.apk is from?
im gonna test the resourse apk from drizzys elite and champion rom.
ill post back with results.
just tried it. none works. idk how to edit so im not gonna attempt to do it.
Follow up
djunio said:
I did it seems like it worked but it gets stuck on the htc screen, I also tried to modify the file in 1.7r2 and that put me in a bootloop
Click to expand...
Click to collapse
dont modify the file in the actual rom - you'll get stuck in a boot loop due to the rom needing to be resigned.
1.7 uses a new hero dump so it may not work.. My phone fell in Kool-Aid so im useless for the time being lol
johnowa636 said:
My results on "cest hero 2" were well..take a look.
Click to expand...
Click to collapse
looks okay but i notice the "AM" is off the actual time display
hiroots said:
does anyone know what hero built this resourse.apk is from?
im gonna test the resourse apk from drizzys elite and champion rom.
ill post back with results.
Click to expand...
Click to collapse
you may have done something wrong as this works with drizzys elite 100%
http://forum.xda-developers.com/showthread.php?t=538942&highlight=skinning+hero+app
Click to expand...
Click to collapse
can someone port the lockscreen from this thread to the new 2.8xxx builds???
the com.htc.resources.apk has some extra images added into this build which is causing the crash when u load in the old one
ok how do i reverse this i use twisteds hero i want the arc back
bigballa said:
can someone port the lockscreen from this thread to the new 2.8xxx builds???
the com.htc.resources.apk has some extra images added into this build which is causing the crash when u load in the old one
Click to expand...
Click to collapse
i have already done this - send me a pm and ill get you set up- im running it on jachero 1.8
is it possible for me to replace my camera wit the htc camera app that is on the hero rom, and if so where can i get it??
not sure if possible, but it's easy to find out.
all you have to do is download the hero rom and extract the files. go into the system folder and look inside of the app folders and look for HTCCamera.apk OR Camera.apk.
take it and push it to your phone and reboot, it should work or not work you can test. it wont harm your phone. make sure you backup your current camera app first so you can revert if the hero camera dont work. Make a note of what file name your current camera is, and rename the hero camera to be the same thing. then push it.
NguyenHuu said:
not sure if possible, but it's easy to find out.
all you have to do is download the hero rom and extract the files. go into the system folder and look inside of the app folders and look for HTCCamera.apk OR Camera.apk.
take it and push it to your phone and reboot, it should work or not work you can test. it wont harm your phone. make sure you backup your current camera app first so you can revert if the hero camera dont work. Make a note of what file name your current camera is, and rename the hero camera to be the same thing. then push it.
Click to expand...
Click to collapse
you dont think i can jus install it as a normal app?? and if not, how do i "push it to my phone"??
gamefan231 said:
you dont think i can jus install it as a normal app?? and if not, how do i "push it to my phone"??
Click to expand...
Click to collapse
this is the exact steps you need to take.. first you need adb installed
adb remount
adb pull /system/app/Camera.apk
adb install directoryoffile/HTCCamera.apk
adb install directoryoffile/HTCAlbum.apk
adb shell remount
if it doesnt work or you get a FAILURE when pushing either one of these .apk files just push back your old Camera.apk
palosjr said:
this is the exact steps you need to take.. first you need adb installed
adb remount
adb pull /system/app/Camera.apk
adb install directoryoffile/HTCCamera.apk
adb install directoryoffile/HTCAlbum.apk
adb shell remount
if it doesnt work or you get a FAILURE when pushing either one of these .apk files just push back your old Camera.apk
Click to expand...
Click to collapse
where can i find "adb" and how do i install it?
gamefan231 said:
where can i find "adb" and how do i install it?
Click to expand...
Click to collapse
ay yi yi... look here... it will tell you exactly how to get ADB up and running... once you do, you will wonder how you ever lived without it...
ADB, Fastboot, Nandroid for n00bs
also, this write up is for the 1.5r2 SDK, the setup for 1.5r3, which is the newest one is exactly the same
IF YOU HAVE THE SDK INSTALLED, THEN YOU ALRREADY HAVE ADB. needed that in caps so you dont go installing stuff u might not need.
if you are on windows, hit start > run. then type CMD, then the dos box will pop up. here you can enter in the commands that palosjr gave earlier.
i was following the directions on the thread posted but when i tried to put the sdk folder in my c/ drive it told me i didnt have enuff space...would it be possible for someone to put the htccamera app into a theme for me?
I tried it but it resulted in following error:
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
For either one (HTCCamera and HTCAlbum)
ya nm good luck im going to see how it turns out i would love to have HTC camera and Album seems nice.
abraxas_son said:
I tried it but it resulted in following error:
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
For either one (HTCCamera and HTCAlbum)
Click to expand...
Click to collapse
probably needing some other framework from hero to make this work... i will do some searching for you and see if i cant get it to work. if you guys want the HTC camera, why dont yall just flash jacheroski1.8 or 2.0? both are solid, and in case you didnt hear, all the SMS issues are fixed.
I have ran those roms and ya they are solid but i like to stick with cyanogen roms. Im only really after the ablum app with multi touch. Now that BFS has hit the scene I'm tempted to give a hero rom a look see but i want to see what cyanogen will do next lol.
I looked around in two hero roms and found in the lib folder two *.so files for the camera and one for album. Those are the only files that are named after the apps. On a side note, do the camera and ablum app rely on one another? The reason i ask is the thread was started about the camera app and then it is recommended to push both by adb. Getting album to work is what caught my eye to begin with all though htc camera app would be nice.
Any progress on this front? I tried a couple Hero roms and really liked the camera and gallery. I can't stay on Hero because it doesn't work right with Google Voice dial-thru. Is there a way to get them ported into Cyanogen 4.1.11.1?
Install_failed_already_exists
Interesting... trying to adb install HTCCamera.apk (taken from the Sprint Hero dump) into Cyanogen 4.1.11.1 fails with the message [INSTALL_FAILED_ALREADY_EXISTS]
Doing the same for HTCAlbum.apk gives the message [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
Anyone thought about this? Surely it must be possible to spoof a few files to make the phone appear to be a HVGA device so we can download apps which are not yet officially supported.
Any idea of the feasibility?
think its just a waiting game till there supported, some what of a let down for the tattoo
Market Enabler dont work...
It is the build.prop that identifies your device, though I don't own a Tattoo, so I can't be sure what else is there. Check out the contents of your / (root) folder.
BTW, do you guys have your HTC Tattoos rooted yet? Working ADB shell? Hard SPLs, and other hacked up goodies?
Anyhow, if you're not rooted, or don't at least have ADB shell running as root, you will not be able to change the build.prop (for instance).
How test if the tattoo (or an Android phone in general) is rooted ?
thanks
Tattoo is not rooted.
fisac71 said:
How test if the tattoo (or an Android phone in general) is rooted ?
thanks
Click to expand...
Click to collapse
Download some Terminal app from the market, open it and type su in the prompt. Push enter. If you see a # in the next line, you are SuperUser.. if you get permission denied, then you dont have root access.
That's too bad though (that it isn't rooted yet). Probably just a matter of time..
I have gotten around by running the .abk of the memory card, luckily I have a magic and can pull apps of the grown up market, things like 3g watchdog and facebook etc all work great.
skrki said:
It is the build.prop that identifies your device, though I don't own a Tattoo, so I can't be sure what else is there. Check out the contents of your / (root) folder.
BTW, do you guys have your HTC Tattoos rooted yet? Working ADB shell? Hard SPLs, and other hacked up goodies?
Anyhow, if you're not rooted, or don't at least have ADB shell running as root, you will not be able to change the build.prop (for instance).
Click to expand...
Click to collapse
The only real hack so far is just reflashing the firmware using the goldcard method. No root, no other goodies.
Yeah... I found this
http://androidforums.com/htc-tattoo/20498-unlocking-htc-tattoo-orange-uk.html
Not really useful to me, but I feel obliged to spread the word
on my htc kaiser, once 1.6 came out , I think it sees ur res and only shows apps that support the sceen res. Even if you go back to 1.5. Solution for us is to boot at 480x320 and sign into market..but i dont think you guys can do that or not..
i flashed the zip via recovery and after i rebooted i had no service and the phone.apk wasnt working so i had to do a nanoid restore. Any ideas what i did wrong? im running DC 2.0.9.1 deodex rom
yep same thing happened to me,had to do a restore
Any ideas?
as far as i can tell it has nothing to do with with what you did, but rather it's a problem with signature matches, when Phone.apk is modified u have to resign it, and Android on startup seems to check the signatures and can tell they dont match what they should be and thus doesn't let the phone app load, which causes a lack of service... i'm still working on this but i dont know if there is a 'fix'... i'm hoping so. If you'd like to take a look at what i've done so far i have a thread in the main Q&A about custom phone apk on the hero....
i know this doesn't help a lot but i hope it clarifies some things
later today i'm going to try to resign every apk in my system folder... mainly just because i'm out of ideas, but hoping it works... who knows, hope i dont end up with a brick!
also it's important to make sure that if u don't go the update.zip route, when pushing any system app that you either do it from recovery or thru adb with the following commands
adb shell stop
adb push ????
adb shell start
after you issue the start command it may be a while but the phone kinda does a soft reset so ya anywho....
For those of you having trouble seeing protected apps, I modified our fingerprint in the build.prop. What this does is spoofs the market into thinking its seeing a Droid 2 (with Froyo) It worked for me, let me know if it does for you.
1. Put build.prop into your AndroidSDK\TOOLS folder
2. Connect via USB.
3. CD (Navigate) in CMD to your tools folder
Mount your /system (adb remount) works for me
Copy and paste this
4. adb remount
5. adb push build.prop /system/build.prop
6. adb reboot
To test if you need this before you push the build.prop fix, search the market for Us Bank. If only 2 or 3 show up, you are not getting the full market. After this fix, you should see 10 items listed when you search for Us Bank.
Hope this helps.
2.2 Market Fix Build.Prop -- WITH STAGEFRIGHT=TRUE
This can also be done via Root Explorer.
Edit: Here is a "clean" build.prop for those of you who do not want the stagefright fix (which breaks video playback) Sorry, I was not aware it did that. Thank you.
Non Stagefright Build.prop -- WITH STAGEFRIGHT=FALSE
For everyone flipping out about Birdmans tweet and you want the stock build.prop, here ya go
Stock Build.prop -- WITH NOTHING! STOCK!
You only need the stock one if you ever plan on doing a factory reset. But, you also cant do a factory reset if you have removed or renamed apps so I feel that should be mentioned. If you've done any modding and you are planning on upgrading, your best bet is to always use the SBF anyway. I dont think birdman realizes the panic he sets in with one little tweet. Factory resets suck anyway. But then again... "you decide..."
Thanks to Jcase for giving me the original idea way back when. I just basically applied his Eris Market Fix to work with our phones.
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Found a fix
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Zaphod-Beeblebrox said:
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Click to expand...
Click to collapse
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
elkniwcire said:
i must say i take no responsibility if this causes problems but this worked for me. Do a search in the market for "eris market fix." it was designed for the eris but works just fine on my droid x. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but i assume most everyone on froyo already is rooted.
Click to expand...
Click to collapse
yes this worked for me aswell thank you
Yes this method definitely works. I have market working now and can search for protected apps etc.
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
he was just explaining where the idea comes from i think... You'd have to be crazy to use the eris market fix app on a droidx, just simply edit the build.prop fingerprint line.
I just used the root explorer meathod and now it wont boot.
I downloaded the file.
renamed my build.prob to build.prob/bak
placed the new build.prob in the system folder
rebooted and now after the M screen it just goes to a black screen with the backlight lit. Wont boot up. Im learning adb so this may be a noob question but can I access adb if the phone wont boot all the way up. That way I could change the build.prob back
Edit Delete Post: Im just retarted haha .prop not .prob :/
Could you plz give us some details on doing this with root explorer. Thanks
Prolly simple but I did try moving current build file then renaming and pasting yours without success doing us bank search. Also rebooted cleared cache and market history prior to search. Appreciate any help with doing this via root explorer.
LexusBrian400 said:
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
Click to expand...
Click to collapse
LexusBrian400 said:
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
Click to expand...
Click to collapse
I took a brief look at each file and I really don't understand how I got into trouble. As I said, I had not yet started doing any mods, just trying to install a few apps.
While I'm no computer or phone neophyte, I don't profess to be up to speed on Android yet. I do typically read through instructions pretty well, and search out multiple sources/explanations so I have a better 'understanding' of what I'm doing, rather than just "parrotting" the steps.
Having said that, I would like to know the difference between using 'adb remount' and the instructions I used in my first post. Is that just the difference in doing this via a shell command and not? ie, they perform the same action, just from a different starting point?
As for the Eris file, I did download that and all seems to be OK right now.
Sorry ahead of time for a possibly stupid question but I just wanted to be sure. Do you have to be rooted to do this fix?
Yes, it requires an edit to a file that you can only be edited when rooted
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
This works for me...thanks!
OP has been updated with original build.prop
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
will2live said:
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
Click to expand...
Click to collapse
Just use the non-stagefright one.
Just like the post says, stagefright breaks HD video playback for SOME people. However some people dont care and just want higher quadrant scores, so they use the stagefright=true build.prop
Use the =false version for better stability.
Thanks for the reply.