Database Info

[MODS][KPU] Pack for odexed/deodexed [24/05/12]

Hey guys,
I made these flashable zips to easly get a stock, but yet powerful, ROM.
This is for odexed KPU and deodexed KPU.
If you have any suggestions, leave a message.
Why odexed? Why not.
See this if you are interested in modding odexed apks.
Here the list of mods in this pack (and "how to" if you want to port them to other firmwares): see below for the updates
Lower brightness levels [services.jar, Settings.apk, SystemUI.apk]
Lower autobrightness levels [framework-res.apk]
1% battery mod [framework-res.apk]
AOSP lockscreen without haptic feedback [android.policy.jar, framework.jar]
SMS + No contact limit + No MMS convert + Sent time [Mms.apk]
Added support for LED notifications [services.jar] (this needs CyanogenMod liblights. See below.)
More smooth scroll [framework.jar]
Extended powermenu [framework-res.apk, android.policy.jar] (only "Reboot" option)
Autobrightness doesn't work properly. Basically the sensor determines the current ambient light every Xseconds. If the value is not so different from the previous lux value, it's ignored. That's good because it prevents random brightness changes, however it works well only with the stock values, while the values I set are too close and sometimes the brightness is "stuck". You should do some changes to prevent this: [1], [2]
FYI: the values I set are not that good. If anyone is interested and know how to change them, here is what I'm using now:
Code:
<integer-array name="config_autoBrightnessLevels">
<item>6</item>
<item>22</item>
<item>110</item>
<item>432</item>
<item>684</item>
<item>2780</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>3</item>
<item>20</item>
<item>35</item>
<item>50</item>
<item>110</item>
<item>180</item>
<item>255</item>
</integer-array>
Note: Clear data for Messaging under Settings->Applications->Manage Applications (it won't delete your messages) to make the changes effective. The stock app can only save one date (sent or received), if you need both of them use another app.
Click to expand...
Click to collapse
I changed few things in the theme (I took some images from CyanogenMod 7).
If you don't like some images, see the last part of this post. (I also wrote why I can't add swipe to remove notifications)
No additional apps included, no apps removed, no data wipes, no kernel included, no tweaks.
Downloads:
odexed
KPU-mods-pack.zip
Restore: restore-KPU.zip
deodexed
KPU-mods-pack-deodex.zip
Restore: KPU-restore-deodex.zip
__________________________________
Extended powermenu with Screenshot option - thanks to cybert and for this.
[android.policy.jar, framework-res.apk]
odexed: extended-screenshot.zip
deodexed: extended-screenshot-deodexed.zip
__________________________________
CRT off effect: (enable animations: Settings->Display->Animation)
[framework-res.apk]
odexed/deodexed: crt-off-effect.zip [framework-res.apk]
__________________________________
Incoming Call Ringtone Flip to Mute (thanks to dhiru1602) + No increasing ring (thanks to YG007)
[Phone.apk]
odexed
flip-no-increasing.zip
Restore: flip-no-increasing-restore.zip
deodexed
flip-no-increasing-deodexed.zip
Restore: flip-no-increasing-deodexed-restore.zip
dhiru1602 said:
Sensor Usage
You might notice some Sensor Usage for Phone app. This is quite normal because the Sensors are used to check the Orientation of the phone. This would last only for the duration of the Call Ring. I have checked to see if the sensors are being stopped and It seems to work fine. Let me know if there are any issues, because if there is any issue with the sensors, it might lead to a battery drain.
Click to expand...
Click to collapse
dhiru1602 said:
Note: I have configured the sensor settings to be effective only when the phone is resting on a flat surface with the screen upwards. I have found that this type of configuration is required to prevent issues with phone going mute accidentally when its in your pocket and you receive a call. Unfortunately, I don't receive many calls to practically test it for accuracy. Hope it serves the purpose.
Click to expand...
Click to collapse
__________________________________
Toggle buttons shortcut: thanks to M_J_Nazari and _JKay_ for this.
If you longpress on a toggle button in the notification bar, you'll get to the respective setting page. [SystemUI.apk]
odexed: systemui-shortcut.zip
deodexed: systemui-shortcut-deodexed.zip
Flash the pack to restore the original file
__________________________________
6 Toggle buttons: http://forum.xda-developers.com/showpost.php?p=26461422&postcount=48
__________________________________
Additional zips:
(these should work on every stock rom)
Disable TouchWiz sounds
Sounds disabled: low battery, charger/usb plugged in, battery charged + boot sound (it simply renames some audio files in /system/media/audio/ui/ and /system/etc/):
disable-sounds.zip
Restore: enable-sounds.zip
disable-boot-sound.zip
Restore: enable-boot-sound.zip
Chainfire touchscreen tweaks
More info here. Probably you won't feel any difference
touchscreen-init.d.zip
Restore: remove-touchscreen-init.d.zip (or simply delete /etc/init.d/10touchscreen)
Button LED notifications
More info here. There's no need to use Lightflow, unless you need missed call notifications (Lightflow takes the control of your LEDs, so it's possible that some apps that natively supports LED notifications won't be able to use them).
You need to do a change in the kernel to fully support this feature.
liblights.zip
Restore: restore-liblights.zip
If you want to convert the partitions in ext4, use CF-Root-ext4-v1.3u1-Addon.apk. You can get it from here.
You can easly convert from and to RFS and check filesystem integrity.
IMPORTANT: Make sure you have at least 10MB of free space in /system before the conversion (you can see the amount of free space from ext4 Manager [CF-Root-ext4-v1.3u1-Addon.apk]), otherwise the conversion will fail, but there's no problem, the addon will automatically convert /system in RFS and restore all the files (the other partitions will be converted in ext4).
Click to expand...
Click to collapse

At this pace no one can stop you . Keep going and keep modding

Your the best modder i've seen so far... Thank you for sharing your mods with the Galaxy SL community...
With you skills maybe you can help porting CM9...

cool, may I only port mms.apk to phone (XXKPU) instead of all?
Additional note : when extract file using 7zip found Mms.odex file inside, do require that file to park in /system/app?
Thanks in advance.

u are an assett to this devise..!
i wud love to learn things from u..!!! and i will catch u for sure...dis is ideal.. odex=faster and that too with mods.. stock+fast..
no mods is the only thing dat deterred me from going to kpu.. i will make the leap now..
awwsome work brother..

The most usefull mod i've seen round here in months...clean without useless options. How about a flip to mute mod? Thank you.

calvinljh said:
cool, may I only port mms.apk to phone (XXKPU) instead of all?
Click to expand...
Click to collapse
Yes
calvinljh said:
Additional note : when extract file using 7zip found Mms.odex file inside, do require that file to park in /system/app?
Click to expand...
Click to collapse
Yes
klau7 said:
The most usefull mod i've seen round here in months...clean without useless options. How about a flip to mute mod? Thank you.
Click to expand...
Click to collapse
I don't know, if it's easy to do, I could do it, but I first need to see what are the changes needed.
Anyway I think you can use system deodexed app, even if your rom is odexed. You simply need to remove from /system/app both the .apk and the .odex files and replace them with the single .apk file. This is not a general rule, you can't replace all the odexed apks, and I'm not a 100% sure that a modded deodexed phone.apk will work (that's the apk you need to mod for "flip to mute").
You can try and if something goes wrong, you can always restore everything with a nandroid backup.

loSconosciuto said:
Yes
Yes
I don't know, if it's easy to do, I could do it, but I first need to see what are the changes needed.
Anyway I think you can use system deodexed app, even if your rom is odexed. You simply need to remove from /system/app both the .apk and the .odex files and replace them with the single .apk file. This is not a general rule, you can't replace all the odexed apks, and I'm not a 100% sure that a modded deodexed phone.apk will work (that's the apk you need to mod for "flip to mute").
You can try and if something goes wrong, you can always restore everything with a nandroid backup.
Click to expand...
Click to collapse
Hi bro, thanks with info, tried also with Odex file /system/app/ no working at all.

Mms.apk no limit doesn't work.
Sent from my Supercharged GT-I9003 with Beats Audio & Xloud

calvinljh said:
Hi bro, thanks with info, tried also with Odex file /system/app/ no working at all.
Click to expand...
Click to collapse
calvinljh said:
when extract file using 7zip found Mms.odex file inside, do require that file to park in /system/app?
Click to expand...
Click to collapse
Should I read the underlined part as "... found Mms.odex and my rom is deodexed ..."?
Use this (you don't have to use the .odex file): Mms.apk
erik07 said:
Mms.apk no limit doesn't work.
Click to expand...
Click to collapse
Sorry, I forgot to add this in the OP:
If it doesn't work, clear the cache, the Dalvik cache, and also clear data for Messaging under Settings->Applications->Manage Applications (it won't delete your messages).
Click to expand...
Click to collapse
Actually, you only need to clear data for Messaging, there's no need to clear the cache and the Dalvik cache.
http://forum.xda-developers.com/showthread.php?t=1065452

Do u think it is better a odexed system or a deodexed one? What are the advantages?

luiseteyo said:
Do u think it is better a odexed system or a deodexed one? What are the advantages?
Click to expand...
Click to collapse
The problem of an odexed rom is that modding, as you probably know, is harder and some mods don't work, unless you reodex the whole rom (there are some scripts here on xda that does it for you, but doing so you can't use your modded files on a stock rom, they'll only work in your reodexed rom).
The main difference is that Android doesn't have to generate .dex files for odexed apks/jars (no .dex files in /data/dalvik-cache/ for them"). This brings, as far as I know, these advantages:
The first boot requires less time (Android has to build .dex files only for apps in /data)
/system is a read-only partition, so it's really hard to corrupt odex files, while it's possible to have a corrupted Dalvik cache (I don't think this is a common issue, it never happened to me). This can also gives problems when you flash a zip because the .dex file made before the flash doesn't work with the new apk, but all these issues can be solved with a Dalvik cache wipe (=> point 1).
An odexed rom requires less space in /data (again, see point 1), but it also true that it uses more space in /system (deodexed apk size < odexed apk + odex size), but, as I said, /system is a read-only partition, so there's no need to have free space there.
But I really don't know if there's any difference in the performance of your rom.
I'm using an odexed rom because that's how it was when I flashed it. Plus I don't have any problem in modding odexed apk, I even made a shell script that helps me in that (maybe I'll release it, I have to clean the code first), so I had no reason to deodex my rom (the few mods I use are made by myself ).

Is it possible that you'll use these mod on a deodexed rom...? Or would it have conflicts...?

landono5 said:
Is it possible that you'll use these mod on a deodexed rom...? Or would it have conflicts...?
Click to expand...
Click to collapse
No, odexed apps can't be used in deodexed rom.
You should use this on a deodexed KPU
I think this is the right one, but I can't test it.
And you if you want to restore the original files you should use this
(to make an odexed apk you need to deodex it first, I already had these files)

good mods mate keep it up
Sent from my GT-I9003 using XDA

i know this sounds very noob but really wants to know this.if i use odexed rom,may i be able to delete samsung bloatware in /system/apps safely?

rarap said:
i know this sounds very noob but really wants to know this.if i use odexed rom,may i be able to delete samsung bloatware in /system/apps safely?
Click to expand...
Click to collapse
Yes. You can. But in this case you have to remove 2 files: application and odexed resources (they will lie in the same directory.
Отправлено с моего GT-I9003

than'k u sir'...

loSconosciuto said:
Hey guys,
I wanted to share these flashables zips to easly get a fast but yet powerful stock rom.
This is for odexed KPU
UPDATE: and deodexed KPU.
Here the list of mods in this pack (and "how to" if you want to port them to other firmwares):
Lower brightness levels [services.jar, Settings.apk, SystemUI.apk]
Lower autobrightness levels [framework-res.apk]
1% battery mod [framework-res.apk]
AOSP lockscreen without haptic feedback [android.policy.jar, framework.jar]
SMS + No contact limit + No MMS convert + Sent time [Mms.apk]
Added support for LED notifications [services.jar] (this needs CyanogenMod liblights. See below.)
More smooth scroll [framework.jar]
Extended powermenu [framework-res.apk, android.policy.jar] (only "Reboot" option)
There's no CRT off effect (maybe I'll provide an additional zip if someone wants it, it's easy to add)
I changed few things in the theme (I took some images from CyanogenMod 7).
No additional apps included, no apps removed, no data wipes, no kernel included, no tweaks.
Note:
Clear data for Messaging under Settings->Applications->Manage Applications (it won't delete your messages).
Downloads:
odexed
KPU-mods-pack.zip
restore-KPU.zip (use this to restore everything)
deodexed
(I didn't post it before simply because it overwrites most of the mods out there):
KPU-mods-pack-deodex.zip (not tested)
KPU-restore-deodex.zip
Additional zips:
Disable TouchWiz sounds
Sounds disabled: low battery, charger/usb plugged in, battery charged + boot sound (it simply renames some audio files in /system/media/audio/ui/ and /system/etc/):
disable-sounds.zip
enable-sounds.zip
disable-boot-sound.zip
enable-boot-sound.zip
Chainfire touchscreen tweaks
More info here. Probably you won't feel any difference
touchscreen-init.d.zip
remove-touchscreen-init.d
Button Led notifications
More info here. There's no need to use Lightflow, unless you need missed call notifications (Lightflow takes the control of your leds, so it's possible that some apps that natively supports LED notifications won't be able to use them).
With Lightflow you can't really control LEDs (we are still looking for a solution).
liblights.zip
restore-liblights.zip
If you want to convert the partitions in EXT4, use CF-Root-ext4-v1.3u1-Addon.apk. You can get it from here.
You can easly convert from and to RFS and check filesystem integrity.
IMPORTANT: Make sure you have more or less 10MB of free space in /system before the conversion (you can see the amount of free space from ext4 Manager [CF-Root-ext4-v1.3u1-Addon.apk]), otherwise the conversion will fail, but there's no problem, this addon is really well done and it will automatically restore everything.
Click to expand...
Click to collapse
will this work on deodexed KPQ? wanna try this out

Maybe, but if I were you, I wouldn't flash it.
This pack will replace a lot of framework files, that means you'll have an hybrid KPQ-KPU rom.
Probably all the mods here included exist for KPQ (it was and maybe it's still the most used rom), just look for them.
You can use all the additional zips, they are not rom specific.
PS: there's no need to quote the OP.

[TWEAK] kuro tweak for ICS

Yaa...I know. you can find a lot of tweak in this forum. I just want to share the tweak I've made for you. this tweak is an enhanced version this old tweak http://forum.xda-developers.com/showthread.php?t=1714217. that tweak is for GB. I'm not recommend you to install that stuff to your system. if you're using ICS device, especially Xperia one, you can use this tweak instead.
all the files could be downloaded here:
v_0.1 : http://www.mediafire.com/?c4ua4cwwd0e774j
v_0.2 : http://www.mediafire.com/download.php?9ua4lz8wafqq79w
v_0.2.1 : http://www.mediafire.com/download.php?2bqcgbkt01banl6
(this latest update only contain add blocker tweak. you need to copy the hosts file into /system/etc to install it.)
sorry, no flashablel zip file yet, since we don't have working cwm at this moment.
PRE-REQUIREMENTS
1. rooted device
2. init.d support system
3. busybox with symlink installed
if you don't have a rom with init.d support, you can made it by yourself. simply create file named "install-recovery.sh" in /etc. and put these stuff inside that file
Code:
#!/system/bin/sh
# init.d activation script
busybox run-parts /system/etc/init.d/
to test your init.d script you can made a simple script in init.d contain
Code:
#!/system/bin/sh
# test code
touch /data/tes_kucing.log
echo "kucing meong" > /data/tes_kucing.log
if it succes, you'll find tes_kucing.log in /data after you reboot your device.
WHAT INSIDE IT?
this tweak consist of several parts.
1. kuro1 tweak - system tweak
2. kuro2 tweak - prop tweak
3. kuro4 tweak - sound enhancement
4. local.prop tweak
5. zipalign tweak
all the details about the tweak is already inside the tweak files.
HOW TO INSTALL
simply copy all files into their respective folders and give them rwxrwxrwx permission. after that type these command in your terminal
Code:
su
rm /data/dalvik-cache/*
reboot
after boot, check /data and see if you could find all the log files. if you got any problem, you can report here and show me the log files.
CHANGELOG:
v_0.2.1 (2-1-12):
- add blocker.
- this is a little addition for v_0.2. you need to install v_0.2 then copy hosts file to /system/etc to use the complete tweak.
v_0.2 (9-12-12) :
- new optimized script
- auto root for blast tool. no need to type su. just type "blast" in your terminal and the script will run with root permission
v_0.1 :
- initial public release
Click to expand...
Click to collapse
TERM OF USE AND SHARING:
this thread intent is for sharing. feel free to use, edit, distribute all material inside this thread which came from me. if there any parts of this mod which comes not from me please refer to the original dev I've mentioned in this thread. if want to share it to another forum or modify it you don't have to ask my permission. no need to credits, put links or whatsoever. you'll only need to remember that you should held all the responsibility by using this mod, modify it or distribute it. DO IT WITH YOUR OWN RISK
Click to expand...
Click to collapse

SPECIAL FEATURE
this tweak pack has special feature to clear up your memory so that you'll have more space to run app or run heavy app like games. in your terminal type
Code:
su
blast
a script will run and your memory will freed up. all the information about the memory you can get in your screen.
EDIT: if you're using the new version you only need to type 'blast' in your terminal.

GPS tweak
this tweak will make your gps acquire your postition relatively faster. to install it simply replace your gps.conf with this one and reboot. http://www.mediafire.com/download.php?vdkrzx55qkzqn27
please note that this gps.conf file is optimized for indonesian region. I'll show you which part I modified from the original one so that you can optimize your gps according to your country.
Code:
# more ntp server
NTP_SERVER=id.pool.ntp.org
# the line above is the ntp server for indonesia. you can replace it with your region id. the form will be <country code>.pool.ntp.org
NTP_SERVER=asia.pool.ntp.org
NTP_SERVER=europe.pool.ntp.org
NTP_SERVER=africa.pool.ntp.org
NTP_SERVER=north-america.pool.ntp.org
NTP_SERVER=south-america.pool.ntp.org
NTP_SERVER=oceania.ntp.org]
I also modify this part
Code:
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=1
# that line above is to enable intermediate position report. less accurate but faster gps lock
# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
# orig 5000
ACCURACY_THRES=100
# this line define the accuracy threshold if you activate intermediate position. If I'm mistaken the value is written in meter. less number means more accurate position, longer gps lock. while higher number means faster gps lock but less accurate position. you can modify this value on your own.

can you make a flashable since we have recovery for a few days now? im gonna test if it works.

Until there's update for this stuff there won't be any flashable zip. I know, its not convenience to copy the files one by one but I need to make sure the filesgot copied into system. Last time I checked into cwm thread there's a report about problem when install a flashable zip.

smokerman said:
can you make a flashable since we have recovery for a few days now? im gonna test if it works.
Click to expand...
Click to collapse
If you want tweaks...
Just visit the super thread for tweaks
http://forum.xda-developers.com/showthread.php?t=1908269
You can get many tweaks in flashable zip... Even bravia engine and xloud
Sent via 'rooted' BEETEL landline

thread updated with a lil new optimized tweak

thread updated with gps tweak as I've promised. check post 3#

3. kuro4 tweak - sound enhancement
Click to expand...
Click to collapse
Does that affect headphones volume which is not the best on stock? I'm sure the headphones volume is limited on purpose and I'm looking to boost it up since none of the Google Play volume boosting apps work on ICS and above.

i'm afraid not. the sound enhancement tweak is used to enhance the sound clarity, not the headphone volume. if you want a louder volume on your headphone you can try using eq app like the one in my beat bass app thread. try the latest one.

thread updated with add blocker tweak.

Nice work........

thanks for the mod... working fine on J .75 firmware . Ah, can you tell me how to enable boot animation. __

Goto /data/local.prop delete debug.sf.nobootanimation or change the value to zero

Not working for my Xperia Miro, phone stuck at Battery status after reboot.
Also cant find my region code for GPS tweak I am from and in Bulgaria.
Thanks

battery status? are you using cm10? which version of it?

Could you make this for flash gordon?
Sent from my ST26i using xda app-developers app

pardon me? what do you mean with flash gordon?

kurotsugi said:
battery status? are you using cm10? which version of it?
Click to expand...
Click to collapse
CM 10 FXP 220, just before enter the system there si battery status for JB 4.1 and my phone stuck there.
Also where to find my region code, I mean I am from, BUlgaria, but dont know is it "bul" or "bg" or someth. for the GPS tweak.

kurotsugi said:
pardon me? what do you mean with flash gordon?
Click to expand...
Click to collapse
Its an application That fakes recovery for xperia j and other phones without cwm. U can flash zips with it
Sent from my ST26i using xda app-developers app

[Q] dialer overlap(dpi change)

recently i have updated my phone to 4.2.2(dark nexus). all working finw without bugs . but the dailer is overlapping . if i change dpi also not working . can anyone helpme out of this

Hey, Bro,
I'm using the same ROM but My dialer is fine!
See the screenshot!
Just modified default density from 210 to 188!

???
sierrarohan said:
Hey, Bro,
I'm using the same ROM but My dialer is fine!
See the screenshot!
Just modified default density from 210 to 188!
Click to expand...
Click to collapse
how did u change ??? what app u used

balaaje said:
how did u change ??? what app u used
Click to expand...
Click to collapse
I used Root Explorer to edit the build.prop's last line.
Default density was 210, I changed it to 188.
Remember, latest Kernel patch restores Original Density.
So, If you want, I can give you step by step instructions.

thanks
sierrarohan said:
I used Root Explorer to edit the build.prop's last line.
Default density was 210, I changed it to 188.
Remember, latest Kernel patch restores Original Density.
So, If you want, I can give you step by step instructions.
Click to expand...
Click to collapse
thanks iam done . thanks for the quick reply

My pleasure dude!!
Dont forget to hit Thanks Button!!

bug found. pls help
sierrarohan said:
My pleasure dude!!
Dont forget to hit Thanks Button!!
Click to expand...
Click to collapse
bro i also on dark nexus rom. in my phone its not showing any gallery items and music items. i dunno what to do. pls help.. :crying:

PingPongLee94 said:
bro i also on dark nexus rom. in my phone its not showing any gallery items and music items. i dunno what to do. pls help.. :crying:
Click to expand...
Click to collapse
First clear mediastorage app data from settings and then reboot
Sent From The Phone That Can™

Density Changed
I Have also dialer problem.. so please help step by step how to changed density...

Dude, for gallery and music items to show, you have to wait for a while.
And regarding density, follow these steps:
1.Download and Install Root Explorer Or your favorite app which can access system files.
2. Go to Root/System and Mount it R/W (Rewritable)
3. Open build.prop file using text editor.
4.Scroll to last line of the file, if there is a line like 'ro.sf.lcd_density=<value>' then alter '<value>' to your suitable DPI (I'm Using 188 DPI). If there is no line like above, then simply add one.
5. Save the file and 'Normal Reboot' your handset.
6.Voila!
Or, You can download ROM toolbox and use the build.prop editor to do the same!!

Dialer problem solve
sierrarohan said:
Dude, for gallery and music items to show, you have to wait for a while.
And regarding density, follow these steps:
1.Download and Install Root Explorer Or your favorite app which can access system files.
2. Go to Root/System and Mount it R/W (Rewritable)
3. Open build.prop file using text editor.
4.Scroll to last line of the file, if there is a line like 'ro.sf.lcd_density=<value>' then alter '<value>' to your suitable DPI (I'm Using 188 DPI). If there is no line like above, then simply add one.
5. Save the file and 'Normal Reboot' your handset.
6.Voila!
Or, You can download ROM toolbox and use the build.prop editor to do the same!!
Click to expand...
Click to collapse
Thanks Buddy, i have no line in build.prop... so i write new line with 210 dpi... now it's working..
thnks once again

riki1811 said:
Thanks Buddy, i have no line in build.prop... so i write new line with 210 dpi... now it's working..
thnks once again
Click to expand...
Click to collapse
Good to know!
Dont forget to hit thanx button!!

build.prop (4.4.2)

1) root explorer/system/build.prop
2) open build.prop in text editor PC
3) edit PC notepad++
ro.product.name=ms013gxx *** ro.product.name=SM-G900F
ro.product.device=ms013g *** ro.product.device=SM-G900F
YouTube http://youtu.be/kQYg7oQ1H98?list=UU_PZh6wWX-dmHS_Le56DS0g

How can a bulid.prop change, change the system ui looks??

unkown rockstar said:
How can a bulid.prop change, change the system ui looks??
Click to expand...
Click to collapse
changes in systemUI S5

unkown rockstar said:
How can a bulid.prop change, change the system ui looks??
Click to expand...
Click to collapse
A famous built-in hack by Samsung, done for all 2013 devices that run KitKat.

i knew build.prop can change device no and stuff but never knew this

Tried editing build. Prop nt worked?? Getting same what was before?? [emoji27]

unkown rockstar said:
Tried editing build. Prop nt worked?? Getting same what was before?? [emoji27]
Click to expand...
Click to collapse
you can edit build.prop (4.4.2)
ro.product.model=SM-N910S
ro.product.name= SM-N910S
ro.product.device= SM-N910S
and go to samsung apps and you can install apps for note 4 (not all applications work)
Kids Mode http://youtu.be/yegXwdWjpjk

unkown rockstar said:
Tried editing build. Prop nt worked?? Getting same what was before?? [emoji27]
Click to expand...
Click to collapse
it works for me after changing the build.prop restart the phone you will notice the changes..
note:after editing the build.prop save it in device/system delete the old one build.prop & provide the appropriate permissions "-rw-r-r"

effect lock screen 4.4.2
1) SQLite Editor(root)
2) Settings storage
3) settings.db
4) system
5) lockscreen_ripple_effect
6) effect 3,effect 4,effect 5,effect 6,effect 7
if you restart the phone, the effect disappears
instruction http://youtu.be/T1gFR9sOcXo
7) effect 6,7 work after reboot phone
enjoy

Cool trick bro ..is there any other trick like this ?

SFinder + QuickConnect
17 ro.product.name=kltexx
18 ro.product.device=klte

How about a build.prop thread?

I'm used to only having one build.prop file to edit; on the SHT-AL09 there are three build.prop files - there's a system/build.prop, a vendor/build.prop, system/vendor/build.prop. The system/build.prop file is different/smaller than the other two files, one of which I presume is a vendor supplied backup.
Please excuse me if this is a stupid question - but which file(s) need to be edited to successfully implement build.prop tweaks?
Also, build.prop permissions are traditionally set to 644. However, out of the box, our build.prop permissions appear to be set to 600.
This thread can also serve as a place to share build.prop tweaks that are confirmed to not result in bootloops. Personally, I am looking forward to increasing sling velocity.

I guess build.prop tweaks are a thing of the past?
I figured out that the system/vendor/ folder is the same as the root/vendor/ folder; change a file in one and it is changed in the other as well. I have also confirmed that editing either the build.prop or default.prop files in the vendor folder affects system config. In the default.prop folder I changed the value for 'qemu.hw.mainkeys,' and afterward Nova Launcher was suddenly unable to turn the color of the text in my status bar to a dark color.
I don't plan on playing around much until we have a working recovery, but so far I have edited the following existing lines in my build.prop file:
dalvik.vm.heapsize=700m
dalvik.vm.heapstartsize=35m
dalvik.vm.heapgrowthlimit=140m
dalvik.vm.heaptargetutilization=0.72
dalvik.vm.heapmaxfree=15m
And have added the following lines:
net.tethering.noprovisioning=true
ro.config.nocheckin=1
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.hspa=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.lte=524288,1048576,2097152,524288,1048576,2097152
net.tcp.buffersize.hspda=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.evdo_b=6144,87380,1048576,6144,87380,1048576
windowsmgr.max_events_per_sec=90
I couldn't say for sure that I have seen an improvement, but I think I've seen some improvement in overall stability/multi-tasking. At least, there have been no ill effects. I am also getting better data speeds in certain parts of town via T-Mo - but that could be random or related to experimentation with my APN.
Also...VOLTE is enabled by default in the stock build.prop - unfortunately it is a known issue that Huawei phones don't get VOLTE on T-Mo (in the US) unless they have US firmware.

thref23 said:
I guess build.prop tweaks are a thing of the past?
I figured out that the system/vendor/ folder is the same as the root/vendor/ folder; change a file in one and it is changed in the other as well. I have also confirmed that editing either the build.prop or default.prop files in the vendor folder affects system config. In the default.prop folder I changed the value for 'qemu.hw.mainkeys,' and afterward Nova Launcher was suddenly unable to turn the color of the text in my status bar to a dark color.
I don't plan on playing around much until we have a working recovery, but so far I have edited the following existing lines in my build.prop file:
dalvik.vm.heapsize=700m
dalvik.vm.heapstartsize=35m
dalvik.vm.heapgrowthlimit=140m
dalvik.vm.heaptargetutilization=0.72
dalvik.vm.heapmaxfree=15m
And have added the following lines:
net.tethering.noprovisioning=true
ro.config.nocheckin=1
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.hspa=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.lte=524288,1048576,2097152,524288,1048576,2097152
net.tcp.buffersize.hspda=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.evdo_b=6144,87380,1048576,6144,87380,1048576
windowsmgr.max_events_per_sec=90
I couldn't say for sure that I have seen an improvement, but I think I've seen some improvement in overall stability/multi-tasking. At least, there have been no ill effects. I am also getting better data speeds in certain parts of town via T-Mo - but that could be random or related to experimentation with my APN.
Also...VOLTE is enabled by default in the stock build.prop - unfortunately it is a known issue that Huawei phones don't get VOLTE on T-Mo (in the US) unless they have US firmware.
Click to expand...
Click to collapse
You mean you added and edited these lines in the vendor build.prop right?
The I can't mod the system build.prop, after every restate it restores the old one. What can I do about it?

Marcopoloy13 said:
You mean you added and edited these lines in the vendor build.prop right?
The I can't mod the system build.prop, after every restate it restores the old one. What can I do about it?
Click to expand...
Click to collapse
I think the system/build.prop is rewritten according to the vendor/build.prop at boot. I'm not sure. You don't have to do anything about it - just edit the vendor file instead of the system file.
Be careful with heapsize values. I pushed the dalvik.vm.heapsize to 900m, with .6 heaptargetutilization - and it bootlooped me. I had tested those values on my Sony Z3TC first and they worked...
Don't know exactly what difference it makes, but I am currently using:
dalvik.vm.heapsize=720m
dalvik.vm.heapstartsize=36m
dalvik.vm.heapgrowthlimit=144m
dalvik.vm.heaptargetutilization=0.67

thref23 said:
I think the system/build.prop is rewritten according to the vendor/build.prop at boot. I'm not sure. You don't have to do anything about it - just edit the vendor file instead of the system file.
Be careful with heapsize values. I pushed the dalvik.vm.heapsize to 900m, with .6 heaptargetutilization - and it bootlooped me. I had tested those values on my Sony Z3TC first and they worked...
Don't know exactly what difference it makes, but I am currently using:
dalvik.vm.heapsize=720m
dalvik.vm.heapstartsize=36m
dalvik.vm.heapgrowthlimit=144m
dalvik.vm.heaptargetutilization=0.67
Click to expand...
Click to collapse
I don't think that the vendor and system ones are the same or will be generated from it, there are not the same, things like dalvik.vm.heapgrowthlimit isn't in the system one just in vendor.
I have instead an GSI, so there are very different .
For Example on the system one it says the right security patch and release (8.1.0 - 2018-07-05) while on the vendor one it is still the values from the EMUI Rom (8.0 - 2018-06-01)
So there must be a way to mod the system build.prop, the MagiskHide Props Config Module runs a script on startup to modify the fingerprint, but I don't know how to modify more that this with this module or write my own script.