Related
This guide attempts to solve the following problems:-
1. The menu and home buttons' keypresses are detected but the respective actions aren't executed.
2. The lockscreen doesn't get activated.
3. The power menu has only reboot and power off as options. The rest of the options like Airplane Mode and Profiles.
PREREQUISITES:
1. ADB
2. SQLITE3
FIX:
1-Copy sqlite3 to /system/bin
2- chmod 777 /system/bin/sqlite3
3-Type following command in ADB or Terminal Emulator
Code:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name,value) VALUES ('device_provisioned','1');"
4- Reboot
5- Done
This guide is based upon this post.
Have you tested this? Does this fix the anoying bug when you press menu and nothing happens so you have to press 2-3 times? Will the phone wake on back/menu press? Mine takes 2-3 clicks to wake with menu/back key, this is not the case with eclair.
2. The lockscreen doesn't get activated. - What do you mean by this? Is it when the lockscreen takes 1-2 seconds to appear after waking the phone? - this doesn't happen to me anymore thankfully.
ka'cipeder said:
Have you tested this? Does this fix the anoying bug when you press menu and nothing happens so you have to press 2-3 times? Will the phone wake on back/menu press? Mine takes 2-3 clicks to wake with menu/back key, this is not the case with eclair.
2. The lockscreen doesn't get activated. - What do you mean by this? Is it when the lockscreen takes 1-2 seconds to appear after waking the phone? - this doesn't happen to me anymore thankfully.
Click to expand...
Click to collapse
I think u misunderstood...
*Sometimes due to a weired bug in android, there are only 4 options in extended power menu..Power Off,Reboot,Recovery n Download.
*Home button does not works at all.
*Lock-screen is completely gone.
*Power menu just turns on the screen
*Sleep mode is gone.
U can search for the same problem over google but there was no sure shot solution... But now there is..
I myself faced it few times while cooking the roms and each time u face this bug, there is no other way than start from zero again....
Had the same problem ages ago.
It occurs if you remove SetupWizard.apk.
Leave it be, do a factory reset and all will be well.
ka'cipeder said:
Have you tested this? Does this fix the anoying bug when you press menu and nothing happens so you have to press 2-3 times? Will the phone wake on back/menu press? Mine takes 2-3 clicks to wake with menu/back key, this is not the case with eclair.
Click to expand...
Click to collapse
that's no bug. it's the normal behavior of froyo that you have to do a double click on the "outside buttons" to wake up the phone.
sent from the desert
Had this exact same problem yesterday. had to reflasb. And this happens after you switch roms with g3mod multiboot.
Sent from my GT-I5800 using XDA App
dilzo said:
Had this exact same problem yesterday. had to reflasb. And this happens after you switch roms with g3mod multiboot.
Sent from my GT-I5800 using XDA App
Click to expand...
Click to collapse
Exactly! thats why i prefer triboot/dualboot
Is it possible to include this fix in a rom?
Or to do it in recovery with a update.zip?
this is not even needed thomas You have deleted setupwizard.apk from system/app I think. If you delete that apk this happens just place it back. If you apply this but do not have the setupwizard.apk in your system it will come back after a while
I dont deleted it but maybe it is because i deodexed the rom... I wil try to replace it
Sent from my GT-I5800 using XDA App
Thanks Werker. It worked!
Sent from my GT-I5800 using Tapatalk
no problem
This tutorial worked for me. Thanks for the re-post and the shell script!
thanks a lot. i had this the 4th time while using cm9 before i came to this thread. and never had this in any other rom except cm9.
does anyone know what causes this bug?
arnab321 said:
thanks a lot. i had this the 4th time while using cm9 before i came to this thread. and never had this in any other rom except cm9.
does anyone know what causes this bug?
Click to expand...
Click to collapse
no, im still having the same problem on CM 7.2, after you remove Setup Wizard this problem occurs
Thanks a lot, I had this problem so many times, but this is the first time I am handling this without reflashing ROM. Thanks again.
Where can I find setupwizard.apk in not present in system/app
? Can u upload for cm7 a 8.3
Sent from my GT-I5800 using xda app-developers app
thanks! this totally saved my @ss.
I am on a SE Xperia Arc, rooted with CWM recovery, and a generic firmware 4.1.B.0.431.
I went into recovery mode and reset the phone, wiping everything. After that, this exact same problem appeared (home button non-functioning, no lock screen, etc...) Also, the phone would not receive calls! Data was working and was able to receive messages that way, and was able to dial out.
A few tips for people running this fix to save some time.
How to run an ADB terminal command line? Don't bother.
1. Just install something like Root Explorer.
2. copy sqlite3 to the /system/bin directory ON YOUR PHONE
3. change the permissions (that's that chmod 777 means)
4. give owner and group read and write permissions
5. IMPORTANT. copy the fix.sh (it's a script) to the ROOT of the phone. not /sdcard, but ROOT
6. just click on the fix.sh and select "excute) and the script will run and you will see output saying (done, reboot) or something.
good luck! and thanks for everybody's help!
rooted device
Hallo, in advance - sorry for my English (haven't spoke nor written for long time)
Do I need rooted device to go through arunmcops's procedure? I have galaxy Y pro (b5510) and after rooting then unrooting and factory reset, I have the same issue when home button doesn't react... Thanx in advance for any response.
Hi!
I have just encountered this bug (on my I9300) and tried to apply your fix, but sqlite crashes saying
Code:
soinfo_relocate(linker.cpp:1013): cannot locate symbol "sqlite3_load_extension" referenced by "sqlite3" ... CANNOT LINK EXECUTABLE
... what can I do?
I am sure all files have the right permissions, but apart from that I wasn't even able to find that error on google :/
hahaha nevermind... It worked the first time I tried it, I just had to reboot and actually turn the lockscreen on
So you want to keep (knox) warranty and still use root?
Well there is RDLV and the "forbidden" Tool for that, BUT you will still have SELinux on enforcing mode, which means you don't have full control even with root. While technically most things still do work, they might work a lil different or need a different approach.
Lets collect our findings here...
---
First of all, remounting system with apps like solid explorer does not seem to work.
A workaround for this is to run the following command in terminal or through quick terminal etc:
Code:
/system/bin/mount -o rw,remount /dev/block/mmcblk0p2 /system
This command gets through where other methods fail. Once you have mounted the system writable like this, you can go back to your root explorer app to delete things etc on system partition. Solid explorer gives me error messages still when I delete apps from /system/app/, but they still disappear / get deleted.
---
This also brings me to my next workaround:
To delete system apps and not just freeze them with Titanium, you need to remount system like above and then delete the apks from the /system/app/ directory. A reboot should then remove everything else related to that app afaik. (like the /data/data/ of the app etc.)
Titanium on the other hand gives me an error when I try to delete a system app, even after remounting system to rw.
---
If you want to edit things from your system partition, like build.prop etc. Copy them to your sd first and edit them there. Then mount system rw, and create a backup of the file you are editing. (make a copy and just append "_bak" or smth to the file name) And finally copy the sd file over the corresponding file in system. Make sure you check permissions before and after you copied everything and edit them if they do not match up.
---
My final Tip for now:
I noticed that most root methods on SELinux (this includes RDLV and the forbidden one) use install-recovery.sh to start su as a system daemon which handles all the su requests. (as far as I understood it at least).
Well we can also use this file (or create an install-recovery-2.sh in /etc/ which gets called by the first one by default when you got the root) to run init.d scripts or other stuff.
I don't have tested it yet but I will put the code below once it works...
Code:
tbd
..
hopefully we find a way to turn off this selinux enforcing mode while keeping knox warranty at some point.. - xposed framework might be the answer but not sure - in theory its able to overwrite all methods used by apps. (but I guess selinux above xposed still in system rights and therefore cannot be affected by it?)
And another one:
Don't like this big n clunky user interface? The DPI for the Note 3 is set to 480, thats for old people! If you have want things a bit more refined and more "space" on the screen, edit your build.prop (like I mentioned above) and set the "ro.sf.lcd_density" value down.
I used 360 instead of 480 and that seems perfect to me. It looks like 240 DPI used to look on the Note 1. - You could try 320 or 400 as well.
If you want to set the dpi of individual apps, install xposed and the app settings module. (I would still set browser to 360 or even 320 dpi, 400 is just too much - the adress bar is so damn huge still)
Glad to see you still at it homie. Kingoapp is great. "Google kingoapp" anyone needing help. Just don't post any links please.
Sent from Heaven.
dallastx said:
Glad to see you still at it homie. Kingoapp is great. "Google kingoapp" anyone needing help. Just don't post any links please.
Sent from Heaven.
Click to expand...
Click to collapse
Definitely try out at least the dpi change to 360 or 400, that one is golden =). (nothing special but still..)
--
so far I haven't found anything that does not work at least with a workaround. Some apps do not work as supposed, but thats because they havent adapted yet to the new environment as far as I can tell. And yea, you cannot edit the selinux stuff or turn it off (at least not easy) but thats it. What I did not yet try, which is for risk-friendly people only anyway, is to mess with the efs folder. (you can change your devices mac there, good for privacy concerns hehe). Could be that selinux blocks that one as well, but other than that most things work alright. Just no custom recovery yet, but this could maybe be made possible through the install-recovery.sh file, telling it to start up a custom recovery but not actually flashing it hard onto the device.
Reboot apps I can't get to work. You know the apps that restart phone, bootloader etc... Even through the side 4 button mod. I can only reboot through factory restart. Pressing the power button and using the default restart button.
Sent from Heaven.
---------- Post added at 06:50 PM ---------- Previous post was at 06:49 PM ----------
Yea I always do DPI changes for Gmail , browser, settings, and few other apps
Sent from Heaven.
aww yea youre right - I havent got any app to reboot the phone yet, only the normal reboot through the stock power menu works for me. Didnt try terminal yet.
Maybe not "reboot" but "shutdown -r now"
dallastx said:
Reboot apps I can't get to work. You know the apps that restart phone, bootloader etc... Even through the side 4 button mod. I can only reboot through factory restart. Pressing the power button and using the default restart button.
Click to expand...
Click to collapse
The 4 way reboot menu from Wanam's xposed module works fine for me if you wanted to check that out.
I got one. Enter download mode by powering off. Then hold volume_down+home+power then press volume_up when promtped. Ok now this is what blows my mind. Everyone says pull battery to exit. I did this and the center off my screen looked messed up for about 8 seconds and I thought there must be a better way. Guess what to exit just hold power by itself for about 10 secs and you reboot out of download mode. Great easy way to check counter and no longer have to remove case, battery, etc.
Sent from my SM-N900W8 using XDA Premium 4 mobile app
TheAvatar said:
The 4 way reboot menu from Wanam's xposed module works fine for me if you wanted to check that out.
Click to expand...
Click to collapse
Yea i tried it but didnt work... It may of been conflicting with other apps. But what root method are you using?
---------- Post added at 07:16 PM ---------- Previous post was at 07:11 PM ----------
JohnnyRebel said:
I got one. Enter download mode by powering off. Then hold volume_down+home+power then press volume_up when promtped. Ok now this is what blows my mind. Everyone says pull battery to exit. I did this and the center off my screen looked messed up for about 8 seconds and I thought there must be a better way. Guess what to exit just hold power by itself for about 10 secs and you reboot out of download mode. Great easy way to check counter and no longer have to remove case, battery, etc.
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yea i have always got out of download mode on Note 3 by just holding power button.
---------- Post added at 07:20 PM ---------- Previous post was at 07:16 PM ----------
zroice said:
And another one:
Don't like this big n clunky user interface? The DPI for the Note 3 is set to 480, thats for old people! If you have want things a bit more refined and more "space" on the screen, edit your build.prop (like I mentioned above) and set the "ro.sf.lcd_density" value down.
I used 360 instead of 480 and that seems perfect to me. It looks like 240 DPI used to look on the Note 1. - You could try 320 or 400 as well.
If you want to set the dpi of individual apps, install xposed and the app settings module. (I would still set browser to 360 or even 320 dpi, 400 is just too much - the adress bar is so damn huge still)
Click to expand...
Click to collapse
Only reason i wouldn't change the DPI for everything because some apps will look crazy. Then you will have apps also like the play store that may not work correctly.
JohnnyRebel said:
I got one. Enter download mode by powering off. Then hold volume_down+home+power then press volume_up when promtped. Ok now this is what blows my mind. Everyone says pull battery to exit. I did this and the center off my screen looked messed up for about 8 seconds and I thought there must be a better way. Guess what to exit just hold power by itself for about 10 secs and you reboot out of download mode. Great easy way to check counter and no longer have to remove case, battery, etc.
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
good finding! (lol i couldve came up with this myself lol - holding power long enough always does a forced reboot).
I noticed too that when you pull the battery that sometimes you get lines on the screen - really scary, thought I messed up my device but after like 10 seconds or so they disappeared. But definitely something you want to avoid!
Holding down power to exit the download mode instead of pulling battery from now on.
I use Rootr Browser Pro... I can delete things out of the system partition and write into the system partition (after setting it for root privelege in settings and supersu) however I can''t just overwrite files.... The file I wish to overwrite must 1st be deleted or renamed,usually with .bak. Haven't had to use terminal.
Another handy tip, in the CSC folder, rename the customer.xls to customer.xls.bak and then a new option will be available in the settings/device/lock screen menu to add app shortcuts to the lock screen
if you add this code to the others.xml file AFTER <FeatureSet> and BEFORE </FeatureSet>
<CscFeature_Sip_UseSymbolInCMKey>true</CscFeature_Sip_UseSymbolInCMKey>
<CscFeature_Sip_EnableSymbolInSecondary>en_GB;en_U S;de;fr;es;it</CscFeature_Sip_EnableSymbolInSecondary>
You will then enable sub symbols on the default keyboard.
Works a dream...
TheAvatar said:
The 4 way reboot menu from Wanam's xposed module works fine for me if you wanted to check that out.
Click to expand...
Click to collapse
wait a minute - the 4 way reboot does work for you? Are you on Knox 0x0 still? And SELinux status enforcing? For me no "reboot" apps seem to work. They all just try to reboot (and SELinux denies it then most likely)
---
one other problem occured: when using xprivacy and deinstalling an app the system locks up. Can someone confirm this?
Why do people insist on DELETING apps from system? Just use pm disable, sheesh.
khaytsus said:
Why do people insist on DELETING apps from system? Just use pm disable, sheesh.
Click to expand...
Click to collapse
The xprivacy lockup also happens with user apps deinstallation. Just want to make sure its not me or my setup but xprivacy thats causing this. I turned it off and it works, turn it on, device hangs on deinstallations.
zroice said:
And another one:
Don't like this big n clunky user interface? The DPI for the Note 3 is set to 480, thats for old people! If you have want things a bit more refined and more "space" on the screen, edit your build.prop (like I mentioned above) and set the "ro.sf.lcd_density" value down.
I used 360 instead of 480 and that seems perfect to me. It looks like 240 DPI used to look on the Note 1. - You could try 320 or 400 as well.
If you want to set the dpi of individual apps, install xposed and the app settings module. (I would still set browser to 360 or even 320 dpi, 400 is just too much - the adress bar is so damn huge still)
Click to expand...
Click to collapse
Yeah, thanks for the tip. I used xpose app setting to set my nova launcher to be about 400. I will try modify the build.prop then.
Ok so what i did to quickly update to mj4 since it is now live. "you will lose root and everything on internal storage so back it up"
Be sure make COPY of backup of your titanium folder if use NOVA be sure to do a backup of your current layout. Copy these folders to your EXTsd. Remove card afterwards.
I was rooted so i kept getting "Cant up dated Modded system". Even unrooting i cant getting Modded system. I use almost the same root method as OP uses called kingoapp "cant provide links so google is your friend"
Anyhow.. i wanted to make sure i didnt trip KNOX and grew impatient for an update.zip. I didnt want to flash anything through ODIN, so i figured would use Kies.
Kies will see your phone as already updated. At the top of the app if you click tools then "firmware and initialization" Kies will override whatever is on your phone and update to mI5. This will take about 30 min but much quicker then trying to download the entire stock firmware from hotfile.
Once your phone is up go ahead and go to to settings on you phone and system update. Update will run and restart your phone. You are now on the latest firmware mj4.
Reroot and reinstall SD card. You are now rooted on latest update.
Notes - I tried everything to try to trick system to thinking its not modded including unrooting. Nothing worked reasoning i resorted to flashing through Kies.
dallastx said:
Ok so what i did to quickly update to mj4 since it is now live. "you will lose root and everything on internal storage so back it up"
....
Click to expand...
Click to collapse
Ohh theres an update? Well I bought a 2nd note today - couldnt resist it was 500€ only (they usually go for about 550 here). And mine had some display issues... gonna sell the first one and keep second - screen is better. Anyway, I got to redo everything now and restore the "old one" to stock.
To restore stock safely I would always suggest using Kies and doing a forced firmware update like dallas described. I read that flashing the same firmware twice with odin can already trip knox. (at least if you were tempering with the system)
But note that this will most likely update the bootloader of your phone as well.
---
Now I got the old bootloader on my new and still branded n3 - can someone explain what the difference actually is to the new bootloader? I mean both don't allow SELinux permissive, and both can be rooted (at least with the "tool")?
On S4 etc I understand that new firmware version introduced knox, and that there was firmware out without knox, but if you upgraded once you couldnt go back. But there are no knox free firmwares for the n3 are there? (I mean stock ones)
zroice said:
Ohh theres an update? Well I bought a 2nd note today - couldnt resist it was 500€ only (they usually go for about 550 here). And mine had some display issues... gonna sell the first one and keep second - screen is better. Anyway, I got to redo everything now and restore the "old one" to stock.
To restore stock safely I would always suggest using Kies and doing a forced firmware update like dallas described. I read that flashing the same firmware twice with odin can already trip knox. (at least if you were tempering with the system)
But note that this will most likely update the bootloader of your phone as well.
---
Now I got the old bootloader on my new and still branded n3 - can someone explain what the difference actually is to the new bootloader? I mean both don't allow SELinux permissive, and both can be rooted (at least with the "tool")?
On S4 etc I understand that new firmware version introduced knox, and that there was firmware out without knox, but if you upgraded once you couldnt go back. But there are no knox free firmwares for the n3 are there? (I mean stock ones)
Click to expand...
Click to collapse
Yea go ahead and do all your updates then root. I think the update may me just for Sprint N900p.
so there is still no way to get rid of "enforcing selinux" without tripping knox counter?
need this only to get my OTG cable to USB OBD working, seems SELinux is blocking serial usb communication :/
zroice said:
wait a minute - the 4 way reboot does work for you? Are you on Knox 0x0 still? And SELinux status enforcing? For me no "reboot" apps seem to work. They all just try to reboot (and SELinux denies it then most likely)
Click to expand...
Click to collapse
Sorry for the late reply. I was Knox 0x0, used Root De La Vega, installed xposed framework then grabbed wanam from the play store. Just had to enable it and it was all good.
Hi,
I've set up an emulator using genymotion and am playing a game on it. What I need to do right now is:
Loop begin
2. Simulate a touch/tap at a particular location on the game.
3. sleep for 10 seconds
Loop end
I used to simulate the touch using xdotool in lunux. However, I think tasker should be able to handle this better. I'm a noob when it comes to tasker. I chanced upon a tutorial where in this guy explains how a touch can be simulated buy I'm stuck. It doesn't work. Here is what I've done so far:
1.Tasker > New task > "Test"
2.Run shell
Command:
while [ 1 ]; do
input tap 545 240
sleep 15
done
3. Run tasker.
4. Open the game.
Aaaaand.....nothing happen.
Please assist.
TIA.
Have you ran the task? You say run Tasker, but you still have to run the task or specify an event/condition when to run it.
polobunny said:
Have you ran the task? You say run Tasker, but you still have to run the task or specify an event/condition when to run it.
Click to expand...
Click to collapse
Um.. I pressed the play button, then switched to the game to see if it works every 10 seconds. But didn't work
blueren said:
Um.. I pressed the play button, then switched to the game to see if it works every 10 seconds. But didn't work
Click to expand...
Click to collapse
You ticked Use Root in Run shell?
polobunny said:
You ticked Use Root in Run shell?
Click to expand...
Click to collapse
Edit - Oh no.. I had forgotten to set a profile. Now that it's done, I'm able to get the basic tap command working. But when i put it in the while loop, it fails.
Yes- root enabled. Basic command works, loop doesnt.
blueren said:
Edit - Oh no.. I had forgotten to set a profile. Now that it's done, I'm able to get the basic tap command working. But when i put it in the while loop, it fails.
Yes- root enabled. Basic command works, loop doesnt.
Click to expand...
Click to collapse
That will help you ;D
http://tasker.dinglisch.net/userguide/en/flowcontrol.html
polobunny said:
That will help you ;D
http://tasker.dinglisch.net/userguide/en/flowcontrol.html
Click to expand...
Click to collapse
I had done a silly mistake -__- how stupid of me. Things work now! Thanks for you help.
<<Thread can be closed>>
Thread closed - OP request.
Got my oneplus today. It has not taken me long to get it rooted with TWRP. Many thanks to Chromium for his step by step process here http://forum.xda-developers.com/showthread.php?t=2788632.
I am a Tasker user and an app that I use is Secure Settings. When I go to enable the System+ Module, it tells me that Root Access Disabled. Root access is currently disabled for all applications by a system setting. This setting will prevent Secure Settings from performing several functions. Would you like to enable it now? When I select "yes" it takes me to my developer options page. I cannot figure out what to select to enable what it wants. I have used this app on my S3 and my LG G2 and have never had this come up. I am stuck!
I am running stock CM11s.
I am confirmed to have root access with Supersu. I am running xposed modules.
Under debugging check the root access setting is set to apps and adb.
Sent from my One using XDA Premium 4 mobile app
Edit-removed
From my N5 or OPO
truckroot said:
In Android Terminal Emulator type:
su (hit enter)
-then grant it SU access
then type:
setprop persist.sys.root_access 3
(hit enter)
Profit?
Read about this on OPO forum. Directions came from dev of Secure Settings.
From my N5 or OPO
Click to expand...
Click to collapse
Not long after submitting this post I managed to get it to accept root access. I think it worked when after it took me to the developer options screen, I turned the developer options to OFF, then back ON. Then, bam!, it worked. Go figure...
Anyway, thanks for the help. I had done a Google search and came up empty handed but should have done a search within the XDA forums. My bad.
truckroot said:
In Android Terminal Emulator type:
su (hit enter)
-then grant it SU access
then type:
setprop persist.sys.root_access 3
(hit enter)
Profit?
Read about this on OPO forum. Directions came from dev of Secure Settings.
From my N5 or OPO
Click to expand...
Click to collapse
I had the same problem as the OP. I did the setprop persist.sys.root_access 3. This allowed me to turn on System+ in Secure Settings. However, now Tasker force closes every time I run it. It will run, but as soon as I switch away or run a task it will stop. How do I undo this change short of reinstalling my rom?
---------- Post added at 02:27 PM ---------- Previous post was at 02:05 PM ----------
frankos72 said:
I had the same problem as the OP. I did the setprop persist.sys.root_access 3. This allowed me to turn on System+ in Secure Settings. However, now Tasker force closes every time I run it. It will run, but as soon as I switch away or run a task it will stop. How do I undo this change short of reinstalling my rom?
Click to expand...
Click to collapse
Okay, so I found somewhere that the default setting for persist.sys.root_access is 1 so I set it back to 1. Still no luck. But I did get it fixed.
First, I backed up tasker, then I uninstalled Tasker and Secure Settings, Reinstalled tasker, restored my backup then installed secure settings. It let me endable System+ Right away and all seems to be working. WHEW. I was getting frustrated to the point of considering selling the phone cause tasker didn't work.
kevinga said:
...I turned the developer options to OFF, then back ON. Then, bam!, it worked...
Click to expand...
Click to collapse
Worked for me, too.. Thanks very much for posting.
kevinga said:
Not long after submitting this post I managed to get it to accept root access. I think it worked when after it took me to the developer options screen, I turned the developer options to OFF, then back ON. Then, bam!, it worked. Go figure...
Click to expand...
Click to collapse
This worked for me as well. Thanks!
kevinga said:
Not long after submitting this post I managed to get it to accept root access. I think it worked when after it took me to the developer options screen, I turned the developer options to OFF, then back ON. Then, bam!, it worked. Go figure...
Anyway, thanks for the help. I had done a Google search and came up empty handed but should have done a search within the XDA forums. My bad.
Click to expand...
Click to collapse
This fixed the issue for me. Thanks!
Sent from my A0001 using Tapatalk
kevinga said:
Not long after submitting this post I managed to get it to accept root access. I think it worked when after it took me to the developer options screen, I turned the developer options to OFF, then back ON. Then, bam!, it worked. Go figure...
Anyway, thanks for the help. I had done a Google search and came up empty handed but should have done a search within the XDA forums. My bad.
Click to expand...
Click to collapse
The on/off method worked for me. Thanks!
kevinga said:
Not long after submitting this post I managed to get it to accept root access. I think it worked when after it took me to the developer options screen, I turned the developer options to OFF, then back ON. Then, bam!, it worked. Go figure...
Click to expand...
Click to collapse
Works for me, too, thanks! I also would like to note, for future Googlers, that this is in a user build variant, not userdebug, with SuperSU zip-flashed. Just so anyone knows that it works for it, too.
Hey guys, just got my Pixel today. I was wondering if there is a mod that turns the earpiece into a loud speaker like the mod for the XL? Thanks.
I am using this:
https://forum.xda-developers.com/pixel-xl/themes/mod-enabling-dual-speaker-audio-playback-t3492257
However, do note that the earpiece speaker is too soft and negligible to work together for Stereo. My goal is to get the speaker to be louder and it does that.
It's all explained in the thread
MasK said:
I am using this:
https://forum.xda-developers.com/pixel-xl/themes/mod-enabling-dual-speaker-audio-playback-t3492257
However, do note that the earpiece speaker is too soft and negligible to work together for Stereo. My goal is to get the speaker to be louder and it does that.
It's all explained in the thread
Click to expand...
Click to collapse
Does this work for the non-XL pixel? The reason I ask is because I thought that was only for the XL. I'll give it a try tomorrow though.
evolzar510 said:
Does this work for the non-XL pixel? The reason I ask is because I thought that was only for the XL. I'll give it a try tomorrow though.
Click to expand...
Click to collapse
Yes it does.
I followed the steps and set to force maximum gain all the time. Then froze the app as I didn't wan't the notification showing up. The setting just stays.
MasK said:
Yes it does.
I followed the steps and set to force maximum gain all the time. Then froze the app as I didn't wan't the notification showing up. The setting just stays.
Click to expand...
Click to collapse
Cool! Thanks.
MasK said:
Yes it does.
I followed the steps and set to force maximum gain all the time. Then froze the app as I didn't wan't the notification showing up. The setting just stays.
Click to expand...
Click to collapse
I just tried to do the mod and it hasn't worked for me. When I try to use the adb commands, it always says no such file or directory. I even tried the older method of dowloading the mixer_paths file but I can't change permissions for that. How did you manage to do it?
evolzar510 said:
I just tried to do the mod and it hasn't worked for me. When I try to use the adb commands, it always says no such file or directory. I even tried the older method of dowloading the mixer_paths file but I can't change permissions for that. How did you manage to do it?
Click to expand...
Click to collapse
Well, there are 3 steps.
For first step, I simply copied the gz file into the /data/local/tmp folder using root explorer. I found this method easier than ADB.
For 2nd/3rd step, you need to execute the commands in root shell. (type su, enter) to grant root access before doing the 2 commands.
MasK said:
Well, there are 3 steps.
For first step, I simply copied the gz file into the /data/local/tmp folder using root explorer. I found this method easier than ADB.
For 2nd/3rd step, you need to execute the commands in root shell. (type su, enter) to grant root access before doing the 2 commands.
Click to expand...
Click to collapse
When I try to type in the commands, it says "can't gzopen chdloc_hardware_audio_mods_pixel__no_ull.tar.gz........."
I've tried typing the adb commands on my computer and on my phone through Material Terminal app.
evolzar510 said:
When I try to type in the commands, it says "can't gzopen chdloc_hardware_audio_mods_pixel__no_ull.tar.gz........."
I've tried typing the adb commands on my computer and on my phone through Material Terminal app.
Click to expand...
Click to collapse
Hmm.. you got root access in your terminal right?
Try posting on the thread itself.. You may get better help there Sorry
MasK said:
Hmm.. you got root access in your terminal right?
Try posting on the thread itself.. You may get better help there Sorry
Click to expand...
Click to collapse
Yep, I finally managed to do it. And it is true what they say, the earpiece volume is a lot quieter than the bottom speaker but at least it's something, lol.
MasK said:
Yes it does.
I followed the steps and set to force maximum gain all the time. Then froze the app as I didn't wan't the notification showing up. The setting just stays.
Click to expand...
Click to collapse
Can you show me where you edited this setting, I built a magisk module for this mod and it is in the xl forum. People are asking about it being louder