Related
Sorry for my English.
I tried all the rom, all, and no work for me either. Use two ext2 partitions for data and system. Using the latest zimage, haret and initrd 2.6.32, tested all options with default.txt
When I install, the first time, everything is right, but the second time I boot android, everything goes wrong. After installing, wait 15 minutes before touching anything.
What else I can try?
WM 6.1
radio 1.70.19.09
SD 8GB class6 with fat32, ext2, ext2, linuxswap
Thanks.
Go to NAND ?
vellowax said:
Go to NAND ?
Click to expand...
Click to collapse
Now prefer haret.
My bootlog.txt
** /dev/block/mmcblk0p1
** Phase 1 - Read FAT (compare skipped)
Attempting to allocate 7032 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
Free space in FSInfo block (1093801) not correct (1078495)
Fix? yes
Next free cluster in FSInfo block (640022) not free
Fix? yes
1961 files, 119676 free (1078495 clusters)
sh: 2: unknown operand
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/loop1 is mounted
/dev/block/loop1: clean, 710/65536 files, 97021/262144 blocks
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/loop0 is mounted
/dev/block/loop0 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/loop0: 625/65536 files (12.8% non-contiguous), 19711/262144 blocks
My default.txt
#alloctest 0x2000
set RAMSIZE 0x08000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
set initrd initrd.lzma
#
# The following kernel parameters are useful
# ppp.nostart - Set ppp.nostart=1 to disable starting the ppp connection on boot
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 1, use 1 for best power savings
# board-htckaiser.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
# lcd.density - Defaults to 160, 128 shows more on screen
#
set cmdline "ppp.nostart=0 pm.sleep_mode=0 lcd.density=120 mddi.width=240 mddi.height=320 no_console_suspend board-kaiser-keypad.atttilt=0 board-htckaiser.panel_type=2 hw3d.version=1 board-kaiser-battery.battery_capacity=2160 board-kaiser-battery.haret_divisor=2200 board_htckaiser.pmem_size=4 board_htckaiser.pmem_adsp_size=1 clock-7x00.a11=400"
boot
Please explain what goes wrong on the second boot.
What is showing on the screen at the end?
Everything you posted looks right, as far as I can see.
n2rjt said:
Please explain what goes wrong on the second boot.
What is showing on the screen at the end?
Everything you posted looks right, as far as I can see.
Click to expand...
Click to collapse
Thanks for your help.
On the second boot every few minutes installation screen appears (the rays forming X) and finally the screen turns white and kaiser does not respond and I have to go back to WM.
Can be the problem have installed this WM rom?
I can install android in NAND if that solve my problems, I like it android.
Sorry for my English.
Maybe when you turned off after the first boot, the filesystem was not cleanly dismounted. It might help to clear the dalvik cache during the boot, using the boot menu. To open the boot menu, push the middle of the screen when Linux starts to boot. Choose the option to clear the dalvik cache. When that finishes, choose the "Exit" option. I don't know, but it might help.
NAND will give fewer problems, but still has problems dismounting the filesystem cleanly when shutting down.
n2rjt said:
Maybe when you turned off after the first boot, the filesystem was not cleanly dismounted. It might help to clear the dalvik cache during the boot, using the boot menu. To open the boot menu, push the middle of the screen when Linux starts to boot. Choose the option to clear the dalvik cache. When that finishes, choose the "Exit" option. I don't know, but it might help.
NAND will give fewer problems, but still has problems dismounting the filesystem cleanly when shutting down.
Click to expand...
Click to collapse
Thanks, I'll do it again (clear dalvik cache), I tried it once after reading a lot, but did not help.
Clear dalvik cache but problems persist, now the kaiser after working a few hours, as before, the screen stays black and does not respond, back to WM.
At least now do not see the X and white screen. If everything is like most people, why do not I have the same results?
THIS POST IS OUTDATED, FOLLOW THE GUIDE IN THE STICKY INTRODUCTION TO ANDROID - THIS BUG HAS BEEN FIXED
DISREGARD THE POSTS UNTIL PAGE 5, THEY WERE POSTED BEFORE THIS ORIGINAL POST WAS EDITED WITH THIS FIX.
The problem some users are experiencing is that their phones freeze soon after their first boot until APN (access point name) is changed, this is somewhat difficult to do due to the freezes.
Note: this is for GSM users. I have no idea if this will work with CDMA, or even if they receive freezes.
Highlandsun and I have stumbled upon a fix that worked for me RHOD110 - this has been tested on GSM only (Froyo).
Using this fix, there should no longer be a need to manually select APN.
There are two files you need:
Highlandsun's RIL
and
Customized ROOTFS (F22's keymap rootfs (Mar 1st) edited - it WILL work with all his custom key bindings)
You will probably want to use this kernel if you are not already, it has great battery life and most failed wakes and SoDs are fixed. It is also what I used when testing this fix.
Firstly, extract put the downloaded RIL onto your SD card, I put mine in a folder named Android in the root of my SD, I recommend you do this also.
now edit conf/froyo.user.conf contained wherever you keep your HaRET.exe on your SD. If you are using Linux or a UNIX based operating system, use any editor you wish. If you are running windows, use notepad ++ to edit this file.
Add the following within the { } after custom_shells at the bottom of this file.
Code:
mount --bind /sdcard/Android/libhtcgeneric-ril.so /lib/froyo/libhtcgeneric-ril.so
so that your file should look something like this, I have highlighted the added line. You could even copy and paste the below to replace your whole file.
Code:
# General parameters
general{
renice=1 # Run the renice script to inprove call answering
}
#compcache related parameters
compcache{
compcache_en=1 # enable(1) or disable(0)20 compcache
cc_disksize=100 # Ram swap disksize - any number between 1 to 98 should work; default is 1/4 of the RAM (24)
cc_memlimit=64 # Limit the memory usage for backing swap (cc .5x known issue-defaults to 15% of total RAM)
cc_backingswap_en=0 # enable(1) or disable(0) backing swap
cc_backingswap=/dev/block/mmcblk0p4 # pointing to the backingswap partition device, swap
}
#create swap file for compcache or linux swap
swap_file{
swap_file_en=0 # set to 1 to create swap file
# set to 0 to del the swap file
linux_swap_file_size=32 # swap file size in MB
linux_swap_file=/sdcard/swapfile # pointing to the swap file location ( must be /system/sd/)
}
#Linux swap parameters
#
# linux swap can only be enabled if cc_backingswap_en is set to "0"
#
linux_swap{
linux_swap_en=0 # enable(1) or disable(0) linux swap
linux_swap_partition=/dev/block/mmcblk0p4 # swap partition device
}
#virtual memory
sys_vm{
sys_vm_en=1 # enable(1) or disable(0) virtual memory configurations
swappiness=0 # default 60
page_cluster=0 # default 3, (0 since CM3.9.6+)
laptop_mode=5 # default 0
dirty_expire_centisecs=3000 # default 3000
dirty_writeback_centisecs=1500 # default 500
dirty_background_ratio=3 # default 5
dirty_ratio=5 # default 10
vfs_cache_pressure=200 # default 100 (tendency of the kernel to reclaim cache memory)
overcommit_memory=1 # default 0 (0=Heuristic 1=Always overcommit 2=Don't overcommit)
overcommit_ratio=80 # default 50 (% of Physical+Virtual memory to allow allocation)
}
# custom shell commands, these commands run last
custom_shells{
chmod 777 /etc/dbus.conf
echo 2 > /sys/devices/platform/msm_hsusb/usb_function_switch
rm -f /sdcard/*.rec
mount --bind /sdcard/Android/libhtcgeneric-ril.so /lib/froyo/libhtcgeneric-ril.so
modprobe ipv6
#echo "Hello!!!" # example
#echo "You can create your own commands here" # example
}
Once you have done that, save it and make sure it is saved. You may have to copy it to your pc, edit it, delete the one on your sd, copy it back across - if using droidexplorer to manage files. You could also edit this file from within Android using ASTRO to browse to it.
Now extract that rootfs.img mentioned above and replace your current one.
You will now have improved reliably and hopefully no freezes on boot. The device may also seem faster now.
This fix was suggested to me by Highlandsun (hyc) on #xdandroid irc. He deserves all the credit.
---------For Developers-----------
The modified rootfs has /init.etc/ppp/options.smd edited to the following with changes bolded:
Code:
debug
defaultroute
updetach
[B]#persist[/B]
local
usepeerdns
noipdefault
unit 0
linkname gprs
novj
novjccomp
[B]lcp-restart 1
lcp-max-configure 3
ipcp-restart 1
ipcp-max-configure 3[/B]
highlandsun said:
The hang is because the ril is stuck, it launches pppd and waits for a success status from it. But in this particular case, the connection used the wrong APN so pppd cannot succeed. With the "persist" setting in the ppp options file, pppd also never returns on failure, so ril waits forever, and everything grinds to a halt.
Commenting out the persist setting is the main fix for this. The additional ipcp/lcp lines are to decrease the time pppd spends retrying the connection setup, so that it will quit in less than 60 seconds, which allows ril to recover from the error sooner. I have some more patches for ril which will hopefully make the recovery even faster, coming up.
Click to expand...
Click to collapse
Well you really need to break it down better.
What kernel/modules combo have you tried? How far back did you go? What rootfs have you tried? What builds? System images? Have you looked at your startup.txt? What is in it?
I don't have a 110, but on my 400 most everything "works" flawlessly - assuming you have it configured correctly, yours should be the same.
arrrghhh said:
Well you really need to break it down better.
What kernel/modules combo have you tried? How far back did you go? What rootfs have you tried? What builds? System images? Have you looked at your startup.txt? What is in it?
I don't have a 110, but on my 400 most everything "works" flawlessly - assuming you have it configured correctly, yours should be the same.
Click to expand...
Click to collapse
Okay, firstly my startup.txt
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 clock_7x00.grp=0xa99 hw3d.force=1 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod110"
boot
Full Packages I have tried:
FROYO X RED 2011.02.06
ProjectAndroid2.2Froyo.012311
RhodiumXDAndroid23.01.10
XDAndroid2.2Froyo.012211
SENSE x 2011.02.10
Along with these Modules:
htc-msm-linux-20101204_010857-package
htc-msm-linux-20110210_213850-package
modules-2.6.27.46-01253-gd53ddf6-dirty
initrd:
initrd-20100813-b11116a
Rootfs:
rootfs-20110210-2cb7ec0
(and many others i have just deleted)
ryannathans said:
Okay, firstly my startup.txt
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 [color=red][B]msmts_calib=0x9f.0x39a.0x35c.0x78 clock_7x00.grp=0xa99[/B][/color] hw3d.force=1 msmvkeyb_toggle=off [color=red][b]pmem.extra=1[/color][/b] gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod110"
boot
Full Packages I have tried:
FROYO X RED 2011.02.06
ProjectAndroid2.2Froyo.012311
RhodiumXDAndroid23.01.10
XDAndroid2.2Froyo.012211
SENSE x 2011.02.10
[ 175.542358] hw3d: current 1343 ppid 1 file d5bb27c0 count 2
[ 175.580810] binder: 1329:1342 transaction failed 29189, size 564-0
[ 175.730926] hw3d: closing
[ 175.730987] hw3d_release: in release for pid=1338 tid=1343
[ 175.731018] hw3d: releasing 1338
Along with these Modules:
htc-msm-linux-20101204_010857-package
htc-msm-linux-20110210_213850-package
modules-2.6.27.46-01253-gd53ddf6-dirty
initrd:
initrd-20100813-b11116a
Rootfs:
rootfs-20110210-2cb7ec0
(and many others i have just deleted)
Click to expand...
Click to collapse
Ok, first the rhod110 physkeyboard option only exists in F22's rootfs.
Have you tried with FRX04?
Have you tried with a "regular" rootfs from the autobuild service?
You also have deprecated commands in your startup.txt, I highlighted them in red.
I'm assuming when you try different kernel/modules you're removing the old zImage/modules-xxx.tar.gz and replace with the new zImage/modules-xxx.tar.gz...
I don't see any other issues. You might need to go way back in the kernel archives, start around the beginning of November and work your way backwards.
If you can get any logs that would be helpful, as I'm just grabbing at straws since I don't actually know what the problem is. Could be your SD card, have you tried a different SD?
arrrghhh said:
Ok, first the rhod110 physkeyboard option only exists in F22's rootfs.
Have you tried with FRX04?
Have you tried with a "regular" rootfs from the autobuild service?
You also have deprecated commands in your startup.txt, I highlighted them in red.
I'm assuming when you try different kernel/modules you're removing the old zImage/modules-xxx.tar.gz and replace with the new zImage/modules-xxx.tar.gz...
I don't see any other issues. You might need to go way back in the kernel archives, start around the beginning of November and work your way backwards.
If you can get any logs that would be helpful, as I'm just grabbing at straws since I don't actually know what the problem is. Could be your SD card, have you tried a different SD?
Click to expand...
Click to collapse
Tried multiple SD cards, my current card is 16GB (could there be a problem here?)
where could I grab logs from?
Tried FRX04 too.
Just making sure im doing it right
Dowloaded RAR - Android v2.2.1 Froyo: Reference
unrar to 'andboot' on sd card.
edit startup.txt
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 hw3d.force=1 rel_path=andboot"
boot
Downloaded and put modules-2.6.27.46-01212-ge59fdaf.tar and its zImage in andboot
(deleted old ones first)
replaced rootfs with rootfs-20110210-2cb7ec0 (renamed of couse to rootfs.img)
.....
run haret.exe
past all the booting
past the xdandroid logo loop
screen is horizontal
slow and laggy android
screen flips to verticle
seems to be more stable
set up my wifi, connected.
so looks like the modules-2.6.27.46-01212-ge59fdaf has stopped it freezing seconds after booting into android.
what do you need now? Am I forever stuck with this old module?
ryannathans said:
Tried multiple SD cards, my current card is 16GB (could there be a problem here?)
where could I grab logs from?
so looks like the modules-2.6.27.46-01212-ge59fdaf has stopped it freezing seconds after booting into android.
what do you need now? Am I forever stuck with this old module?
Click to expand...
Click to collapse
Well at least an old kernel/modules boots. You sound like you're doing it correctly - just to be clear the modules ends in .tar.gz - you shouldn't be uncompressing this file whatsoever.
Now, on to logs. Since you never really boot adb is the only option. If you have Windows, Droid Explorer does most of the hard work for you. Once you get it setup, do a pull
Code:
adb pull /data/system/dropbox/ /path/to/folder/on/your/pc
It will dump all the files in that folder on your phone, onto that folder on your PC. Look at the last SYSTEM_LAST_KMSG file, attach it here.
Hell, attach a few of them.
arrrghhh said:
Well at least an old kernel/modules boots. You sound like you're doing it correctly - just to be clear the modules ends in .tar.gz - you shouldn't be uncompressing this file whatsoever.
Now, on to logs. Since you never really boot adb is the only option. If you have Windows, Droid Explorer does most of the hard work for you. Once you get it setup, do a pull
Code:
adb pull /data/system/dropbox/ /path/to/folder/on/your/pc
It will dump all the files in that folder on your phone, onto that folder on your PC. Look at the last SYSTEM_LAST_KMSG file, attach it here.
Hell, attach a few of them.
Click to expand...
Click to collapse
Just to clear it up, logs from module that dont boot or the one that does?
ryannathans said:
Just to clear it up, logs from module that dont boot or the one that does?
Click to expand...
Click to collapse
The dropbox will have logs from failed boots hopefully.
If you can get a log when it's failing to boot, that would be ideal. Might want to rename your data.img, grab the newest 1253 kernel from GIT and boot. See if you can grab a dmesg from adb,
Code:
adb shell dmesg > dmesg.txt
Will dump the dmesg.txt file to where ever you're running that command from. You can change the path on the right side of that command if you want to direct the output to a different folder.
i cant get droid explorer to find me device =/
scratch that, it picked up a "00000" that seems to be it.
new data.img, kernel and module from 1253. loads home screen with the google search bar and the android and it just froze up, performing soft reset, putting on the working modules and retrieving the logs for you.
done!
see attachment
is that all you need?
What should I do next?
ryannathans said:
is that all you need?
What should I do next?
Click to expand...
Click to collapse
The only log in there is from Sat Oct 23 02:21:48 CEST 2010. Can you get any adb interface running while it's booting...? Have you traced it down to which kernel is the one that fails to boot?
arrrghhh said:
The only log in there is from Sat Oct 23 02:21:48 CEST 2010. Can you get any adb interface running while it's booting...? Have you traced it down to which kernel is the one that fails to boot?
Click to expand...
Click to collapse
any kernel after november 2010 just freezes after booting (something to do with the panel?)
Trying a different 'package' and hopefully I can get the logs.
this time im using: http://forum.xda-developers.com/showthread.php?t=933177
okay is seems to be working -.- its modules-2.6.27.46-01232-gb7033df
ill try and load 1253
Ok, so start at 1232 and work your way towards 1253 - which kernel stops booting? I can't troubleshoot this as 1253 works fine on mine and most devices .
arrrghhh said:
The only log in there is from Sat Oct 23 02:21:48 CEST 2010. Can you get any adb interface running while it's booting...? Have you traced it down to which kernel is the one that fails to boot?
Click to expand...
Click to collapse
arrrghhh said:
Ok, so start at 1232 and work your way towards 1253 - which kernel stops booting? I can't troubleshoot this as 1253 works fine on mine and most devices .
Click to expand...
Click to collapse
can you point me to where I can download 1232 - 1253? appreciate the help so far
EDIT: I think i found them.
Trying now.
EDIT:
01245 - PASS
01246 - PASS
01250 - PASS
perhaps it was my 'noobiness' previously causing it to crash, I cant seem to reproduce it anymore -.-' I think i was using a different zImage to the Modules version
using FRX04, latest rootfs, my FN button on the keyboard is an @ and there is no other button that works as FN.
keyboard layout in startup.txt is set to rhod110
{
"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"
}
ryannathans said:
perhaps it was my 'noobiness' previously causing it to crash, I cant seem to reproduce it anymore -.-' I think i was using a different zImage to the Modules version
using FRX04, latest rootfs, my FN button on the keyboard is an @ and there is no other button that works as FN.
keyboard layout in startup.txt is set to rhod110
Click to expand...
Click to collapse
Heh, it happens.
Have you tried F22's new rootfs? Adds all sorts of interesting keys, read thru his thread. I don't think the RHOD110 layout is in any other rootfs TBH...
arrrghhh said:
Heh, it happens.
Have you tried F22's new rootfs? Adds all sorts of interesting keys, read thru his thread. I don't think the RHOD110 layout is in any other rootfs TBH...
Click to expand...
Click to collapse
ahh noo. still same problem with it
thanks anyway
EDIT: everything's working sweet now that I had a chat with F22 and we got rhod110 support now
I faced same issue, it froze while installing, or so it seems. then one fine day, i accidently clicked on screen for 2-3 secs with stylus and then ... the screen moved one line up showing some message related to 'point 2' or in other words caliberation. My guess was it was waiting for caliberation and i thought it froze. Not sure of this is the same case with yours, but you can try it once. I clicked for 2-3 seconds on top-left corner first, then top-right, bottom-left, bottom-right, and lastly center of screen. After that everything worked properly.
I got this mod from the galaxy S2 thread and tried it on the GN running stock gsm 4.0.2. It kinda worked i got it to boot everything but something went wrong. it changed my lockscreen so that the time is not showing properly and the settings menu was messed up(kinda looked like the honeycomb setting menu). The brightness mod did work though. i was able to get it to work on Gingermod rom on the atrix without any side effects but it didnt work on the Wetdream rom. it is also reported to be working for the GS2. So hopefully it will work on the GN with a different build or rom.
Basically what you have to do is decompile the framework-res.apk and change the values is arrays.xml and recompile and push it back using adb. here's the instructions from that GS2 thread
1. Download APK manager
2. Grab framework-res.apk from your phone under \system\framework\ (you can use root explorer or adb push) and place it in the "place-apk-here-for-modding" folder
3. Run Script.bat and select option 9
4. go to projects\framework-res.apk\res\values\arrays.xml and edit your values with the ones roger posted in my link above
5. Once edited, compile the apk using option 11
6. Is this a system apk. Ans: y
7. Qn: Aside from the signatures...least. Ans: y
8. Prompt: In the apk manager folder u'll find a keep folder..... done then press enter on this script. Press any key to continue . . . go to "keep" folder and delete resources.arsc and then press any key
9. Choose option 22 to set project to unsignedframework-res.apk
10. Choose option 5 to zipalign the new apk.
11. rename the unsignedframework-res.apk to framework-res.apk and push it to system/framework with these commands in adb.
Code:
Mount System in recovery
adb push framework-res.apk /system/framework/framework-res.apk
reboot
here are the values in arrays.xml to be changed.
Code:
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>16</item>
<item>40</item>
<item>60</item>
<item>70</item>
<item>70</item>
<item>250</item>
</integer-array>
here's what i had the new values at
Code:
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>5</item>
<item>20</item>
<item>50</item>
<item>70</item>
<item>150</item>
<item>250</item>
</integer-array>
What i was looking to change since i've noticed that sometimes the screen is not bright enough if its at the second last level(70) and i wanted to change the 16 to 5. When i did this with my atrix i had the lowest setting at 2 and it was perfect at night. You can play around with the numbers to see what suits you. Just make sure you do a nandroid backup before attempting this mod.
So what this will allow you to have a higher screen brightness than normal and a lower price rightness that normal, so basically increasing the range of brightness
Sent from my Galaxy Nexus using XDA App
yes thats right the first value 16 is the lowest brightness, you can set this to 1 and the highest is 250. You can set anything you want in between. i was also wondering if i can put a few more levels in there as the GN only has 6. My atrix has 16 levels. i tried to make it 10 levels on one of my attempts and i got a bunch of force closes. tomorrow i will flash a different build and try again.
it's already writed on he_steone64 3ad how to set the brightness with all the files to change...but thanks ayway fotr this tuto..
sert00 said:
it's already writed on he_steone64 3ad how to set the brightness with all the files to change...but thanks ayway fotr this tuto..
Click to expand...
Click to collapse
ahh i didnt see his thread when i was trying this mod for the GN
I rooted my device yesterday fresh factory install
but weirdly it has changed my charging/usb tone
Instead of playing the chargingstarted.ogg file it plays a file I can't locate and I'm not sure how to change... It's not exactly a "great" sound
I'm assuming the phone uses system/media/audio
For default.ui sounds but I'm unsure how to change this "new" default sound and it doesn't seem to be located here either....
I didn't have any idea how to change my UI sounds so I attempted a magisk module for something like OnePlus sounds to see if that would change the sound but alas my issue still exists.
I'm by no means a novice user but I wouldn't say I'm advanced either, I can't mount parts of the system using file managers so I assume changes would have to be made in adb using fastboot?
Edit, here is a quick video of the mysterious sound I'm unable to find.
https://youtu.be/JPkVRtcncC8
Edit#2 it seems this is a issue with a clean install of android10(pixel devices?) as I read a dirty flash doesn't cause this issue, here is a snippet from bug tracker on Google's site
The sound played is fallbackring.ogg from framework resources.:
09-04 15:54:44: OggExtractor for mime NULL, source TinyCacheSource(CallbackDataSource(784->787, RemoteDataSource(FileSource(fd(/system/framework/framework-res.apk), 7369304, 14611)))), pid 787: active
track {srte: (int32_t) 44100, mime: (char*) audio/vorbis, dura: (int64_t) 1567551, csd1: no type, size 3189), csd0: no type, size 30), chnm: (int32_t) 1, brte: (int32_t) 80000, #chn: (int32_t) 1} : active
I don't know exactly when we fall back to this sound but probably when the charging sound cannot be located.
Click to expand...
Click to collapse
Same happened to me, also lockscreen locking sound Not working anymore
Nightf0x_007 said:
Same happened to me, also lockscreen locking sound Not working anymore
Click to expand...
Click to collapse
Mines doing the same... If I can find the weird charge sound location perhaps this is fixable?
co4 said:
Mines doing the same... If I can find the weird charge sound location perhaps this is fixable?
Click to expand...
Click to collapse
Idk the location but when i first clean flashed android 10, none of this issues was there but after that i clean flashed several times and this is happening since then, changed charging sound and no locking sound
My fix for charging sound for now is that im using edxposed with gravitybox module, gravitybox have an option to change some power options sounds like charging, stop charging, .... etc, so i changed it to the default charging sound in folder system/audio/ui
co4 said:
Edit#2 it seems this is a issue with a clean install of android10(pixel devices?) as I read a dirty flash doesn't cause this issue, here is a snippet from bug tracker on Google's site
Click to expand...
Click to collapse
Do you have a link to this issue on Google's tracker? This has been an issue since the Q betas and I'd like to star/follow it. I was hoping it would have been fixed in the October update, but it's still playing this horrible sound.
I can confirm the bug is present on both the original Pixel and the Pixel 2 XL after a clean factory image flash. Upgrading from 9.0 Pie there is no issue.
Syxx14 said:
Do you have a link to this issue on Google's tracker? This has been an issue since the Q betas and I'd like to star/follow it. I was hoping it would have been fixed in the October update, but it's still playing this horrible sound.
I can confirm the bug is present on both the original Pixel and the Pixel 2 XL after a clean factory image flash. Upgrading from 9.0 Pie there is no issue.
Click to expand...
Click to collapse
Sure, I should of added it to begin with so more people would star it and elevate it's status
https://issuetracker.google.com/issues/140447165
This happend to me too. Lock screen sounds also dont work. Also my gmail notification sound most of the time only plays a fraction of the sound.
I rooted the phone to see if the sound files were actually there and they are.
krolla03 said:
This happend to me too. Lock screen sounds also dont work. Also my gmail notification sound most of the time only plays a fraction of the sound.
I rooted the phone to see if the sound files were actually there and they are.
Click to expand...
Click to collapse
I'm not sure if there is also more at play as flashing different sounds to the folder doesn't change anything... I'm no coder but I'd imagine there is a issue/typo in the framework and it's not pointing to the right directory, hence fallback sound file... I broke my NFC when I swapped to a new shell so not sure if all the ui sounds are barfed... And if somehow the soundsui program is messing, it's all speculation and not urgent to Google in fixing
ok so i managed to pull the framework-res.apk off my phone and decompile it
in framework-res.apk/res/xml/audio_assets.xml contains the following:
<?xml version="1.0" encoding="utf-8"?>
<audio_assets version="1.0">
<group name="touch_sounds">
<asset file="Effect_Tick.ogg" id="FX_KEY_CLICK" />
<asset file="Effect_Tick.ogg" id="FX_FOCUS_NAVIGATION_UP" />
<asset file="Effect_Tick.ogg" id="FX_FOCUS_NAVIGATION_DOWN" />
<asset file="Effect_Tick.ogg" id="FX_FOCUS_NAVIGATION_LEFT" />
<asset file="Effect_Tick.ogg" id="FX_FOCUS_NAVIGATION_RIGHT" />
<asset file="KeypressStandard.ogg" id="FX_KEYPRESS_STANDARD" />
<asset file="KeypressSpacebar.ogg" id="FX_KEYPRESS_SPACEBAR" />
<asset file="KeypressDelete.ogg" id="FX_KEYPRESS_DELETE" />
<asset file="KeypressReturn.ogg" id="FX_KEYPRESS_RETURN" />
<asset file="KeypressInvalid.ogg" id="FX_KEYPRESS_INVALID" />
</group>
</audio_assets>
Click to expand...
Click to collapse
isn't the UI audio settings meant to be in this file too or are they elsewhere? i wish i could check what the stock pie file has
Update
Upon further investigation I have found the issue using magisk & the hidden module on both android 9 factory & 10 I was able to compare the settings and
I have found there is a blatant error in where the sound triggers are being pointed to....
Lock_sound=/product/media/audio/ui/Lock.ogg
When checking the folder using a root browser the audio folder isn't located here, just the boot animation zips, the actual files are stored in
/system/media/audio/ui/Lock.ogg
So by changing /product/ to /system/ I was able to gain the correct sound for locking....
Obviously doing this on phone terminal is a pain so perhaps I can make further edits especially if I can find where hidden accesses those files that have these settings.
What file did you end up modifying to fix the issue?
yurilebbie said:
What file did you end up modifying to fix the issue?
Click to expand...
Click to collapse
Here is a quick and dirty write up:
ok so to fix this issue you need [root] access, and HiddenSettings Module (by Skittles9823) https://github.com/Magisk-Modules-Repo/hidden_settings
this can be done on the phone with a terminal emulator but its janky and slow so I prefer adb shell
what I typed is in Bold
Code:
[B]adb shell[/B]
taimen:/ $ [B]su[/B]
taimen:/ #
taimen:/ #[B] hidden[/B]
==========================
HiddenSettings v0.0.3(003)
by Skittles9823
Skittles9823 is not responsible for any damage caused by the use of this module
==========================
1 - System settings
2 - Secure settings
3 - Global settings
[I] [B]4 - All settings[/B][/I]
r - Reset/Backup setting(s) WIP
d - Donate
0 - Exit
[CHOICE]:[B]4[/B]
Press Enter
==========================
1 - List all settings
2 - Find specific settings
[I][B] 3 - Modify settings[/B][/I]
x - Back to Menu
0 - Exit
[CHOICE]:[B]3[/B]
press enter
===== Modify Settings =====
Enter a setting then value
E.g. navigation_bar_visible 0
x - Back to AllNamespace settings
0 - Exit
[Search?]:[B]wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg[/B]
press enter & reboot
co4 said:
Here is a quick and dirty write up:
ok so to fix this issue you need [root] access, and HiddenSettings Module (by Skittles9823) https://github.com/Magisk-Modules-Repo/hidden_settings
this can be done on the phone with a terminal emulator but its janky and slow so I prefer adb shell
what I typed is in Bold
Code:
[B]adb shell[/B]
taimen:/ $ [B]su[/B]
taimen:/ #
taimen:/ #[B] hidden[/B]
==========================
HiddenSettings v0.0.3(003)
by Skittles9823
Skittles9823 is not responsible for any damage caused by the use of this module
==========================
1 - System settings
2 - Secure settings
3 - Global settings
[I] [B]4 - All settings[/B][/I]
r - Reset/Backup setting(s) WIP
d - Donate
0 - Exit
[CHOICE]:[B]4[/B]
Press Enter
==========================
1 - List all settings
2 - Find specific settings
[I][B] 3 - Modify settings[/B][/I]
x - Back to Menu
0 - Exit
[CHOICE]:[B]3[/B]
press enter
===== Modify Settings =====
Enter a setting then value
E.g. navigation_bar_visible 0
x - Back to AllNamespace settings
0 - Exit
[Search?]:[B]wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg[/B]
press enter & reboot
Click to expand...
Click to collapse
THANK YOU!!!!! This worked for me.
Now can you help me with the missing lockscreen sound? The sound is in the same /system/media/audio/ui folder. But what would i change the "wireless_charging_started_sound" part of the command to?
---------- Post added at 11:42 AM ---------- Previous post was at 11:23 AM ----------
im doing the same process but instead of wreless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg im typing lock_sound /system/media/audio/ui/Lock.ogg
When i do this Hidden gives me error /system/bin/hidden[247]: [: unlock_sound: unexpected operator/operand
HiddenSettings v0.0.3(003)
by Skittles9823
Skittles9823 is not responsible for any damage caused by the use of this module
==========================
BusyBox not found!
==========================
1 - System settings
2 - Secure settings
3 - Global settings
4 - All settings
r - Reset/Backup setting(s) WIP
d - Donate
0 - Exit
[CHOICE]: 4
===== AllNamespace Settings =====
1 - List all settings
2 - Find specific settings
3 - Modify settings
x - Back to Menu
0 - Exit
[CHOICE]: 3
===== Modify Settings =====
Enter a setting then value
E.g. navigation_bar_visible 0
x - Back to AllNamespace settings
0 - Exit
[Search?]: unlock_sound /system/media/audio/ui/Unlock.ogg
/system/bin/hidden[247]: [: unlock_sound: unexpected operator/operand
===== Modify Settings =====
Enter a setting then value
E.g. navigation_bar_visible 0
x - Back to AllNamespace settings
0 - Exit
[Search?]:
krolla03 said:
THANK YOU!!!!! This worked for me.
Now can you help me with the missing lockscreen sound? The sound is in the same /system/media/audio/ui folder. But what would i change the "wireless_charging_started_sound" part of the command to?
Click to expand...
Click to collapse
I have found an easier way and written up a little guide:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-fix-androidq-unlocking-sound-bug-t3989657
This method works on non rooted devices 100% confirmed by myself.
All sounds now work for me this method throws NO errors.
Nightf0x_007 said:
Idk the location but when i first clean flashed android 10, none of this issues was there but after that i clean flashed several times and this is happening since then, changed charging sound and no locking sound
My fix for charging sound for now is that im using edxposed with gravitybox module, gravitybox have an option to change some power options sounds like charging, stop charging, .... etc, so i changed it to the default charging sound in folder system/audio/ui
Click to expand...
Click to collapse
Can you guide me how to fresh Install the Pixel 2XL to Android 10 like the device came out of the box. Help me any proper procedure/video to follow.
Mubashir hussian said:
Can you guide me how to fresh Install the Pixel 2XL to Android 10 like the device came out of the box. Help me any proper procedure/video to follow.
Click to expand...
Click to collapse
Download the latest pixel 2 xl factory image (here it is october update)
https://dl.google.com/dl/android/aosp/taimen-qp1a.191005.007.a1-factory-3ed47161.zip
Extract the .zip file in your computer
Now in your phone go to settings - about - click build number several times until you see you are developer now, go back to settings main page then system then developer settings and enable usb debugging
Connect your phone to your pc, and authorize message will appear enable authroization
Now go to the extracted folder and run the flash-all.bat file and wait until it flashes the firmware to your phone
It will completely wipe your device data and flash latest update, and now setup your device like it is new
And not only charging sound is miss linked, other sounds are also wrong.
here's the fix shell
Code:
adb shell "settings put global car_dock_sound /system/media/audio/ui/Dock.ogg"
adb shell "settings put global car_undock_sound /system/media/audio/ui/Undock.ogg"
adb shell "settings put global desk_dock_sound /system/media/audio/ui/Dock.ogg"
adb shell "settings put global desk_undock_sound /system/media/audio/ui/Undock.ogg"
adb shell "settings put global lock_sound /system/media/audio/ui/Lock.ogg"
adb shell "settings put global low_battery_sound /system/media/audio/ui/LowBattery.ogg"
adb shell "settings put global trusted_sound /system/media/audio/ui/Trusted.ogg"
adb shell "settings put global unlock_sound /system/media/audio/ui/Unlock.ogg"
adb shell "settings put global wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg"
Hello maybe someone can help me here. I installed LineageOS 18. 1. Also works as far as everything is great only the problem is that I have integrated the tablet in the kitchen cabinet door and do not come to the ON/OFF button. I found files in the root directory under sys/android_touch for doubletap2wake, sweep2wake etc. If I open doubletap2wake with the text editor and make the 0 a 1 I can double-tap on the screen and it starts. As soon as I restart but it is again the 0 in it.
Can someone explain to me how I get it to be stored permanently?
Thank you so much.
/system partition is read-only
So everything you modify will be reset to default value
that's why every kernel modifying apps reapply changes after reboot