linuxlike boot-log - G1 Android Development

hi,
i was thinking if there is some way to turn off all boot logo's and make visible kernel log and system log during booting like on regular linux system is...
what do you think?
zet

adb logcat > logcat.txt

I thing the question was to see bootlog instead splash boot screen.

yes, i know that. but i was writing "during booting"... not to show animation but logs when system is starting...
(heh, posting at the same time, thanks QDT anyway

Like when starting jf's recovery image?

I think that is what he is looking for... I would not mind seeing this either

This is actually hard to do. JF's recovery would just run "dmesg" before starting recovery. If you want a real console, you have to use a serial cable or something like mtdoops AFAIK.

I would prefer that as well. I like the linux look of boot.

I second.
Since day one, the splash screen during boot has annoyed the hell out of me. I have to turn it on and walk away for a few minutes just to keep my blood pressure level at normal. Any device that takes more than 5-10 seconds to boot just has to have a verbose option in my book.

You can count me among the people who'd love to see this.
I wonder if we can figure out a way to make this happen?
It doesn't look hopeful if cyanogen says it's difficult, lol.

as far as it may seems a useless feature, I will welcome it very much too.
I like to see what's going on, at boot time.
It's something I hate on Win and Mac.
So here it is another vote for it!

i would love this. plz cyanogen make it happen in your next ROM!

cuss said:
as far as it may seems a useless feature, I will welcome it very much too.
I like to see what's going on, at boot time.
It's something I hate on Win and Mac.
So here it is another vote for it!
Click to expand...
Click to collapse
OS X supports verbose mode startup
http://support.apple.com/kb/HT1492

circa85 said:
OS X supports verbose mode startup
http://support.apple.com/kb/HT1492
Click to expand...
Click to collapse
I just found out... so does windows... http://www.pchijack.com/os/windows-xp/enable-verbose-show-detailed-information-while-windows-start/

I would like it as well. For me doing an "adb -d logcat" or "adb -d logcat |tee log.txt" in a shell on bootup is fine though. Usually I only care right after flashing or if my phone is having problems. When the phone is having problems pushing it to a file on my computer is better than seeing it on the screen anyway.

Its useful only on first boot after reflashing, but it looks sooo sexy

Got another vote from me, I would love to see the linux like boot up also

iVote
i vote for it. just curious what's going on when it takes that long to boot...

http://forum.xda-developers.com/showthread.php?t=443431
check this out

blingblingslyna said:
http://forum.xda-developers.com/showthread.php?t=443431
check this out
Click to expand...
Click to collapse
The thread that you posted as a response to the questions posted in this thread have nothing to do with what the people in this thread are looking for so I am not sure what you read in here or thought you read.

Related

Root Access on the TMobile G1 and why it works

I wrote up instructions on my blog, and someone responded explaining why it works.
To translate: anything the user types on the keyboard is actually being fed into a console shell and potentially executed. So the easiest way to get root on your phone is to simply reboot it, and when it finishes rebooting, type "telnetd" and press enter. Your phone will start doing a contact lookup in your UI, but at the same time it is typing into a root shell.
This is basically a huge oops on Google's part! Looks like some debug related settings that they never took out.
So really, pTerminal was not necessary in this hack, but it it accidentally exposed it!
Edit: should have read the other post about this! Kudos to Jim!
http://forum.xda-developers.com/showthread.php?t=442857
Like the...
Yup, telnetd in essence was the carrot on the stick that led me on.... Further cementing the fact that someone was bound to find this one way or another... Much sooner rather than later.
Obviously this will need to be fixed, I only hope the platform can some how remain open (and be taken even further) even after said fix.
Wow, I will not be taking any updates until I have everything worked out just the way I want it....
forced updating rc30
you may not have a choice short of turning your g1 of and leaving it that way, it has been rumored that this update has a date at which it turn mandatory.
bhang

androids port capacitive touch

ever since the android port came out and i tried it ive loved how the hardkeys light up when you touch them and then immediatly go away. is there anyway to get that on wm?
yeah same here. thats so f#$*n awesome
love to have it on wm
soulds like it would require a touch detector hardware system along with the full preasure detector there already is
Rudegar said:
soulds like it would require a touch detector hardware system along with the full preasure detector there already is
Click to expand...
Click to collapse
it already works with our device. Its just part of the android port that can be found here http://www.htc-android.com/viewtopic.php?f=5&t=237
im suprised no ones tried to do this yet?
i have to say i honestly loved that too. though i would miss the touch to light up all keys so i could see them in the dark. then again, thinking as im typing, i would trade for the android style. i dont think i can make up my mind!
Mine does that already.
are you running android or something? if you got it to work with windows share with the class.
Mr.Sir said:
Mine does that already.
Click to expand...
Click to collapse
How did you get this working?
Please share what you know
android still doesnt let us make calls texts or data on our raphael right?
yep, no sound, data, text, phone, proper keyboard support, wifi, bluetooth. but atleast the capacitive navipad works.
haha that navipad is most important
i tried using android last night followed the instructions . how long did bootup take for you guys? it sat on the text page with the blue box for like 40 minutes and never went farther
Wow, didn't know we could boot Android on our phones.
I didn't try that yet, because from tomorrow I will be traveling for a week, and I will need my phone.
I downloaded it though, and on the installation instructions it says to launch haret.exe, I didn't get that, is this some kind of virtual machine, or will it shut down WM and launch Android?
Smaniac said:
Wow, didn't know we could boot Android on our phones.
I didn't try that yet, because from tomorrow I will be traveling for a week, and I will need my phone.
I downloaded it though, and on the installation instructions it says to launch haret.exe, I didn't get that, is this some kind of virtual machine, or will it shut down WM and launch Android?
Click to expand...
Click to collapse
It shuts down WM and launches Android. It isn't a permenant flash because not everything works on it. Android itself loads fine, but there are still some key linux drivers that are required for normal day to day use. The more important thing is the microphone/speaker. The phone works and things like SMS.
player you have obviously had it working
how long does it take to boot for you?
i have the tmp folder on my card with the boot folder in that. in there i click haret18.exe then the box comes up saying it will run default.txt then linux starts and i just get all the small writing on screen but it never goes farther
EDIT- i was told it must be the wrong version. i have the fuze so which raph is that? i tried two diff versions already
you need to either rename the text files in the boot folder or choose the one you want.
If you have the fuze use the raph100 I think it is...don't have my phone on me, but it isn't the 800 one.
I just renamed the default.txt to something else and then the default _raph100 or whatever to default.txt and it worked fine.
Before I realized this I had the same issue you did.
thanks i got it running
so is there really anything we can do at this point? or just play around with the home screen
soooo anyway back to the question i asked... lol
has anyone or is there a way to make it work to when you touch the pad only the area you touch only lights up like it does in the android port?
Wow after loading up the latest port of android, I finally understand what the OP means, this is really cool! I would love to have this. Not only does it look cool, but it will actually reduce error due to pressing the wrong part of the button.
lbhocky19 said:
thanks i got it running
so is there really anything we can do at this point? or just play around with the home screen
Click to expand...
Click to collapse
No, as of right now nothing is really working besides Andriod running. No data or voice services work yet...
you can mess with home AND navipad. cant forget what this thread is all about. i think the fact that you can run android and do it without wiping wm is pretty amazing. theres alot of work that needs to be done if you are planning on doing something useful with android. the phone was meant for wm and is set more up with drivers, configuration, and development for such. hopefully in the future it will do both well and your epeen length will grow as you show off to everyone what your phone can do.

Htc Touch Pro (Raphael 500) Running Android , How to overclock?

Alright so Yesterday I installed the android os on my touch pro (raph 500)
i orginally have windows mobile 6.5 which is preety fast
but android is really slow!
i turned off all the settings which i would think it used alot of memory but still no help, so i started seeing videos on overclcking?
can someone explain to me on how to do this,
with links to the download
i really need to speed this up ,it would be amazing if it worked.
also if you give me a response that helps me , ill donate 10.00+ to you .
I do not require funds as I enjoy helping out!
From THIS thread and THIS post:
Overclocking
acpuclock.oc_freq_khz=XXXXXX ( suggested 600000-640000 )
but it is very unstable if you try to get higher than 650000-700000
Click to expand...
Click to collapse
Basically, you add that to the startup.txt file somewhere between the parentheses with an added space between the next command. Keeping in mind, with added OC, you may and may not notice a difference in stability. I honestly never use OC and I am using FroYo from THIS thread. Additionally you can try out Gingerbread Alpha from THIS thread. Please leave feedback in their respective threads, thanks!
n-Joie! (Enjoy)
thanks but this is my startup text :
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 acpuclock.force_turbo=1"
boot
Click to expand...
Click to collapse
so which am i supposed to edit, sorry im a noob lol
& u said that was the one you used,
is it fast?
Actually, I can't use that one because I have an at&t Fuze. If you have a RAPH500, you might want to use the following:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 pm.sleep_mode=1 acpuclock.oc_freq_khz=XXXXXX"
boot
Click to expand...
Click to collapse
Where XXXXXX is equal to a value between 600000-640000
Additional note: make sure you type something like 600000 or any value up to 640000
lol thanks im trying to see if theres a difference in speed.
but you used froyo?
is that running fast?
It's running fine with sync and a few other apps running in the background. I would be mindful of livewallpaper and HQ video at the moment as this project is currently still under development, at best. At least that is what I have noticed as far as performance is considered. I have also run a stripped Gingerbread alpha build (the one I linked you to earlier) and it is running faster/smoother than FroYo. To be expected without all the bells and whistles...
NOTE: Speed is relative to performance at the moment. Hence why I say it's still under development...
intresting ill test that out in about 15 mins
but does yours take a long time to come out of sleep mode?
Hmmm, that might be the notorious sleep of death SOD. I usually do something that most don't like but I sort of turn off the screen time out by first making the screen time out greater than 10 or 30 minutes. After that it should make things easier as far as disabling the auto back light/screen timeout feature. Keep in mind this is only a work around, I believe there is mention of actually fixing this issue. You'll need to download a free app called batterybooster (use the link if you want to read up on it a little). Once installed, run it and look for the far right icon and tap it. Set the timeout to Never and you'll notice a decent performance enhancement in the screen off and screen on.
NOTE: You will need to manually turn it off from here-on. You can try to play around with the setting but I find it somewhat problematic. Meaning that if you enable the timeout, it might and it might not work.
alright well i tried the gingerbread and that didnt work it lagged .
i tried froyo , it was amazing then i found out wifi didnt work
so now im back to the regular android one i had before ill be trying to see if theres a difference now that i "overclocked" it .
but thanks for all the help.
ill post back if i need something!
Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.
R^7Z said:
Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.
Click to expand...
Click to collapse
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .
ndnmaster096 said:
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .
Click to expand...
Click to collapse
NVM I got the wifi to work now .
Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock
R^7Z said:
Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock
Click to expand...
Click to collapse
well i set it to never timeout and i have a lock pattern
but since it never times out it wont lock .
also now im starting to notice froyo is rebooting for some weird reason automatically .
Calm down, that is kind of "usual behavior" . There are quire a few things going on and the OS is attempting to "handle it". Sometimes it can't and just quits instead of freezing up ( which would be the lesser of two evils ). To get it to lock, you will have to turn it off manually (power button). Unfortunately, I think if the keyboad slides out, it self unlocks (kind of a self defeating purpose, more or less). If you turn the screen off and wait like 10 seconds then turn the screen on (power key), you should see the lock. I can't say for sure but it does work for me. I don't really have much time for troubleshooting today, as I am at work currently but do look over the threads I linked you to earlier if at all possible.
okay so i turned it off using the power button and it booted to windows mobile (odd)
then i tried running haret.exe & got this message:
"The file HARET cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. IF the problem persists, try reinstalling or restoring the file."
im not sure what to do.
i tryed reformatting the card and installing fresh files, which didnt work so now im left questioned?
When you say you turned it off, did you hold the button or just press it once? If you pressed it once, then, that is definitly not "usual" behavior. I recall having that issue once upon a time but for the life of me, I don't recall what I did to recover from it. However, it sounds like you are attempting to run from a shortcut that references the program(haret) that is no longer there. To resolve this, I need you to confirm that you are running from the microSD and not a shortcut. Also, you aren't formatting under windows, right? If you are formatting from windows, that would be a "no-no"
Find something like the HP tool (can be googled) that everyone else talks of or even something like the free version of partition wizard should work.
i held the button and it gave me options
1) airplane mode
2)shutoff
3)vibrate
i did try to make a shortcut but i deleted it and now when i checked i was running it from the actual application.
lastly, i did format from windows but i downloaded hp format tool
and formated my device in quick format.
reinstalled the programs and it still gave me the same error message,
please help, i really miss android =(
Try deleting data.img and letting it recreate the file. To clarify about the screen off issue, when you press the power button once (not hold), what does it do? Also, which kernel package are you using and have you attempted to download a newer kernel package yet?
Also, try THIS kernel package; I got it from THIS site. It looks like that kernel package is specific to our devices.

[Q] keyboard to stay lit longer

Howdy,
I have looked at the threads suggested to check out before starting a new one, and they did not help me much. I am a noob, and that may be why.
I have a sidekick 4g and would like the keyboard to stay lit a lot longer than it does. I slide it out and if I pause for the briefest of time, and the light goes out. Id there a way to make it stay lit until I close the keyboard?
Do I have to root the phone in order to make this happen? I have been reading all the root stuff I can find but not quite ready to take the plunge yet. I most likely can do it b sometimes I lack confidence when starting new things.
Thanks for the help ahead of time.
XcntrK
xcntrk said:
Howdy,
I have looked at the threads suggested to check out before starting a new one, and they did not help me much. I am a noob, and that may be why.
I have a sidekick 4g and would like the keyboard to stay lit a lot longer than it does. I slide it out and if I pause for the briefest of time, and the light goes out. Id there a way to make it stay lit until I close the keyboard?
Do I have to root the phone in order to make this happen? I have been reading all the root stuff I can find but not quite ready to take the plunge yet. I most likely can do it b sometimes I lack confidence when starting new things.
Thanks for the help ahead of time.
XcntrK
Click to expand...
Click to collapse
rooting is real simple
first download one click hedmial root (in either a stick in development or my ref)
go to settings on phone then applications then development turn debugging on
open one click
now hit root
finished
and yes to do anything good you need to root
Changing your screen timeout seems to affect how long the keyboard stays lit also. For example, I changed my screen timeout to 1 minute, and the keyboard stayed lit the whole time. Just go into Android Settings, find "Display" --> "Screen timeout" and set it to your choosing. Also, just tapping the Shift or Alt button turns the keyboard backlight on again.
I concur with immorality, rooting is no big deal. It's when you start messing with the system and flashing ROMs that things can go wonky if you don't know what you're doing and aren't careful, but most failures are recoverable using the aforementioned Heimdall.
Thanks for the info. I am going to go ahead and do the root. I would love to get rid of all this tmobile junk on the phone. And there are some other cool things that I have been reading about that you can do after you have rooted your phone. I will keep the forum up and running though just in case LOL
Thanks again y'all
tell you what, ill look into the keyboard light in the next day or so and when i find how to control them ill create you a flashable zip so you can easily change the time they stay on. or maybe even add it to my aroma package
but for now root your phone as you wont be able to do anything without it, follow the above method if youd like, i personally dont like one click root methods for various reasons so heres a quick guide i made
http://forum.xda-developers.com/showpost.php?p=40198560&postcount=27
again follow any method you would like, and i suggest to at least read up on the various ways. hopefully by the time your done and ready to flash your first rom ill have had time to look into the keyboard lights issue
good luck and happy flashing!
@demkantor thank you so very much. I am downloading the aroma, and have copied the notes on your link.
My Kaspersky is not letting me downliad the rage against the machine. I will see if I can get around it and let you know the outcome
I really do appreciate your help with the lights on the keyboard. I have tried resetting the screen timeout and every other thing suggested or that I can think of and it still goes out a second or so after the last letter entered.
hey no problem! try another browser maybe or turn virus protection off, any script that works to exploit a loophole will through the virus protection. hell some wont let you download superuser
but i assure you its legit
as for the keyboard lights, my sk4g is incapacitated right now so i ran a few tests in another android:
When i run this in a shell:
busybox find / -name 'timeout' 2> /dev/null | busybox grep -i timeout
I get this:
2> /dev/null | busybox grep -i timeout <
/system/xbin/timeout
/sys/class/firmware/timeout
/sys/module/uvcvideo/parameters/timeout
/sys/module/nf_conntrack_netbios_ns/parameters/timeout
and if i run:
busybox find / -name 'brightness' 2> /dev/null | busybox grep -i backlight
gives me:
ss' 2> /dev/null | busybox grep -i backlight <
/sys/devices/platform/pwm-backlight/backlight/pwm-backlight/brightness
so i know where to start digging in my other androids, and hopefully if i find a fix in one it will be similar in the sidekick. ill keep you posted!
Got it, had to shut of part of Kaspersky and then make a exclusion for it when I unzipped LOL BUT I GOT IT YEAH!!! LOL
Thanks for all the effort with this.

[Q]Crazy Wallpaper Issues[Q]

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

Categories

Resources