Related
I find it strange that there's no "restart" feature in Android, and you have to completely turn the phone off and then turn it back on. I looked in the Market for a restart widget but couldn't find one. Does anyone know of one (for non-rooted phones)?
They exist. I think I used one called "Quick Boot". I stopped using it after I corrupted my sdcard once. I guess it was in use when I decided to reboot. I figure the time it takes to do a normal power off on sequence it worth it.
:edit: It does need root. Your phone cant do much without root
If you are the kind of user that wants to add features (reboot) you are going to need root access. If you just want to use your phone out of the box and not add any functionality, dont worry about root
reboot would be a better word to use while searching. There are several apps but all require root. Here is a free one if you decide to root for this feature.
BenKranged said:
They exist. I think I used one called "Quick Boot". I stopped using it after I corrupted my sdcard once. I guess it was in use when I decided to reboot. I figure the time it takes to do a normal power off on sequence it worth it.
:edit: It does need root. Your phone cant do much without root
Click to expand...
Click to collapse
I'm sure "quick" booting and "re" booting are two different things. A normal off/on would be a reboot. Quickbooting is some kind of condensed version developed to not take as much time. I also has negative results trying to quickboot my Captivate, so I haven't tried it again since.
rpimps said:
I find it strange that there's no "restart" feature in Android, and you have to completely turn the phone off and then turn it back on. I looked in the Market for a restart widget but couldn't find one. Does anyone know of one (for non-rooted phones)?
Click to expand...
Click to collapse
try widgetsoid.it has reboot and other things like temp
WiredPirate said:
I'm sure "quick" booting and "re" booting are two different things. A normal off/on would be a reboot. Quickbooting is some kind of condensed version developed to not take as much time. I also has negative results trying to quickboot my Captivate, so I haven't tried it again since.
Click to expand...
Click to collapse
The app "quick boot" I was using has several options including "reboot" and "hot boot". "Hot boot" never worked sucessfully on my captivate. The sd corruption I mentioned happened using the (full) "reboot" option. It worked fine lots of other times so Im not pointing my finger and saying this app will always do that. Just sharing my experience that it is a possibility.
rpimps said:
I find it strange that there's no "restart" feature in Android, and you have to completely turn the phone off and then turn it back on. I looked in the Market for a restart widget but couldn't find one. Does anyone know of one (for non-rooted phones)?
Click to expand...
Click to collapse
ps:all of restart appz need root
My daughters Huawei Ideos U8150 has a cracked screen, you can not unlock the screen because the crack is right in the middle of where you slide the unlocker.
So the phone although can be used to receive calls, can not be accessed via the screen.
She has also managed to somehow set it to not unlock the screen when receiving a call(no idea how she did this).
So I have 0 access to the phone.
I have a program Lock_2.0.apk but can not just install it with ADB because her phone of course is NOT in development mode.
In the custom AmonRA recovery, I can enable USB, and ADB will see the phone as "recovery".
But if I try to install the app that turns off the screen unloocker it says "/sbin/sh: pm: not found".
All I need to do is install that app to remove the screen locker and the phone is useable again.
Any idea how to get it into development mode with adb? Or some other way?
Thanks.
Sorry to dissapoint you, I don't know. But I want to know how's the the phone? I want one to give it to a friend, is it good?
You can buy a used phone on ebay, i saw them cheap.
netomx said:
Sorry to dissapoint you, I don't know. But I want to know how's the the phone? I want one to give it to a friend, is it good?
You can buy a used phone on ebay, i saw them cheap.
Click to expand...
Click to collapse
Screen is broken has a crack but its still useable im not buying her another one she has to learn to take care of her stuff.
But this problem is ridiculous its the screen lock that's causing the problem because you can still use the phone if it wasn't for screen lock.
There must be some way to install the no lock program.
Well, you can try to install a VNC server and access it via WiFi. Or you can try to make a factory reset... it will reset the lockscreen
And if you still interested:
http://www.ebay.com/itm/HUAWEI-COME...0726409219?pt=Cell_Phones&hash=item415c991003
netomx said:
Well, you can try to install a VNC server and access it via WiFi. Or you can try to make a factory reset... it will reset the lockscreen
And if you still interested:
Click to expand...
Click to collapse
Wifi is not turned on either
The only thing I have to do is install that un lock program and it will be fine but this is easier said than done.
Well, you can try, in recovery, to push the no lock apk to the folder /system/app and reboot... may be you can be lucky enough
netomx said:
Well, you can try, in recovery, to push the no lock apk to the folder /system/app and reboot... may be you can be lucky enough
Click to expand...
Click to collapse
It says it transferred it but its not working not installed.
Uber_Guber said:
It says it transferred it but its not working not installed.
Click to expand...
Click to collapse
I'm sorry I can't help you
a simple way would be just to get the screen replaced however you could refer to http://www.xda-developers.com/android/locked-out-learn-to-crack-the-android-pattern-lock/ to help get rid of lockscreen
bkr32 said:
a simple way would be just to get the screen replaced however you could refer to http://www.xda-developers.com/android/locked-out-learn-to-crack-the-android-pattern-lock/ to help get rid of lockscreen
Click to expand...
Click to collapse
Dude. Don't bring dead threads back to life. This hasn't had any posting in a year - how the hell do people even find these threads to resurrect? Reported.
bkr32 said:
a simple way would be just to get the screen replaced however you could refer to http://www.xda-developers.com/android/locked-out-learn-to-crack-the-android-pattern-lock/ to help get rid of lockscreen
Click to expand...
Click to collapse
Generally we very much appreciate users helping each other with questions, but not when the thread hasn't had any activity in around a year. That means the person's question has either long since been answered, or they've moved on to another device, etc, etc. Thread closed.
been playing around with build.prop tweaks today. here's some that i have had good results with:
setting dalvik to 64
yes, that's high, but, switching screens on the homescreen has been a lot smother. you may have some issues with smaller apps, if so, try a lower setting. stock is 42, 48 may work good if you have a lot of smaller apps.
i also added these, so far so good, no problems. these are older tweaks, but they seem to be working here, but it's hard to tell
Code:
ro.HOME_APP_ADJ=1
locks home in memory
Code:
ro.media.enc.JPEG.quality=100
makes pics display at 100% quality
Code:
debug.sf.hw=1
enables hardware rendering of UI and home
take caution when editing build.prop. the file is located /system
do not delete or change anything else if you don't know what you're really doing.
debug.sf.nobootanimation=1
Disables the boot animations
svtfmook said:
ro.HOME_APP_ADJ=1
locks home in memory
Click to expand...
Click to collapse
Do you know if that works with 3rd party launchers (i.e. is HOME_APP whatever is linked to the home button, not hard coded to the moto home app)?
Wow, nice work guys. Quick question, does disabling the boot animation = faster boot time.
Sent from my MB865 using XDA App
916x10 said:
Wow, nice work guys. Quick question, does disabling the boot animation = faster boot time.
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
Not sure. You will still have the android boot animation. You just won't have the AT&T boot animation
Sent from my MB865 using XDA App
I tried using the these settings and it bricked my phone. Just FYI for anyone thinking of trying them out.
I think it has to do with the hardware rendering setting, because when I boot the video is very distorted and slow. It then goes black and vibrates every few seconds and I can't get it back. Restore to factory default was no help at all.
Any thoughts on how I might get this thing running again?
here's the stock build.prop
if the device will power on, extract it from this zip and try to adb push it to /system
not sure how these settings would brick your phone though. are you sure you added them to build.prop and not default.prop? did you change anything else in build.prop?
Yeah, I only added the options listed in the forum post, and didn't change anything else.
The first thing I tried was shelling into the phone using adb, but it didn't work at all in the state the phone was in. After restoring to factory defaults I was able to boot and get the initial setup screen for the phone where it asks you to add your email accounts, etc., but when clicking "done" the app would crash and restart effectively locking me out of the phone.
I'm assuming the crash is because I de-bloated the phone previously, and maybe it's missing a system library? Who knows.
In any case it looks like I may be taking a trip to the AT&T store
mspaulding06 said:
Yeah, I only added the options listed in the forum post, and didn't change anything else.
The first thing I tried was shelling into the phone using adb, but it didn't work at all in the state the phone was in. After restoring to factory defaults I was able to boot and get the initial setup screen for the phone where it asks you to add your email accounts, etc., but when clicking "done" the app would crash and restart effectively locking me out of the phone.
I'm assuming the crash is because I de-bloated the phone previously, and maybe it's missing a system library? Who knows.
In any case it looks like I may be taking a trip to the AT&T store
Click to expand...
Click to collapse
Thats odd. A factory restore would have overwritten any changed files and added any missing apks from /system
Sent from my MB865 using XDA App
svtfmook said:
Thats odd. A factory restore would have overwritten any changed files and added any missing apks from /system
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
Did you use a text editor on the phone or on a computer? If you use one that word wraps it will fubar the whole thing.
Here's a list of build.prop tweaks I found searching around, I haven't tried any myself yet, but hey, the more the merrier, right?
dasfiend said:
Did you use a text editor on the phone or on a computer? If you use one that word wraps it will fubar the whole thing.
Click to expand...
Click to collapse
i used an on the phone editor. windows editors will wreck it, linux editors are fine with build.prop though. not sure what the member who bricked his phone used.
I just tested the boot animation setting with a stopwatch and it's pretty much the same time one way or the other.
moofree said:
I just tested the boot animation setting with a stopwatch and it's pretty much the same time one way or the other.
Click to expand...
Click to collapse
Ya, but at least we don't have to look at the annoying super bright white at&t animation anymore.
moofree said:
I just tested the boot animation setting with a stopwatch and it's pretty much the same time one way or the other.
Click to expand...
Click to collapse
Thank you for checking and confirming that. I'll hit the button when I get to my pc.
Sent from my MB865 using XDA App
I did in fact use my phone to edit the build.props file (instead of using adb shell). I used the text editor feature of root explorer. I didn't notice the text wrap on the screen or anything like that when I was typing. I suppose that could've been the culprit.
mspaulding06 said:
I did in fact use my phone to edit the build.props file (instead of using adb shell). I used the text editor feature of root explorer. I didn't notice the text wrap on the screen or anything like that when I was typing. I suppose that could've been the culprit.
Click to expand...
Click to collapse
root explorer is fine, that wasn't your problem. i use root explorer as well. i think that either something else was changed, or something else is the problem.
svtfmook said:
Code:
ro.media.enc.JPEG.quality=100
makes pics display at 100% quality
Click to expand...
Click to collapse
With this setting does it change the display of your contact photos? Which show pretty crappy on the call screen.
jshinn1 said:
With this setting does it change the display of your contact photos? Which show pretty crappy on the call screen.
Click to expand...
Click to collapse
That's one thing I hope can be modded once the bootloader gets unlocked. My X10 showed the contact pics the top 1/3rd of the screen and the quality was very good, would be nice to see something similar on this phone.
moofree said:
I just tested the boot animation setting with a stopwatch and it's pretty much the same time one way or the other.
Click to expand...
Click to collapse
Same here, it just doesn't show the animation, but takes the same amount of boot time.
916x10 said:
That's one thing I hope can be modded once the bootloader gets unlocked. My X10 showed the contact pics the top 1/3rd of the screen and the quality was very good, would be nice to see something similar on this phone.
Click to expand...
Click to collapse
Exactly its annoying to have these great pics and when that person calls me it looks like crap not necessarily a huge deal but something I would like to see
This is starting to really frustrate me now!
When applying a background to my phone, weather it be from the Gallery or integrated wallpapers, sometimes it will jump around on the homescreen. For example I will be in an app, press the home button and on going to the home screen the wallpaper will momentarily zoom in then zoom back out to normal. As this is happening the phone has excessive lag.
I've tried to isolate the issue, thought it might be a bad factory reset but my sister is over this weekend and hers is the same! it doesn't happen when running any applications in particular, it's literally random but when it starts doing it it will keep doing it. Restarting the phone doesn't fix.
jaaystott said:
This is starting to really frustrate me now!
When applying a background to my phone, weather it be from the Gallery or integrated wallpapers, sometimes it will jump around on the homescreen. For example I will be in an app, press the home button and on going to the home screen the wallpaper will momentarily zoom in then zoom back out to normal. As this is happening the phone has excessive lag.
I've tried to isolate the issue, thought it might be a bad factory reset but my sister is over this weekend and hers is the same! it doesn't happen when running any applications in particular, it's literally random but when it starts doing it it will keep doing it. Restarting the phone doesn't fix.
Click to expand...
Click to collapse
What ROM and wallpaper?
Sent from my EVO using Tapatalk
numel007 said:
What ROM and wallpaper?
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
My bad, should have mentioned. Both of us are 100% stock, just checked my mums is doing it too. Any wallpaper, it doesn't matter.
jaaystott said:
My bad, should have mentioned. Both of us are 100% stock, just checked my mums is doing it too. Any wallpaper, it doesn't matter.
Click to expand...
Click to collapse
Weird. I'm on stock and everything is fine... Try downloading a different launcher for now and see if it still happens. Doesn't have to be permanent, this is just for testing purposes.
numel007 said:
Weird. I'm on stock and everything is fine... Try downloading a different launcher for now and see if it still happens. Doesn't have to be permanent, this is just for testing purposes.
Click to expand...
Click to collapse
Already tried that too and it doesn't do it. I will try and get a video of it, just depends if they will let me borrow one of their phones.
jaaystott said:
Already tried that too and it doesn't do it. I will try and get a video of it, just depends if they will let me borrow one of their phones.
Click to expand...
Click to collapse
Get a logcat too if you can. I probably won't be able to read it, but hopefully somebody with more experience will wander by.
Sent from my EVO using Tapatalk
numel007 said:
Get a logcat too if you can. I probably won't be able to read it, but hopefully somebody with more experience will wander by.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
I should know this but been out of the game for a long time, how do I go about getting a logcat? Managed to get a video of it, just transferring it to my phone now.
I heard someone else mentioning they were having these issues, they put it down to an update with google Search, however google Search has since been updated and the issues are persisting.
jaaystott said:
I should know this but been out of the game for a long time, how do I go about getting a logcat? Managed to get a video of it, just transferring it to my phone now.
I heard someone else mentioning they were having these issues, they put it down to an update with google Search, however google Search has since been updated and the issues are persisting.
Click to expand...
Click to collapse
It's all good. First you'll need adb to be installed. I usually run adb on ubuntu, so I'm not experienced with windows commands.
On ubuntu. open terminal, connect phone, make sure usb debugging is enabled. You'll probably recieve a warning about an RSA fingerprint, which you will accept. Then in terminal, do
sudo su
adb start-server
now cd into whatever directory you want to store your logcat in
Once in the directory, run "adb logcat -v long > wallpaper.txt"
Reporduce the problem
Kill the logcat
Open the text file that was created
Either upload the file or pastebin it and post the link
Done!
numel007 said:
It's all good. First you'll need adb to be installed. I usually run adb on ubuntu, so I'm not experienced with windows commands.
On ubuntu. open terminal, connect phone, make sure usb debugging is enabled. You'll probably receive a warning about an RSA fingerprint, which you will accept. Then in terminal, do
sudo su
adb start-server
now cd into whatever directory you want to store your logcat in
Once in the directory, run "adb logcat -v long > wallpaper.txt"
Reporduce the problem
Kill the logcat
Open the text file that was created
Either upload the file or pastebin it and post the link
Done!
Click to expand...
Click to collapse
Doesn't that require root? Not 100% how to do that though, I used to be pretty good with ADB but unfortunately that was back in the Desire days and I've not really been into rooting since I got my HOX last year I change devices too much. Anyway, here is the video documenting the issue.
http://youtu.be/pBeNpwP5TFQ
jaaystott said:
Doesn't that require root? Not 100% how to do that though, I used to be pretty good with ADB but unfortunately that was back in the Desire days and I've not really been into rooting since I got my HOX last year I change devices too much. Anyway, here is the video documenting the issue.
http://youtu.be/pBeNpwP5TFQ
Click to expand...
Click to collapse
And you said your entire family is experiencing this? Ok go to about phone and tap Build Number a bunch of times. Should activate dev settings. Just see if you can get adb to work at all. I'm not certain whether it requires root or not. It confuses me that your family all has this problem, but it hasn't been reported by the rest of the Nexus 5 users around the world...
numel007 said:
And you said your entire family is experiencing this? Ok go to about phone and tap Build Number a bunch of times. Should activate dev settings. Just see if you can get adb to work at all. I'm not certain whether it requires root or not. It confuses me that your family all has this problem, but it hasn't been reported by the rest of the Nexus 5 users around the world...
Click to expand...
Click to collapse
Well I have to go out right now but I will try when I get back in. I'll do a Google Search and see if i can find how to.
You could try wiping data for your Home launcher. Just go to Settings/ Apps then swipe to " All" tab and open Google Search. Wipe its data and it will reset your launcher to default. See if it still persists.
I'd say it's because the launcher wasn't designed to have many additional screens as shown.
Looks like it's redrawing the launcher after leaving and returning to it.
Try getting rid of the extra home screens and retest.
WR
Sent from my Nexus 5
you are not the only one who has this issue..Even my nexus 5 does this..
ROM-Dirty Unicorns
Kernel-Franko r35
lordvoldemort said:
you are not the only one who has this issue..Even my nexus 5 does this..
ROM-Dirty Unicorns
Kernel-Franko r35
Click to expand...
Click to collapse
Happens on stock or on DU too?
WarRaven said:
I'd say it's because the launcher wasn't designed to have many additional screens as shown.
Looks like it's redrawing the launcher after leaving and returning to it.
Try getting rid of the extra home screens and retest.
WR
Sent from my Nexus 5
Click to expand...
Click to collapse
Not true. I've read reviews where people have tried upto 20-30pages with no issue.
bushako said:
Not true. I've read reviews where people have tried upto 20-30pages with no issue.
Click to expand...
Click to collapse
Ok.. was an idea is all.
WR
Sent from my Nexus 5
WarRaven said:
Ok.. was an idea is all.
WR
Sent from my Nexus 5
Click to expand...
Click to collapse
that's alright, I was just stating what I had read else where.?
My phone phone was doing this, but I figured out that it was an issue with how you zoom or place the wallpaper when applying it. When I applied with zedge, it was causing problems. Are you using a 3rd party app to find and apply wallpapers? Try switching by long-pressing a blank area on your home screen, and hitting wallpaper.
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 02:07 PM ---------- Previous post was at 02:02 PM ----------
I actually just managed to replicate it. To fix it, try this... First select one of the stock wallpapers that came with the phone, using the stock method I mentioned above. Then test, your problem should be 100 percent gone. Then go to change your wallpaper back to the one you want, but do NOT select it from where it is on the bottom bar. Hit 'pick image' and then choose the wallpaper you want. Before you hit the check mark in the upper left hand corner, make sure the wallpaper is centered and fully zoomed out. That should fix it.
Sent from my Nexus 5 using xda app-developers app
What the title says- just have to buy $2.00 Andromeda add-on and download and run the desktop client.
Installed Swift Dark and it works great. Said there was 1 error during applying, but I can't tell; everything looks good to me. Great to have substratum working.
With substratum and LMT working, along with button mapper for vol button next/prev track long press ... I'm actually doing okay without root or custom roms.
Oh yeah Def glad to have the Andromeda add on for Substratum, all my themes work great and its so easy to use.
Chronzy said:
What the title says- just have to buy $2.00 Andromeda add-on and download and run the desktop client.
Installed Swift Dark and it works great. Said there was 1 error during applying, but I can't tell; everything looks good to me. Great to have substratum working.
With substratum and LMT working, along with button mapper for vol button next/prev track long press ... I'm actually doing okay without root or custom roms.
Click to expand...
Click to collapse
I downloaded the substratum and paid for a theme but when i hook up my pixel 2 to my computer and run the desktop app it never gets rid of the red window on my phone with the X. What am i doing wrong?
kevincuomo said:
I downloaded the substratum and paid for a theme but when i hook up my pixel 2 to my computer and run the desktop app it never gets rid of the red window on my phone with the X. What am i doing wrong?
Click to expand...
Click to collapse
Are you switching to USB file transfer instead of charging in the notification when you plug it in? Do you have developer settings enabled and USB debugging checked?
Sent from my Pixel 2 using XDA Labs
Chronzy said:
Are you switching to USB file transfer instead of charging in the notification when you plug it in? Do you have developer settings enabled and USB debugging checked?
Sent from my Pixel 2 using XDA Labs
Click to expand...
Click to collapse
Yes, I changed to file transfer when i connected it and i also turned on developer mode and USB debugging as the tutorial said. I read a few forum posts on here about it boot looping the Pixel 2 XL but i wanted to try it anyways and still couldn't get it to work. Do i have to restart it at some point? I also tried to use the Java steps but i couldn't get that to work either.
kevincuomo said:
Yes, I changed to file transfer when i connected it and i also turned on developer mode and USB debugging as the tutorial said. I read a few forum posts on here about it boot looping the Pixel 2 XL but i wanted to try it anyways and still couldn't get it to work. Do i have to restart it at some point? I also tried to use the Java steps but i couldn't get that to work either.
Click to expand...
Click to collapse
Once you have both substratum and andromeda installed on your phone, have the desktop client downloaded, and run the "start_andromeda" batch file while the phone's plugged in, it should automatically start substratum on your phone, and then apply like normal.
Those are the steps; if that's not working for you then I'd recommend reading through the original thread: https://forum.xda-developers.com/ap...top-clients-release-notes-t3668682?styleid=18
kevincuomo said:
I downloaded the substratum and paid for a theme but when i hook up my pixel 2 to my computer and run the desktop app it never gets rid of the red window on my phone with the X. What am i doing wrong?
Click to expand...
Click to collapse
At least for OS X, you need to connect phone to computer, open substratum app on phone, mount dmg on desktop, open andromeda on desktop, and select the mounted dmg.
Too bad I don't have a working computer xD
Is it normal that it slows down the app launching and themed apps in general?