Related
Lite version of stock firmware: UK I8160XXLK7 (built 30.11.2012, changelist #1214896).
Rooted with SuperSU v0.99
The ROM is for ODIN flashing and it won't increase your flash counter.
There's also a ZIP version for CWM/TWRP.
You can always add CWM and custom kernel by ADB and dd command also without increasing the counter so.. make your own decisions from now on
Apps added:
AppWidgetPicker v1.2.3: groups widgets in selection screen
HoloLauncher v1.2.8: fast and light ICS style launcher, alternative to TW Launcher
Apps removed:
Code:
AnalogClock, AnalogClockProvider, BluetoothTestMode, BuddiesNow, ChatON
ChocoEUKor, Days, Divx, Dlna, DSMForwarding, DSMLawmo, DualClock
DualClockProvider, EdmVpnServices, Email, EmailWidget, FactoryTest15
fotaclient2, FTM, FTS, GameHub, Gmail, HelvNeueLT, HTMLViewer, Kies
kieswifi, lcdtest, Maps, Memo, MiniDiary, MinimalHome, MobilePrint
MobileTrackerEngineTwo, MusicHub_15, PanningTryActually, PhotoRetouching
PlusOne, PolarisOffice, PostIt, Protips, PRUI, SamsungApps, SamsungAppsUNA3
Samsungservice, SamsungWidget_News, SamsungWidget_ProgramMonitor
SamsungWidget_StockClock, SamsungWidget_WeatherClock, SecretWallpaper1
SecretWallpaper2, SelfTestMode, shutdown, SnsAccountFb, SnsAccountLi
SnsAccountTw, SnsDisclaimer, SnsImageCache, SnsProvider, SocialHub
SocialHubWidget, SPPPushClient, Street, Tasks, VoiceToGo, WlanTest
wssyncmlnps, YouTube
and some files:
Code:
etc/1_Power_on.ogg
etc/PowerOn.wav
etc/kies
lib/libpolarisoffice.so
lib/libKiesDataRouter.so
build.prop addons:
Code:
#
# MODIFIED BY aeM
#
# Disable boot animation for faster boot
debug.sf.nobootanimation=1
# Disable debugging notify icon on statusbar
persist.adb.notify=0
# Force launcher into memory
ro.HOME_APP_ADJ=1
# Improves audio and video recording quality
ro.media.enc.jpeg.quality=100
ro.media.enc.hprof.vid.bps=8000000
ro.media.enc.hprof.vid.fps=25
# Video acceleration and HW debugging
video.accelerate.hw=1
debug.egl.profiler=1
debug.egl.hw=1
# Disables error reports
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
# Saves power
ro.ril.power_collapse=1
pm.sleep_mode=1
wifi.supplicant_scan_interval=120
# Disables logcat
logcat.live=disable
# Phone rings immediately
ro.telephony.call_ring.delay=500
ring.delay=500
# Better signal
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
# Better call voice quality
ro.ril.enable.amr.wideband=1
# Disables sending of usage data
ro.config.nocheckin=1
# More volume steps in call
ro.config.vc_call_steps=10
# Uses Google's DNS for better internet speed
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
net.ppp0.dns1=8.8.8.8
net.ppp0.dns2=8.8.4.4
net.dns1=8.8.8.8
net.dns2=8.8.4.4
# Signal (3G) tweaks
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=10
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
# Net speed tweaks
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
Installation:
1. Download and flash stock LK7 ROM:
United Kingdom (sammobile hotfile)
2. Download and flash lited LK7 availible in two versions:
aeM_ROM_v1.3 for CWM/TWRP - 206.13 MB (dev-host)
aeM_ROM_v1.3 for ODIN - 175.14 MB (dev-host)
3. Check if I bricked your phone.. (just kidding )
Side notes:
Use 7zip to unpack downloaded files (http://7-zip.org/)
Use Odin v1.85 to flash (https://docs.google.com/open?id=0B9GFVatYEi9jbWYtalVMVFdBbWc)
USB Debugging in Settings->Application->Development must be ticked on for proper rooting
Flashing stock LK7 and lited LK7 wont remove your apps and files. It just reflash the system partition.
I've removed google apps (gmail, youtube, maps) so if you use them just download them from the market.
Try using Holo Launcher which in my opinion is superior to TW Launcher.
Credits:
Samsung and Google
Szaby59 for the procedure to root without changing the counter (http://forum.xda-developers.com/showthread.php?t=1881964)
dark_knight35 for the collection of tweaks for build.prop
Chainfire for the SuperSU
boombuler for AppWidgetPicker
dsixda for dsixda's Android Kitchen
probably some more people but can't seem to remember now.. sorry
If you have some ideas about changes feel free to share
Removed apps (deodexed):
LK7 apps - 91.49 MB (dev-host)
Just copy apk file to /system/app folder and set permissions to 644 (rw- r-- r--)
Changelog:
2012-12-22 aeM ROM v1.3
updated source firmware to UK I8160XXLK7 (built 30.11.2012, changelist #1214896)
restored some system apps to maintain functionality (ie.: Stock TWLauncher, Swype, LiveWallpapers, SimToolkit)
bumped the version number
2012-12-10 aeM ROM v1.2
aeM_ROM_v1.2 for CWM/TWRP - 178.15 MB (dev-host)
aeM_ROM_v1.2 for ODIN - 147.52 MB (dev-host)
updated source firmware to multiCSC I8160XXLK6 (built 15.11.2012, changelist #1211243)
restored some system apps to maintain functionality (ie.: MTP, TWLauncher, Voice Search)
made ZIP package for custom recovery
added more build.prop tweaks
restored TWLauncher (but modded) to maintain STOCK look
bumped the version number
2012-12-02 aeM ROM v1.1
aeM_ROM_v1.1 odexed - 127.84 MB (dev-host)
aeM_ROM_v1.1 deodexed - 131.05 MB (dev-host)
updated source firmware to UK I8160XXLK5 (built 15.11.2012, changelist #1211379)
removed more apps
removed TWLauncher and replaced it with Holo Launcher
added AppWidgetPicker
made deodexed and zipaligned package
bumped the version number
2012-10-24 aeM ROM v1.0
aeM_ROM_v1.0 - 155.56 MB (dev-host)
initial release
ToDo:
0. Ideas?
FAQ:
1. Will this ROM void my warranty?
YES! But you can revert to stock and the phone will look as a brand new and will revert the warranty.
2. Will this ROM increase my flash counter?
NO!
3. I've got a LK7 firmware and a custom kernel right now. Will I have to reflash the kernel after flashing this ROM?
No. The kernel remains intact as you only flash the csc and system.
4. I've got many apps installed right now and I don't want to loose them.
Upgrading the firmware with ODIN doesn't format the system partition, it only 'repopulate' it with the 'new' files so all your settings, sms/mms, apps and other stuff will remain intact.
5. I see some bloatware like 'Google books', you said it was lite..!?
This app is only in specific CSCs and I can't remove it without voiding the samsung signature thus breaking the CSC procedure during the first reboot after flashing. You can remove this app yourself (i.e. TitaniumBackup).
TIPS:
If you want a REALLY clean system then you could make this VERY complicated procedure:
[Req: rooted rom, adb and odin 'installed' on pc, phone connected to pc by usb]
1. enter recovery (turn on the phone with VolUp+Home)
2. on pc:
adb shell
su
wipe all (disregard the warning about /etc not being empty)
exit (exits su)
exit (exits shell)
adb kill-server
3. select 'reboot the system' in the recovery and enter download mode (during turning on VolDown+Home)
4. on pc: flash my rom with odin
5. wait for reboot and live happily with CLEAN system
or for CWM/TWRP just format data/cache/system partitions
WiCiO_MeDi said:
reserved
If you have some ideas about changes feel free to share
Looking for answers:
1. How to decrease the img filesize?
I've removed more then 100mb and the size is still the same even after compressing, weird...
2. That's all for now
Click to expand...
Click to collapse
Great to see that we have an other 'custom' rom. It's a great base to add a theme, other tweaks,..
@WiCiO_MeDi
You can always deodex those apps that has been left. Also you can make this ROM flashable thru CWM or TWRP. Please do not add any apps/themes/transitions. This ROM is a GREAT base for anyone who want to play on his own rules with modding. Anyway... dobra robota!
@WiCiO_MeDi
You can add Init.d support support to your ROM.
I tested this script on my phone and it works.
Here you can find information to manual enable support for Init.d.
Will try with init.d, why not.
As of themes/apps/transitions i'm adamant about not including any so don't worry
Regarding CWM:
My idea was to create light rom, easy to flash (odin) and without any fuss with commands in adb/recovery/terminal. Also the "NO" status of the flash counter is a big issue for me since we haven't got any way to reset it as of now and the warranty is a must with todays electronics.. unfortunately
Oh, and deodexing... forgot about it since I don't use themes
Can u explain what is DBT and the contents of your dropbox folder, since it's a lot faster to download from?
WiCiO_MeDi said:
build.prop addons:
Code:
#
# MODIFIED BY aeM
#
# Improves audio and video recording quality
ro.media.enc.jpeg.quality=100
ro.media.enc.hprof.vid.bps=8000000
ro.media.enc.hprof.vid.fps=25
# Video acceleration and HW debugging
video.accelerate.hw=1
debug.egl.profiler=1
debug.egl.hw=1
# Disables error reports
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
# Saves power
ro.ril.power_collapse=1
pm.sleep_mode=1
wifi.supplicant_scan_interval=120
# Disables logcat
logcat.live=disable
# Phone rings immediately
ro.telephony.call_ring.delay=500
ring.delay=500
# Better signal
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
# Better call voice quality
ro.ril.enable.amr.wideband=1
# Disables sending of usage data
ro.config.nocheckin=1
# More volume steps in call
ro.config.vc_call_steps=10
# Uses Google's DNS for better internet speed
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
net.ppp0.dns1=8.8.8.8
net.ppp0.dns2=8.8.4.4
net.dns1=8.8.8.8
net.dns2=8.8.4.4
Click to expand...
Click to collapse
You are a genius. GENIUS.
Sine my counter is @15 most of this is not very important for me, but this tweaks to /system/build.prop are just great.
Phone has speed up twice - at least (I'll check battery life later).
So thank you veeery much
A no i: Dobra Robota
all best
Man, chill, it's just placebo i think 'cause those tweaks are really minor. Maybe you got something screwed with the system before the flash or the bloatware was choking up your phone.
Anyway: your welcome and dzięki
Sent from my GT-I8160 using xda app-developers app
Fantastic job mate
Taptaptapatalkerz dari GT-i8160 saya.
this is good rom to use as base
P.S why post this in Q&A
every i8160 topic is in Q&A since there's no section for our pretty ACE2
WiCiO_MeDi said:
Man, chill, it's just placebo i think 'cause those tweaks are really minor. Maybe you got something screwed with the system before the flash or the bloatware was choking up your phone.
Anyway: your welcome and dzięki
Sent from my GT-I8160 using xda app-developers app
Click to expand...
Click to collapse
It crossed my mind but ...since i've got root i just remount /system to give it read-write permissions and modified inside stok build.props.
Then rebooted and phone went crazy fast
I'm running stok XXLI2 with 2.6.35.7HDTWRP kernel (TWRP 2.3.1.1) and Your's tweeks
All best and keep up good work
Powodzenia
Do this file have a mirror.. The file on dropbox is very slow
Taptaptapatalkerz dari GT-i8160 saya.
@ WiCiO_MeDi
I think you should left 2 apps, that you have removed:
app/GenieWidget.apk ---> Cool News and Weather app
app/MobileTrackerEngineTwo.apk ---> This is the only app that can help is your phone is stolen. It helped my wife when she lost her i9070.
Also san you prepare the TWRP flashable version, for guys like me? I do not want to go thu ODIN and then Kernel change again.
arroyo said:
@ WiCiO_MeDi
I think you should left 2 apps, that you have removed:
app/GenieWidget.apk ---> Cool News and Weather app
app/MobileTrackerEngineTwo.apk ---> This is the only app that can help is your phone is stolen. It helped my wife when she lost her i9070.
Also san you prepare the TWRP flashable version, for guys like me? I do not want to go thu ODIN and then Kernel change again.
Click to expand...
Click to collapse
Not sure ofcourse, but since this is a modified/cleaned stock rom, I suspect there's no kernel included. So flashing this via odin won't touch your kernel
I can be certain about this part, because I flashed and reflashed roms via odin for the sole purpose of testing to see if my kernel would change, and it never did.
You are right Carpe-Dimi, as far as you have DBT version of rom. If you don't, then you need to flash DBT before you flash Stock Lite, and this will flash your kernel.
I can't download this rom. It's show me:
"Error (509)
This account's public links are generating too much traffic and have been temporarily disabled!"
whne I open the dropbox link.
Yep, both of you are right
My rom wont touch kernel but you have to have DBT rom before the flash.
As for the apps.. I you really want them then just install them after the flashing.
Copy to /system/app and chmod 644
as for dropbox:
it seems that DB has download limits so i have to move to another mirror
any suggestions? mediafire is not free for files >200mb
Try with
http://www.4shared.com/
This must be the most asked question I have googled in a long time
There are so many results but nothing that resolves my dilemma
Without any tweaks I can access channel 13 via the router with my Xperia Ray running the latest nightly CM10
So whats the issue you may be asking, well this is the strange part
If I turn off the SSID of the router so it no longer broadcasts its name then the issue starts
My mobile will not connect to channel 13 thereafter it just disconnects
HOWEVER I have no issues with channels 1 - 12 with the SSID turned off
and certainly had no issues with Miui v4 with the same kernel installed
I have seen this happen with a few tablets but once the tablet has seen the network on channel 13 it was fine and then I could turn off the SSID
SO why do I need to turn off the SSID - because I prefer it was off in an area high with WiFi activity that's all
and I need to use channel 13 because of the high volume of wifi traffic in the area constantly changing there channels
Wifi 13 seems more stable and quicker anyhow I am in the UK and the routers in our street are all set to auto channel???????!!! why I dont know, but none use channel 13
So is there a solution to this very bizarre issue or am I going to have to leave my SSID on
SOLUTION Found thanks sirkay
Thanks to sirkay I can now access any hidden non broadcasting SSID wifi network
http://forum.xda-developers.com/showpost.php?p=23564367&postcount=5
A simple script that is supposed to enable extra channels actually fixed my issue with a hidden SSID
-----------------------------------------------------
Channel 13 issues
[ SOLUTION: To Enabled Wifi Channels 12-14 ]
1. using Root Explorer, goto /system/etc/init.d
2. open one of your init.d scripts, i suggest first in the list (Menu > Open in text editor)
3. paste line below
Code:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name, value) VALUES ('wifi_country_code', 'JP');"
4. close and save
5. reboot
note: to enabled channel 12-13 just change "JP" to "EU" or "ES"
-------------------------------------------------------------------------------------------------------------------------------------------
I created a fresh file called 10wifi
and add these lines
#!/system/bin/sh
#
# Fix wifi channels 12 - 14
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name, value) VALUES ('wifi_country_code', 'EU');"
-------------------------------------------------------------------------------------------
I put the file into an install-able zip and added permissions to the update_script
set_perm(0, 0, 0777, "/system/xbin/10wifi");
NeilDownx said:
Thanks to sirkay I can now access any hidden non broadcasting SSID wifi network
http://forum.xda-developers.com/showpost.php?p=23564367&postcount=5
A simple script that is supposed to enable extra channels actually fixed my issue with a hidden SSID
-----------------------------------------------------
Channel 13 issues
[ SOLUTION: To Enabled Wifi Channels 12-14 ]
1. using Root Explorer, goto /system/etc/init.d
2. open one of your init.d scripts, i suggest first in the list (Menu > Open in text editor)
3. paste line below
Code:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name, value) VALUES ('wifi_country_code', 'JP');"
4. close and save
5. reboot
note: to enabled channel 12-13 just change "JP" to "EU" or "ES"
-------------------------------------------------------------------------------------------------------------------------------------------
I created a fresh file called 10wifi
and add these lines
#!/system/bin/sh
#
# Fix wifi channels 12 - 14
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name, value) VALUES ('wifi_country_code', 'EU');"
-------------------------------------------------------------------------------------------
I put the file into an install-able zip and added permissions to the update_script
set_perm(0, 0, 0777, "/system/xbin/10wifi");
Click to expand...
Click to collapse
I copied the script and saw that actually in my settings.db the value wifi_country_code is correctly added, but my galaxy tab s with Blisspop rom still doesn't see the 13th channel...
someone can help me please?
tribio said:
I copied the script and saw that actually in my settings.db the value wifi_country_code is correctly added, but my galaxy tab s with Blisspop rom still doesn't see the 13th channel...
someone can help me please?
Click to expand...
Click to collapse
Have a look in your build.prop file and amend as below
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=13
now finally reboot and if it still fails you may need to change kernels......
I no longer have to bother with these settings as changing the kernel fixed my past issues
...Another solution
1. Turn off WiFi
2. Copy /data/misc/wifi/wpa_supplicant.conf to /sdcard
3. Rename /data/misc/wifi/wpa_supplicant.conf to /data/misc/wifi/wpa_supplicant.conf.old
4. Copy /sdcard/wpa_supplicant.conf to /data/misc/wifi
5. Edit /data/misc/wifi/wpa_supplicant.conf (using ES File Explorer) and remove the pmf=1 line
6. Save the file and make sure the permissions are appropriately set to rw-rw----, the owner is system and the group is wifi otherwise your WiFi will not turn on.
7. Reboot
8. Turn on WiFi
Found this solution on the CM12 errors list - lost of people having similar wifi issues
Tried to update build.prop and nothing change...
Opened wpa_supplicant.conf and there is not "pmf=1" written in the file..
I suppose I have to change kernels?
Thanks a lot for the help!!!
none of the above methods worked for me either
tribio said:
Tried to update build.prop and nothing change...
Opened wpa_supplicant.conf and there is not "pmf=1" written in the file..
I suppose I have to change kernels?
Thanks a lot for the help!!!
Click to expand...
Click to collapse
I seem to have the same problem. Did you resolve your issue? Thanks in advance.
nope!
working with CM12
tribio said:
nope!
Click to expand...
Click to collapse
I got fed up with this and decided to go all out and install Lollipop. I installed Installed Cyanogenmod (CM12) and then Temasek ROM port. I did this at home where the router is using a low channel number. I took the tablet to work and voila channel 13 was working. No need to mess with any wifi_country_codes. I am pretty sure it would work fine without the Temasek port. It might also have worked fine with CM10 or CM11. The disadvantage to this whole process is that I don't have the same spen functionality as stock. I'm still figuring out what apps to using for my "new" Note 10.1.
everything that has something to do with sound is simply not working (sometimes make my RN3SD restart)
1. phone calls : cant make any phone calls (when dialing the numbers, the screen show calling but cant connect, then restart. while reboot, the dialed number rang)
2.video (cant play any video with sound, including youtube. always show problem while trying to play)
3.music (cant play any music, alwasy show unsupported files)
QC TESTS :
1.play music on SD -> fail
2. Mic Speak loop -> fail : intenal applivation error and unable to access system space!)
3. Call test ;> fail
(java.lang.illegalargumenexception: invalid audio buffer size.
at android.media.audiorecord.audiobuffsizecheck(uidiorecord.java:674)
at android.media.audiorecord.<init>(audiorecord.java:374 and 271)
at com.longcheertel.cit.loopbackbaseactivity $record.run(loopbackbaseactivity.java:177)
at java.lang.thread.run(thread.java:818)
4. sub mic to speaker loopback ->fail (same as mic cpeak loop)
5. Headset plug in ;>fail
6. Headset key;> fail
7. Headset loopback-> fail
8. FM test -> fail
9. Headset plug out;>fail
APP tests
sound recorder :fail (check if another app is currently using the recording feature)
java:2894, 153, 1434, 102, 148, 5441, 738, 628, 674, 374, 271, 1288, 1265, 2884, and 8 more
soundabout does not help at all, no google setting
please if anyone can show me the right ways to solve this sound problem
About my RN3SD (KENZO):
android version : 6.0.1 MMB29M
MIUI version : MIUI Global 8.1 Stable 8.1.4.0 (MHOMDI)
baseband : -8976_GEN_PACK-1.7444 6.1.75478.1
kernel : 3.10.84-perf-g4b39ed7
PS : another thing i found, settings, additional settings, Headphone and audio effects ---> result is back to settings page
settings, sound and vibration, audio settings --> same, back to setting page
Did you try factory reset? Or even better fastboot flash latest ROM?
already did, no result
Hi, guys! New user here and let's start!
Well, I own a tablet which the model is Innovator 7DTB41...
I bought it from Greece!
Although I found out that model's name varies at Amazon which there is named Hipstreet 7DTB41-8GB Electron 7" (Quad Core 1.3GHz Google Certified Android 5.1 (Lollipop) Tablet 8GB -Black). I'm sure 99% that Amazon's link have right specs with the other link from E-shop that i bought it!
The images from Amazon, like volume button, power button, port micro USB, port auxiliary are the same position with my tablet! If that tells something!
At first, the tablet was rooted to remove bloatware, and I tweaked the build.prop...The tweak settings I'll write them below... the problem is that suddenly the internal storage went from (read-write) to (read-only) and when I was changed back to read-write with ES file explorer it didn't do something.. So I decided to give a reboot if this fixes the problem...After the reboot, the OS disappeared and more simple it does not boot...
Also, it has recovery and I just boot into that! The choices that were given to me is 7
Android system recovery <3e>
7DTB41_20170119
1. Reboot system now
2. apply update from ADB
3. wipe data/factory reset
4. wipe cache partition
5. reboot to bootloader
6. power down
7. View recovery logs
Recovery system v5.0
E: failed to mount /mnt/internal_sd (No such device)
Tweak Settings:
#Faster Scrolling
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
#Liquid Smooth Ui (not the custom rom)
persist.service.lgospd.enable=0
persist.service.pcsync.enable=0
ro.ril.enable.a52=1
ro.ril.enable.a53=0
#Better internet browsing & download speed
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.hspa=6144,87380,524288,6144,163 84,262144
net.tcp.buffersize.lte=524288,1048576,2097152,5242 88,1048576,2097152
net.tcp.buffersize.hsdpa=6144,87380,1048576,6144,8 7380,1048576
net.tcp.buffersize.evdo_b=6144,87380,1048576,6144, 87380,1048576
# Saves some battery without reducing performances
wifi.supplicant_scan_interval=497
pm.sleep_mode=1
power.saving.mode=1
ro.ril.disable.power.collapse=0
ro.vold.umsdirtyratio=20
# Increase general Performance
debug.performance.tuning=1
# Increase some Performance
ro.secure=0
persist.sys.use_16bpp_alpha=1
ro.product.gpu.driver=1
ro.min.fling_velocity=8000
# Reduce the black screen time of the proximity sensor
ro.lge.proximity.delay=15
mot.proximity.delay=15
# Increase camera's photo and video recording quality
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.enc.hprof.vid.fps=65
#Better RAM managment
ro.HOME_APP_ADJ=1
Disables built-in error reporting.
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
#Disables logcat
logcat.live=disable
#Faster boot.
ro.config.hw_quickpoweron=true
#Disables error checking.
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
#Disables sending of usage data.
ro.config.nocheckin=1
#Disable strict mode checking.
persist.android.strictmode=0
#build.prop tweaks for improved performance
debug.performance.tuning=1
Thanks for reading until now!!
Sorry for any mistakes! I cannot put links! :/
angel1998 said:
So I decided to give a reboot if this fixes the problem...After the reboot, the OS disappeared and more simple it does not boot...
Also, it has recovery and I just boot into that! :/
Click to expand...
Click to collapse
Γειά σου φίλε!!!
Have to keep it in English though for everybody to understand. If system partitions got messed up trough the process you described, well... Chances are you might need to flash full stock...
However... Since you can get to stock recovery, can you do a factory reset? Does it work? Or does it come back giving you a whole bunch of red lettered errors? If that is the case full stock flashing is the solution...
Unfortunately, I personally can't think of a way to make this work without losing your data. But, hey... You won't through away the device!!!
Post a little more info if you wish, or update on how you are doing with the device, so others can also help. Also please check your private messages.
Well, guys, I gave up, cause Windows doesn't recognize the tablet in download mode or in bootloader, and I had to mess finding drivers which are not easy with this whatever brand name is and i sent it to the shop i bought, and they will give me a replacement!
Special thanks to r&xp for helping me at private messages!
UPDATE: Add persist.data.iwlan.enable=true persist.radio.calls.on.ims=1 to /system/build.prop I'm not sure why they only added it to NA 16s. There appears to still be issues getting this to work on LOS. I suspect it has to do with modem firmware and android driver mismatches as LOS also can't properly read the sim address book.
While testing to see if WiFi Calling worked on custom roms I flashed back to stock cn EUI 23s and noticed it doesn't even appear to work on it. It activates and doesn't give an error message on EUI 23s (once got an Error81), and it shows that it is enabled. However it doesn't appear to actually work and checking with 'Network Cell Info' it shows 'WiFi Call avail: No'.
[UPDATE] - I tracked down what makes it work. Apparently all that is needed is something in the le_x2_na (US/CA) 16s build. You can use modem 50 with it and it still works so its something about the android software itself that changed that broke it in the China 23s/India 19s roms. I tested it with Airplane mode on and only wifi enabled and it made calls so it definitely works. It appears all the other builds give Error81 eventually and will not work. I think the other builds don't even try to connect as they didn't show anything when using tcpdump. The 16s build shows lookups to 3gppnetwork.org for mnc260 "US" mcc310 "T-Mobile" (my provider) and a bunch of ISAKMP and ESP packets to the resulting ip address.
Grepping for the 3gppnetwork.org text in /system turns up the following files:
Code:
$ grep -r 3gppnetwork.org *
Binary file bin/wpa_supplicant matches
Binary file etc/firmware/modem_pr/mcfg_sw_tmo.mbn matches
Binary file etc/firmware/modem_pr/mcfg_sw_cmcc.mbn matches
Binary file framework/oat/arm64/wifi-service.odex matches
Binary file priv-app/Settings/oat/arm64/Settings.odex matches
Binary file vendor/lib/lib-imsqimf.so matches
Binary file vendor/lib64/lib-imsqimf.so matches
Generic Access Network
If no one else knows what's going on with it I might throw a packet sniffer in between and see if its actually sending out the request properly. It should also help to see if a call is actually being routed, but it fails when I turn off the cell connection so I think it may not be working. There also isn't a wifi calling icon at top so probably isn't working.
Code:
05-13 00:01:30.219 2280 3293 I NetworkController: onReceive: intent=Intent { act=android.net.wifi.RSSI_CHANGED flg=0x4000010 mCallingUid=1000 (has extras) }
05-13 00:01:30.228 2280 3293 I NetworkController: onReceive: intent=Intent { act=android.net.wifi.RSSI_CHANGED flg=0x4000010 mCallingUid=1000 (has extras) }
05-13 00:01:30.361 12051 12051 I ViewRootImpl: finishMotionEvent: handled = true stage=10: View Post IME stage,inputElapseTime=2 eventTime = 2467238 downTime = 2467238 title= com.android.settings/com.android.settings.Settings$WifiCallingSettingsActivity
05-13 00:01:30.439 2280 3293 I NetworkController.MobileSignalController(slotId:0 subId:1): mWfcImsObserver onChange()
05-13 00:01:30.458 1605 2698 W AppOps : isskipsystem code:40 uid:1001
05-13 00:01:30.466 2755 3770 E ImsConfigImpl: getImsConfigListener returns null
05-13 00:01:30.466 2755 3770 E ImsConfigImpl: onSetFeatureResponseDone listener is not valid !!!
05-13 00:01:30.470 1605 2604 W AppOps : Finishing op nesting under-run: uid 1001 pkg org.codeaurora.ims code 40 time=0 duration=0 nesting=0
05-13 00:01:30.484 1605 2628 W AppOps : isskipsystem code:40 uid:1001
05-13 00:01:30.510 1605 2681 W AppOps : Finishing op nesting under-run: uid 1001 pkg org.codeaurora.ims code 40 time=0 duration=0 nesting=0
I also notice that while VoLTE appears to work on 23s if you turn it off and on it doesn't, the logcat output also looks a bit odd, like it might not be doing anything at all, ugh.
Code:
05-13 00:20:02.742 2755 2755 I ViewRootImpl: finishMotionEvent: handled = true stage=10: View Post IME stage,inputElapseTime=1 eventTime = 3580090 downTime = 3580090 title= com.android.phone/com.android.phone.MobileNetworkSettings
05-13 00:20:02.878 1605 1633 W AppOps : isskipsystem code:40 uid:1001
05-13 00:20:02.887 2755 3770 E ImsConfigImpl: getImsConfigListener returns null
05-13 00:20:02.887 2755 3770 E ImsConfigImpl: onSetFeatureResponseDone listener is not valid !!!
05-13 00:20:02.967 1605 2628 W AppOps : Finishing op nesting under-run: uid 1001 pkg org.codeaurora.ims code 40 time=0 duration=0 nesting=0
It works on the us rom x829 5.8.16s and maybe on some of the dev roms.
Edit: You can check by enabling airplane mode
whymoo said:
It works on the us rom x829 5.8.16s and maybe on some of the dev roms.
Click to expand...
Click to collapse
Thanks, I'll have to take a look at what it is doing differently between 16s and 23s so hopefully it will work on more roms.
So running tcpdump on 23s and turning off and on WiFi Calling does not appear to produce any network packets at all, or at least not any that tcpdump saw. I'll have to try it out on 16s sometime soon.
Updated OP, US 16s apparently will work with various modem firmwares, v24 v50 tested, but India 19s and China 23s do not.
I'm not certain but I think the issue is due to the newer builds not including WfcService at all. Copying it from 16s though causes com.android.phone to crash continuously.
ccheney said:
Updated OP, US 16s apparently will work with various modem firmwares, v24 v50 tested, but India 19s and China 23s do not.
Click to expand...
Click to collapse
Nice to see someone digging into this. Getting sick of the 16s firmware.
Another thing which is a bit interesting is that with the original 16s radio, WiFi calling tends to be a bit less finicky about connecting. After reading your post, I flashed the v50 modem, and got the REG99 "Unable to connect" error message upon booting. This almost never happens with the original modem file. I did manage to get it to work, but only after putting the phone into Airplane mode and enabling WiFi. If you only need to call numbers in your contacts, or receive calls, you can leave it in Airplane. Otherwise, the dialer shows "Emergency calls only", and you have to put it back into normal mode. The 16s seems more seamless, but the newer modem files are probably better overall for other radio functions.
I wish LeEco would release the sources for the 16s firmware, to make the job of the devs easier for this, but I don't see that happening.
If anyone knows more details about how WFC works in Android please let us know or point to reading material.
I have some prior Android hw development experience but have been previously using an iPhone and finally made the switch permanent with this phone. So I'm still learning how WFC works under Android, but it seems there are also two sets of modem files. The ones in /system/etc/firmware/modem_pr/ and the ones in /firmware/image/modem_pr/mcfg/configs/mcfg_sw/generic . I'm not sure why they are different (the md5sums don't match). There are much fewer of them in the system area as well as compared to firmware. I suspect the ones in /firmware are from qualcomm for global use and perhaps LeEco just picked a few to actually use for some reason? Looking at how the Pixel phones do it they seem to copy the files out of the /firmware dir to use at boot time. I'll have to try out v50 again later on 16s but I'm pretty sure I got it to work fine. VoLTE activation also seems to be a bit flaky even on the EUI firmware.
I suspect that WFC does not work for carriers in Europe or most of Asia even on 16s unless the 'others' modem profile allows them to work somehow. There are more modem profiles in /firmware we could potentially use if we determine how this works.
I'm going to go back to EUI 23s again and see if it ever tries to communicate to the WFC website via tcpdump. It certainly didn't show much in the logcat output that I could see. I'm not sure if I can start tcpdump with the network down, but it does seem to work with just disabling/reenabling WFC on 16s.
I'm probably wrong, but couldn't someone just take the WFC code from another SD820 phone and use that to make it work?
/system/etc/firmware/modem_pr/
mcfg_sw_att.mbn - US - AT&T
mcfg_sw_cmcc.mbn - China - CMCC
mcfg_sw_ct.mbn - China - CT
mcfg_sw_cu.mbn - China - CU
mcfg_sw_le_others.mbn - ??
mcfg_sw_others.mbn - ??
mcfg_sw_reliance.mbn - India - Reliance
mcfg_sw_tmo.mbn - US - T-Mobile
mcfg_sw_verizon.mbn - US - Verizon
I did another round of testing on 23s and I turned airplane mode on/off while running tcpdump, just toggling wifi didn't give any error and didn't work, WFC gave Error81 but there was no visible attempt to connect to the WFC server or even do a DNS lookup for it during the entire time. No points for LeEco making their newer roms buggier.
Interestingly CN 16s also gives Error81, so it might be that only the NA (US/CA) 16s works for some reason. I suspect it might have something to do with the modem firmware.
UPDATE: I think I solved the issue on EUI, testing against 26s now to see if it fixes it. Having trouble verifying if I fixed it as its not giving Error81 anymore but not saying WFC is enabled either, will have to look at tcpdump output some more I suppose.
Ok, so I managed to get IN 19s to work with the change. For some reason CN 23s/26s did not seem to work.
All you have to do is add the following and it works:
persist.data.iwlan.enable=true
At the top of the screen it shows "T-Mobile Wi-Fi Calling LTE" (I'm using T-Mobile) I noticed that if I have Airplane mode enabled it does not appear to be able to make calls so it may be only partially working, will have to look at tcpdump output to see if its actually registering. It may need persist.radio.always_send_plmn=true but I'm not sure yet. I can't really tell from the tcpdump if its working or not, will have to capture a full call under 16s to see what it looks like to compare it. There was lots of ipv4/ipv6/da1a data being transferred, but I don't know which part was the call, lol.
There may be other useful props to add from NA 16s but I'm not sure.
But I'm still pretty new at this, only had an Android phone for a couple weeks.
ccheney said:
Ok, so I managed to get IN 19s to work with the change. For some reason CN 23s/26s did not seem to work.
All you have to do is add the following and it works:
persist.data.iwlan.enable=true
At the top of the screen it shows "T-Mobile Wi-Fi Calling LTE" (I'm using T-Mobile) I noticed that if I have Airplane mode enabled it does not appear to be able to make calls so it may be only partially working, will have to look at tcpdump output to see if its actually registering. It may need persist.radio.always_send_plmn=true but I'm not sure yet. I can't really tell from the tcpdump if its working or not, will have to capture a full call under 16s to see what it looks like to compare it. There was lots of ipv4/ipv6/da1a data being transferred, but I don't know which part was the call, lol.
There may be other useful props to add from NA 16s but I'm not sure.
But I'm still pretty new at this, only had an Android phone for a couple weeks.
Click to expand...
Click to collapse
If you can get Wi-Fi Calling and VoLTE to work in Nougat ROMS it would be amazing.
So I found out how to make IN 19s work properly after looking at the LOS 14.1 x2 device tree.
You need both of the following:
persist.data.iwlan.enable=true
persist.radio.calls.on.ims=1
I can now turn on airplane mode and only turn on wifi and still make calls so it is going over WiFi like it should.
LOS 14.1 does not support it due to a 'feature' in the code they copied from LeEco. They turn off support for WiFi Calling for the X820 model for some unknown reason. Even the cellular providers in China support WiFi calling so its unclear why they did that. Oh and this might also fix VoLTE but I haven't tested that part yet...
device/leeco/msm8996-common/init/init_leeco_msm8996.cpp
Code:
else if (isLEX820)
{
// This is LEX820
property_set("ro.product.model", "LEX820");
property_set("persist.data.iwlan.enable", "false");
// Dual SIM
property_set("persist.radio.multisim.config", "dsds");
// Disable VoLTE
property_set("persist.radio.cs_srv_type", "1");
property_set("persist.radio.calls.on.ims", "0");
property_set("persist.radio.jbims", "0");
}
else if (isLEX829)
{
// This is LEX829
property_set("ro.product.model", "LEX829");
property_set("persist.data.iwlan.enable", "true");
// Dual SIM
property_set("persist.radio.multisim.config", "dsds");
// Enable VoLTE
property_set("persist.radio.cs_srv_type", "0");
property_set("persist.radio.calls.on.ims", "true");
property_set("persist.radio.jbims", "true");
}
I flashed today's official LOS 14.1 and noticed there isn't an option to even turn on/off VoLTE/WFC at all. I'm guessing it is disabled in the settings gui in the build?
Anyone happen to know what I need to change to make it show up?
ccheney said:
I flashed today's official LOS 14.1 and noticed there isn't an option to even turn on/off VoLTE/WFC at all. I'm guessing it is disabled in the settings gui in the build?
Anyone happen to know what I need to change to make it show up?
Click to expand...
Click to collapse
Maybe editing the settings.db and/or dialing *#*#4636#*#*. Great work so far.
whymoo said:
Maybe editing the settings.db and/or dialing *#*#4636#*#*. Great work so far.
Click to expand...
Click to collapse
Thanks!
The secret menu shows its disabled but won't let me change it but and I don't see a settings.db file in /system, is it somewhere else?
Looking *#*#4636#*#* menu it seems to be having some issues reading the SIM properly. It claims that ViLTE is unprovisioned, WiFi Calling is unprovisioned, IMS is not registered, no SIM Address Book, etc.
Searching online it seems that at least on some versions of Android that if it doesn't detect you can use the feature (VoLTE/ViLTE/WFC) it is auto hidden, so the problem may lay with the problems reading the sim.
Update: Flashed back to NA 16s and the SIM address book has entries in it so its definitely something wrong with LOS 14.1 ability to read the SIM card properly. Unfortunately the hidden menu in 16s doesn't show the VoLTE/ViLTE/WFC status like the version in LOS 14.1
With NA 16s 'Network Cell Info' shows the following:
VoLTE capable: Yes
WiFi call Available: Yes
Video call av: No
Video call en: No
So ViLTE may take extra effort to make work, but VoLTE/WFC should work once we resolve why the SIM isn't being read properly.
settings.db is supposed to be in /data/data/com.android.providers.settings/databases/settings.db but its missing. Have you tried Resurrection Remix? In the *#*#4636#*#* menu volte and wi-fi calling are enabled but they don't work.
I'll have to take a look at that. I just grabbed the 23s failed logcat output and am about to compare it to NA 16s working output to see if anything obvious sticks out.
ccheney said:
I'll have to take a look at that. I just grabbed the 23s failed logcat output and am about to compare it to NA 16s working output to see if anything obvious sticks out.
Click to expand...
Click to collapse
infrag was able to fix volte in this nougat ROM https://drive.google.com/open?id=0B4k5OpXTXcS9bVRVVkZMY2RORDQ
Here is the thread https://forum.xda-developers.com/le-max-2/development/kernel-blackscreen-leeco-x2-t3604445