bypass 5GHz hotspot restriction - Xiaomi Mi Max 3 Questions & Answers

bypass 5GHz hotspot restriction - Xiaomi Mi Max 3 Questions & Answers

ok, this has lead to a point i need some help and advice.
background:
i have unlocked and rooted mi max 3, which has twrp and magisk. because of reason i have installed dotos, which seems to work enough. i probably test back miui coming months but i have quite dissapointed to it.
5 GHz hotspot/tethering does not work. well there is e.u. and xiaomi behind it. in my knowledge e.u. does not totally ban 5GHz hotspot.
how to i bypass this 5GHz tethering restriction? (extreme measures can be proposed).

Hello, I have the same problem. My phone is blocked on China region and 5ghz does not work.

On the Global ROM and EU ROM it works and also on the custom AOSiP Pie ROM it works.

SuperL0L said:
On the Global ROM and EU ROM it works and also on the custom AOSiP Pie ROM it works.
Click to expand...
Click to collapse
for me, in global rom 5GHz hotspot did not work. eu rom is not tested. is there some kind of specialized situation where 5GHz works? (old version of global rom works, which is tested by me).
AOSiP works though. i can confirm that.

5GHz hotspots have been heavily regulated all over the world because the same frequencies are used (to an extend) for radar.
As such 5GHz hotspots are now being regulated as a "indoor-only" thing (seen from a legal point of view).
Given phones are heavily mobile devices however, it can't be guaranteed that you will be indoors at all times... due to this 5GHz hotspots are no longer a thing (except for some custom ROMs that work around those limitations).
As for AOSiP and the way I dealt with it... there is a overlay flag one can set in the framework that allows automatic 2.4GHz fallback in case your region isn't listed as a country with legal 5GHz mobile hotspots.
It still isn't 5GHz... but at least it won't throw a nasty error in case your country has banned 5GHz mobile hotspots.
This is also why the newest AOSiP builds now label the option "5GHz preferred"... because in reality its not guaranteed that the hotspot function will actually host your hotspot on a 5GHz band.
It now simply checks against the regulatory domain and uses 5GHz if its allowed in your current location... if not, it will automatically (and silently) fall back to 2.4GHz.
As for MIUI... some custom ROM spinoffs based on it fake a certain WiFi region to force the hotspot to operate on 5GHz, regardless of where you are... this is of course a legal greyzone.

MrColdbird said:
As for AOSiP and the way I dealt with it... there is a overlay flag one can set in the framework that allows automatic 2.4GHz fallback in case your region isn't listed as a country with legal 5GHz mobile hotspots.
It still isn't 5GHz... but at least it won't throw a nasty error in case your country has banned 5GHz mobile hotspots.
Click to expand...
Click to collapse
thanks for clarification. i tested AOSiP before and it worked in that time, although i didn't know how it worked, i.e. which band. i usually check for these frequencies and bands. now i have probably slightly different AOSiP and 5GHz hotspot does not work, it doesn't work any channel or band (not even that channel 12 or 13). possible reasons might be different underlying miui or different AOSiP.
MrColdbird said:
This is also why the newest AOSiP builds now label the option "5GHz preferred"... because in reality its not guaranteed that the hotspot function will actually host your hotspot on a 5GHz band.
It now simply checks against the regulatory domain and uses 5GHz if its allowed in your current location... if not, it will automatically (and silently) fall back to 2.4GHz.
Click to expand...
Click to collapse
i just wonder how android actually checks country or region. miui did have "region" setting which did lot of annoying stuff but i don't think it was actual location setting. most android system do not have location setting (those what i have used).
MrColdbird said:
As for MIUI... some custom ROM spinoffs based on it fake a certain WiFi region to force the hotspot to operate on 5GHz, regardless of where you are... this is of course a legal greyzone.
Click to expand...
Click to collapse
MrColdbird said:
5GHz hotspots have been heavily regulated all over the world because the same frequencies are used (to an extend) for radar.
As such 5GHz hotspots are now being regulated as a "indoor-only" thing (seen from a legal point of view).
Given phones are heavily mobile devices however, it can't be guaranteed that you will be indoors at all times... due to this 5GHz hotspots are no longer a thing (except for some custom ROMs that work around those limitations).
Click to expand...
Click to collapse
when i found out long time ago channel 12 or 13 in 2.4GHz band, i was pissed about incompatibility. as of now 5GHz band has lot of little variations between countries and what makes matters even more annoying is this indoor usage only, which is vague and ambiguous criteria. better option would have been to limit hotspot power. generally speaking, wifi should have global standards.

bypass is done with catches
this post is more informational rather than something to be done. i don't guarantee anything on this post and you take whole responsibility for anything happens when you do something with this information. which includes legal problems, because using these can circumvent some restrictions.
bypassing is done, however it does have some catches. hotspot may go to unwanted channels and todays settings do not have manual channel selection. i tried this on another machine as well but other machine is always wifi country code "00" (global), both before and after edit. most likely it means wifi drivers and/or wifi hardware does not support country code, only global "00". other machines is huawei p10lite was-lx1, which is based on mediatek chipset.
crucial information is, wifi-service gets country code either from sim-card or operator codes. other settings usually won't matter.
i tested mi max 3 with aosip, https://forum.xda-developers.com/mi-max-3/development/aosip-t3933754
command "iw reg get" gives information
https://bitbucket.org/JesusFreke/smali/downloads/
use smali and baksmali, some version. i used 2.4.0
!! remember to backup original file
get wifi-service.jar from device, probably /system/frame/wifi-service.jar
(do these in own directory to avoid a mess)
unzip jar file
(default goes to directory "out") (some cases odexing is required)
java -Xms1g -jar baksmali-2.4.jar d -d framework/arm64 classes.dex
find file WifiServiceImpl.smali , most likely out/com/android/server/wifi/WifiServiceImpl.smali
modify file
Code:
from this (probably varies heavily)
~~~~
.method public setCountryCode(Ljava/lang/String;)V
.registers 5
.line 2213
const-string v0, "WifiService"
new-instance v1, Ljava/lang/StringBuilder;
invoke-direct {v1}, Ljava/lang/StringBuilder;-><init>()V
const-string v2, "WifiService trying to set country code to "
invoke-virtual {v1, v2}, Ljava/lang/StringBuilder;->append(Ljava/lang/String;)Ljava/lang/StringBuilder;
invoke-virtual {v1, p1}, Ljava/lang/StringBuilder;->append(Ljava/lang/String;)Ljava/lang/StringBuilder;
invoke-virtual {v1}, Ljava/lang/StringBuilder;->toString()Ljava/lang/String;
move-result-object v1
invoke-static {v0, v1}, Landroid/util/Slog;->i(Ljava/lang/String;Ljava/lang/String;)I
.line 2214
invoke-direct {p0}, Lcom/android/server/wifi/WifiServiceImpl;->enforceConnectivityInternalPermission()V
.line 2215
iget-object v0, p0, Lcom/android/server/wifi/WifiServiceImpl;->mLog:Lcom/android/server/wifi/WifiLog;
const-string v1, "setCountryCode uid=%"
invoke-interface {v0, v1}, Lcom/android/server/wifi/WifiLog;->info(Ljava/lang/String;)Lcom/android/server/wifi/WifiLog$LogMessage;
move-result-object v0
invoke-static {}, Landroid/os/Binder;->getCallingUid()I
move-result v1
int-to-long v1, v1
invoke-interface {v0, v1, v2}, Lcom/android/server/wifi/WifiLog$LogMessage;->c(J)Lcom/android/server/wifi/WifiLog$LogMessage;
move-result-object v0
invoke-interface {v0}, Lcom/android/server/wifi/WifiLog$LogMessage;->flush()V
.line 2216
invoke-static {}, Landroid/os/Binder;->clearCallingIdentity()J
move-result-wide v0
.line 2217
iget-object v2, p0, Lcom/android/server/wifi/WifiServiceImpl;->mCountryCode:Lcom/android/server/wifi/WifiCountryCode;
invoke-virtual {v2, p1}, Lcom/android/server/wifi/WifiCountryCode;->setCountryCode(Ljava/lang/String;)Z
.line 2218
invoke-static {v0, v1}, Landroid/os/Binder;->restoreCallingIdentity(J)V
.line 2219
return-void
.end method
~~~~
to this
~~~~
.method public setCountryCode(Ljava/lang/String;)V
.registers 6
.line 2213
const-string v0, "WifiService"
const-string v3, "US"
new-instance v1, Ljava/lang/StringBuilder;
invoke-direct {v1}, Ljava/lang/StringBuilder;-><init>()V
const-string v2, "WifiService trying to set country code to "
invoke-virtual {v1, v2}, Ljava/lang/StringBuilder;->append(Ljava/lang/String;)Ljava/lang/StringBuilder;
invoke-virtual {v1, v3}, Ljava/lang/StringBuilder;->append(Ljava/lang/String;)Ljava/lang/StringBuilder;
invoke-virtual {v1}, Ljava/lang/StringBuilder;->toString()Ljava/lang/String;
move-result-object v1
invoke-static {v0, v1}, Landroid/util/Slog;->i(Ljava/lang/String;Ljava/lang/String;)I
.line 2214
invoke-direct {p0}, Lcom/android/server/wifi/WifiServiceImpl;->enforceConnectivityInternalPermission()V
.line 2215
iget-object v0, p0, Lcom/android/server/wifi/WifiServiceImpl;->mLog:Lcom/android/server/wifi/WifiLog;
const-string v1, "setCountryCode uid=%"
invoke-interface {v0, v1}, Lcom/android/server/wifi/WifiLog;->info(Ljava/lang/String;)Lcom/android/server/wifi/WifiLog$LogMessage;
move-result-object v0
invoke-static {}, Landroid/os/Binder;->getCallingUid()I
move-result v1
int-to-long v1, v1
invoke-interface {v0, v1, v2}, Lcom/android/server/wifi/WifiLog$LogMessage;->c(J)Lcom/android/server/wifi/WifiLog$LogMessage;
move-result-object v0
invoke-interface {v0}, Lcom/android/server/wifi/WifiLog$LogMessage;->flush()V
.line 2216
invoke-static {}, Landroid/os/Binder;->clearCallingIdentity()J
move-result-wide v0
.line 2217
iget-object v2, p0, Lcom/android/server/wifi/WifiServiceImpl;->mCountryCode:Lcom/android/server/wifi/WifiCountryCode;
invoke-virtual {v2, v3}, Lcom/android/server/wifi/WifiCountryCode;->setCountryCode(Ljava/lang/String;)Z
.line 2218
invoke-static {v0, v1}, Landroid/os/Binder;->restoreCallingIdentity(J)V
.line 2219
return-void
.end method
~~~~
point is to add one register, that is used instead temporary ones. register has string "US" or other country.
repack
mv classes.dex classes.dex.original-backup
java -Xms1g -jar smali-2.4.0.jar a -o classes.dex out
jar -cvf wifi-service.jar classes.dex
transfer file back to device. did you remember backup just in case!
information is based on https://forum.xda-developers.com/pixel/themes/mod-wifi-country-code-fix-root-required-t3558044

Related

[CALLING ALL Devs/Advanced Users][HELP NEEDED] Let's overclock S5360!

Hello,the title describes this thread's reason.
i need help oc'ing this device.
let's start.
In arch/arm/mach-bcm215xx/board-totoro.c,i found some intersting lines
Code:
static struct regulator_init_data dldo3_init_data = {
.constraints = {
.min_uV = 1800000,
.max_uV = 3000000,
.valid_ops_mask = REGULATOR_CHANGE_VOLTAGE |
REGULATOR_CHANGE_STATUS,
.always_on = 0,
.boot_on = 0,
and several such lines.But nowhere did i find clock frequencies(only voltages)
also,i found this-
Code:
#if defined(CONFIG_TARGET_LOCALE_AUS_TEL)
static u32 TempAdcTable[] = { 775,721,664,602,541,479,420,366,315,270,230,196,166,141,119,100,93,88,};
#else
static u32 TempAdcTable[] = { 786,732,674,612,550,488,428,373,322,276,236,201,171,145,123,104,97,91,};
#endif
static u32 TempDegreeTable[] ={-10,-5, 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 63,65,67,};
wonder what this could be?

another intesting folder is arch/arm/plat-bcmap

very interesting.
*trying to absorb the lines of code*

Anyone????

c'mon eaglerazor123 and pratyush.creed!
and here in something interesting in clock-21553.c
Code:
static u32 clk_armahb_reg_to_arm11_freq_mapping[] = {
FREQ_MHZ(52),
FREQ_MHZ(156),
FREQ_MHZ(104),
FREQ_MHZ(104),
FREQ_MHZ(156),
FREQ_MHZ(13),
FREQ_MHZ(26),
FREQ_MHZ(312),
FREQ_MHZ(312),
FREQ_MHZ(156),
FREQ_MHZ(156),
FREQ_MHZ(312),
FREQ_MHZ(312),
FREQ_MHZ(468),
FREQ_MHZ(468),
FREQ_MHZ(624)
};
but the catch is that i can't find the OPP/PLL for 832 Mhz(that's what the phone is clocked at,right?)

sakindia123 said:
c'mon eaglerazor123 and pratyush.creed!
and here in something interesting in clock-21553.c
Code:
static u32 clk_armahb_reg_to_arm11_freq_mapping[] = {
FREQ_MHZ(52),
FREQ_MHZ(156),
FREQ_MHZ(104),
FREQ_MHZ(104),
FREQ_MHZ(156),
FREQ_MHZ(13),
FREQ_MHZ(26),
FREQ_MHZ(312),
FREQ_MHZ(312),
FREQ_MHZ(156),
FREQ_MHZ(156),
FREQ_MHZ(312),
FREQ_MHZ(312),
FREQ_MHZ(468),
FREQ_MHZ(468),
FREQ_MHZ(624)
};
but the catch is that i can't find the OPP/PLL for 832 Mhz(that's what the phone is clocked at,right?)
Click to expand...
Click to collapse
I am no dev, but yeah..
Processor : ARMv6-compatible processor rev 5 (v6l)
BogoMIPS : 832.90
Features : swp half thumb fastmult vfp edsp java
CPU implementer : 0x41
CPU architecture: 6TEJ
CPU variant : 0x1
CPU part : 0xb36
CPU revision : 5
Hardware : BCM21553 ThunderbirdEDN31 platform
Revision : 0000
Serial : 0000000000000000
$

sakindia123 said:
c'mon eaglerazor123 and pratyush.creed!
and here in something interesting in clock-21553.c
Code:
static u32 clk_armahb_reg_to_arm11_freq_mapping[] = {
FREQ_MHZ(52),
FREQ_MHZ(156),
FREQ_MHZ(104),
FREQ_MHZ(104),
FREQ_MHZ(156),
FREQ_MHZ(13),
FREQ_MHZ(26),
FREQ_MHZ(312),
FREQ_MHZ(312),
FREQ_MHZ(156),
FREQ_MHZ(156),
FREQ_MHZ(312),
FREQ_MHZ(312),
FREQ_MHZ(468),
FREQ_MHZ(468),
FREQ_MHZ(624)
};
but the catch is that i can't find the OPP/PLL for 832 Mhz(that's what the phone is clocked at,right?)
Click to expand...
Click to collapse
Lol! I'm Not a Kernel Dev! I Only Compiled ICS kernel! I'll Look Into it! Just Pm'd a recognzd dev frnd of mine! I'll let you know!

eaglerazor123 said:
Lol! I'm Not a Kernel Dev! I Only Compiled ICS kernel! I'll Look Into it! Just Pm'd a recognzd dev frnd of mine! I'll let you know!
Click to expand...
Click to collapse
What do u mean?compile ics kernel,not a kernel dev......

sakindia123 said:
What do u mean?compile ics kernel,not a kernel dev......
Click to expand...
Click to collapse
I Compiled ICS Kernel from source Once or twice! i Didn't Add OC To It Or Some other features to it! So,I'm N00b at Kernels ! I Told You i have contacted someone! So i'll def look into it!

If it's qualcomm processor, take a look in the acuclock file under /arch/arm/mach-msm

it's broadcom processor.. new soc...

qualcomm's are the easiest to overclock,just a speed hack.
Galaxy Y uses the 'Totoro' board,which is bcm21553
The overclocking code whould be found in plat-bcmap/bcm_cpufreq.c,and it does call a cpu freq table,but i can't find that darn table.

sakindia123 said:
qualcomm's are the easiest to overclock,just a speed hack.
Galaxy Y uses the 'Totoro' board,which is bcm21553
The overclocking code whould be found in plat-bcmap/bcm_cpufreq.c,and it does call a cpu freq table,but i can't find that darn table.
Click to expand...
Click to collapse
erm.. this? https://github.com/sakindia123/Cranium_S5360/blob/master/common/drivers/cpufreq/freq_table.c

noobwithgalaxyy said:
erm.. this? https://github.com/sakindia123/Cranium_S5360/blob/master/common/drivers/cpufreq/freq_table.c
Click to expand...
Click to collapse
no
it usually is somewhere in arch/arm/(board-name)

sakindia123 said:
no
it usually is somewhere in arch/arm/(board-name)
Click to expand...
Click to collapse
just wanted to help
btw, I went through most of the files and only direct mention to frequencies was in the governor file /mach/bcm21553_cpufreq_gov.h :/

hi friend
i notice we have already got overclock on 5360 ...
but i'm currently trying to work on S6120 (i.e. Galaxy Y Duos)
it uses same processor bcm-21553
so overclocking and enabling 624mhz etc should work here too
i just want to know what changes are need to clock-21553.c file to get other frequencies working??
i have developed only snapdragon kernels till now and the bcm clock file is giving me headaches
any help will be appreciated
the kernel sources for S6102 i have pushed to github (as of now, without any changes at all made to original sources..totally untouched)
https://github.com/championswimmer/kCernel-S6120

vivekalady has already succed oc sgy to 900 mhz but all the result shows that the overall performance is decreased. the same result is also observed in mar-oc's test. when the freq is set to 1ghz it run a lot slower.

kurotsugi said:
vivekalady has already succed oc sgy to 900 mhz but all the result shows that the overall performance is decreased. the same result is also observed in mar-oc's test. when the freq is set to 1ghz it run a lot slower.
Click to expand...
Click to collapse
lets see...maybe my kernel can fare better...
I'll work with vivek's and maroc's help only as I'm new to broadcomm SoC ...
we have no dev at S6120 .... so we dearly need a custom kernel there.... to add tun/tap, ext support, governors and schedulers blah blah...
Sent from my X10S using xda premium

championswimmer said:
lets see...maybe my kernel can fare better...
I'll work with vivek's and maroc's help only as I'm new to broadcomm SoC ...
we have no dev at S6120 .... so we dearly need a custom kernel there.... to add tun/tap, ext support, governors and schedulers blah blah...
Sent from my X10S using xda premium
Click to expand...
Click to collapse
Our kernel cant work on yours???
Sent from my GT-S5360 using XDA

hell_lock said:
Our kernel cant work on yours???
Sent from my GT-S5360 using XDA
Click to expand...
Click to collapse
nope has to compiled separately....
the cpu portion is same but ril (read gsm, data, hspa etc etc) is not same as it has dual active module... so needs separate compiling
Sent from my X10S using xda premium

Hardware/driver info gathering for ICS/JB

In response to the ICS leak, I have abandoned this thread in favor of a different approach. I'm leaving it here purely for archival purposes.
I have something stewing. I'll make a thread when I'm ready.
Compiling a list of the drivers required and making sure we've got them all checked off; that's the first step to making an ICS port happen, right? I'm giving it the old gentleman try.
All input is nice; I'm a complete noob to kernel-level Android. I'm familiar with troubleshooting drivers on x86 but I don't know the buses and whatnot involved here.
KEY: RED == we don't know enough about the item to find/make an appropriate driver; YELLOW == enough info is available to write a driver but we haven't found/made one yet; GREEN == A driver that SHOULD work for ICS/JB is already available.
So, all the drivers we need:
Video. Tegra 2 Ventana. Driver Available.
Audio. Wolfson WM8994. Driver Available.
Power/volume buttons. Dedicated interrupts. Even if a driver is not available, it should be trivial to do, unless I'm naive of some major ARM architecture quirk.
Flash/microSD access. CWM can do this, so we know how to do it, but is there a 3.0 driver available or are we gonna need a kernel hacker?
Cell radio. Appears to be a Samsung custom proprietary something or other, because they wrote their own damn driver for it. I'm gonna be digging through the Samsung source release for the kernel bits, but we have a big ugly problem in the form of two closed source binary blobs in the pipeline from Android to hardware named libsec-ril.so and libsecril-client.so. We need to either a) get the official blobs to somehow work correctly in the ICS/JB environment (potentially very hard), b) replace these blobs entirely (even harder), c) wait for official straight-from-Samsung ICS/JB versions (yeah, when's that happening again?) or d) substitutde official blobs from another phone (which is likely to not work at all).
USB device mode. Fairchild FSA9480. Galaxy Nexus has the same chip so I'm going to assume a driver is available.
Physical keyboard. Interrupt 215 is mapped to an "STMPE1801". A quick peek at the datasheet strongly suggests this is our keyboard controller. A datasheet is available, but I have yet to find evidence of a 3.0 driver. It may conform to some standard -- does anyone know more about this chip or ones like it?
Touchscreen. Atmel MXT224. An official driver is available on GitHub.
Cameras. Not yet identified. A simply stupid amount of V4L drivers are included in the GB kernel config.gz. Hunting down which ones are actually used may take some time. "CONFIG_TEGRA_CAMERA" looks promising though.
Battery/Charger controller. /proc/interrupts shows a MAX8907C while dmesg shows a MAX8922. Both chips have appeared in devices that have officially gone ICS, so we should be good.
Wi-Fi and Bluetooth. Broadcom BCM4330, a working driver is in the 3.0 kernel tree.
GPS. The GB driver calls itself "gps_sirf" in logcat. Perhaps part of the SiRFstar family? Don't have anything more specific yet.
Accelerometer. The MPU3050 gyroscope has a second I2C port for the express purpose of attaching an accelerometer to it. That port may be empty, or there may be an accelerometer there, and that accelerometer probably wouldn't need its own driver, but no guarantees; there's no easy way to tell until we've actually booted a kernel and seen what the MPU3050 driver gives us.
Proximity and ambient light sensors. Capella CM3663. 3.0 driver is available.
Compass/Orientation Sensor. Asahi Kasei AK8975. 3.0 driver is in the tree.
Gyroscope. InvenSense MPU3050. A 2.6 driver is available; not sure about 3.0.
MHL/HDMI. Yeah, you know what? I'll tackle that when I have everything else more-or-less working.
Saving this and this for me to take a closer look at later.
Wikipedia claims we have a gyroscope a magnetometer HDMI... really? Can anyone confirm this? And what the heck is MHL? There *is* an interrupt mapped for it...
/proc/ioports revealed that we have a Broadcom BCM4330, which is a Wi-Fi plus Bluetooth plus goddamned FM RADIO all-in-one. It apparently can transmit in FM too. If that's actually hooked up to a usable antenna... holy ****.
Here's the raw /proc/interrupts, in case more enlightened eyes grace my presence:
Code:
CPU0 CPU1
36: 150598 0 PPI tegra-avp
46: 4943342 0 PPI mmc2
51: 305330 0 PPI mmc1
52: 11794 0 PPI tegra-otg, fsl-tegra-udc
53: 335496 0 PPI ehci_hcd:usb1
61: 0 0 PPI rpc-arbsema
63: 11198199 0 PPI mmc0
70: 7880675 0 PPI tegra-i2c
73: 9025413 0 PPI timer0
74: 3059444 0 PPI timer_lp2wake
77: 0 0 PPI spdif_out
85: 6188775 0 PPI tegra-i2c
86: 70301 0 PPI stat_mon_int
99: 0 0 PPI host_status
105: 598486 0 PPI tegradc.0
106: 0 0 PPI tegradc.1
116: 1104236 0 PPI tegra-i2c
118: 16978 0 PPI max8907c
124: 80 0 PPI tegra-i2c
136: 7 0 PPI dma_channel_0
137: 0 0 PPI dma_channel_1
138: 0 0 PPI dma_channel_2
139: 615533 0 PPI dma_channel_3
140: 385356 0 PPI dma_channel_4
141: 347 0 PPI dma_channel_5
142: 1283 0 PPI dma_channel_6
143: 0 0 PPI dma_channel_7
144: 0 0 PPI dma_channel_8
145: 0 0 PPI dma_channel_9
146: 0 0 PPI dma_channel_10
147: 0 0 PPI dma_channel_11
152: 0 0 PPI tegra_cpuidle_both_idle
153: 0 0 PPI tegra_cpuidle_tear_down_cpu1
169: 441390 0 syncpt disp0_a
173: 6 0 syncpt vi_isp_1
175: 3 0 syncpt vi_isp_3
178: 577637 0 syncpt 2d_0
180: 695 0 syncpt disp0_b
182: 1890786 0 syncpt 3d
192: 238662 0 GPIO mpuirq
215: 5942 0 GPIO stmpe1801
223: 223163 0 GPIO mxt224_ts
248: 0 0 GPIO mhl_int
261: 0 0 GPIO max17043 fuel alert
276: 454855 15 GPIO akm_int
281: 29 0 GPIO fsa9480 micro USB
305: 136 0 GPIO proximity_int
321: 114 0 GPIO KEY_VOLUMEUP
322: 114 0 GPIO KEY_VOLUMEDOWN
324: 1194 0 GPIO sec_touchkey
338: 0 0 GPIO bt_host_wake_irq_handler
357: 533 0 GPIO KEY_POWER
358: 0 0 GPIO nct1008
362: 1 0 GPIO cp_act
370: 44475 0 GPIO hst_wkp
371: 98 0 GPIO HALL
417: 4 12 max8907c max8907c-vchg_f
418: 4 12 max8907c usb_phy_vbus
438: 3607 5008 max8907c rtc-alarm0
IPI: 7366740 17570126
LOC: 16779564 13867086
Err: 0
NCT1008 is a temperature sensor. Battery temp, I'm guessing.
Here's /proc/ioports. Nothing too interesting.
Code:
00000000-00000000 : sim_det
0000004d-0000004d : bcm4330_nshutdown_gpio
00000073-00000073 : cp_on
00000080-00000080 : hsic_sus
00000083-00000083 : cp_req
00000085-00000085 : hsic_act
0000008c-0000008c : slv_wkp
00000091-00000091 : bcm4330_btwake_gpio
000000a8-000000a8 : hsic_en
000000a9-000000a9 : ap_act
000000aa-000000aa : cp_act
000000b1-000000b1 : bcm4330_nreset_gpio
000000b2-000000b2 : hst_wkp
000000b9-000000b9 : cp_rst

Z-DeviceTest lists the accelermator as "MPL accel" and vendor as Invensource, if that helps.

bobbinthreadbare said:
Z-DeviceTest lists the accelermator as "MPL accel" and vendor as Invensource, if that helps.
Click to expand...
Click to collapse
Taking a closer look, I see that the MPU3050 has an I2C port intended for an accelerometer. Hmmm.... Well, updated in any case.

roothorick said:
And what the heck is MHL? There *is* an interrupt mapped for it...
Click to expand...
Click to collapse
MHL stands for Mobile High Definition Link, it takes Micro USB out to an adapter which has a power cable connected and then outputs through a male-male HDMI cord to your TV mirroring what's on the screen. It's pretty sweet!
http://www.monoprice.com/products/p...=10833&cs_id=1083314&p_id=8675&seq=1&format=2

what about the so called NFC chip, did you see any indication to that in your digging of drivers need?

No NFC so not needed I think

roothorick said:
[*]Physical keyboard. Interrupt 215 is mapped to an "STMPE1801". A quick peek at the datasheet strongly suggests this is our keyboard controller. A datasheet is available, but I have yet to find evidence of a 3.0 driver. It may conform to some standard -- does anyone know more about this chip or ones like it?
Click to expand...
Click to collapse
The keyboard chip is indeed a STMPE1801, controlled by drivers/input/keyboard/stmpe-keypad.c (in Sammy sources for 2.6.36).
There is even a version in the main Linux tree: http://git.kernel.org/?p=linux/kern...=blob;f=drivers/input/keyboard/stmpe-keypad.c
However, the files differ and I did not try using the mainline version on my Glide.

taiber2000 said:
what about the so called NFC chip, did you see any indication to that in your digging of drivers need?
Click to expand...
Click to collapse
Neither Samsung, AT&T, nor Rogers have ever claimed that the Glide has NFC, and I haven't found any hint of otherwise.

Tested with my s3 and no dice. If there happens to be it's definitely not on GB. My battery in my s3 has NFC printed on the back

I927UCLG9 - ICS leak, coming your way soon.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IMM76D
ro.build.display.id=IMM76D
ro.build.version.incremental=UCLG9
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Fri Jul 27 23:37:33 KST 2012
ro.build.date.utc=1343399853
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-121
ro.build.tags=release-keys
ro.product.model=SGH-I927
ro.product.brand=samsung
ro.product.name=SGH-I927
ro.product.device=SGH-I927
ro.product.board=SGH-I927
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=I927UCLG9
ro.build.hidden_ver=I927UCLG9
ro.build.changelist=970642
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SGH-I927
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SGH-I927-user 4.0.4 IMM76D UCLG9 release-keys
ro.build.fingerprint=samsung/SGH-I927/SGH-I927:4.0.4/IMM76D/UCLG9:user/release-keys
ro.build.characteristics=default
# end build properties
dalvik.vm.heapsize=64m
ro.opengles.version = 131072
wifi.interface=wlan0
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
#rild.libpath=/system/lib/libril-icera.so
#rild.libargs=-e wwan0
persist.sys.storage_preload=1
#ril.fastdormancy_to=50
# Icera fild
#modem.fild.rootdir=/data/rfs
#modem.fild.blocksize=65528
#modem.fild.baudrate=3500000
#modem.fild.hif=0
#modem.fild.coredump=enabled
#modem.fild.coredumpdir=/data/rfs/data/debug
#modem.powercontrol=disabled
#modem.power.device=/sys/class/gpio/gpio169/value,0,1
#ro.ril.devicename=/dev/ttyACM1
#
# ADDITIONAL_BUILD_PROPERTIES
#
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.ms=android-att-us
ro.com.google.clientidbase.am=android-att-us
ro.com.google.clientidbase.yt=android-samsung
ro.com.google.clientidbase.gmm=android-samsung
ro.error.receiver.default=com.samsung.receiver.error
ro.monkey=0
ro.com.google.gmsversion=4.0_r3
ro.config.ringtone=ATT_Firefly.ogg
ro.config.notification_sound=S_Sherbet_Default_message.ogg
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.kernel.qemu=0
ro.secdirenc=true
ro.secsddecryption=true
ro.secfulldirenc=true
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

If you don't mind me asking, where did you get that info?

Aquethys said:
If you don't mind me asking, where did you get that info?
Click to expand...
Click to collapse
from the oneclick exe sitting on my hdd

You own a glide?
Mines ready for crazy testing. Running aokp job on s3, all I need for happiness. Lol

Aquethys said:
You own a glide?
Mines ready for crazy testing. Running aokp job on s3, all I need for happiness. Lol
Click to expand...
Click to collapse
I don't have a glide, someone asked if there was an ICS leak for the Glide, I asked and it magically appeared on my hdd

For all
http://forum.xda-developers.com/showthread.php?t=1590614
If we can get proprietary files ics will boot. Problem is i think it has to be ics proprietary so we will need leak

Aquethys said:
For all
http://forum.xda-developers.com/showthread.php?t=1590614
If we can get proprietary files ics will boot. Problem is i think it has to be ics proprietary so we will need leak
Click to expand...
Click to collapse
It will be leaked soon.
127.93 MB of 665.39 MB (19%) Speed: 8.46 MB/sec
It's uploading very fast
leak thread:
http://forum.xda-developers.com/showthread.php?p=30182275

Thinks working/not working on the leaked rom:
Video. Working (Tested: YouTube-App)
Audio. Working (Tested: YouTube-App, System Sounds)
Power/volume buttons. Working.
Flash/microSD access. Internal /sdcard seems woking. Currently I have no external sdcard for testing
Cell radio. This means GSM/Edge/3g? GSM & Edge are working (Germany). No 3g connection arround here because of my provider...
USB device mode. I can access /sdcard from windows explorer
Physical keyboard. Keys working, Backlight not
Touchscreen. Working.
Cameras. Both Working, also flashlight
Battery/Charger controller. Phone is currently charging.
Wi-Fi and Bluetooth. Wifi: Yes. BT: No device for testing
GPS. I was out for some minutes but couldn't get a gps-fix (gps status app)
Accelerometer. GPS-Status app changes the value when moving the phone...
Proximity and ambient light sensors. Don't know how to test
Compass/Orientation Sensor. Orientation changes by rotating the phone, GPS Status app shows N/S/W/E Orientation
Gyroscope. Don't know how to test
MHL/HDMI. Not owning a HDMI adapter
Supported Languages are: English, German, Espanol, French, Italiano, (something like chinese)

Roeni said:
Thinks working/not working on the leaked rom:
Video. Working (Tested: YouTube-App)
Audio. Working (Tested: YouTube-App, System Sounds)
Power/volume buttons. Working.
Flash/microSD access. Internal /sdcard seems woking. Currently I have no external sdcard for testing
Cell radio. This means GSM/Edge/3g? GSM & Edge are working (Germany). No 3g connection arround here because of my provider...
USB device mode. I can access /sdcard from windows explorer
Physical keyboard. Keys working, Backlight not
Touchscreen. Working.
Cameras. Both Working, also flashlight
Battery/Charger controller. Phone is currently charging.
Wi-Fi and Bluetooth. Wifi: Yes. BT: No device for testing
GPS. Not tested yet
Accelerometer. Don't know how to test
Proximity and ambient light sensors. Don't know how to test
Compass/Orientation Sensor. Orientation changes by rotating the phone
Gyroscope. Don't know how to test
MHL/HDMI. Not owning a HDMI adapter
Click to expand...
Click to collapse
There is an app called GPS Status, the icon is a orange antenna, you can test accel, gps, light sensor, gyro, compass with it

Roeni said:
Thinks working/not working on the leaked rom:
Video. Working (Tested: YouTube-App)
Audio. Working (Tested: YouTube-App, System Sounds)
Power/volume buttons. Working.
Flash/microSD access. Internal /sdcard seems woking. Currently I have no external sdcard for testing
Cell radio. This means GSM/Edge/3g? GSM & Edge are working (Germany). No 3g connection arround here because of my provider...
USB device mode. I can access /sdcard from windows explorer
Physical keyboard. Keys working, Backlight not
Touchscreen. Working.
Cameras. Both Working, also flashlight
Battery/Charger controller. Phone is currently charging.
Wi-Fi and Bluetooth. Wifi: Yes. BT: No device for testing
GPS. I was out for some minutes but couldn't get a gps-fix (gps status app)
Accelerometer. GPS-Status app changes the value when moving the phone...
Proximity and ambient light sensors. Don't know how to test
Compass/Orientation Sensor. Orientation changes by rotating the phone, GPS Status app shows N/S/W/E Orientation
Gyroscope. Don't know how to test
MHL/HDMI. Not owning a HDMI adapter
Supported Languages are: English, German, Espanol, French, Italiano, (something like chinese)
Click to expand...
Click to collapse
Just Tested With AT&T
Everything That You've tested works for it, I tested External And its fine but It Changes The Way your music was set up by giving every song and artist which is really confusing when its the same artist, 3G/4G Works, and yep except theres trouble with The slide down notifications and sometimes they won't open, other than that its working.

I can confirm as well that backlight does not work on the physical keyboard. All sensors are functioning as expected.
Facial recog. is working as expected. Developer's tools mostly work - enabling screen updates causes a soft restart.
I have experienced no soft restarts otherwise.

Your opinion about v6 Supercharger.

Hi Um... I've known about this v6 Supercharger for a while now, and I used it before. I just want to know what you guys think about this modification. Also, how does the seeder app work? Does it even do anything? Finally, I would appreciate it if you guys could answer this one question: What kernal setting do I use? The DONT PANIC or the PANIC ones? Thanks.(Using perseus 31.2)

The seeder app works on the same exact premise as you sitting on the John and taking a dump all day, thus causing your toilet to flush faster.

Skripka said:
The seeder app works on the same exact premise as you sitting on the John and taking a dump all day, thus causing your toilet to flush faster.
Click to expand...
Click to collapse
That is an amazing explanation. As for V6, I have used it but haven't seen any performance improvements from it. The 3G tweaks from the 3G turbocharger script work quite well. If you are going to run V6 and are selecting the kernel options I recommend the first one. I believe it is rock solid or something like that. Every kernel for this phone is stable. Now if you are experiencing random reboots and such you could try the middle option.
Sent from my SPH-L900 using Tapatalk 2

Im using v6, 3g and KAK and use the custom oom from v6 keeps alot of background crap cleaned up I hate when a game I havent played in a few days is hanging out in the background for no reason. If you use KAK skip the I/O tweaks.
I like to break stuff!

Brightness goes down after overheating

When im playing some heavy game after a while my brightness goes to 85% and i cant move it to 100% because overheating,is there
A way to stay at 100% all the time?

Bill_windows said:
When im playing some heavy game after a while my brightness goes to 85% and i cant move it to 100% because overheating,is there
A way to stay at 100% all the time?
Click to expand...
Click to collapse
1) Edit /system/etc/thermald-8064.conf
or
2) change to a kernel that uses an alternate thermal control(IntelliThermal, Bricked thermal)
It's doing that for a reason though...

What exacly i must edit ?Some lines?and where can i find a kernel for stock rom?

Bill_windows said:
What exacly i must edit ?Some lines?and where can i find a kernel for stock rom?
Click to expand...
Click to collapse
I'm mobile and I can't find a tutorial on changing the settings but info is out there. They are at bottom of file under patherrm or something like that, it's not intuitive.
AICbeta2 will give you intellithermal. Have to switch to it in something like trickster mod.
http://forum.xda-developers.com/showpost.php?p=54482330&postcount=229
Uninstaller is a few post later.

aicjofs said:
I'm mobile and I can't find a tutorial on changing the settings but info is out there. They are at bottom of file under patherrm or something like that, it's not intuitive.
AICbeta2 will give you intellithermal. Have to switch to it in something like trickster mod.
http://forum.xda-developers.com/showpost.php?p=54482330&postcount=229
Uninstaller is a few post later.
Click to expand...
Click to collapse
Thanks a lot,i would like to know what i need to modify in that file when you got time,thanks a lot

Bill_windows said:
Thanks a lot,i would like to know what i need to modify in that file when you got time,thanks a lot
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=51061076
Under [pa_therm0] you will see 2 lines under the threshold temps
Code:
actions cpu+gpu+battery+hotplugcpu+lcd+fps cpu+gpu+battery+hotplugcpu+lcd+fps cpu+gpu+battery+hotplugcpu+lcd+fps cpu+gpu+battery+hotplugcpu+lcd cpu+gpu+battery+hotplugcpu+lcd cpu+gpu+battery+hotplugcpu+lcd cpu+gpu+battery+hotplugcpu+lcd
Code:
action_info 1728000+400000000+1+0+255+60 1512000+400000000+2+2+231+60 1242000+400000000+3+2+219+54 1242000+320000000+3+2+200 1134000+320000000+3+2+185 1134000+200000000+4+2+185 1134000+128000000+4+3+145
First line is the actions it takes, i.e CPU throtlle, GPU throttle. You would be concerned with lcd.
Second line is what value it sets at each threshold. You can see lcd gets stepped down from 255(max brightness) to 231, then 219, 200, 185, 145. Edit what you want back to 255. Like I said previous these values are there for a reason so if some damage occurs you only will have yourself to blame. The tablet is overheating and you are editing the protective actions. I would recommend at first just changing the 231 to 255, and if it continues to be an issue 219 to 255.

aicjofs said:
http://forum.xda-developers.com/showthread.php?p=51061076
Under [pa_therm0] you will see 2 lines under the threshold temps
Code:
actions cpu+gpu+battery+hotplugcpu+lcd+fps cpu+gpu+battery+hotplugcpu+lcd+fps cpu+gpu+battery+hotplugcpu+lcd+fps cpu+gpu+battery+hotplugcpu+lcd cpu+gpu+battery+hotplugcpu+lcd cpu+gpu+battery+hotplugcpu+lcd cpu+gpu+battery+hotplugcpu+lcd
Code:
action_info 1728000+400000000+1+0+255+60 1512000+400000000+2+2+231+60 1242000+400000000+3+2+219+54 1242000+320000000+3+2+200 1134000+320000000+3+2+185 1134000+200000000+4+2+185 1134000+128000000+4+3+145
First line is the actions it takes, i.e CPU throtlle, GPU throttle. You would be concerned with lcd.
Second line is what value it sets at each threshold. You can see lcd gets stepped down from 255(max brightness) to 231, then 219, 200, 185, 145. Edit what you want back to 255. Like I said previous these values are there for a reason so if some damage occurs you only will have yourself to blame. The tablet is overheating and you are editing the protective actions. I would recommend at first just changing the 231 to 255, and if it continues to be an issue 219 to 255.
Click to expand...
Click to collapse
Thanks alot appreciate that

watch out Samsung is being sneaky.

Samsung is sneaky about syncing their Samsung calendar from your Google account. when you open up Google calendar it shows in the screenshot below but it shows that you need to enable sync for your Google account calendar. when you enable this enable Samsung's calendar from your Google account calendar. I turned off Samsung calendar sync and when I open up Google calendar it said you need to sync your account and I enable it thinking that Google account calendar is not synced. so I had a suspicion to check Samsung's account settings sync for Samsung calendar, lo and behold it was freaking enabled. I turned it off go to Google calendar and I dismissed the notification of need to sync to my Gmail account and I open up Samsung's account under settings sync and Samsung calendar is not enabled then I go to Google account under Android settings, lo and behold my Google account calendar sync is enabled which is what I want. sneaky sly snake in the grass.
Android 11 one ui 3.1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Android 11 one UI 3.1 Samsung tab S7 plus 5G versus Samsung S10 plus Android 11 one UI 3.0.

Samsung has a lot of things under the hood that even disabling those system apps via adb is not enough to stop them.
Back then I disabled Game Manager as I thought it would get in the way with gameplay (I don't have any use of it), but turned out disabling the app alone was not enough. Some of its functionalities remain active as the logcat keeps spamming stuffs related to it.
In overall, the system is spamming a lot of logcats in a speed I have never seen before, which I suspect the performance issues I'm having might be related to this.
It's possible that some Samsung secret functions are masquerading as, or hiding behind some supposedly "innocent" system apps (in the latter case, disabling it would also break core system functions)... Since the logcat itself doesn't really tell me much about which "real" app was spamming the logcats in question, I cannot be really sure.

LSS4181 said:
Samsung has a lot of things under the hood that even disabling those system apps via adb is not enough to stop them.
Back then I disabled Game Manager as I thought it would get in the way with gameplay (I don't have any use of it), but turned out disabling the app alone was not enough. Some of its functionalities remain active as the logcat keeps spamming stuffs related to it.
In overall, the system is spamming a lot of logcats in a speed I have never seen before, which I suspect the performance issues I'm having might be related to this.
It's possible that some Samsung secret functions are masquerading as, or hiding behind some supposedly "innocent" system apps (in the latter case, disabling it would also break core system functions)... Since the logcat itself doesn't really tell me much about which "real" app was spamming the logcats in question, I cannot be really sure.
Click to expand...
Click to collapse
horrible, samsung has best high performance devices besides apple out there crunching other brands.

I firewall block many Samsung and Android apks with Karma Firewall.
Most are rarely needed.
Samsung is a real pain in this respect.
Be glad you don't have Bixby which I completely disabled. No.
It's EULA is like signing your soul over to the devil.

i have bixby default installed but not sigmed in.

blackhawk said:
I firewall block many Samsung and Android apks with Karma Firewall.
Most are rarely needed.
Samsung is a real pain in this respect.
Be glad you don't have Bixby which I completely disabled. No.
It's EULA is like signing your soul over to the devil.
Click to expand...
Click to collapse
It's better to do some detailed tests if possible and make a list. I think Samsung is way too sneaky about things a system app would do as disabling the apps on the surface do not really disable the functionality itself (at least that's what the system logcats told me), in order to deter people from disabling them.
I do have a Samsung account but haven't used it on the tablet. I'm using it on my watch, which is currently paired with my phone that uses microG. At least this is something good from Samsung, that I'm finally able to ditch GApps on my phone for good.

LSS4181 said:
It's better to do some detailed tests if possible and make a list. I think Samsung is way too sneaky about things a system app would do as disabling the apps on the surface do not really disable the functionality itself (at least that's what the system logcats told me), in order to deter people from disabling them.
I do have a Samsung account but haven't used it on the tablet. I'm using it on my watch, which is currently paired with my phone that uses microG. At least this is something good from Samsung, that I'm finally able to ditch GApps on my phone for good.
Click to expand...
Click to collapse
Knox can't be fully disabled.
KMLS is always running; stopping it kills it for a while.
Samsung Payment is untouchable... damn crap app. Problem is they are set as embedded system administrators.
The Google verification system is even worse. I'm not worried about the phone being stolen; I'm worried about getting locked out by it.

blackhawk said:
Knox can't be fully disabled.
KMLS is always running; stopping it kills it for a while.
Samsung Payment is untouchable... damn crap app. Problem is they are set as embedded system administrators.
The Google verification system is even worse. I'm not worried about the phone being stolen; I'm worried about getting locked out by it.
Click to expand...
Click to collapse
Aegis is a better solution for 2FA codes. It has more features, and supports everything Google Authenticator could offer.
From what I read you should be able to secure (add a master password) and move (backup/restore) your vaults around with Aegis, so as long as you have a backup of the vault and a device you can access, you shouldn't be locked out.
I was originally thinking Samsung would do well enough to keep people on stock with Android 11 update... seeing how it's turning out now makes me even more want to switch to a custom ROM/GSI (in turn giving up whatever good Knox might be able to offer)... just that I'm yet to hear any success stories of GSI for such tablets from someone reputable.

LSS4181 said:
Aegis is a better solution for 2FA codes. It has more features, and supports everything Google Authenticator could offer.
From what I read you should be able to secure (add a master password) and move (backup/restore) your vaults around with Aegis, so as long as you have a backup of the vault and a device you can access, you shouldn't be locked out.
I was originally thinking Samsung would do well enough to keep people on stock with Android 11 update... seeing how it's turning out now makes me even more want to switch to a custom ROM/GSI (in turn giving up whatever good Knox might be able to offer)... just that I'm yet to hear any success stories of GSI for such tablets from someone reputable.
Click to expand...
Click to collapse
Not rooted so just working in the system. Rooting seems too time intensive and not having done it, perplexing as hell to flash successfully.
I do prefer to run as system administrator though on my Windows machines so the temptation is there

TL;DR: Guess I really need to be careful about Samsung in some ways...
Okay... just unlocked and rooted this tablet.
Although I can safely disable most bloated apps using this script (root not required at this point), there are some untouchable ones, especially Game Optimization Service/GOS, which I suspect it responsible for all the game issues.
You cannot disable com.samsung.android.game.gos because some Samsung service keeps re-enabling it, in a malware-like behavior.
I added these into NanoDroid overlay so the package in question can be banished to nothingness:
Code:
GameHome
GameOptimizingService
GameTools_Dream
This way the GOS is gone for good and I don't see it in the package list nor in most of the logcat. However, the logcat still mentions something like this, means the "malware" lies much deeper into the system.
Code:
02-11 17:13:42.447 1133 1541 D GameManagerService: GameService deos not exist
So the GameManagerService is not the three packages in question, with the GOS package gone, it can do nothing but complain about the package it wants "deos [sic] not exist".
For now it's one fewer app interfering with games, but I still worry about the performance as the stock firmware is spamming logs like crazy. Just keep adb logcat on for about 10-15 secs I got a whopping 20MB of logcat!

LSS4181 said:
TL;DR: Guess I really need to be careful about Samsung in some ways...
Okay... just unlocked and rooted this tablet.
Although I can safely disable most bloated apps using this script (root not required at this point), there are some untouchable ones, especially Game Optimization Service/GOS, which I suspect it responsible for all the game issues.
You cannot disable com.samsung.android.game.gos because some Samsung service keeps re-enabling it, in a malware-like behavior.
I added these into NanoDroid overlay so the package in question can be banished to nothingness:
Code:
GameHome
GameOptimizingService
GameTools_Dream
This way the GOS is gone for good and I don't see it in the package list nor in most of the logcat. However, the logcat still mentions something like this, means the "malware" lies much deeper into the system.
Code:
02-11 17:13:42.447 1133 1541 D GameManagerService: GameService deos not exist
So the GameManagerService is not the three packages in question, with the GOS package gone, it can do nothing but complain about the package it wants "deos [sic] not exist".
For now it's one fewer app interfering with games, but I still worry about the performance as the stock firmware is spamming logs like crazy. Just keep adb logcat on for about 10-15 secs I got a whopping 20MB of logcat!
Click to expand...
Click to collapse
wow.
I read about the script thanks!

This time I tried the Root method (which utilizes a Magisk module to systemlessly replace files, and can complement my NanoDroid overlay) so all the Samsung stuffs in question can be banished from the system.
I did not add other lists (namely the GFAM ones) as I might need to manually install some of those stuffs back and they don't appear to be behaving malware-like (that keep being re-enabled by something elses), just the Samsung list.
However, the logcat still has mentions to the GameManagerService and it keeps scanning for the packages in question.
Code:
02-12 11:34:45.759 1125 1125 D GameManager.DatabaseHelper: loadPkgDataFromDb(). entry size: 1
02-12 11:34:45.760 1125 1125 I GameManagerService: PkgUpdateReceiver, : ctor
02-12 11:34:45.760 1125 1125 I GameManagerService: SecFamilyPkgChangeReceiver, : ctor
02-12 11:34:45.760 1125 1125 D GameManagerService: Now checking pkgs enabled...
02-12 11:34:45.760 1125 1125 D GameManagerService: com.samsung.android.game.gos does not exist
02-12 11:34:45.760 1125 1125 D GameManagerService: isPkgEnabled(), begin
02-12 11:34:45.760 1125 1125 D GameManagerService: isPkgEnabled(), com.samsung.android.game.gamehome does not exist.
02-12 11:34:45.760 1125 1125 D GameManagerService: isPkgInstalled(), begin
02-12 11:34:45.760 1125 1125 D GameManagerService: isPkgInstalled(), com.samsung.android.game.gametools does not exist.
02-12 11:34:45.761 1125 1125 I GM:SystemHelper: ctor
02-12 11:34:45.761 1125 1125 D GameManagerService$Lifecycle: onStart
02-12 11:34:45.762 600 1404 I servicemanager: Adding 'u:r:system_server:s0' service (gamemanager:1125)
02-12 11:34:45.762 1125 1125 I SystemServer: GameManagerService Started
02-12 11:34:45.762 1125 1125 D SystemServerTiming: GameManagerService took to complete: 11ms
02-12 11:34:45.762 1125 1125 I SystemServer: GameSDKService
So there's definitely something hiding very deep (as system services) in stock ROM that monitors and re-enables certain other services if possible, should the users attempts to disable them. For now, as I've systemlessly banished them, it could do nothing but complain (for now).
PS: Wow... looked at the PID and found out the "malware" in question turned out to be system_server. Seriously, this behavior totally shocked me, to insert malware-like functions there...
Code:
gts7xl:/ $ ps -p 1125
USER PID PPID VSZ RSS WCHAN ADDR S NAME
system 1125 838 20193644 565008 0 0 S system_server
In this case there's really an immediate need for a ROM/GSI because this practice is way too scary if abused... Not to mention the performance improvement might be limited as the size for a 10-second logcat is only reduced by about one megabyte.
blackhawk said:
Samsung Payment is untouchable... damn crap app. Problem is they are set as embedded system administrators.
Click to expand...
Click to collapse
EDIT: Just noticed there were some follow-ups in that... Now I understood why Samsung Payment is untouchable...

At least all my Samsung devices, once I bought them, if I can't put them LineageOS, then I would disable everything from Google.
No problems from my side.
If you are very privacy concern, then you shouldn't have any Google app installed. If you need something from Google Play store, there is an alternative called Aurora Store.

LSS4181 said:
This time I tried the Root method (which utilizes a Magisk module to systemlessly replace files, and can complement my NanoDroid overlay) so all the Samsung stuffs in question can be banished from the system.
I did not add other lists (namely the GFAM ones) as I might need to manually install some of those stuffs back and they don't appear to be behaving malware-like (that keep being re-enabled by something elses), just the Samsung list.
However, the logcat still has mentions to the GameManagerService and it keeps scanning for the packages in question.
Code:
02-12 11:34:45.759 1125 1125 D GameManager.DatabaseHelper: loadPkgDataFromDb(). entry size: 1
02-12 11:34:45.760 1125 1125 I GameManagerService: PkgUpdateReceiver, : ctor
02-12 11:34:45.760 1125 1125 I GameManagerService: SecFamilyPkgChangeReceiver, : ctor
02-12 11:34:45.760 1125 1125 D GameManagerService: Now checking pkgs enabled...
02-12 11:34:45.760 1125 1125 D GameManagerService: com.samsung.android.game.gos does not exist
02-12 11:34:45.760 1125 1125 D GameManagerService: isPkgEnabled(), begin
02-12 11:34:45.760 1125 1125 D GameManagerService: isPkgEnabled(), com.samsung.android.game.gamehome does not exist.
02-12 11:34:45.760 1125 1125 D GameManagerService: isPkgInstalled(), begin
02-12 11:34:45.760 1125 1125 D GameManagerService: isPkgInstalled(), com.samsung.android.game.gametools does not exist.
02-12 11:34:45.761 1125 1125 I GM:SystemHelper: ctor
02-12 11:34:45.761 1125 1125 D GameManagerService$Lifecycle: onStart
02-12 11:34:45.762 600 1404 I servicemanager: Adding 'u:r:system_server:s0' service (gamemanager:1125)
02-12 11:34:45.762 1125 1125 I SystemServer: GameManagerService Started
02-12 11:34:45.762 1125 1125 D SystemServerTiming: GameManagerService took to complete: 11ms
02-12 11:34:45.762 1125 1125 I SystemServer: GameSDKService
So there's definitely something hiding very deep (as system services) in stock ROM that monitors and re-enables certain other services if possible, should the users attempts to disable them. For now, as I've systemlessly banished them, it could do nothing but complain (for now).
PS: Wow... looked at the PID and found out the "malware" in question turned out to be system_server. Seriously, this behavior totally shocked me, to insert malware-like functions there...
Code:
gts7xl:/ $ ps -p 1125
USER PID PPID VSZ RSS WCHAN ADDR S NAME
system 1125 838 20193644 565008 0 0 S system_server
In this case there's really an immediate need for a ROM/GSI because this practice is way too scary if abused... Not to mention the performance improvement might be limited as the size for a 10-second logcat is only reduced by about one megabyte.
EDIT: Just noticed there were some follow-ups in that... Now I understood why Samsung Payment is untouchable...
Click to expand...
Click to collapse
its a sh*t show imho.

blackhawk said:
Knox can't be fully disabled.
KMLS is always running; stopping it kills it for a while.
Samsung Payment is untouchable... damn crap app. Problem is they are set as embedded system administrators.
The Google verification system is even worse. I'm not worried about the phone being stolen; I'm worried about getting locked out by it.
Click to expand...
Click to collapse
How is Pay untouchable? I uninstalled it easliy with no problems. Along with Bixby

Greatness83 said:
How is Pay untouchable? I uninstalled it easliy with no problems. Along with Bixby
Click to expand...
Click to collapse
How?* It's set as an invisible system administrator.
*without root excess that is

blackhawk said:
How? It's set as an invisible system administrator.
Click to expand...
Click to collapse
Plus, Samsung would lock you out if you dare to touch anything related to it.
EDIT: I think it depends on how you debloat. If you debloat them all at once (I used this debloater's Root/Magisk mode to do so) you would be fine, so some Samsung system apps probably have watchdogs to ensure the presence of each other.

even xda forums website pissing me off with the bouncing up and down pages wtf?
anyways samsung is at it again. removed natural blue on the volume control to grey wtf
am I the only one going ???
samsung and xda's forum.

Hitti2 said:
even xda forums website pissing me off with the bouncing up and down pages wtf?
anyways samsung is at it again. removed natural blue on the volume control to grey wtf
am I the only one going ???
samsung and xda's forum.
Click to expand...
Click to collapse

Develop Bugs

welcome