Develop Bugs

[MOD] Disable the increasing ring on Galaxy S - JVT

Get rid of the increasing ring when someone calls you. As long as I can remember, most samsung phones had a "feature" where when you receive a call, the ringtone will gradually fade in to the volume that you have set. This mod will get rid of that annoying fade in and allow your ringtone to play at the volume YOU set it to!
REMEMBER~! Your phone needs to be deodexed for this to work!!! Also, this mod is version specific! Only use the modified APK with the same deodexed ROM. You have been warned.
Here is the fixed Phone.apk I created for firmware JPK:
http://forum.xda-developers.com/showpost.php?p=8515539&postcount=49
Instructions: (Thanks goes to Ferdimage for the Flight Mode trick!)
MAKE SURE your firmware is deodexed and you are using the right fix to the proper firmware!!
1. Put the phone into "Flight Mode" either by holding power while the device is on and selecting Flight Mode from the submenu, or by selecting Flight Mode from the Settings menu.
2. Use a terminal, or root explorer, or any app you want to copy Phone.apk to /system/app/. Make sure the file is Phone.apk instead of phone.apk. Some people copied it as phone.apk (lowercase P) and in the linux world, both files would exist, and the Android OS would use Phone.apk instead of phone.apk. --(If you still get a FC, don't worry, just proceed to step 3.)
3. Reboot the phone.
Attached is the Phone.apk for JPO firmware. I made it using Doc's 7.5 ROM.
UPDATE: Added Phone.apk for JPU firmware.
UPDATE 12/31/2010: The deodexed file from Doc's JPY ROM and the JPY kitchen did NOT work, so I deodexed the file myself this time. Here is the Phone.apk for JPY firmware!!!
Happy new year everyone! Enjoy!
Anyone who wants to thank me, feel free to buy me a beer!! Enjoy!
PS: Sorry for the delay, but I was one of the guys who bought a i9000M phone with the failing internal SD [replaced 4 times!!]. I just got my phone back last night and went straight to work to build you guys this working Phone.apk for JPY. Hope you guys appreciate it as much as I do!!
UPDATE 12/5/2011:
Wow, its been almost a year since I last used my i9000. I decided to pick it up again and update it to JVT, so... here's the Phone.apk made by me for JVT. DEODEXED only! It's CWM this time!! Enjoy!

YG007 said:
I know this is on the Galaxy S I9000 General section of the forum, but this seems like its going to need a lot of dev people to find a solution to this one. The increasing ring "feature" should be an option and not enforced on people who do not want this feature on.
So, I propose we put our heads together and find a solution to this problem.
My .02, for what its worth (probably not much.. ), but when I owned the Samsung u900 (soul), the fix was to go into the service menu, under SPK Config Menu -> AV-QTune (MP3) Menu -> SPK MP3 Vol. Menu -> Then change one of the lower volume levels (I used volume level 1) to a dB that is high. The reason for this was, the increasing ring method was only implemented at higher volume settings. So, changing the ring volume to a lower volume setting where the increasing ring method implementation wasn't used and setting THAT volume to a high volume level solved all my problems.
... but, those menu items do not exist in the Samsung Galaxy S service menu.
Also, the thing I notice here is the only volume where the increasing ring does not get implemented is volume 1. (which still might be implemented since the volume is so quiet). So, for the SGS, the increasing ring method might be implemented all the time, which will make it harder to disable, who knows.
Hopefully someone can figure this one out. I've been poking around the device and even the sound files to see if theres anything about the device modifying the volume, but I guess I'm not looking in the right spot.
Click to expand...
Click to collapse
+1.
I really hate the ascending ringtone "feature"

any development on this?

Yes I'd like to see this too, increasing ring should definitely be OPTIONAL.

I don't like it either

I hate it so much!! What idiot made it as a feature?!
My temporary solution was to use the app called Volume Locker. The delay should be "0". But... In that case you have the same audio settings all the time. If you want to use Profile manager with different audio settings you have to switch off Volume Locker first. Every time. Not good.
Anyone who indeed kan solve the problem??

+1
All of the samsung phones have this feature (problem) ...
Omnia , Omnia II and now Galaxy S ....
I really looking for a way to disable this annoying feature !!!!

+1 This has been bugging me for a long time.. I hope someone can come up with a solution...
Sent from my GT-I9000 using XDA App

Uhm... let's tell Supercurio, maybe he can do something about it in Voodoo Sound.

Anybody ??????

I did some poking around... I still didn't solve the problem with the increasing ring, but I did find something that might be useful.
This is in asound.conf, which is in the /system/etc/ folder:
Code:
pcm.AndroidPlayback_Earpiece_ringtone {
type hooks
slave.pcm {
type hw
card 0
device 0 # Must be of type "digital audio playback"
}
hooks.0 {
type ctl_elems
hook_args [
# Enable audio output from the DSP
{name "Playback Path" value 6} # 0:OFF 1:RCV 2:SPK 3:HP 4:DUAL 5:BT 6:RING_SPK 7:RING_HP 8:RING_DUAL 9:EXTRA_DOCK_SPEAKER
]
}
}
pcm.AndroidPlayback_Speaker_ringtone {
type hooks
slave.pcm {
type hw
card 0
device 0 # Must be of type "digital audio playback"
}
hooks.0 {
type ctl_elems
hook_args [
# Enable audio output from the DSP
{name "Playback Path" value 6} # 0:OFF 1:RCV 2:SPK 3:HP 4:DUAL 5:BT 6:RING_SPK 7:RING_HP 8:RING_DUAL 9:EXTRA_DOCK_SPEAKER
]
}
}
pcm.AndroidPlayback_Headset_ringtone {
type hooks
slave.pcm {
type hw
card 0
device 0 # Must be of type "digital audio playback"
}
hooks.0 {
type ctl_elems
hook_args [
# Enable audio output from the DSP
{name "Playback Path" value 7} # 0:OFF 1:RCV 2:SPK 3:HP 4:DUAL 5:BT 6:RING_SPK 7:RING_HP 8:RING_DUAL 9:EXTRA_DOCK_SPEAKER
]
}
}
pcm.AndroidPlayback_Bluetooth_ringtone {
type hooks
slave.pcm {
type hw
card 0
device 0 # Must be of type "digital audio playback"
}
hooks.0 {
type ctl_elems
hook_args [
# Enable audio output from the DSP
{name "Playback Path" value 4} # 0:OFF 1:RCV 2:SPK 3:HP 4:DUAL 5:BT 6:RING_SPK 7:RING_HP 8:RING_DUAL 9:EXTRA_DOCK_SPEAKER
]
}
}
pcm.AndroidPlayback_Speaker_Headset_ringtone {
type hooks
slave.pcm {
type hw
card 0
device 0 # Must be of type "digital audio playback"
}
hooks.0 {
type ctl_elems
hook_args [
# Enable audio output from the DSP
{name "Playback Path" value 8} # 0:OFF 1:RCV 2:SPK 3:HP 4:DUAL 5:BT 6:RING_SPK 7:RING_HP 8:RING_DUAL 9:EXTRA_DOCK_SPEAKER
]
}
}
I tried changing earpiece and speaker ringtone to 2, headset to 3, and speaker_headset to 4. Rebooted, and tried calling myself... still has the increasing ring. So, the sound is being altered before it outputs to the sound card it seems.
I hope this points SOMEONE into the right direction, as I really don't like having this increasing ring "feature" as it is really annoying.

Heh, I just added a second of silence in the beginning of my ringtone. Still would be nice to know if it could be disabled.

Hello,
I've just found a (not easy) way to disable increasing ring.
This involves using Apk Manager to backsmali Phone.apk,
which then have to be replaced by patched version, either by root access or creation of update.zip.
Procedure:
1. Get your Phone.apk (\system\app\Phone.apk) and copy it to computer.
2. Use Apk Manager to decompile it.
3. Open folder with Phone source (<Apk Manager folder>\projects\Phone.apk\smali\com\android\phone).
4. Open file Ringer$1.smali with your favourite text editor.
5. Find line that reads:
Code:
invoke-virtual {v1, v5, v4, v3}, Landroid/media/AudioManager;->setStreamVolume(III)V
6. Delete this line, save the file.
7. Compile Phone.apk, put it back to phone.
8. Enjoy constant-volume ringtones.
Side effects:
- currently not known
- if you have problem decompiling Phone.apk, >here< is the solution
Maybe somebody will make pre-patched packages, I'm currently using JM5
so I can only provide one for this firmware.

Anybody feel like trying this out ? Thanks though... much appreciated...!
Sent from my GT-I9000 using XDA App

Just gave it a try but i stuck in the part you have to edit the file. Actually after successfully decompiling without errors, it seems that i dont have "smali" folder under \Phone.Apk\ I also manually search for the file "Ringer$1.smali" (the one that needs to get edited) but didn't find it also :/
Edit. JM8

vipercubic said:
Just gave it a try but i stuck in the part you have to edit the file. Actually after successfully decompiling without errors, it seems that i dont have "smali" folder under \Phone.Apk\
Click to expand...
Click to collapse
Are you sure that decompilation was successful?
Check log.txt file in Apk Manager directory.
Maybe you just unpacked it, not decompiled?
I'm attaching patched JM5 Phone.apk, for those who want to try it.

optional or not ... i like this feature ... or is it a bug ?

the_ozyrys said:
Are you sure that decompilation was successful?
Check log.txt file in Apk Manager directory.
Maybe you just unpacked it, not decompiled?
Click to expand...
Click to collapse
Well i'm not really sure But i saw no errors when running decompile (just did it again)
There's my log
Code:
--------------------------------------------------------------------------
|’œ« 06/10/2010 -- 14:30:14,31|
--------------------------------------------------------------------------
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b07)
Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode, sharing)
ƒœ¤ ™¨βŸž΅œ C:\apk_manager_4.9\place-apk-here-for-modding\../place-apk-here-for-modding/signedPhone.apk
ƒœ¤ ™¨βŸž΅œ C:\apk_manager_4.9\place-apk-here-for-modding\../place-apk-here-for-modding/unsignedPhone.apk
I: Loading resource table...
W: Skipping "android" package group
I: Decoding resources...
I: Loading resource table from file: C:\Documents and Settings\User\apktool\framework\1.apk
I: Loading resource table from file: C:\Documents and Settings\User\apktool\framework\2.apk
I: Copying assets and libs...

I don't see "backsmaling" in this log.
Did you choose option number 9?
This is the one you should use.

the_ozyrys said:
Are you sure that decompilation was successful?
Check log.txt file in Apk Manager directory.
Maybe you just unpacked it, not decompiled?
I'm attaching patched JM5 Phone.apk, for those who want to try it.
Click to expand...
Click to collapse
Unable to decompile ... tried options 9 and 10 ... Even looked at that link which you posted but that seems a little too much for my n00b brain to comprehend ...
when i click option 9 i get:
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b07)
Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode, sharing)
'adb' is not recognized as an internal or external command,
operable program or batch file.
Could Not Find C:\Documents and Settings\Khambatta\My Documents\Downloads\apk_manager_4.9\place-apk-here-for-modding\../place-apk-here-for-modding/signedPhone.apk
Could Not Find C:\Documents and Settings\Khambatta\My Documents\Downloads\apk_manager_4.9\place-apk-here-for-modding\../place-apk-here-for-modding/unsignedPhone.apk
I: Loading resource table...
W: Skipping "android" package group
I: Decoding resources...
I: Loading resource table from file: C:\Documents and Settings\Khambatta\apktool\framework\1.apk
W: Could not decode attr value, using undecoded value instead: ns=android, name=textAppearance, value=0x0207000d
W: Could not decode attr value, using undecoded value instead: ns=android, name=textAppearance, value=0x0207000e
W: Could not decode attr value, using undecoded value instead: ns=android, name=textAppearance, value=0x0207000f
W: Could not decode attr value, using undecoded value instead: ns=android, name=textAppearance, value=0x0207000f
And when i click option 10 the log shows:
Exception in thread "main" brut.androlib.AndrolibException: java.io.FileNotFoundException: decompile (The system cannot find the file specified)
at brut.androlib.res.AndrolibResources.installFramework(Unknown Source)
at brut.androlib.Androlib.installFramework(Unknown Source)
at brut.apktool.Main.cmdInstallFramework(Unknown Source)
at brut.apktool.Main.main(Unknown Source)
Caused by: java.io.FileNotFoundException: decompile (The system cannot find the file specified)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(Unknown Source)
at java.util.zip.ZipFile.<init>(Unknown Source)
... 4 more
'and' is not recognized as an internal or external command,
operable program or batch file.
Exception in thread "main" brut.androlib.AndrolibException: Arsc file contains zero or multiple packages
at brut.androlib.res.decoder.ARSCDecoder$ARSCData.getOnePackage(Unknown Source)
at brut.androlib.res.AndrolibResources.installFramework(Unknown Source)
at brut.androlib.Androlib.installFramework(Unknown Source)
at brut.apktool.Main.cmdInstallFramework(Unknown Source)
at brut.apktool.Main.main(Unknown Source)
'and' is not recognized as an internal or external command,
operable program or batch file.
Any ideas ?

[Q] Nokia Lumia 735 notification led

Hello everybody!!! Someone know how it's possible edit the registry to activate the notification led in lumia 735?? thanks!!

find the registry first and share with us

Actually support for the M8 for Windows would probably be easier to implement considering how HTC's diag app can access the notification LED, which shows the support is not only firmware based but also into the OS, one way or another.
I'm not sure if the 735 has any support right now, but if you are running Redstone, run the SSH CMD and go over to the M8 for windows notification LED project, there is a file to see whether the LED is supported.

AlvinPhilemon said:
Actually support for the M8 for Windows would probably be easier to implement considering how HTC's diag app can access the notification LED, which shows the support is not only firmware based but also into the OS, one way or another.
I'm not sure if the 735 has any support right now, but if you are running Redstone, run the SSH CMD and go over to the M8 for windows notification LED project, there is a file to see whether the LED is supported.
Click to expand...
Click to collapse
Here is output from drvapp.exe on Lumia 735 (14393.67):
Code:
C:\Data\Users\Public\Documents>drvapp.exe
drvapp.exe
HWN Driver testing app..........
Finding list size.....
Finding device path.....
Creating file........
CreateFile OK!
Gathering information about HWN devices.......
Calling DeviceIoControl.....
DeviceIoControl1 returned:
Bytes returned: 48
DeviceIoControl2 returned
------------------------------------------------
Payload size: 48
Payload version: 1
Requests number: 1
------------------------------------------------
Information about HWN devices:
Device 0
Type 1
Off-On-Blink 0
Settings 0 0
Settings 1 0
Settings 2 0
Settings 3 0
Settings 4 0
Settings 5 4294967295
------------------------------------------------
------------------------------------------------
Trying to set state......
Intensity 100
On-Off 1
Trying to enable......
Bytes written 48
DeviceIoControl Returned 1
GetLastError returned
------------------------------------------------
Maybe it will be helpful.

krevedko said:
Here is output from drvapp.exe on Lumia 735 (14393.67):
Code:
C:\Data\Users\Public\Documents>drvapp.exe
drvapp.exe
HWN Driver testing app..........
Finding list size.....
Finding device path.....
Creating file........
CreateFile OK!
Gathering information about HWN devices.......
Calling DeviceIoControl.....
DeviceIoControl1 returned:
Bytes returned: 48
DeviceIoControl2 returned
------------------------------------------------
Payload size: 48
Payload version: 1
Requests number: 1
------------------------------------------------
Information about HWN devices:
Device 0
Type 1
Off-On-Blink 0
Settings 0 0
Settings 1 0
Settings 2 0
Settings 3 0
Settings 4 0
Settings 5 4294967295
------------------------------------------------
------------------------------------------------
Trying to set state......
Intensity 100
On-Off 1
Trying to enable......
Bytes written 48
DeviceIoControl Returned 1
GetLastError returned
------------------------------------------------
Maybe it will be helpful.
Click to expand...
Click to collapse
Hi, so what can I say from the output, that:
1. A device is only one and it is LED. Unknown device would be 0, vibrator would be 2.
2. It's turned off. On would be 1 and blink mode would be 2.
This is all the driver can show
Also, could you test updated version. Would be nice to see output

djtonka said:
find the registry first and share with us
Click to expand...
Click to collapse
Here it is!!

lukjok said:
Hi, so what can I say from the output, that:
1. A device is only one and it is LED. Unknown device would be 0, vibrator would be 2.
2. It's turned off. On would be 1 and blink mode would be 2.
This is all the driver can show
Also, could you test updated version. Would be nice to see output
Click to expand...
Click to collapse
Updated version output:
Code:
C:\Data\Users\Public\Documents>drvapp.exe
drvapp.exe
HWN Driver testing app..........
Finding list size.....
Finding device path.....
Creating file........
CreateFile error: The system cannot find the path specified.
3

canapo92 said:
Here it is!!
Click to expand...
Click to collapse
Open LED subkey

You can put any key.

I Have a Lumia 730 running latest insider build #14915, interop unlocked
Can you guide me the steps how to enable led notifications.
Lumia 730 does have a led sensor, so if u tell me where to start to enable i'll do all things

ipradyu said:
I Have a Lumia 730 running latest insider build #14915, interop unlocked
Can you guide me the steps how to enable led notifications.
Lumia 730 does have a led sensor, so if u tell me where to start to enable i'll do all things
Click to expand...
Click to collapse
Thats not how it works -_-

canapo92 said:
Here it is!!
Click to expand...
Click to collapse
LED keys aren't there. Those are of no use.
The ones that are necessary is in :
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Nocontrol\LedAlert]
"LedHwAvailable"="dword:0000001"
If that and a number of other keys exist then the OS will indicate LED support. If not then it doesn't.

mapping keys (recentapps, application) in keyboard layout file

I am trying to map the recent apps and applications key on samsung bluetooth keyboard to teh recnet apps and apps buttons, just like the app_switch capactive button. The Home button and back button the the physical keyboard already work. Following the below guide, one would modify /system/usr/keylayout/Generic.kl with relevant scan codes
Code:
#http://www.thriveforums.org/forum/toshiba-thrive-development/9626-how-create-customized-keylayout-any-usb-bluetooth-keyboard-rooted.html
#/system/usr/keylayout/Generic.kl
key 704 RECENTAPPS
key 705 APPLICATION
and save the file as /system/usr/keylayout/Vendor_04e8_Product_a006.kl, where the keyboard's vendor and product id are found by
Code:
cat /proc/bus/input/devices
; on my device this gets the following
I: Bus=0005 Vendor=04e8 Product=a006 Version=0001
N: Name="Samsung Bluetooth Keyboard EJ-CT800"
P: Phys=
S: Sysfs=/devices/virtual/misc/uhid/input11
U: Uniq=
H: Handlers=sysrq event11 sec_debug
B: PROP=0
B: EV=12001b
B: KEY=147 0 0 0 0 0 0 0 0 0 0 0 0 0 0 10003 2010007 ff9f317a c14057ff febeffdf ffefffff ffffffff fffffffe
B: ABS=ffffff00 0
B: MSC=10
B: LED=1f
However, this does not work; niether does copying the appropriate keylayout file Vendor_04e8_Product_a006.kl directly from samsung stock rom, which shows the key scancoes above. Instead, it seems some people got it working by changing the source code related to whievever key code you desire and compile android.policy.jar ike this:
evilisto said:
platform/frameworks/base/policy/src/com/android/internal/policy/impl/PhoneWindowManager.java
from :
Code:
} else if (keyCode == KeyEvent.KEYCODE_APP_SWITCH) {
if (down && repeatCount == 0) {
showOrHideRecentAppsDialog(RECENT_APPS_BEHAVIOR_SHOW_OR_DISMISS);
}
return -1;
}
to :
Code:
} else if (keyCode == KeyEvent.KEYCODE_APP_SWITCH) {
if (down && repeatCount == 0 && !keyguardOn) {
try {
mStatusBarService.toggleRecentApps();
} catch (RemoteException e) {
Slog.e(TAG, "RemoteException when showing recent apps", e);
}
}
return -1;
}
Click to expand...
Click to collapse
It seems simple enough, but i am not compilng yet; it would be useful to have this for cm roms, but not sure about compatibility with different rom versions (i.e., cm-11, 12, 13, 14); if someone builds this, perhaps comment on this... thanks
would someone like to compile this and try, as i'm sure a lot of people have this keyboard? :laugh:

err, found my error with the recentapps button; making it app_switch instead of recentapps makes it work, so it only remains to make the application button, which opens the app drawer. i ohpe this interests somebody, but if not whatever

I have the same issue. I guess it's a rom compatibility thing. My Samsung Bluetooth keyboard works fine except for recent apps key (F2) then F3 and F4 don't work as in when you hit those keys, nothing happens at all. I hope we can find a workaround for this.

Same issue here as well.
I am using as well the Original keyboard of tab s (EC-JT800) with aicp ROM 7.1. (preatty good i would say) but there are several issues with the hardware keyboard like:
change between 2-3 languages (no keyboard mapping)
app switching (F2) and app drawer (F3) buttons are not working
caps lock light not turn on
lang does nothing
etc.
I have tried another ROM which is based on the samsung stock firmware: IronRom V3.2 ( https://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107) and i noticed that the keyboard is fully working as expected. Therefore i assume that the keyboard layout is the original from samsung incorporated into the ROM. If we copy this layout it will work on a 7.* ROM version ?
Update: Searching inside the above mentioned ROM i found the file Vendor_04e8_Product_a006.kl which i am planning to copy over. The thing is that the system filesystem is read only.
Any Idea ?
---------- Post added at 15:07 ---------- Previous post was at 14:33 ----------
I research and it seems that ssome of the mapping missings are :
key 368 LANG
# F2 F3 F4
key 704 RECENTAPPS
key 705 APPLICATION
key 706 SIP_ON_OFF
# LEDs
led 0x01 CAPS_LOCK
Will copy the file over from the other ROM and update about the results.

I'm trying to do the same here, with Lineage OS on an SM-T800.
As already said, the stock keylayout, which includes something like this:
Code:
key 704 RECENTAPPS
key 705 APPLICATION
key 706 SIP_ON_OFF
key 707 VOICESEARCH
key 708 QPANEL_ON_OFF
key 710 SFINDER
key 712 MULTI_WINDOW
does not work on non-stock ROMs. I can also verify that setting scancode 704 to keycode APP_SWITCH, does work.
Indeed, these keycodes (RECENTAPPS, etc) are not mentioned in the KeyEvent android developers page, nor can I find a substitute for the missing ones.
For the language switch, I tried running inside an adb shell the command
Code:
input keyevent LANGUAGE_SWITCH
and sure enough, I was able to switch language on my keyboard.
I then checked to see what is emitted when I press the "LANG" key on the keyboard, and it seems that it's just SHIFT+SPACE. So I went ahead and defined a keychar file (/system/user/keychars/Vendor_04e8_Product_a006.kcm) where I asked for Shift+Space to send the LANGUAGE_SWITCH keycode. No luck
As a temporary solution, I've mapped the "keyboard" key (just right of the Function key) to LANGUAGE_SWITCH, and that is working fine.
So my keylayout for now includes:
Code:
key 704 APP_SWITCH
key 706 LANGUAGE_SWITCH
Last (but not least), I have no clue how to drive the led for caps-lock. I tried all led numbers from 0x00 to 0x1f in the keylayout file, nothing seems to be doing the trick. I also cannot find any proper documentation on that, to understand how it works.
I'll keep digging. I really don't get why the key character map file didn't work for setting the language. At least that part should be feasible.

Quite strange.
I have installed the IronRom V3.2 (https://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t297310 ) and the keyboard layout is working fine !!! Functions keys, language key and the caps lock led are all working. Keep in mind that this ROM is based on stock and is running android 6.0.1
I wonder if a copy of the files /system/user/keychars/* to a newer android version might work. I also noticed on other nougat versions (AICP, LIneage) that the keyboard settings are completely different that Marshmallow.

ale_kons said:
Quite strange.
I have installed the IronRom V3.2 (https://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t297310 ) and the keyboard layout is working fine !!! Functions keys, language key and the caps lock led are all working. Keep in mind that this ROM is based on stock and is running android 6.0.1
I wonder if a copy of the files /system/user/keychars/* to a newer android version might work. I also noticed on other nougat versions (AICP, LIneage) that the keyboard settings are completely different that Marshmallow.
Click to expand...
Click to collapse
Your link seems to be wrong.
If this ROM is based on samsung stock, then my guess would be that this is what makes it work with the keyboard, not necessarily the android version. Did you use the ROM with the stock kernel or the "ironstock" kernel?

I guess I have the stock kernel, have to check though

My kernel version is: 3.4.113-IronStock_SM-T800_V3.2
Current ROM: IronRom V3.2_T800
As mentioned above the keyboard is working as it was supposed too.

Gamepad detection

I have this issue since I started using custom roms.
The issue is my phone detects a gamepad which I have never owned one and I don't think there is any nearby. It makes some of the games unplayable (takes over the controls). I couldn't find anything on the internet like this
(I did clean flash xiaomi.eu) PLEASE HELP!!

If necessary I can root my phone

Same thing

To test you can try flats

Bump

I don't know why doesn't any of the developers try to help!!

It's really weird... Could you send a screenshot?

cyker31 said:
It's really weird... Could you send a screenshot?
Click to expand...
Click to collapse
For what

Sorry I am not English but it says "to shoot press R2"
"modern combat 5"

Bardbarian, bottom row show A, B, X, Y, when the gamepad is not plug to the phone

Matehoo said:
Bardbarian, bottom row show A, B, X, Y, when the gamepad is not plug to the phone
Click to expand...
Click to collapse
Yeah same on me

I am currently on miui9 7.9.21 xiaomi.eu release.
When i plug the xbox 360 controller via usb otg, the phone doesnt register the conected controller. But phone in games and apps acts like the controller is conected.
And the developers are currently on holidays, so the fix will not be released soon.

I found something like this on connected (gamepad tester):
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="qpnp_pon"
P: Phys=qpnp_pon/input0
S: Sysfs=/devices/virtual/input/input0
U: Uniq=
H: Handlers=event0 cpufreq
B: PROP=0
B: EV=3
B: KEY=14000000000000 0
I: Bus=0000 Vendor=0000 Product=0003 Version=2065
N: Name="synaptics_dsx"
P: Phys=synaptics_dsx/touch_input
S: Sysfs=/devices/soc/c179000.i2c/i2c-5/5-0020/input/input1
U: Uniq=
H: Handlers=mdss_fb kgsl mouse0 event1 cpufreq
B: PROP=2
B: EV=b
B: KEY=420 0 0 40008800 4000000000 0
B: ABS=263800000000003
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="hbtp_vm"
P: Phys=
S: Sysfs=/devices/virtual/input/input2
U: Uniq=
H: Handlers=mouse1 event2 cpufreq
B: PROP=2
B: EV=7
B: KEY=30000 0 0 0 0
B: REL=3
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="uinput-goodix"
P: Phys=
S: Sysfs=/devices/virtual/input/input3
U: Uniq=
H: Handlers=event3 cpufreq
B: PROP=0
B: EV=3
B: KEY=3100000 40000800 1c16c100000000 0
I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="gpio-keys"
P: Phys=gpio-keys/input0
S: Sysfs=/devices/soc/soc:gpio_keys/input/input4
U: Uniq=
H: Handlers=event4 cpufreq
B: PROP=0
B: EV=23
B: KEY=8000000000000 0
B: SW=1
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="msm8998-tasha-snd-card Headset Jack"
P: Phys=ALSA
S: Sysfs=/devices/soc/1711a000.sound-9335/sound/card0/input5
U: Uniq=
H: Handlers=event5
B: PROP=0
B: EV=21
B: SW=780d4
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="msm8998-tasha-snd-card Button Jack"
P: Phys=ALSA
S: Sysfs=/devices/soc/1711a000.sound-9335/sound/card0/input6
U: Uniq=
H: Handlers=event6 cpufreq
B: PROP=40
B: EV=3
B: KEY=3e 400000000 0 0 0
I: Bus=0006 Vendor=0000 Product=0000 Version=0000
N: Name="uinput-fpc"
P: Phys=
S: Sysfs=/devices/virtual/input/input7
U: Uniq=
H: Handlers=event7 cpufreq
B: PROP=0
B: EV=b
B: KEY=1f000000000000 0 0 16c000000000 0
B: ABS=4

Synaptics_dsx seemed so suspicious

I asked miui forum a member said I should use global rom. But I don't know if I will lock my bootloader if I flash it via TWRP please let me know if it locks

I found the problem.. It was not something with the roms that I used it was related to miui 7.9.22 firmware. How do I know you ask.. First I downloaded global stable (8.5.1.0) it didn't have any bugs about gamepad but then I flashed miui global beta(7.9.22) and the gamepad issue came back. Hope developers fix the firmware

So anyone found any way to fix it? Im on Version: V9.2.3.0.OCAMIEK and i have this problem,anyone?

Same issue in miui 13 android 12 i can't play many of my favourite games like real racing 3 , gangster vegas , dead trigger 2 etc because of auto gamepad detection without connecting anything to the phone even my bluetooth is off iam rooted now is there any tweaks to disable it so that i can use touch controls to play my favourite games

[EOL][SODP][ROM][AOSP][XZ2, XZ2C, XZ3] SonyAOSP 12.1

Central project page
[EOL][SODP][ROM][AOSP][XZ2, XZ2C, XZ3] SonyAOSP 12.1 [Alpha]
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc) :) Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you! Official site...
forum.xda-developers.com

09.02.2022
android-12.0.0_r28 (February security patchlevel)
OEMv1c support
Click to expand...
Click to collapse

14.02.2022
hotfix for the bootloop
Click to expand...
Click to collapse

30.03.2022
android-12.1.0_r1 (March security patchlevel)
Click to expand...
Click to collapse

MartinX3 said:
30.03.2022
Click to expand...
Click to collapse
a question why you don't upload photos of the user interface, and what options are available, I currently have the Xperia XZ2 Compact, and I'm thinking of changing the rom for this one based on Android 12.1

Carljaynp03 said:
a question why you don't upload photos of the user interface, and what options are available, I currently have the Xperia XZ2 Compact, and I'm thinking of changing the rom for this one based on Android 12.1
Click to expand...
Click to collapse
It's 90% aosp.
Please report any bug in the linked issue tracker.

MartinX3 said:
It's 90% aosp.
Please report any bug in the linked issue tracker.
Click to expand...
Click to collapse
any direct contact number for more information I am new in the world of custom roms, I want help, I can contribute with the work done please

Carljaynp03 said:
any direct contact number for more information I am new in the world of custom roms, I want help, I can contribute with the work done please
Click to expand...
Click to collapse
Thank you, please follow the link in the first post.
There it is also in the first post.

12.04.2022
android-12.1.0_r3 (April security patchlevel)
Click to expand...
Click to collapse

Bug....the touch does not work and it seems to reboot intermittently

Mint rhfo said:
Bug....the touch does not work and it seems to reboot intermittently
Click to expand...
Click to collapse
Bug....report?

MartinX3 said:
Bug....report?
Click to expand...
Click to collapse
Yeah! It's Bug report!

Mint rhfo said:
Yeah! It's Bug report!
Click to expand...
Click to collapse
I don't see a valid bug report according to the instructions.
Or you claim that I'm god and know everything.
But maybe I'm god, who knows.

Hello,
Android Custom Rom noob here. Just picked up a XPERIA zx2 Compact and wanted to use this guide to flash a more current Android on the phone (came with Android10).
I followed some guides and was able to unlock my bootloader and enable USB Debugging. I used adb platform tools to boot the device in fastboot mode and flashed the files as described in the instructions.
Errors encountered:
fastboot flash oem _a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
fastboot: error: cannot load '_a': No such file or directory
I changed the command to: fastboot flash oem_a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
Sadly, the device reboots after a few seconds showing the sony logo. Reboots about three times and then says corrupted image, then shuts down. What am I doing wrong?
Thanks for your help guys!

BigWoodFarmer said:
Hello,
Android Custom Rom noob here. Just picked up a XPERIA zx2 Compact and wanted to use this guide to flash a more current Android on the phone (came with Android10).
I followed some guides and was able to unlock my bootloader and enable USB Debugging. I used adb platform tools to boot the device in fastboot mode and flashed the files as described in the instructions.
Errors encountered:
fastboot flash oem _a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
fastboot: error: cannot load '_a': No such file or directory
I changed the command to: fastboot flash oem_a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
Sadly, the device reboots after a few seconds showing the sony logo. Reboots about three times and then says corrupted image, then shuts down. What am I doing wrong?
Thanks for your help guys!
Click to expand...
Click to collapse
Hey,
I'm sorry and fixed the type.
There was a wrong whitespace character in the manual.
It's `oem_a`, that's correct.
Did you flash everything and wiped the userdata before?
Because other XZ2C owners were able to post logs.
Also it is mandatory to run the latest stock firmware on both slots once before in the lifetime of your phone.

Hi,
Thank you for your fast reply. I flashed everything and wiped as described with "fastboot -w"
I am unsure what you mean by both slots, you mean Firmware and Software Content Erase? I used EMMA to flash: H8324 52.1.A.0.618 Customized_UK 1313-5469 R3C User-Live COM on the device.
Some other questions I had:
a) Do I need Magisk for root on the device?
b) can I use another Version the twrp 3.4.0.0.? If I install this to my recovery partition, I can't use it when booting since the screen seems frozen.

sry for asking some dumb questions in my last post. I was now able to install this Android 12 Version. I think the problem was, that i didn't wipe the device before the deployment.
Thanks again for all your work on this.
*EDIT*
Can you suggest a twrp version I should use? I cannot start 3.4-0-0 (2020-06-14_21-07-37) anymore using fastboot boot
**EDIT #2**
I received the following error: "there is an internal problem with your device, contact manufacturer". I will attach output of logcat -b all

BigWoodFarmer said:
sry for asking some dumb questions in my last post. I was now able to install this Android 12 Version. I think the problem was, that i didn't wipe the device before the deployment.
Thanks again for all your work on this.
*EDIT*
Can you suggest a twrp version I should use? I cannot start 3.4-0-0 (2020-06-14_21-07-37) anymore using fastboot boot
**EDIT #2**
I received the following error: "there is an internal problem with your device, contact manufacturer". I will attach output of logcat -b all
Click to expand...
Click to collapse
Nice that you achieve to flash it.
The camera is currently not implemented because of the russian invasion in the ukraine.
Code:
04-12 19:02:48.363 0 0 I init : starting service 'vendor.camera-provider-2-4'...
04-12 19:02:48.451 3114 3114 I [email protected]: [email protected] legacy service is starting.
04-12 19:02:48.452 3114 3114 D ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
04-12 19:02:48.453 3114 3114 D hw-ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
04-12 19:02:48.452 0 0 I binder : 3114:3114 ioctl 40046210 7ff5fbfc44 returned -22
04-12 19:02:48.453 0 0 I binder : 3114:3114 ioctl 40046210 7ff5fbfc24 returned -22
04-12 19:02:48.489 3114 3114 E [email protected]: Could not load camera HAL module: -2 (No such file or directory)
04-12 19:02:48.489 3114 3114 E [email protected]_64: getProviderImpl: camera provider init failed!
04-12 19:02:48.490 3114 3114 D RefBase : RefBase: Explicit destruction, weak count = 0 (in 0xb400007a624ceaa0)
04-12 19:02:48.491 3114 3114 W RefBase : CallStack::getCurrentInternal not linked, returning null
04-12 19:02:48.491 3114 3114 W RefBase : CallStack::logStackInternal not linked
04-12 19:02:48.492 3114 3114 E HidlServiceManagement: Could not find instance 'legacy/0' in library [email protected] Keeping library open.
04-12 19:02:48.493 3114 3114 E LegacySupport: Could not get passthrough implementation for [email protected]::ICameraProvider/legacy/0.
04-12 19:02:48.501 0 0 I init : Service 'vendor.camera-provider-2-4' (pid 3114) exited with status 1
04-12 19:02:48.501 0 0 I init : Sending signal 9 to service 'vendor.camera-provider-2-4' (pid 3114) process group...
04-12 19:02:48.501 0 0 I libprocessgroup: Successfully killed process cgroup uid 1047 pid 3114 in 0ms
04-12 19:02:48.504 0 0 E init : process with updatable components 'vendor.camera-provider-2-4' exited 4 times in 4 minutes
04-12 19:02:48.513 0 0 I init : processing action (sys.init.updatable_crashing=1) from (/system/etc/init/flags_health_check.rc:10)
04-12 19:02:48.514 0 0 I init : starting service 'exec 29 (/system/bin/flags_health_check UPDATABLE_CRASHING)'...
04-12 19:02:48.541 0 0 I init : SVC_EXEC service 'exec 29 (/system/bin/flags_health_check UPDATABLE_CRASHING)' pid 3115 (uid 1000 gid 1000+0 context default) started; waiting...
04-12 19:02:48.564 3115 3115 I flags_health_check: ServerConfigurableFlagsReset reset_mode value: 1
04-12 19:02:48.565 3115 3115 I flags_health_check: ServerConfigurableFlagsReset updatable crashing detected, resetting flags.
Please subscribe to
[Tama][XZ2C][AOSP12][4.19] Apollo camera provider init failed (every 5secs) · Issue #751 · sonyxperiadev/bug_tracker
Platform: Tama Device: XZ2C (apollo) Kernel version: 4.19.188-ge73c1a837c4f-dirty Android version: AOSP12 Software binaries version: 12_4.19_v1c_tama Previously working on n/a (latest official Sony...
github.com
[Tama][4.19][AOSP12] Device reboots for no clear reason any time it is not idle · Issue #755 · sonyxperiadev/bug_tracker
Platform: Tama Device: Apollo Kernel version: 4.19 Android version: AOSP12 Software binaries version: 12_4.19_v1c_tama Previously working on n/a Description The device reboots after a few minutes o...
github.com
[TAMA][12][4.19] Bootloop · Issue #748 · sonyxperiadev/bug_tracker
Platform: Tama Device: Apollo Kernel version: 4.19 Android version: 12 Software binaries version: v1c Previously working on Stock Description Bootloop and no ADB logs available. The device was flas...
github.com
and firstly this will get fixed: https://github.com/sonyxperiadev/bug_tracker/issues/770

20.05.2022
android-12.1.0_r5 (May security patchlevel)
Click to expand...
Click to collapse
Because of problems with the ftp server the new release is on google drive.
Click to expand...
Click to collapse

Hello, what changes between this rom and the stock based roms ?