Database Develop

Problem while deodexing

Hey guys! I've recently tried to deodex my ROM but when I flash the deodex files the phone won't boot. It just keeps on the "GALAXY Ace" screen and stays there. I've tried everything: re-deodex, new kernel, wipe data, cache, dalvik... and nothing.
What am I doing wrong?
This is my updater-script:
Code:
assert(getprop("ro.product.device") == "GT-S5830L" ||
getprop("ro.product.board") == "GT-S5830L" ||
getprop("ro.build.product") == "GT-S5830L" ||
getprop("ro.product.device") == "GT-S5830B" ||
getprop("ro.product.board") == "GT-S5830B" ||
getprop("ro.build.product") == "GT-S5830B" ||
getprop("ro.product.device") == "GT-S5830T" ||
getprop("ro.product.board") == "GT-S5830T" ||
getprop("ro.build.product") == "GT-S5830T" ||
getprop("ro.product.device") == "GT-S5830" ||
getprop("ro.product.board") == "GT-S5830" ||
getprop("ro.build.product") == "GT-S5830" ||
getprop("ro.product.model") == "GT-S5830" ||
getprop("ro.product.device") == "cooper" ||
getprop("ro.product.board") == "cooper" ||
getprop("ro.build.product") == "cooper"
);
show_progress(0.1, 0);
package_extract_file("format.sh", "/tmp/format.sh");
package_extract_file("mkfs.ext4", "/tmp/mkfs.ext4");
set_perm(0, 0, 0755, "/tmp/format.sh");
set_perm(0, 0, 0755, "/tmp/mkfs.ext4");
run_program("/tmp/format.sh");
delete("/tmp/format.sh");
delete("/tmp/mkfs.ext4");
mount("ext4", "EMMC", "/dev/block/stl12", "/system");
mount("ext4", "EMMC", "/dev/block/stl13", "/data");
package_extract_dir("system", "/system");
symlink("toolbox", "/system/bin/cat");
symlink("toolbox", "/system/bin/chmod");
symlink("toolbox", "/system/bin/chown");
symlink("toolbox", "/system/bin/cmp");
symlink("toolbox", "/system/bin/date");
symlink("toolbox", "/system/bin/dd");
symlink("toolbox", "/system/bin/df");
symlink("toolbox", "/system/bin/dmesg");
symlink("toolbox", "/system/bin/getevent");
symlink("toolbox", "/system/bin/getprop");
symlink("toolbox", "/system/bin/hd");
symlink("toolbox", "/system/bin/id");
symlink("toolbox", "/system/bin/ifconfig");
symlink("toolbox", "/system/bin/iftop");
symlink("toolbox", "/system/bin/insmod");
symlink("toolbox", "/system/bin/ioctl");
symlink("toolbox", "/system/bin/ionice");
symlink("toolbox", "/system/bin/kill");
symlink("toolbox", "/system/bin/ln");
symlink("toolbox", "/system/bin/log");
symlink("toolbox", "/system/bin/ls");
symlink("toolbox", "/system/bin/lsmod");
symlink("toolbox", "/system/bin/lsof");
symlink("toolbox", "/system/bin/mkdir");
symlink("toolbox", "/system/bin/mount");
symlink("toolbox", "/system/bin/mv");
symlink("toolbox", "/system/bin/nandread");
symlink("toolbox", "/system/bin/netstat");
symlink("toolbox", "/system/bin/newfs_msdos");
symlink("toolbox", "/system/bin/notify");
symlink("toolbox", "/system/bin/printenv");
symlink("toolbox", "/system/bin/ps");
symlink("toolbox", "/system/bin/reboot");
symlink("toolbox", "/system/bin/renice");
symlink("toolbox", "/system/bin/rm");
symlink("toolbox", "/system/bin/rmdir");
symlink("toolbox", "/system/bin/rmmod");
symlink("toolbox", "/system/bin/route");
symlink("toolbox", "/system/bin/schedtop");
symlink("toolbox", "/system/bin/sendevent");
symlink("toolbox", "/system/bin/setconsole");
symlink("toolbox", "/system/bin/setprop");
symlink("toolbox", "/system/bin/sleep");
symlink("toolbox", "/system/bin/smd");
symlink("toolbox", "/system/bin/start");
symlink("toolbox", "/system/bin/stop");
symlink("toolbox", "/system/bin/sync");
symlink("toolbox", "/system/bin/top");
symlink("toolbox", "/system/bin/umount");
symlink("toolbox", "/system/bin/uptime");
symlink("toolbox", "/system/bin/vmstat");
symlink("toolbox", "/system/bin/watchprops");
symlink("toolbox", "/system/bin/wipe");
symlink("dumpstate", "/system/bin/dumpcrash");
symlink("dumpstate", "/system/bin/dumpmesg");
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
set_perm(0, 3003, 06755, "/system/bin/ip");
set_perm(0, 3003, 02750, "/system/bin/netcfg");
set_perm(0, 3004, 02755, "/system/bin/ping");
set_perm(0, 2000, 06750, "/system/bin/run-as");
set_perm_recursive(1002, 1002, 0755, 0440, "/system/etc/bluetooth");
set_perm(0, 0, 0755, "/system/etc/bluetooth");
set_perm(1000, 1000, 0640, "/system/etc/bluetooth/auto_pairing.conf");
set_perm(3002, 3002, 0444, "/system/etc/bluetooth/blacklist.conf");
set_perm(1002, 1002, 0440, "/system/etc/dbus.conf");
set_perm(1014, 2000, 0550, "/system/etc/dhcpcd/dhcpcd-run-hooks");
set_perm(0, 2000, 0550, "/system/etc/init.goldfish.sh");
set_perm_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
set_perm_recursive(0, 0, 0777, 0777, "/system/etc/init.d");
set_perm(0, 0, 06755, "/system/xbin/su");
set_perm(0, 0, 04755, "/system/xbin/sqlite3");
set_perm(0, 0, 04755, "/system/xbin/su-v1");
set_perm(0, 0, 04755, "/system/xbin/su-v2");
set_perm(0, 0, 04755, "/system/xbin/su-v3");
set_perm(0, 0, 04755, "/system/xbin/sh");
set_perm(0, 0, 04755, "/system/xbin/busybox");
show_progress(0.1, 10);
show_progress(0.2, 0);
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
show_progress(0.2, 10);
unmount("/system");
unmount("/data");
ui_print("Done!");
Thanks!
Btw, the ROM is the latest XWKTM, from Spain, with Brazilian modem.

Logcat?
Any mods done to framework?
Sent from my GT-S5830 using xda premium

I would recommend u to switch over to a custom rom..they pre deodexed amd better...try stocklite if u wish too...i cant help in this de odexing stuff but its a wise tip indeed
Sent from my GT-S5830 using xda premium

Did you use xUltimate?
xUltimate is easier to use. xUltimate deodexes the apps and frameworks and outputs them! All you need to do is format /system/app and /system/framework and push the new deodexed files with adb and chmod them to 644!

CoolCatGetHome said:
Logcat?
Any mods done to framework?
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
Don't know how to do a logcat :x sorry. I've sent my frameworks (both stock and twframework) to UOT Kitchen, for ICS animations.
Manvendra05 said:
I would recommend u to switch over to a custom rom..they pre deodexed amd better...try stocklite if u wish too...i cant help in this de odexing stuff but its a wise tip indeed
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
I've used CM7 for a long time, but it's battery drain (and lack of some stock apps, specifically Mms and Memo) are something that I can't live without, and many of the alternatives aren't as good or as simple as the stock ones.
galaxyace152 said:
Did you use xUltimate?
xUltimate is easier to use. xUltimate deodexes the apps and frameworks and outputs them! All you need to do is format /system/app and /system/framework and push the new deodexed files with adb and chmod them to 644!
Click to expand...
Click to collapse
xUltimate doesn't recognize my Java installation, no matter how much I try. This is one of the mainly reasons that I keep a second partition with Ubuntu installed, so I can use dsixda's kitchen in it. (in fact, I think I only switch to Ubuntu when I want to deodex a ROM).

Renan Lazarotto said:
Don't know how to do a logcat :x sorry. I've sent my frameworks (both stock and twframework) to UOT Kitchen, for ICS animations.
I've used CM7 for a long time, but it's battery drain (and lack of some stock apps, specifically Mms and Memo) are something that I can't live without, and many of the alternatives aren't as good or as simple as the stock ones.
xUltimate doesn't recognize my Java installation, no matter how much I try. This is one of the mainly reasons that I keep a second partition with Ubuntu installed, so I can use dsixda's kitchen in it. (in fact, I think I only switch to Ubuntu when I want to deodex a ROM).
Click to expand...
Click to collapse
Have you specified Java in your environment path ?
"Friends forever." - Ventus

CallMeVentus said:
Have you specified Java in your environment path ?
"Friends forever." - Ventus
Click to expand...
Click to collapse
hm... no. but this happened before, even when I had java path specified.

Renan Lazarotto said:
hm... no. but this happened before, even when I had java path specified.
Click to expand...
Click to collapse
Java version > 6 and xultimate doesn't recognize it. Atleast in my case..
___________XDA Premium__________
Don't be a noob. Be a newbie..!!
Details here.
____________________________________

Try stocklite v7.1 it is based in stock only and has awesome battery life and features..
Sent from my GT-S5830 using xda premium

shaaan said:
Java version > 6 and xultimate doesn't recognize it. Atleast in my case..
___________XDA Premium__________
Don't be a noob. Be a newbie..!!
Details here.
____________________________________
Click to expand...
Click to collapse
Then that is the problem, I have the latest Java installed. Both JRE and JDK.
Manvendra05 said:
Try stocklite v7.1 it is based in stock only and has awesome battery life and features..
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
You really like stocklite, don't you? :laugh: I'll give it a shot.

Renan Lazarotto said:
Then that is the problem, I have the latest Java installed. Both JRE and JDK.
You really like stocklite, don't you? :laugh: I'll give it a shot.
Click to expand...
Click to collapse
Hahahaha....oh yess...u should try it...:thumbup:
Sent from my GT-S5830 using xda premium

Nice, now Java cannot be found at all. WHY it have to be Java-based??

It happens. Just go back one step and try again
___________XDA Premium__________
Don't be a noob. Be a newbie..!!
Details here.
____________________________________

shaaan said:
It happens. Just go back one step and try again
___________XDA Premium__________
Don't be a noob. Be a newbie..!!
Details here.
____________________________________
Click to expand...
Click to collapse
I did everything that I think I could. Removed all Java 7 installations, installed Java 6, set-up the environment variable (JAVA_HOME, according to the Android SDK installer), tried again, no luck. Installed Java 7, did the same, no luck again.
Gosh, I HATE Java and pretty much everything that needs this to run!

[GUIDE]How to port Cm7 roms

How to port Cm7 based roms
Guys, as i did a port of Reincarnation to s5830i, i received some PM questioning how to port. But i'll tell you, i take zero (0) credits on method. I used this: http://forum.xda-developers.com/showthread.php?t=2276871. Even so, it still needs some changes in build.prop for making the rom usable. So, i decided to make a guide about it.
Things needed:
bieltv.3 RC1 build
rom you'll port
Rom porter tool by mnishamk
Notepad++
Okay, here are the steps:
1.Enter "Start porting rom"
2.Enter "Cyanogen Based"
3.Drag the base rom (bieltv.3 RC1) and press enter
4.Drag the port rom and press enter
5.Press enter until you see "editing build.prop file"
6.Enter "GRI40"
7.Enter "GINGERBREAD"
8.Press "1" and press enter
9.Enter just numbers, with the version of your rom (like for SGS3 V5, should be entered 5.0)
10.Enter CyanogenMod version (7.2)
11.Enter "21"
12.Enter "14"
13.Enter the name of the rom
14.Wait 'til it finishes compressing
15.Close the tool.
16.Extract rom in OUTPUT folder
17.Enter build.prop
18.In build.prop, do this changes:
18a: Change every "cooper" to "cooperve"
18b: Change S5830 to S5830i
18c: Change "system.prop for XXXXX" until "ADDITIONAL_BUILD_PROPERTIES" to this:
#
# system.prop for GT-S5830i
#
# Dalvik
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.startheapsize=32m
dalvik.vm.dexopt-data-only=1
dalvik.vm.dexopt-flags=m=y
dalvik.vm.heapsize=32m
dalvik.vm.checkjni=false
dalvik.vm.execution-mode=int:jit
dalvik.vm.lockprof.threshold=500
dev.sfbootcomplete=0
# Screen Rotation
persist.sys.rotationanimation=false
# Bluetooth
net.bt.name=Android
# RIL
rild.libpath=/system/lib/libbrcm_ril.so
ro.telephony.ril_class=samsung
rild.libargs=-d /dev/smd0
DEVICE_PROVISIONED=1
ro.ril.ntmodeglobal=true
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
mobiledata.interfaces=pdp0,eth0,gprs,ppp0
ro.telephony.call_ring.delay=0
ro.ril.disable.power.collapse=0
# Display
ro.sf.lcd_density=160
qemu.sf.lcd_density=160
video.accelerate.hw=1
ro.opengles.version=131072
# Google Location
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
# Wifi interface
wifi.interface=eth0
wifi.supplicant_scan_interval=15
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
net.dns1=8.8.8.8
net.dns2=8.8.4.4
# USB / SD card
persist.service.usb.setting=0
persist.sys.vold.switchexternal=1
# Statgefright
media.stagefright.enable-player=true
ro.media.dec.jpeg.memcap=10000000
#Alsa
alsa.mixer.playback.master=Speaker
alsa.mixer.capture.master=Mic
alsa.mixer.playback.earpiece=Earpiece
alsa.mixer.capture.earpiece=Mic
alsa.mixer.playback.headset=Headset
alsa.mixer.capture.headset=Mic
alsa.mixer.playback.speaker=Speaker
alsa.mixer.capture.speaker=Mic
alsa.mixer.playback.bt.sco=BTHeadset
alsa.mixer.capture.bt.sco=BTHeadset
alsa.mixer.playback.bt.a2dp=BTHeadset
alsa.mixer.capture.bt.a2dp=BTHeadset
# Performance Tweaks
ro.compcache.default=0
persist.sys.use_dithering=0
view.fading_edge_length=8v
view.minimum_fling_velocity=25
view.scroll_friction=0.008
view.touch_slop=15 X
debug.composition.type=mdp
windowsmgr.max_events_per_sec=150
debug.performance.tuning=1
# CM parts hack
persist.sys.use_16bpp_alpha=1
persist.sys.jit-mode=int:jit
persist.sys.jit-mode=1
persist.sys.scrollingcache=3
#Tweaks
ro.setupwizard.enable_bypass=1
persist.sys.purgeable_assets=1
Click to expand...
Click to collapse
19.Change Torch.apk of the rom you ported to RC1's Torch.apk (otherwise Torch won't work)
20.Compress and test on your Ace-I
Hit thanks if i helped

Nice for noobs! Now Ace-I will be flooded with CM7.2 ROMs

Sniper Killer said:
Nice for noobs! Now Ace-I will be flooded with CM7.2 ROMs
Click to expand...
Click to collapse
It already is

Sniper Killer said:
Nice for noobs! Now Ace-I will be flooded with CM7.2 ROMs
Click to expand...
Click to collapse
iamareebjamal said:
It already is
Click to expand...
Click to collapse
It is always better to have more roms

Good guide!It would be better for porting CM7 ROM based on biel's CM RC Version.I will try porting NIghtlyfourE1 again and as Sniper said it would have a flood of CM ROM.
edit:Now NFe1 is stable.

Sniper Killer said:
Nice for noobs! Now Ace-I will be flooded with CM7.2 ROMs
Click to expand...
Click to collapse
Sniper, if this guide is followed correctly it will result in a bugless port. Having bugless cm roms is nice, right?
Sent from my GT-S5830i using xda app-developers app

Wow, thanks for this. I will try it tommorow!

Hi
ROM Ace-i-Sure 11.1 is the port?

TiTaN_88 said:
Hi
ROM Ace-i-Sure 11.1 is the port?
Click to expand...
Click to collapse
No
Care to read OP of the ROM?
If it's a port, it will be written there

TiTaN_88 said:
Hi
ROM Ace-i-Sure 11.1 is the port?
Click to expand...
Click to collapse
Hmm... please explain.

Lol I port manually, without using any additional software. Only Total Commander, Notepad++ and apktools. :laugh:

ivchek said:
Lol I port manually, without using any additional software. Only Total Commander, Notepad++ and apktools. :laugh:
Click to expand...
Click to collapse
I port that way, like i did with Miui cream and CoD rom. I used this software to port only the Reincarnation Rom. When you ported LeWa rom, did you face any trouble with phone.apk?

mathm2013 said:
When you ported LeWa rom, did you face any trouble with phone.apk?
Click to expand...
Click to collapse
Fortunately, no... I port it manually... at all users 4pda are operated manually or using almost no services, it reduces the chances for error to 1%.

ivchek said:
Fortunately, no... I port it manually... at all users 4pda are operated manually or using almost no services, it reduces the chances for error to 1%.
Click to expand...
Click to collapse
I ported manually and using software, and even so faced problems. Did you ported from cooper?

mathm2013 said:
I ported manually and using software, and even so faced problems. Did you ported from cooper?
Click to expand...
Click to collapse
Yea..Porting manually gives less errors.(Based on experience) certain phone.apks give error...Find another one from some other build.
Sent from my GT-S5830i using xda app-developers app

mathm2013 said:
I ported manually and using software, and even so faced problems. Did you ported from cooper?
Click to expand...
Click to collapse
Yes, of course, I think it is so much easier.

Manual porting could be beneficial.
Maybe you could add some lines in OP about manual porting, just a suggestion! :good:

if only we could port kernels T.T

[Q&A] [MOD][FIX] Mar. 31 | Fix Proximity Sensor on any 5.1 ROM

Q&A for [MOD][FIX] Mar. 31 | Fix Proximity Sensor on any 5.1 ROM
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [MOD][FIX] Mar. 31 | Fix Proximity Sensor on any 5.1 ROM. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Proximity Sensor
Thank you so much for this, I'm back to loving my N6. I no longer have to get in my car to use Bluetooth just to make a phone call. Donation sent.

Fix Proximity Sensor on any 5.1 ROM
Hi,
I have downloaded this ROM and when i come to look for it on NRT it cant find the file, if you could help me on this matter, it would be helpful.
Kind regards
pretesh

Hello,
The download file for the proximity fix isn't exactly a ROM itself. It is a zip file containing the necessary adjustments needed to allow the proximity sensor to function properly with a screen saver in place. Perhaps it adjusts the sensitivity level, I'm not certain. To use it requires root, and the ability to flash the zip file. I believe making a Nandroid back up, or having one available, is always recommended prior to flashing something. I download it, flashed it via TWRP, rebooted, and it has worked flawlessly all day. Hope that helps.

Please Help
I have been banging my head since the 5.1 update(Screen going blank during Call) on my Nexus 6 and then I found you. I have downloaded the file named "prox-fix-5.1.zip". I dont know how to proceed with the flashing, Since I am new to android. Can you please send in me the steps
Thanks in Advance
Anuvab
---------- Post added at 06:36 PM ---------- Previous post was at 06:30 PM ----------
dyoung33 said:
Hello,
The download file for the proximity fix isn't exactly a ROM itself. It is a zip file containing the necessary adjustments needed to allow the proximity sensor to function properly with a screen saver in place. Perhaps it adjusts the sensitivity level, I'm not certain. To use it requires root, and the ability to flash the zip file. I believe making a Nandroid back up, or having one available, is always recommended prior to flashing something. I download it, flashed it via TWRP, rebooted, and it has worked flawlessly all day. Hope that helps.
Click to expand...
Click to collapse
I have been banging my head since the 5.1 update(Screen going blank during Call) on my Nexus 6 and then I found you. I have downloaded the file named "prox-fix-5.1.zip". I dont know how to proceed with the flashing, Since I am new to android. Can you please send in me the steps
Thanks in Advance
Anuvab
---------- Post added at 06:46 PM ---------- Previous post was at 06:36 PM ----------
I have been banging my head since the 5.1 update(Screen going blank during Call) on my Nexus 6 and then I found you. I have downloaded the file named "prox-fix-5.1.zip". I dont know how to proceed with the flashing, Since I am new to android. Can you please send in me the steps
Thanks in Advance
Anuvab

Thank you. Tried this and it worked but it broke my root.

[email protected] said:
I have been banging my head since the 5.1 update(Screen going blank during Call) on my Nexus 6 and then I found you. I have downloaded the file named "prox-fix-5.1.zip". I dont know how to proceed with the flashing, Since I am new to android. Can you please send in me the steps
Thanks in Advance
Anuvab
---------- Post added at 06:36 PM ---------- Previous post was at 06:30 PM ----------
I have been banging my head since the 5.1 update(Screen going blank during Call) on my Nexus 6 and then I found you. I have downloaded the file named "prox-fix-5.1.zip". I dont know how to proceed with the flashing, Since I am new to android. Can you please send in me the steps
Thanks in Advance
Anuvab
---------- Post added at 06:46 PM ---------- Previous post was at 06:36 PM ----------
I have been banging my head since the 5.1 update(Screen going blank during Call) on my Nexus 6 and then I found you. I have downloaded the file named "prox-fix-5.1.zip". I dont know how to proceed with the flashing, Since I am new to android. Can you please send in me the steps
Thanks in Advance
Anuvab
Click to expand...
Click to collapse
First, your N6 must be rooted, and have a custom recovery like TWRP. Once that is completed, and you have everything safely backed up. You simply reboot into recovery via TWRP, click on install, locate the proximity fix file in your downloads, click on it, drag the slider to install. When complete, reboot your device, and test to see if it's working properly.

Cool. I've been chrooted.
I was going to provide useful feedback to the thread: [Q&A] [MOD][FIX] Mar. 31 | Fix Proximity Sensor on any 5.1 ROM
Didn't seem to work for my nexus 6 on rom 47i, for whatever that's worth.
---------- Post added at 05:33 PM ---------- Previous post was at 05:28 PM ----------
Nirgali said:
Cool. I've been chrooted.
I was going to provide useful feedback to the thread: [Q&A] [MOD][FIX] Mar. 31 | Fix Proximity Sensor on any 5.1 ROM
Didn't seem to work for my nexus 6 on rom 47i, for whatever that's worth.
Click to expand...
Click to collapse
I am curious though. What is the reason for the cache clearing? Also what exactly is the patch changing?
Code:
ui_print(" Flashing changes...");
ui_print(" ");
show_progress(0.99, 30);
unmount("/system");
unmount("/data");
unmount("/cache");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
run_program("/sbin/mount", "/data");
run_program("/sbin/mount", "/cache");
ui_print("----------------------------------------------");
ui_print("| Wiping Cache and Dalvik... |");
ui_print("----------------------------------------------");
delete_recursive("/data/dalvik-cache");
delete_recursive("/cache");
delete_recursive("/data/anr");
delete_recursive("/data/lost+found");
delete_recursive("/data/tombstones");
delete_recursive("/data/local/tmp");
delete_recursive("/data/dontpanic");
delete_recursive("/data/data/com.android.vending/cache");
delete_recursive("/data/data/com.google.android.apps.maps/cache");
delete_recursive("/data/system/usagestats");
package_extract_dir("system", "/system");
set_metadata("/system/vendor/firmware", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
show_progress(1.0, 1);
unmount("/system");
unmount("/data");
unmount("/cache");
ui_print("----------------------------------------------");
ui_print("| Done!!! |");
ui_print("----------------------------------------------");
ui_print("");

help with flashing this
Sorry ...i just saw the answer to my question so deleted my question

I simply noticed when music plays, Ambient triggers constantly. Oh well.

This fix seems to also be effective with Cyanogenmod 12.1 so far.

Won't work on 5.1 BenzoRom, any flash to disable the proximity sensor altogether?

dyoung33 said:
First, your N6 must be rooted, and have a custom recovery like TWRP. Once that is completed, and you have everything safely backed up. You simply reboot into recovery via TWRP, click on install, locate the proximity fix file in your downloads, click on it, drag the slider to install. When complete, reboot your device, and test to see if it's working properly.
Click to expand...
Click to collapse
It also did not work for me. Running CM 12.1.

Compatible with Cyanogenmod?
Has anyone tried this with Cyanogenmod 12.1?
EDIT: Whoops. I was looking in the main thread, not the Q&A. I see there are various answers here about CM 12.1 compatibility. I will be make a NANDroid backup, install the patch, and report back.
---------- Post added at 08:01 PM ---------- Previous post was at 07:14 PM ----------
gojoco said:
Has anyone tried this with Cyanogenmod 12.1?
Click to expand...
Click to collapse
Success! I flashed this on top of my current install (12.1-20150521-NIGHTLY-shamu) via ADB sideload (wiped cache and Dalvik). Now the proximity sensor functions as intended (screen only blacks out when the proximity sensor is covered).
Many thanks!

I have less than 10 posts so I have to post here:
Don't try this on Xiaomi MI3 running MIUI (Android 5.1).
I've tried it and half of my apps crashed, boot took like 5 minutes, I couldn't turn on WiFi or Bluetooth, everything was just F... up.
I had to do complete wipe and reflash and proximity sensor still sucks.

5.1.1 Update
Can anybody confirm if this flashable fix works on 5.1.1 because I still have the problem.

Help Lollipop Sensors S5
My galaxy s5 had an accident and ended up staying submerged for several hours with the open back cover. Dried well , he came back normal, but reset time, date and some definitions . All sensors like accelerometer , screen tilt , barometer are not working anymore . I believe it is only setting . I've heard that when it occurs in S4 may be just BIN files that redefined . In the S5 I did root and changed the attributes of the file \system\lib\libgnustl_shared.so for rw-r-r- but sensors still not working .
Could anyone help?
Model: S5 SM-G900M with Lollipop 5.0 ROM "Trinidad and Tobago"
[email protected]

Hey, guys. I have a problem. I flashed it last night and it worked perfectly. But today when I woke up it wasn't working anymore. I flashed it again, but no luck.
I'm on Pure Nexus Marshmallow ROM.

In case anyone is wondering, this is CONFIRMED WORKING (!!!) on Android 6.0. Currently running latest build of Pure Nexus with Elemental X kernel and this has allowed me to continue using my tempered glass screen protector.
GREAT FIX! Works across multiple versions of Android.

[SM-T110][KERNEL] Andriva Custom Kernel 4.2.2

Iam not responsible for any domaged caused to your device !!!!
Here goes for the features of the kernel :
- Resolution 1024 x 768 to 1280 x 768.
- Support for OTG cable.
- Support for mouse and keyboard.
- Support for gamepad and joystick.
- Support for external wifi adapter.
- Support for NTFS filesystem read and write native.
Not all tested
INSTRUCTION
flash to custom recovery and reboot
LINK
https://db.tt/3dzFFfQJ
Have fun

For North Americain device T110UEUANB3

gm
what ??
what do mean by not all tested.
1 some r teted.
2nothing is tested
3is this support sm t111 ?/cause they r somewhat similar.
thanx for effotrts

@nannaniel please Sm-t210 one build dev kernel 4,1.2 android version can you otg support bla blaa

nannaniel what does not work and this kernel. I installed this kernel and does nothing.

Deleted this thread, kernel does not work!

Andriva updater script
delete_recursive("/cache");
mount("ext4", "EMMC", "/dev/block/mmcblk0p10", "/data");
delete_recursive("/data/dalvik-cache");
format("ext4", "EMMC", "/dev/block/mmcblk0p5");
package_extract_file("flash_image", "/tmp/flash_image");
package_extract_file("zImage", "/tmp/zImage");
set_perm(0, 0, 0755, "/tmp/flash_image");
run_program("/tmp/flash_image", "/dev/block/mmcblk0p5", "/tmp/zImage");
delete("/tmp/flash_image");
delete("/tmp/zImage");
(what's the point of deleting /tmp files before reboot ?)

Can somone explain why it's not working? It's like stock kernel in zip . Well this first(resolution change) is really interesting, i would love to have 1280x768.

Bl!nd said:
Can somone explain why it's not working? It's like stock kernel in zip . Well this first(resolution change) is really interesting, i would love to have 1280x768.
Click to expand...
Click to collapse
I tried that in the Dr, aroma rom and the readabillity of the rom wss very bad. What I would love to see is a way to over clock tbe cpu for this ememic tablet. I didnt notice any changes on the tablet after flashing though either. But thank you anyways for all the wok on it Dev...
"Chance Favors the Prepared"

is this working?

It sucks
first of all nothing changed and second it BRICKED MY DEVICE THIS SUCKS I HAD TO SPEND 1 WHOLE DAY FIXING IT SO FIX IT AND MAKE A NEW KERNEL THAT SUPPORTS OVERCLOCK.

can i install this rom for tab 3 lite t111 ???

TheedAndroid said:
It sucks
first of all nothing changed and second it BRICKED MY DEVICE THIS SUCKS I HAD TO SPEND 1 WHOLE DAY FIXING IT SO FIX IT AND MAKE A NEW KERNEL THAT SUPPORTS OVERCLOCK.
Click to expand...
Click to collapse
No developer is your slave. Shut the f*ck up.

nannaniel said:
Iam not responsible for any domaged caused to your device !!!!
Here goes for the features of the kernel :
- Resolution 1024 x 768 to 1280 x 768.
- Support for OTG cable.
- Support for mouse and keyboard.
- Support for gamepad and joystick.
- Support for external wifi adapter.
- Support for NTFS filesystem read and write native.
Not all tested
INSTRUCTION
flash to custom recovery and reboot
LINK
https://db.tt/3dzFFfQJ
Have fun
Click to expand...
Click to collapse
Hello, do you happen to have the source code for your kernel? Thank you!

[Velocity_Kernel] Nougat 7.1.1

Code:
Warning, this is a custom Kernel which is not developed by Samsung. I'm not responsible of eventual bugs that can append, bricks and any problem. So please, do a backup in TWRP before installing this. By installing this Kernel, you agree with this disclaimer.
Velocity Kernel v14.1 [latest build] for all Nougat ROMs full flashing procedure.(It is advised to store the kernel zip file in your internal storage as storing in external storage may cause some issues.)The Kernel is compatible with all YU Devices having Nougat OS and all other devices having Nougat 7.1.1 support like Resurrection Remix,Lineage OS,AOKP, AOSP etc.
it dont support Resurrection Remix 7.1.2 And Lineage OS 7.1.2
Test Version
Unknown
Bugs
PM Me if It Doesn't Boot in that Model

For which models my man?

Fild5x said:
For which models my man?
Click to expand...
Click to collapse
What Model U have? A 2015 , A 2016 , A 2017 ?

a500h 20 15

Fild5x said:
a500h 20 15
Click to expand...
Click to collapse
I didn't tested that model yet but it may work?

Ok but please maybe stupid question, on which roms stock or custom do think I can use this? If stock, then which one would you suggest I download and install?

Fild5x said:
Ok but please maybe stupid question, on which roms stock or custom do think I can use this? If stock, then which one would you suggest I download and install?
Click to expand...
Click to collapse
Works Stock ROM/ doesn't work in custom ROM because it may not be Compatible

Thanks for the response. So I need to download a noogat 7.1.1 stock rom? I am thinking, there is no stock nougat rom for a500h. Therefore can I use stock marshmallow? Please forgive ny nubeness.

Fild5x said:
Thanks for the response. So I need to download a noogat 7.1.1 stock rom? I am thinking, there is no stock nougat rom for a500h. Therefore can I use stock marshmallow? Please forgive ny nubeness.
Click to expand...
Click to collapse
Try if it works if it dozen boot PM Me

Ok. I will

Hi , on which model this kernel turn

ÉNITSED said:
Hi , on which model this kernel turn
Click to expand...
Click to collapse
Any A Model But only in Nougat stock rom

@AnotherOneTest, I think you don't know anything about kernel or ROM. Why do you keep bringing stuffs from other devices? (even not samsung!)
https://forum.xda-developers.com/yu...elocity-kernel-64-bit-lollipop-5-1-1-t3253776

But.. one kernel for all devices?! What?

Markxdx said:
But.. one kernel for all devices?! What?
Click to expand...
Click to collapse
Yes.. Feradroid engine can support all device too
Sent from my Samsung SM-A500F using XDA Labs

jjjhitel said:
@AnotherOneTest, I think you don't know anything about kernel or ROM. Why do you keep bringing stuffs from other devices? (even not samsung!)
https://forum.xda-developers.com/yu...elocity-kernel-64-bit-lollipop-5-1-1-t3253776
Click to expand...
Click to collapse
Trying hard to get thanks, I bet. Please close thread.

XenRon said:
Trying hard to get thanks, I bet. Please close thread.
Click to expand...
Click to collapse
Well Its Not Taken From Closed Thread its just a modified
Kernel. Well The Name is the same from Closed Thread idk
There to find that thread i guess its just the are same.

AnotherOneTest said:
Well Its Not Taken From Closed Thread its just a modified
Kernel. Well The Name is the same from Closed Thread idk
There to find that thread i guess its just the are same.
Click to expand...
Click to collapse
Dude our device is not a yu device even your op states so. You didn't even credit anybody or open source it.

AnotherOneTest said:
Well Its Not Taken From Closed Thread its just a modified
Kernel. Well The Name is the same from Closed Thread idk
There to find that thread i guess its just the are same.
Click to expand...
Click to collapse
Just close this thread yourself.
updater-script
Code:
package_extract_dir("tools", "/tmp");
ui_print("---------------------------------------");
ui_print("Flashing [B]Velocity Kernel[/B] (64-BIT) v14.1");
ui_print("---------------------------------------");
set_perm(0, 0, 0777, "/tmp/mkbootimg");
set_perm(0, 0, 0777, "/tmp/unpackbootimg");
set_perm(0, 0, 0777, "/tmp/flash_kernel.sh");
ui_print("The Most");
run_program("/tmp/flash_kernel.sh");
ui_print("Efficient Kernel");
delete("/tmp/boot.img");
delete("/tmp/mkbootimg");
delete("/tmp/unpackbootimg");
delete("/tmp/flash_kernel.sh");
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system");
delete("/system/bin/ims_rtp_daemon");
delete("/system/lib/modules/wlan.ko");
delete("/system/etc/init.d/Velocity-Core_Settings");
package_extract_dir("system", "/system");
set_perm(0, 0, 0755, "/system/etc/init.d/Velocity-Core_Settings");
unmount("/system");
ui_print("for [B]Yu-Devices[/B]");
ui_print("----------------------------");
ui_print("Developed by [B]Shoaib Anwar[/B] :)");
ui_print("----------------------------");

Thread closed.
Clearly, this is not developed by the OP, and doesn't appear to be for this device. Not only that there are no credits or kernel source.