Database Users

[Q] Phone freezes when in lock for too long.

Hi, I have a problem with the whole locking the Android for too long. The problem is this, when I lock my HTC HD2 for too long, the screen freezes and doesnt come back on unless I remove the battery and re-boot.
Is there a solution for this?
And if so, can it be posted?
Thanks in advance

Sklar said:
Hi, I have a problem with the whole locking the Android for too long. The problem is this, when I lock my HTC HD2 for too long, the screen freezes and doesnt come back on unless I remove the battery and re-boot.
Is there a solution for this?
And if so, can it be posted?
Thanks in advance
Click to expand...
Click to collapse
Try using SETCPU application from market. Set the setting to SMARTASS...

jalshah05 said:
Try using SETCPU application from market. Set the setting to SMARTASS...
Click to expand...
Click to collapse
Thanks for the quick response, but how do I set it to SMARTASS?
I have SetCPU 2.0.2 autodetect read-only. It doesnt seem I can edit this 'Scaling'
Dropdown box, is this where the SMARTASS option is?

Sklar said:
Thanks for the quick response, but how do I set it to SMARTASS?
I have SetCPU 2.0.2 autodetect read-only. It doesnt seem I can edit this 'Scaling'
Dropdown box, is this where the SMARTASS option is?
Click to expand...
Click to collapse
Set Scaling to smartass

jalshah05 said:
Set Scaling to smartass
Click to expand...
Click to collapse
It won't let me, the box is grey, and just says 'ondemand' I can edit it.

Sklar said:
It won't let me, the box is grey, and just says 'ondemand' I can edit it.
Click to expand...
Click to collapse
Do you have rooted build? Mostly all the builds are rooted. But sometimes in some builds root permissions have problem. You can check whether you have root or not by following method:-
Download terminal emulator from market(free)
Open emulator and type "su" without quotations and press enter
if you do not get any errors then you have root enabled. If you have some errors then you might have to find solution to root your build.

I also got lock freezes that appeared at some point. I started remembering what I was installing and guessed it might be the poweramp lockscreen widget. I disabled it yesterday and did not have any lockscreen freezes today.
Sent from my HTC HD2 using XDA App

jalshah05 said:
Do you have rooted build? Mostly all the builds are rooted. But sometimes in some builds root permissions have problem. You can check whether you have root or not by following method:-
Download terminal emulator from market(free)
Open emulator and type "su" without quotations and press enter
if you do not get any errors then you have root enabled. If you have some errors then you might have to find solution to root your build.
Click to expand...
Click to collapse
When I try this in the terminal I get the 'Permission Denied' Error.
How can I solve this?

Sklar said:
When I try this in the terminal I get the 'Permission Denied' Error.
How can I solve this?
Click to expand...
Click to collapse
Well I am not a pro in the matter of rooting the build... I would recommend you to search the thread of your own build. May be someone else had the same problem. Another thing you can do is post another question about rooting the phone, may be someone expert will help you out....

jalshah05 said:
Well I am not a pro in the matter of rooting the build... I would recommend you to search the thread of your own build. May be someone else had the same problem. Another thing you can do is post another question about rooting the phone, may be someone expert will help you out....
Click to expand...
Click to collapse
What on Earth is rooting? D:

Sklar said:
What on Earth is rooting? D:
Click to expand...
Click to collapse
Well in regular android you do have access to some part of the system. To get that access you need to root your android.

jalshah05 said:
Well in regular android you do have access to some part of the system. To get that access you need to root your android.
Click to expand...
Click to collapse
Do you have any clue how to do that?

Which Build are you using??? Posting the Build version and kernel you're using might help others help you.

Sklar said:
Do you have any clue how to do that?
Click to expand...
Click to collapse
No man... I am also a newb... I do not know much about this. What I would do is flash another build. There are plenty of them out there.

Try z4root http://forum.xda-developers.com/showthread.php?t=833953

WiFi APs with PASSWORDs get FORGOTTEN

I'm having the issue after updating my ROM MJ1->MJ4, from older stock rooted to newer stock rooted.
My WiFi network Passwords Keep Getting Forgotten.
I notice the network entries with passwords inside the [ wifi_supplicant.conf ] file keeps getting erased, once you turn OFF and ON the WiFi
Is anyone on MJ4 ROM having or NOT HAVING this problem?
Any suggestions?

SOLUTION:
kevg77 said:
I have seen that others are having the same issue that I am having where my phone forgets WiFi settings after every reboot since MJ4 update. What is the fix for this?
Thanks
Click to expand...
Click to collapse
kevg77 said:
WiFi problems?
Try this:
Due to "securestorage" being set to true in build.prop, changes to the ROM or kernel that aren't reflected in the ss_id file in /system/etc/secure_storage/.system.bin.wpa_supplicant/ can cause issues with WiFi among other things. You can set this to false yourself, or simply flash the zip file below.
Download: Set Secure Storage to False
For those that prefer to do it manually, simply change this line ro.securestorage.support=true to false in /system/build.prop.
Click to expand...
Click to collapse
YOU'RE A LIFE SAVER!!!!!!!!!!!!!!!!!!!
:good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good:
Why was [ ro.securestorage.support=true] set to true? --Is this by ROM's default?
What functionality do we lose once it's set to "false"?

klau1 said:
SOLUTION:
YOU'RE A LIFE SAVER!!!!!!!!!!!!!!!!!!!
:good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good:
Why was [ ro.securestorage.support=true] set to true? --Is this by ROM's default?
What functionality do we lose once it's set to "false"?
Click to expand...
Click to collapse
Fixed for me as well - but why is this needed (ro.securestorage.support=false) even on stock ROM ?

AlexVK79 said:
Fixed for me as well - but why is this needed (ro.securestorage.support=false) even on stock ROM ?
Click to expand...
Click to collapse
I shall want to know also why it does not work on rom stock without root after full wipe with nand erase and pit file...
If somebody has a solution thank you

udate 13.3.2.2_user_322095220

AMAZON is at it again with update 13.3.2.2_user_322095220
i think we have a snitch for amazon in this forum and im pretty sure i know who it is!!!!!!
he always acts like he is going to do things to help other and then never comes through with the files and stuff that he says he is going to make for everyone and his brother just do happens to work for them!!!
http://dl.xda-developers.com/attach.../5/7/1/9/5/Screenshot_2014-03-29-09-58-38.png

Seriously... snitch? Wats the change log?

adix82 said:
Seriously... snitch? Wats the change log?
Click to expand...
Click to collapse
i would not doubt it
i dont know the change log
but i have seen two users report the 13.2.2.2 update
it could not be anything more than to mess up the work around that people have been getting away with by updating the build.prop
because when i try to change the build.prop to 14.3.2.2_user_322095220 in all the right places and try to save it the way i did before using root explorer it saves as 0 kb and is blank when i look at it.so i delete it and change the build.prop.bak file that is created when changing the build.prop back to build.prop because i am afraid to reboot with the blank one in fear of a brick

jjrizzelcincy said:
i would not doubt it
i dont know the change log
but i have seen to users report the 13.2.2.2 update
it could not be anything more than to mess up the work around that people have been getting away with by updating the build.prop
Click to expand...
Click to collapse
Would it be possible to post the build.prop file?
Thanks in advance...

sw01 said:
Would it be possible to post the build.prop file?
Thanks in advance...
Click to expand...
Click to collapse
i did not get updated.
i have mine in airplane mode

jjrizzelcincy said:
i did not get updated.
i have mine in airplane mode
Click to expand...
Click to collapse
Never mind, got the update file...Thanks!

sw01 said:
Never mind, got the update file...Thanks!
Click to expand...
Click to collapse
where did you find the file ?

jjrizzelcincy said:
where did you find the file ?
Click to expand...
Click to collapse
Go to Amazon download site and get the old link, substitute new version info...

sw01 said:
Go to Amazon download site and get the old link, substitute new version info...
Click to expand...
Click to collapse
i tried that by changing the build.prop but it would not let me it was just saving as a blank

jjrizzelcincy said:
i tried that by changing the build.prop but it would not let me it was just saving as a blank
Click to expand...
Click to collapse
Google "hdx 8.9 download"
Find the Amazon page that lets you manually download the updates
The download link points to 14.3.2.1..
Copy that link into a new browser window and edit it in two places
this is for 8.9 obviously

sw01 said:
Google "hdx 8.9 download"
Find the Amazon page that lets you manually download the updates
The download link points to 14.3.2.1..
Copy that link into a new browser window and edit it in two places
this is for 8.9 obviously
Click to expand...
Click to collapse
This Amazon page linked the download below: https://www.amazon.com/gp/help/customer/display.html?nodeId=201357220
https://s3.amazonaws.com/kindle-fire-updates/update-kindle-14.3.2.1_user_321093620.bin

What Changed?
Wonder what changed... the recovery, kernel(s) and system apps all appear to be the same. There must be some critical bugs that had to be urgently patched with this latest update coming so quick on the tail of the 13.3.2.1 update.
[Edit]Upon closer inspection, looks like there are some noticeable changes in the following apps:
WhisperlinkSdk.apk
WhisperplayActivityView.apk
WhisperplayCDSSettings.apk
WhisperplayCore.apk
WhisperplayQCSource.apk
com.amazon.communication.apk
com.amazon.tcomm.apk
[/Edit]

THANLS
I've updated 13.3.2.2, somehow opened when the machine is updated immediately so!!

I wonder if it would be possible to insert the SU binaries in this new update and then manually install it without breaking the signature

I just did a manual "Check Update" on my HDX 7 and it said no new updates, but only has 13.3.2.1.
I did sniff the traffic from the Kindle during this check and found that it contacted "softwareupdates.amazon.com" - which I now blocked in my router for what its worth.
Captured packets attached just in case they're useful.

Well crap. Blocking the server as above on my home LAN did stop the update from ever happening but I forgot to turn WiFi off at School and what do you know, 13.2.2 snuck right on in in a matter of minutes

Cevyn said:
Well crap. Blocking the server as above on my home LAN did stop the update from ever happening but I forgot to turn WiFi off at School and what do you know, 13.2.2 snuck right on in in a matter of minutes
Click to expand...
Click to collapse
Sucks.

evilgrin98 said:
Sucks.
Click to expand...
Click to collapse
Couple questions...
1. Once I stay out of the Stock rom it shouldn't update. Am I right on that?
2. If I have a rom slot with Fire OS loaded to it and in use. Can I turn on wifi and it not update?
3. I have the AOSP rom in as lot. Can I turn on wifi in this without fear of update?

Reckerr said:
Couple questions...
1. Once I stay out of the Stock rom it shouldn't update. Am I right on that?
2. If I have a rom slot with Fire OS loaded to it and in use. Can I turn on wifi and it not update?
3. I have the AOSP rom in as lot. Can I turn on wifi in this without fear of update?
Click to expand...
Click to collapse
install safestrap on both stock and rom slot one
so it will not be able to fully update it will bootloop back to safestrap according to GSLEON3

Update the hosts file on the kindle to point to localhost(127.0.0.1) or something. That might, or might not offer some help on WiFi you don't control. You'll need to still have root to do this of course.

Verizon Pixel XL- Toggling the oem unlock switch *SOLVED*

I have the Verizon Pixel XL and can now toggle the oem unlock switch in developers settings. Annoyed with the "grey out" I have done several things to make the switch useable. Well... Something worked. Now it's time to figure out what did the trick.
Solved. Using a root file explorer, got to /data/system/users/ 0.xml Open it up and edit it to reflect no restrictions. Or clone mine, might wanna remove my name though.. One requirement for this to work, all testing shows it will not work on stock kernel. Not sure if its a selinux issue or not but the modified ElementalX I made does boot up permissive and removes forceencryption. And using it Confirmed working..

I am decrypted and running permissive. All done through kernel editing. Not sure that made a difference or not but did notice any changes beforehand.

So you added the supercid through the kernel editing?

blueyes said:
I am decrypted and running permissive. All done through kernel editing. Not sure that made a difference or not but did notice any changes beforehand.
Click to expand...
Click to collapse
Sorry to be a bit off-topic but do you plan to document how you did the decrypt and permissive mode anywhere?

I'm guessing one of the unlock properties is what did it. I think something on the phone is recognizing it as a VZW model and is setting one of the properties to 0 and graying it out. I'll do some digging this weekend

dualityim said:
Sorry to be a bit off-topic but do you plan to document how you did the decrypt and permissive mode anywhere?
Click to expand...
Click to collapse
To decrypt you must fastboot format userdata. Flash a kernel the does NOT force encryption. Don't know if any are available so I edited the radial my self , on both kernel and boot-to-root images. To run permissive you simply add androidboot.selinux=permissive. I can upload the edited images later if your unfamiliar with modifications

jjayzx said:
So you added the supercid through the kernel editing?
Click to expand...
Click to collapse
Just added it to the kernel cmdline

blueyes said:
Just added it to the kernel cmdline
Click to expand...
Click to collapse
Thanks. I'll be back in a moment.
Update: It didn't work that way. Trying something a little different.
Update 2: Managed to change cid but still 0 for unlock support and grey. Going to try 1 more thing.

jjayzx said:
Thanks. I'll be back in a moment.
Update: It didn't work that way. Trying something a little different.
Update 2: Managed to change cid but still 0 for unlock support and grey. Going to try 1 more thing.
Click to expand...
Click to collapse
The kernel cmdline has to be edited before flashing. Try adding the persist.sys.oem_unlock... Line. Before run su , then set enforce 0

Why is being able to toggle it a big deal? If your unlocked then why does that matter ?

Rootuser3.0 said:
Why is being able to toggle it a big deal? If your unlocked then why does that matter ?
Click to expand...
Click to collapse
Who said it was a big deal. I clearly stated in op that it annoyed me. If you've got nothing positive to say then don't say anything.

blueyes said:
Who said it was a big deal. I clearly stated in op that it annoyed me. If you've got nothing positive to say then don't say anything.
Click to expand...
Click to collapse
And it's not just about being greyed out. I can now lock my bootloader and unlock it without any exploits. Simply using fastboot. Which sir, I do find to be a nice feature...

blueyes said:
Who said it was a big deal. I clearly stated in op that it annoyed me. If you've got nothing positive to say then don't say anything.
Click to expand...
Click to collapse
I never said you said" it was a big deal" I said that. Go kick rocks

I lost my ability of changing the cid but then i remembered it was after i had did the supercid. So when i put them both back my cid is now changed but my unlock support is still 0. I tried adding persist to default.prop but it didn't take or i did it wrong.

blueyes said:
To decrypt you must fastboot format userdata. Flash a kernel the does NOT force encryption. Don't know if any are available so I edited the radial my self , on both kernel and boot-to-root images. To run permissive you simply add androidboot.selinux=permissive. I can upload the edited images later if your unfamiliar with modifications
Click to expand...
Click to collapse
Did you do the kernel command on the phone? How do I edit default. Prop? I feel like that's where the transformation takes place since it's not editable like the build prop

jjayzx said:
I lost my ability of changing the cid but then i remembered it was after i had did the supercid. So when i put them both back my cid is now changed but my unlock support is still 0. I tried adding persist to default.prop but it didn't take or i did it wrong.
Click to expand...
Click to collapse
Did you add the line persist.sys.oem_unlock_supported=1.
Persists seems to be equivalent to a system override

Rootuser3.0 said:
I never said you said" it was a big deal" I said that. Go kick rocks
Click to expand...
Click to collapse
Go troll somewhere else.

blueyes said:
Did you add the line persist.sys.oem_unlock_supported=1.
Persists seems to be equivalent to a system override
Click to expand...
Click to collapse
Here's my build.prop
https://www.dropbox.com/s/bxgrk7ug66jiuz1/logs.zip?dl=0

cam30era said:
Use Android Image Kitchen > http://forum.xda-developers.com/showthread.php?t=2073775
Click to expand...
Click to collapse
Ok thank you and is this done through terminal or pc

cam30era said:
There are Windows and Linux versions (which I use). There's also a mobile version, but I've never used it.. Read @osm0sis thread. Very helpful.
Click to expand...
Click to collapse
That may be over my head as far as my abilities and I hate to create a new brick

[EXP] Verizon Pixel/Pixel 2 (& XL) Potential Bootloader Unlock Method

Since Android O implements a mechanism for us to "overlay" frameworks values via OMS, I thought maybe we could leverage that to find a way to disable the OEM unlock check that block Verizon Pixels from unlocking the bootloader.
For science, let's do an experiment If this works, then great, we have a bootloader unlock method for our Verizon brethren. If not, at least the APK is easy to uninstall.
Before proceeding, be advised that any experiments performed here may result in unforeseen consequences. By proceeding, you agree that neither I nor anyone else will be held responsible for said consequences, and that this will solely be at your own risk. Since this experiment applies only to Verizon phones, assume all warranties are null and void.
Prerequisites:
- Verizon Pixel/Pixel 2/XL
- Android OS updated to 8.1.0
- USB debugging enabled on the phone
- ADB installed and properly configured on your PC
- USB-C to USB-A cable (unless you have a USB C port on your PC, then you can use a C-to-C cable instead)
How to enable the experiment:
Download the attached APK
Sideload the APK
Open Command Prompt/PowerShell/Terminal, and type in "adb shell"
Type in "cmd overlay list" and hit enter
Confirm that "[ ] com.pixeloembypass" is in the list
Type in "cmd overlay enable com.pixeloembypass", and hit enter
Reboot the phone
Go into Developer Options to see if "OEM unlocking" can now be toggled on. If so, congratulations!
If "OEM unlocking" is able to be enabled, do so, and reboot the phone into fastboot mode. Unlock as per directions on the factory images site.
NOTE: As usual, if bootloader is unlocked/relocked, a factory reset will be performed.
How to uninstall the experiment:
Open Command Prompt/PowerShell/Terminal, and type in "adb shell"
Type in "cmd overlay list" and hit enter
Confirm that "[x] com.pixeloembypass" is in the list
Type in "cmd overlay disable com.pixeloembypass", and hit enter
Go into Settings->Apps, and uninstall "Pixel OEM Bypass"
Reboot the phone

This is amazing! Will try it here in about an hour and report back

Maybe tell these guys. They've been at it for a while. You might even get the bounty.
https://forum.xda-developers.com/pixel-2-xl/how-to/temp-root-bounty-verizon-users-t3710652

TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Sent from my iPhone using Tapatalk

djkinetic said:
TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
So? Come on dj! Lol
Sent from my Pixel 2 using XDA-Developers Legacy app

djkinetic said:
TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Click to expand...
Click to collapse
have more faith.. john mccain posted it after all

Hope it works
Sent from my Pixel 2 XL using Tapatalk

PresidentMcCain said:
Since Android O implements a mechanism for us to "overlay" frameworks values via OMS, I thought maybe we could leverage that to find a way to disable the OEM unlock check that block Verizon Pixels from unlocking the bootloader.
For science, let's do an experiment If this works, then great, we have a bootloader unlock method for our Verizon brethren. If not, at least the APK is easy to uninstall.
Before proceeding, be advised that any experiments performed here may result in unforeseen consequences. By proceeding, you agree that neither I nor anyone else will be held responsible for said consequences, and that this will solely be at your own risk. Since this experiment applies only to Verizon phones, assume all warranties are null and void.
Prerequisites:
- Verizon Pixel/Pixel 2/XL
- Android OS updated to 8.1.0
- USB debugging enabled on the phone
- ADB installed and properly configured on your PC
- USB-C to USB-A cable (unless you have a USB C port on your PC, then you can use a C-to-C cable instead)
Click to expand...
Click to collapse
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry, I am not trying to be a Debbie downer.
Edit:
I downloaded it on my phone just to see what permissions is calls for and it doesn't open the file.

Didn't work for me. Any tips to try?

thompatry said:
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry I am not trying to be a Debbie downer.
Click to expand...
Click to collapse
u can decompile the apk lol.. pretty sure its just an overlay thats suppose to "ungrey" the oem unlock switch to allow u to toggle it.. had afew ppl trying it.. first report it didnt do anything

elliwigy said:
u can decompile the apk lol.. pretty sure its just an overlay thats suppose to "ungrey" the oem unlock switch to allow u to toggle it.. had afew ppl trying it.. first report it didnt do anything
Click to expand...
Click to collapse
Ehh I am just lazy to decompile it. Just tell everyone what's inside of it from the get go and move on from there.
I figure it wouldn't work but hey, worth the try.

thompatry said:
Ehh I am just lazy to decompile it. Just tell everyone what's inside of it from the get go and move on from there.
I figure it wouldn't work but hey, worth the try.
Click to expand...
Click to collapse
i understand lol.. when im lazy i just use a file browser n view as an archive lol

collinjames said:
Didn't work for me. Any tips to try?
Click to expand...
Click to collapse
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed

thompatry said:
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry, I am not trying to be a Debbie downer.
Click to expand...
Click to collapse
That's okay, it's completely understandable. I agree - typically, you wouldn't want to install a random APK built by a stranger.
I wish I could test it myself, but both my Pixels are from the Google Store, and shelling out $650+ for a test device for a shot-in-the-dark experiment doesn't sound like very responsible spending.

Tried on my P2XL device and no luck..

nelsonTituaAa said:
Tried on my P2XL device and no luck..
Click to expand...
Click to collapse
Thanks for volunteering...have you gave this a try?
PresidentMcCain said:
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed
Click to expand...
Click to collapse

nelsonTituaAa said:
oops.. no haha.. will try again
Click to expand...
Click to collapse
PresidentMcCain said:
Thanks for volunteering...have you gave this a try?
Click to expand...
Click to collapse
tried it and still no luck.

PresidentMcCain said:
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed
Click to expand...
Click to collapse
Tried the command and doesn't seem like it disable android.auto_generated_rro__ on the overlay list.

tried this plus added recommendation and no luck. Verizon Pixel, 8.1

Anybody tried this on a Verizon Pixel 2? I'm willing to give it a shot, but would need a little more detail on the procedure if anyone is willing to help out.