Related
Anyone ever have the volume up/down buttons on the side of the phone stop functioning correctly?
Looks like the buttons themselves still work (they now scroll up/down on pages instead of adjusting volume up/down). Any suggestions?
I'm running Energy Rom sense 2.5, cookie hometab 1.6 and HDwalls with cookie patch.
Thanks
Didy ou install the keyboard fix after installing the energy ROM?
Thanks for the response. No - was not aware of one. I can check out the energy thread for it.
Odd though because this just happened yesterday (volume sidebar was working fine before then) and ive been running the rom for like two weeks now. Only new thing I did yesterday was install transparent tabs, a cookie tab fix and new wallpaper thru HD Wall.
Matt
stenuine said:
Thanks for the response. No - was not aware of one. I can check out the energy thread for it.
Odd though because this just happened yesterday (volume sidebar was working fine before then) and ive been running the rom for like two weeks now. Only new thing I did yesterday was install transparent tabs, a cookie tab fix and new wallpaper thru HD Wall.
Matt
Click to expand...
Click to collapse
I know there are reg edits available in cab form that change the vol up/down buttons into up/down scroll buttons. Nothing in your list would be likely to include that, but it's possible...that's the only thing I can think of that would change their behavior like that.
Thanks. I might just look to isolate those two areas and try to set back. I also have that zoombar app (to use for other purposes) but dont think that would affect it, plus I didnt have the problem until days after i installed.
Tried soft/hard reset as well with no avail.
sirphunkee said:
I know there are reg edits available in cab form that change the vol up/down buttons into up/down scroll buttons. Nothing in your list would be likely to include that, but it's possible...that's the only thing I can think of that would change their behavior like that.
Click to expand...
Click to collapse
stenuine said:
Thanks. I might just look to isolate those two areas and try to set back. I also have that zoombar app (to use for other purposes) but dont think that would affect it, plus I didnt have the problem until days after i installed.
Tried soft/hard reset as well with no avail.
Click to expand...
Click to collapse
I'm guessing you mean just a soft-reset (rebooting)..? A hard-reset is where you wipe the memory clean putting everything in the OS back to stock settings (or back to the fresh version of a custom ROM, if you've flashed one on to your device). If you've hard-reset and this problem still persisted, then you can pretty much rule out software as a cause...
Yes, my approach would be to just start uninstalling stuff in reverse order, soft-resetting and testing after each item removed.
Yep - definitely meant soft reset. I'll try your advice. Thanks so much.
sirphunkee said:
I'm guessing you mean just a soft-reset (rebooting)..? A hard-reset is where you wipe the memory clean putting everything in the OS back to stock settings (or back to the fresh version of a custom ROM, if you've flashed one on to your device). If you've hard-reset and this problem still persisted, then you can pretty much rule out software as a cause...
Yes, my approach would be to just start uninstalling stuff in reverse order, soft-resetting and testing after each item removed.
Click to expand...
Click to collapse
stenuine said:
Yep - definitely meant soft reset. I'll try your advice. Thanks so much.
Click to expand...
Click to collapse
No problem! Good luck, and let us know what you find
Hi SirPhunk
Deleted everything that I'd installed since the problem occured and still no luck :-/. Buttons on side of phone still scrolling up/down, instead of adjusting volume.
I also tried the Sprint keyboard fix for Energy roms, but no luck there as well. Any other ideas? Do you happen to know if theres a way to search for the value in my registry?
Thanks again
If you want to go searching in your resgistry for it, PHM_Regedit and Total Commander can both search for specific keys...I would just try the string "volbutton" or even just "volb*", something like that.
Now, even though you didn't see the issue immediately when you installed it, I think there's still a possibility that the zoombar app could be the culprit....I would try uninstalling that too (if you haven't already) before you start doing the extra work.
EDIT: It also might be easiest to just install Rhodium Keyboard Controller (attached below) and use it to manually map them back to stock function (don't ask me why I didn't think of that in the first place ). In fact, if you do that, try uninstalling RKC right after doing that mapping, and I'll bet they return to their stock function after that even without the app being needed anymore.
Sir Phunk, Thank you for taking the time to investigate and the response, Sir Phunk. I went ahead and dloaded the cab to my storage card, but cant seem to find the files in order to run and edit the keys manually. Sorry if this is a stupid question - I'm still learning the ins n' outs. Maybe this will help me fully install programs that may be hanging around (even though I went to the "remove programs" section and deleted them).
Please advise if you have a chance. Again, my apologies as I am still learning. Thank you again.
stenuine said:
Sir Phunk, Thank you for taking the time to investigate and the response, Sir Phunk. I went ahead and dloaded the cab to my storage card, but cant seem to find the files in order to run and edit the keys manually. Sorry if this is a stupid question - I'm still learning the ins n' outs. Maybe this will help me fully install programs that may be hanging around (even though I went to the "remove programs" section and deleted them).
Please advise if you have a chance. Again, my apologies as I am still learning. Thank you again.
Click to expand...
Click to collapse
Will do...full instructions coming first thing in the morning
Hey stenuine, let's see if we can get this working for you...
First, I'm again guilty of not explaining things well enough (seriously), my apologies. That file I posted earlier is actually a .zip file, with 2 .cab files inside...it'll be easiest if you download it to your PC desktop, unzip the 2 files out of there, and then copy them over to the SD card.
[TIP: I would strongly recommend creating a "cabs" folder at the root-level of your storage card, and using that to retain any cabs that you run and know that work, even if you're not still using them at the moment. That way, you'll always have easy access to any of them, even through flashes and hard-resets]
The first file in that .zip is the sdkcerts cab, run that one first. It allows your phone to use many of the homebrewed apps and tweaks found here at xda. After that one's installed (do a soft-reset again if the install doesn't force that anyway, always a good habit), then you can just run the keyboard controller cab to install it. Once you have the app installed, the icon to run it is found in:
Settings -> All Settings -> System (it will say "Keyboard Config").
Once you get it installed ok, here's how to use it to get your key's mapped the way you want:
1. When you first open the app, you'll see what's in the first screenshot below(pretty much a blank screen).
2. Click "Menu" in the bottom right
3. Click "Add key" from the menu
4. You'll see the dialog in the 2nd screenshot below, go ahead and tap the volume-up button
5. Now you'll see what's in the 3rd screenshot below, the setup window. There's a lot of stuff there, but we'll only need some of it for this. First, in the "Key mode" drop-down list, choose "Direct key mapping"
6. Now you see what's in the 4th screenshot. Now what you need to do is click the "Key" dropdown list, and scroll all the way down to pick "117 F6-VOL UP"...if you did all that right, it should look like the 5th screenshot.
7. Click "Ok" in the bottom left of the screen. Now, you should be back to the very first screen you saw, but now with the mapping you just created (screenshot 6).
8. VERY IMPORTANT...at this point you must remember to hit "Update config" in the bottom left, or the work you just did won't have any effect. It'll confirm for you that it updated, and that's it! You just mapped one of the volume buttons
9. Now, follow steps 2-9 again, with the following exceptions:
Step 4 - tap the volume down button this time
Step 6 - pick "118 F7-VOL DOWN"
As long as you did all that, and hit "update config" after each one, you should now be able to close the app and have normal volume-button operation.
As you noticed there's a lot of versatility in this little app, so if that still doesn't work for you, there's other ways we can try...this is just the most direct and should work just fine.
Hey SirPhunk,
Thanks for your time and the very detailed breakdown. I was able to install the app and run it, but no luck re-assigning the buttons :-/. Tried re-assigning vol-up button to vol-up and vol-down button to vol-down, but no change. To test, I also re-assigned the "up" key on my flip-out keyboard to "volume-up" and still no dice. Made sure to save the registry after each change and tried with and w/o soft resets after the changes. The vol-up and vol-down buttons still just scroll up/down on the screen and up button on keybard still just scrolls up as well.
I saw what you meant about other functions for this program, just not sure which to try next in order to fix this issue. Thank you again.
bumping my post...
i just ended up doin a hard reset. My best guess is it could have been the zoombar scroller v2 app that screwed with the settings.
hello all...
ive been away from kaiser community a long time because i got an desire...
but i have my kaiser here ehehe
so i decided to see how android for kaiser is...
and i see theres a lot of progress in this!!
but my question is... after this time i dont understand how do i run it...
i see now there is and androidinstall.tgz and an andboot folder...
i want to run it with haret.. dont want to flash it....
can anyone point me to a tutorial for this new metod ?
i have this so far..
sdcard/andboot/androidinstall.tar
sdcard/andboot/default.txt
sdcard/andboot/haret.exe
sdcard/andboot/initrd.gz
sdcard/andboot/zImage
and when i run haret... it says that doenst find the system image...
can anyone help me to update my knowledge ?
thanks
hold the center button when it tells you then hit install system.
Same problem here. I tried the above suggestion but it doesn't load any menu for me when I do that.
Any other suggestions? Thanks.
If holding the dpad button does not work, try pressing the centre of the screen, ( think of it like a giant dpad, it does work, in fact it is my usual method after too many times of pressing the dpad wrong).
The reason so many people have trouble with this is that if you hit another key when pressing the dpad button it will not enter the install menu, and it is easy to do that if you are a bit nervous or in a hurry to press before the pause ends.
I have large fingers, and often miss the keys, and believe me I have a lot of experience in this, so now I use the screen method instead.
also make sure you are only hitting the button when it asks, if you hold before it asks then it won't go to the menu.
Hi to all!
On monday I for the first time tested Android on my Rhodium and must admit that I'm really impressed! There are, however, some minor problems in the version I'm using (Stock 2.2 Oct 28):
Pressing Power Button does nothing
German keyboard layout doesn't allow to imput all the umlauts. FN+u always gives you Ü instead of ü. And composing FN+Shift+[a/u/o] to get a capital umlaut doesn't work at all.
So I did a bit of hacking to fix this:
As far as the power button is concerned, the problem is a wrong keycode. Power used to be 102 but somehow now it became 116 which was not accordingly changed in the layout files. So all what I did was to change
rootfs.img/init.etc/keymaps/rhod100_de_navi_pad.kl
by replacing
Code:
key 102 HOME WAKE # Power button
by
Code:
key 116 HOME WAKE # Power button
As far as German keyboard layout is concerned, I just took rhod100_de_microp-keypad.kcm.bin and replaced a few HEX-values via GHex, accoring to this table. Well, the keys look like
A A a A ä A
U U u U Ü Ü
O O o O Ö Ö
so I figured out that the 5th one should FN+button and the 6th one FN+Shift+button and changed the hex codes accordingly. As far as I can see, the layout is correct now.
FN+ u -> ü
FN+Shift + u -> Ü
and so on. So far I didn't notice any bugs. I've uploaded the modified file for devs to test and may be include it into a next build.
Regards
Bombenbach
Hey Bombenbach,
great Work though. I just tried to edit this a few times but my work wasn't that effective.
So i guess everyone can replace the files in the sysmtefolder of Android. I tried that and with Root Explorer it was possible. Does the file persist if i reboot than??
I'm not really familiar with Root Explorer, since I directly mount the root.img in Ubuntu on my Laptop, but basically replacing the file should be enough. And editing rhod100_de_navi_pad.kl, if you want the home button to work. It will be persistent until you install a new build with a new root.img
Good work! I'll have a look at this at the weekend.
Can I check - the change you made gives you:
Power button short press: sleep/wake
Power button long press: Silent/Airplane/Power off menu
End button short press: Home
End button long press: Recent applications
If so, then that would be a great fix. It might be worth trying to mod the key map too, to add things like pipe and tab...
snalbansed said:
Good work! I'll have a look at this at the weekend.
Can I check - the change you made gives you:
Power button short press: sleep/wake
Power button long press: Silent/Airplane/Power off menu
End button short press: Home
End button long press: Recent applications
If so, then that would be a great fix. It might be worth trying to mod the key map too, to add things like pipe and tab...
Click to expand...
Click to collapse
First of all, my fix doesn't change the default behaviour of the buttons. My problem was, that Power button didn't work at all, making me use Back button all the time. So my fix only makes it work again.
What you're asking about is probably swapping Power and End buttons. Well, that can be done too, of course. The problem is that Android doesn't differentiate between sleep and end call, e.g. these two functions always has to be performed by the same button. Thus, swapping Power and End will indeed allow you to use Power button for sleep/wake but you'll also have to end calls with the Power button only. End button will then work only as Home/Recent apps.
I've found a thread about this, in which devs argue that ending calls with Power button would greatly confuse most users. I can understand that, but nevertheless I also can tell you how to change this. It's actually quite easy. All you have to do is go to /init.etc/keymaps/ (rootfs.img) and modify the appropriate kl-file:
rhod100_[uk/de/fr/it/nordic]_navi_pad.kl
or
tilt2_navi_pad.kl
depending on you Rhodium model
there you'll find the following lines:
Code:
key 102 HOME WAKE # Power button
key 107 ENDCALL WAKE_DROPPED
changing them to
Code:
key 107 HOME WAKE # Power button
key 116 ENDCALL WAKE_DROPPED
should do the trick (at least it in my case on rhod100_de). I replace 102 by 116 because on my Rhodium the Power button's keycode is 116 and not 102. It might be the case that on other Rhodiums it's still 102 although I'm not quite sure about that. Anyway, either 116 or 102 should definitely work.
I don't know how you guys usually modify your rootfs.img but as a Linuxer I simply mount it with
Code:
sudo mount rootfs.img /mnt -o loop
do the changes and then unmount it with
Code:
sudo umount /mnt
P.S. Somehow I must admit that ending a call with Power button is very convenient.
I see. It looks like you are using a relatively old rootfs, ie after they swapped the power and home buttons, but before they fixed the power button correctly. So next time you update your rootfs, you should find that bit works already.
The current rootfs file for the German rhod100 has the lines as follows:
Code:
key 116 POWER WAKE
key 107 ENDCALL WAKE_DROPPED
I'll still have a play with the keymap though!
Oh. Well, I downloaded my rootfs just a few days before the current release came so I thought that it's still quite recent. My bad. Anyway, you should be able to switch the buttons back just by switching 116 and 107.
I have had a play with adding HOME to the key 107 line in addition to the other two commands, but it didn't work. I was hoping to be able to regain the Home key long press functionality. Oh well.
On the other hand, I have now added | (pipe) to the Fn Z key press, which will be useful when using ssh. Also, I was going to add tab for the same reason, but I discovered that it is already mapped to Fn space, so I didn't need to!
Somehow that's strange. I've just updated to the latest rootfs (XDAndroid2.2Froyo.110110.rar) and am using the latest kernel (3.11.2010) and in my rootfs I still have
Code:
key 102 HOME WAKE # Power button
key 107 ENDCALL WAKE_DROPPED
which means that Power button does nothing at all. If I change this to
Code:
key 107 HOME WAKE # Power button
key 116 ENDCALL WAKE_DROPPED
I basically get all what I want: Power Button becomes sleep/wake/end call and End button is Home. Long pressing it gives me the list of the recent apps.
Can it be that you're using some other rootfs?
Hey Bombenbach,
is your ä, ö and ü working correctly now with your modified keymap? Always writing big, sucks
If the Funcion is well, how can i replace the old one?! With rootexplorer i can replace the old file but no change to the old problems .
Bieka said:
Hey Bombenbach,
is your ä, ö and ü working correctly now with your modified keymap? Always writing big, sucks
If the Funcion is well, how can i replace the old one?! With rootexplorer i can replace the old file but no change to the old problems .
Click to expand...
Click to collapse
I haven't tried, but if you replace it when running Android then reboot, does it not work?
Sent from my MSM using XDA App
As I've already said in my first post, with my modified keyboard all umlauts work fine including capital letters.
I replaced the file by mounting rootfs.img on the SD card in Linux. This way everything is persistent.
Maybe you can't edit rootfs.img when running Android, like you tried with rootexplorer. Unfortunately, I'm not really familiar with Android file permissions or rootexplorer, so I can't tell another way to replace the file except of using a Linux distro for that.
Bombenbach said:
As I've already said in my first post, with my modified keyboard all umlauts work fine including capital letters.
I replaced the file by mounting rootfs.img on the SD card in Linux. This way everything is persistent.
Maybe you can't edit rootfs.img when running Android, like you tried with rootexplorer. Unfortunately, I'm not really familiar with Android file permissions or rootexplorer, so I can't tell another way to replace the file except of using a Linux distro for that.
Click to expand...
Click to collapse
Hey Bombenbach,
of course i read your posts but i thought you explored other ways to replace this file . I've got a Kubuntu version installed and tried to change the files inside the .img files but i wasn't able to open then. I must say that my Linux knowledge is not that good .
I tried to replace the files inside with droid explorer. I could explore and replace both existing *.kcm.bin files inside the folders "/init.etc/keymaps/" and "/etc/keymaps/" but after the reboot I started to write a sms just to test if i could type ä,ö and ü but there was no change before the replacement . So did you know any further folders where i can replace these files? Or must i replace them in the *.img files as Bombenbach said to make a permanent result?!
@Bombenbach are you running the newest kernel (11/3) on your Rhodium100_de? I still search for a reason why my and other Rhodiums are freezing with kernels newer then 10/23 (1st). The funny thing is, i got auto backlight in the first kernel although it was just announced for the second kernel .
Best regards
Bieka
Bieka said:
I've got a Kubuntu version installed and tried to change the files inside the .img files but i wasn't able to open then. I must say that my Linux knowledge is not that good .
I tried to replace the files inside with droid explorer. I could explore and replace both existing *.kcm.bin files inside the folders "/init.etc/keymaps/" and "/etc/keymaps/" but after the reboot I started to write a sms just to test if i could type ä,ö and ü but there was no change before the replacement .
Click to expand...
Click to collapse
Extract bombenbach's kcm.bin file to your home directory. I have used ~/ below to represent your home directory (~/ will expand to /home/username/ automatically)
Work out from the automounted SD card what the path is to your rootfs.img. Or put a copy in your home directory. Either way, substitute appropriately below.
Open a shell/command line in kubunu
Code:
mkdir rootfsimg
sudo mount path-to-rootfs.img ~/rootfsimg -o loop
sudo cp ~/rhod100_de_microp-keypad.kcm.bin ~/rootfsimg/init.etc/keymaps/
sudo umount rootfsimg
sudo is linux speak for 'Do what I tell you, don't argue', so don't abuse it!
Hope that helps.
Edit: I just remembered that I think when I did this, I needed to reset the permissions and/or ownership of the new file.
Code:
ls -l ~/rootfsimg/init.etc/keymaps
will indicate if the permissions or ownership look wrong.
'chmod' is the command to change permissions, and 'chown' is the command to change ownership. Both will require sudo in this instance, but I can't give you the full command without knowing what they were supposed to be!
Bieka said:
Or must i replace them in the *.img files as Bombenbach said to make a permanent result?!
Click to expand...
Click to collapse
I guess you should try it this way. If it still won't work, I'll take a further look at it.
Bieka said:
Hey Bombenbach,
@Bombenbach are you running the newest kernel (11/3) on your Rhodium100_de? I still search for a reason why my and other Rhodiums are freezing with kernels newer then 10/23 (1st). The funny thing is, i got auto backlight in the first kernel although it was just announced for the second kernel .
Click to expand...
Click to collapse
Yes and it actually runs pretty well. As far as freezing is concerned, I guess there might be more differences between different Rhodium flavours then we are aware of, like the hardware of two different Rhod100_de's is not completely identical.
While I was still devving on Rhobuntu there also were always people who complained about freezes and crashes whereas others claimed that they had no problems whatsoever.
But that is just a speculation.
Hey,
first of all thanks snalbansed and Bombenbach for your help. I started Kubuntu and tried your way. The Sudo command is explaind very funny of course i know this command from debian on my VServer . Some commands are in my brain but very unsorted. I'm just happy that i rent the server with a friend who knows Linux better then me . But back to Topic.
I have done all what you explained, but first thing i saw when I umount the rootfsimg is that the img file only got a filesize of 1.6MB and not 15 MB. I copied it to my card and started Android but after some text flying by in the bootsequence i just can read that he found an error and restarts in 3...2...1...reboot.
So the easy way should be that i find out what i made wrong but with this fast flying text, it is impossible.
I just tested again replacing the file with root explorer. This time i discovered a mysterious thing. When i delete the kcm.bin file go out of the folder and come back to it, it is just there. So i think, this was just temporarly deleted. I don't know if i am the only one with this "problem" but this is just curious.
So before posting thousands of sites full of noob questions i just wanted to ask if someone can upload a modified version with this file in it and meanwhile i teach myself in Linux .
Otherwise, if someone has another clue. Just as replacing the file in the img with an application in windows like a Zip Folder, i am all ears.
Here is a modified rootfs.img from XDAndroid2.2Froyo.110110.rar
Modifications:
- replace rhod100_de_microp-keypad.kcm.bin
- switch Home and End on Rhodiums (as described by me in this thread)
Bieka said:
I just tested again replacing the file with root explorer. This time i discovered a mysterious thing. When i delete the kcm.bin file go out of the folder and come back to it, it is just there. So i think, this was just temporarly deleted. I don't know if i am the only one with this "problem" but this is just curious.
Click to expand...
Click to collapse
I guess within Android, this might be considered to be ROM?
Bieka said:
So before posting thousands of sites full of noob questions i just wanted to ask if someone can upload a modified version with this file in it and meanwhile i teach myself in Linux .
Otherwise, if someone has another clue. Just as replacing the file in the img with an application in windows like a Zip Folder, i am all ears.
Click to expand...
Click to collapse
Once mounted, you can use cd and ls to work your way round the img, less to see the contents of files and nano to edit them. You could also use the file explorer in kubuntu to do the job (again, once mounted), but I think you will need the file explorer to run as root. In Gnome/Ubuntu, you would type gksudo nautilus and nautilus (the Gnome file explorer) will start with root permissions. I can't remember the kde equivalent off the top of my head. If you can do it this way, you'll also be able to check/fix permissions etc with a right click - properties.
Sent from my MSM using XDA App
Hey Bombenbach,
thanks for the uploaded rootfs.img. In the meantime i did it and got the rootfs.img changed as described. Again a very big thanks to you and your work!!! Finally typing an e-mail is a real pleasure and didn't looks like my Capslock is brocken for only Ü Ö and ä .
Also a big thank to snalbansed for your patience . You were right with your expect that my failure were the rights. I started sudo dolphin so i could replace the file in init.etc and do a sudo umount rootfsimg. Suprise suprise it worked .
So now for the next quest Is it possible to map some keys on Keyboard to Applications, Functions or like winmo a board of signs. Or isn't there equivalent in Android to that?
Best Regards
Bieka
looking for a volunteer
I've been working on updating the keymaps & layouts for those rhodiums that have keymap source files available and I've noticed that there isn't a source file available for the German rhod100. Judging by the activity in this thread, there appears to be quite a bit of interest in the German keymap. I was thus wondering if someone who speaks German and has a German rhodium would be interested in making a kcm source file for inclusion into the official rootfs that everyone can use.
If someone is willing to make the file, I can provide the sources for the T-Mobile US Rhod 210 and the Nordic version of the Rhod 100 from the XDAndroid repo as examples/templates. I can also compile it for you if you don't already have the kcm compiler. If it works well and people are happy with it, I'll roll it into the keymap update that I plan to submit to the rootfs git in the near future. This way you won't have to add it in again yourself every time the rootfs gets updated.
Ok so I have a problem, I would think most users have this too: The max volume level being too low. So I went ahead to search google for help, and downloaded "Ultra volume mod" now what I'm supposed to do is to overwrite the "default_gain.config" but when I do, it says permission denied. So I tried another method, manually editing the code. Now it justs says that an error occured when I try to save it. I did a little digging on the internet, and found out that my system is apparently read-only, how do I change that? Oh yeah, I'm currently using ES File Explorer, most people said theres a button to mount something but I can't find the button, maybe thats the fix to it? I have the latest updated version of the root explorer and I still cant find the mount button.
Well, while you're here can you help me with another one? On game hacking apps such as GameCIH or GameGuardian, either right after I grant root permission, it says "error: root denied" or it says nothing and when I try to change the code, nothing happens. Thanks for helping.
Device: Samsung Galaxy Note II GT-17005
Root: Yes
OS: Android Jellybean 4.3, Stock.
Any other info thats needed? Please say so, I will do my best to provide them. And please don't post complicated stuff, the most I can do is read simple codes and edit them, such as the volume one. I cant decode, read complex codes or create codes, if theres anything complicated, please try your best to explain how to do it. Thank you in advance for your help.
Portalception said:
Ok so I have a problem, I would think most users have this too: The max volume level being too low. So I went ahead to search google for help, and downloaded "Ultra volume mod" now what I'm supposed to do is to overwrite the "default_gain.config" but when I do, it says permission denied. So I tried another method, manually editing the code. Now it justs says that an error occured when I try to save it. I did a little digging on the internet, and found out that my system is apparently read-only, how do I change that? Oh yeah, I'm currently using ES File Explorer, most people said theres a button to mount something but I can't find the button, maybe thats the fix to it? I have the latest updated version of the root explorer and I still cant find the mount button.
Well, while you're here can you help me with another one? On game hacking apps such as GameCIH or GameGuardian, either right after I grant root permission, it says "error: root denied" or it says nothing and when I try to change the code, nothing happens. Thanks for helping.
Device: Samsung Galaxy Note II GT-17005
Root: Yes
OS: Android Jellybean 4.3, Stock.
Any other info thats needed? Please say so, I will do my best to provide them. And please don't post complicated stuff, the most I can do is read simple codes and edit them, such as the volume one. I cant decode, read complex codes or create codes, if theres anything complicated, please try your best to explain how to do it. Thank you in advance for your help.
Click to expand...
Click to collapse
Open ES file explorer hit menu button ,scroll down, check mark root explorer ,slider will turn blue,then click extreme left of root explorer you'll get a pop up with few options,click on Mount R/W then another pop up comes up and you'll see RO and RW columns,and 4 rows of options.Select the RW column for each of the row options.That would mount your system to read and write files just like you are doing right now.Once you change your default_gain.conf it will ask you to replace it with existing one (you should make a back up of your original one on the sd card) then replace it,long press on the new file click on MORE at the bottom right then Properties then you'll see permissions as RWX-RWX-RWX- and Change next to it.click on change and you'll see 3 rows and 3 columns make it read as RW-R-R basically selecting first 2 columns for first option and only the first option for 2nd and 3rd row.Click ok,exit the es file explorer and reboot your phone. I am attaching images below so you can get visual help as well (my options differ a bit under es file explorer since im not running TW ROM but concept is same
Note: Root is must (I see you've mentioned you are rooted)
Thank you so much for the help, it worked perfectly, now my volume is just as its supposed to be. Thank you for your help, now i just need someone to answer my second question.
2nd one sounds like an app issue now you have confirmed it's not a root issue. Probably don't work on 4.3. Think I remember seeing groans from game cheaters about apps not being supported.
Oh okay... well, i tried out the mod, forgot that 1db more is 3 times a loud as the bd before. Almost busted my cheapass earphones. Also the static noise you hear in idk, clash of clans during start up increased by at least 5 times. Switching back, luckily i took your advice on making a backup.Thanks guys, really helped me. In the shortest time of any other forum too.
Portalception said:
Oh okay... well, i tried out the mod, forgot that 1db more is 3 times a loud as the bd before. Almost busted my cheapass earphones. Also the static noise you hear in idk, clash of clans during start up increased by at least 5 times. Switching back, luckily i took your advice on making a backup.Thanks guys, really helped me. In the shortest time of any other forum too.
Click to expand...
Click to collapse
Ya many of us eat , breathe and sleep on xda and love to help out people cause we were also once in your shoes so I know how it feels when something doesn't work right ,the anxiety levels sky rocket at once and panick sets in.
Edit: You might want to quote people when responding to someone in particular so he/she gets notified otherwise they might not check back on the thread and your future questions might be left unanswered.Just a suggestion
Well if its just thanks i think they would like it if they didnt get spammed on email. Anyway i fixed the static problem, seems like the old speakerboost app i tried but did not delete was jealous of the mod, uninstalled and mod works like a charm.
hello i have a big trouble, i need to do a
hard reset to a galaxy tab 3 but the button up doesn't work
and the tablet its blocked by "too many pattern attempts", and don't have the USB debugging activate.
exist one way of do a hard reset by software or with other buttons ? or
how i jump( or break ) the "too many pattern attempts" locked display ??.
alfredosaurio said:
hello i have a big trouble, i need to do a
hard reset to a galaxy tab 3 but the button up doesn't work
and the tablet its blocked by "too many pattern attempts", and don't have the USB debugging activate.
exist one way of do a hard reset by software or with other buttons ? or
how i jump( or break ) the "too many pattern attempts" locked display ??.
Click to expand...
Click to collapse
open your tab very carefully and look at the buttons , see if you can find some kind of hard plastic
nub to super-glue to the plastic vol-up button. don't ask for a tutorial you can figure it out.
if the button is not fixable by that approach try to remove enough of the broken vol-up button
so you have room to fit a hard piece of plastic in the space left to actuate the actual trigger for vol-up.
do not use metal! requires dexerity.
alternately, if your tab is rooted, connect via adb and run
adb reboot recovery
once in recovery perform factory reset
or while in recovery locate the file you need to delete to nullify the lockscreen and delete them, do all of that
through adb shell. requires knowledge of command line operation. look it up.
be patient, be deliberate. you'll get it sorted.
m
moonbutt74 said:
open your tab very carefully and look at the buttons , see if you can find some kind of hard plastic
nub to super-glue to the plastic vol-up button. don't ask for a tutorial you can figure it out.
if the button is not fixable by that approach try to remove enough of the broken vol-up button
so you have room to fit a hard piece of plastic in the space left to actuate the actual trigger for vol-up.
do not use metal! requires dexerity.
alternately, if your tab is rooted, connect via adb and run
adb reboot recovery
once in recovery perform factory reset
or while in recovery locate the file you need to delete to nullify the lockscreen and delete them, do all of that
through adb shell. requires knowledge of command line operation. look it up.
be patient, be deliberate. you'll get it sorted.
m
Click to expand...
Click to collapse
I was afraid of having to open the device,
* because I have not the tools or the ability to do and honestly did not want to resort to a technician in my city,
* I thought that maybe It could be a solution out there that I do not know, but it seems that is the only, really thank you very much for your answer.
alfredosaurio said:
I was afraid of having to open the device,
* because I have not the tools or the ability to do and honestly did not want to resort to a technician in my city,
* I thought that maybe It could be a solution out there that I do not know, but it seems that is the only, really thank you very much for your answer.
Click to expand...
Click to collapse
You can try pressing on the up button really hard, or pressing hard slightly above the up button. (This sometimes works for me).
That said, it would be better in the long run if you actually fix the button. I should probably fix mine, but I haven't really wanted to take the time or the effort (I need to get a plastic stub of some sort).
As for opening up your device, it is easier than it may seem (if you have the tools). But you mentioned you don't have tools.
I would recommend buying some -- its only a few dollars, and it is worth it (especially if you are prone to breaking screens).
Seriously, seriously, look into fixing the button.
Going back to why you want to go into recovery mode, you may want to consider reflashing the device.
I have a few packages for Heimdall, but you would (probably) be better off using Kies. You will want to use the bad flash option (or something like it) in order to reflash your device. You will need to look at the back of your device for the information that Kies needs for a reflash. Since you are resetting anyway, you won't lose anything with this method.
You will need to go into download mode, which is [Power]+[Home]+[Vol Down].