Related
Good evening everyone.
To start with, yes I've read all the similar topics and none of them helped me
To my problem now. My phone has been flashed with a custom ROM for 1-2 months now (I don't remember exactly) and this morning I woke up to find my phone turned off. While trying to turn it on, no matter how much time has passed, it's stuck on the splash screen refusing to load the home screen
Is there any suggestion that does not involve me losing all my data because I have no backup of them?
Waiting for any suggestions.
See if you can connect with usb, and adb can communicate with device.
If yes, you can save the /data/data folder(in which are all configurations) + /data/app folder(in which are all apps except these on sdcard if any).
You can also run adb logcat from command prompt and see if you can find what app causes the error and the bootloop, and if maybe you can uninstall/reinstall this app, or delete the folder of that app on /data/data folder, to hopefully solve the error.
Try to install a program like QtADB, droid explorer or Android manager to avoid use command line and simplify some of above operations as copy/delete folders or install/uninstall apps.
If you need more help, PM me to speak in greek(it' s better)
I've just installed QtADB and connected the phone while being inside ClockwordMod v4.0.0.5.
The truth is that from here I don't get almost any useful information (don't know why). One positive aspect is that I can copy data from/to the phone.
While stuck in the splash screen I can't connect through adb though.
You mean not at all? Usually when appears IDEOS screen you can connect via adb, after some time and when the error start maybe the device freezes and then adb probably disconects, but until then you can take some useful logcat info for the error.
You can also have some more functions with QtADB on recovery mode if you mount the partitions first.
Maybe and the app manager work then(I haven't tested though).
Managed to get logcat information while turning on the phone. I'm attaching the log file with the error lines.
Trying to read them right now to find a solution. Any help appreciated.
gkaran said:
Managed to get logcat information while turning on the phone. I'm attaching the log file with the error lines.
Trying to read them right now to find a solution. Any help appreciated.
Click to expand...
Click to collapse
By reading your log i think the problem is permissions. Try to fix permissions with recovery tool.
Hi everyone,
If you have any questions relating to Arch on the TF300, please post them here and not in the dev thread
I'll do my best (as well as others, I'm sure) to answer them, but bear in mind that you should have some basic Linux knowledge before flashing!
this is awesome!
cb22 said:
Hi everyone,
If you have any questions relating to Arch on the TF300, please post them here and not in the dev thread
I'll do my best (as well as others, I'm sure) to answer them, but bear in mind that you should have some basic Linux knowledge before flashing!
Click to expand...
Click to collapse
I can't thank you enough for this, it's been fantastic so far! I only have a few questions, as I am extremely new to arch linux...as in this is the first time I've used anything aside from debian in the linux world.
To start, how would we go about changing DE's? I've downloaded a couple, but i get errors every time i try to start one saying that another window manager is already running. With ubuntu one just logged out and chose from the log in screen, but there doesn't appear to be a log out process for this, i get a black screen every time i do. Other than that, are there any general programs/settings/tweaks that you would suggest applying? While this is very nice, it still seems to be missing some basic functions, such as putting the screen to sleep and having a set system time.
Despite all of that, this has breathed new life into my tablet, you're doing fantastic work and I hope you only continue to make it more amazing!
fankuan19 said:
To start, how would we go about changing DE's? I've downloaded a couple, but i get errors every time i try to start one saying that another window manager is already running. With ubuntu one just logged out and chose from the log in screen, but there doesn't appear to be a log out process for this, i get a black screen every time i do. Other than that, are there any general programs/settings/tweaks that you would suggest applying? While this is very nice, it still seems to be missing some basic functions, such as putting the screen to sleep and having a set system time.
Click to expand...
Click to collapse
Take a look at the .xinitrc file in the home directory. It's a hidden file so you may need to "show hidden" or give an editor the full path (/home/user/.xinitrc)
The file runs the following by default:
Code:
exec startxfce4 --with-ck-launch
You can change everything after `exec` to the script for a different DE, such as `startkde`. If you don't know the command, there should be a list of session templates in /usr/share/xsessions/. Inside each .desktop file there's an "Exec=" line, everything after that is the command to sub in.
My crappy bash skills threw together a quick command to get a list of installed xsessions:
Code:
grep "Exec=" /usr/share/xsessions/*.desktop | sed -E 's/^Exec=(.+)$/\1/'
The output on the default rootfs will just be "startxfce4". If you have KDE another line should output "startkde", and so on. Put the command in your .xinitrc (making sure to replace the current one) and then reboot as there's no proper way to log out.
whoops
timothyb89 said:
Take a look at the .xinitrc file in the home directory. It's a hidden file so you may need to "show hidden" or give an editor the full path (/home/user/.xinitrc)
The file runs the following by default:
Code:
exec startxfce4 --with-ck-launch
You can change everything after `exec` to the script for a different DE, such as `startkde`. If you don't know the command, there should be a list of session templates in /usr/share/xsessions/. Inside each .desktop file there's an "Exec=" line, everything after that is the command to sub in.
My crappy bash skills threw together a quick command to get a list of installed xsessions:
Code:
grep "Exec=" /usr/share/xsessions/*.desktop | sed -E 's/^Exec=(.+)$/\1/'
The output on the default rootfs will just be "startxfce4". If you have KDE another line should output "startkde", and so on. Put the command in your .xinitrc (making sure to replace the current one) and then reboot as there's no proper way to log out.
Click to expand...
Click to collapse
First of all, thanks for the help! Unfortunately, I appear to have done something incorrectly, as the Linux partition will no longer boot. That code didn't return anything but a ">", although as I type this i realize I may have needed to be root...haha, regardless, I tried to edit the .xinitrc file with "exec /bin/usr/startlxde", which is what was after "exec=" in the xsessions directory, nothing happened after waiting quite a while after boot.
I suppose I'll have to reflash the entire partition, considering i can't access the filesystems to change it back. Ah, the wonders of linux!
Sorry if I repeat my question,but how can i activate the keyboard without using a pc with linux ?
fankuan19 said:
First of all, thanks for the help! Unfortunately, I appear to have done something incorrectly, as the Linux partition will no longer boot. That code didn't return anything but a ">", although as I type this i realize I may have needed to be root...haha, regardless, I tried to edit the .xinitrc file with "exec /bin/usr/startlxde", which is what was after "exec=" in the xsessions directory, nothing happened after waiting quite a while after boot.
I suppose I'll have to reflash the entire partition, considering i can't access the filesystems to change it back. Ah, the wonders of linux!
Click to expand...
Click to collapse
You should be able to gain access easily via Recovery. Just adb shell in, mount /dev/mmcblk0p8 /mnt and look in /mnt/linux - that's your root file system...
Razorbacktrack5535 said:
Sorry if I repeat my question,but how can i activate the keyboard without using a pc with linux ?
Click to expand...
Click to collapse
Without using a PC... Hmm, that could be tricky. If you're in Android, and you add this line to the top of /data/linux/home/user/.xinitrc
Code:
maliit-server &
(before the exec line)
It should give you the virtual keyboard when you restart into Linux.
cb22 said:
You should be able to gain access easily via Recovery. Just adb shell in, mount /dev/mmcblk0p8 /mnt and look in /mnt/linux - that's your root file system...
Click to expand...
Click to collapse
I was actually able to just use the terminal emulator in android to navigate back to the .xinitrc file, turns out i wasn't supposed to leave the "--with-yadda-yadda" bit, so i got lxde working...and as it turns out, i don't like it nearly as much as the DE you included, so i'll be switching back to that!
First off: thank you SO much for your hard work at this! My tab has never browsed the web this well. It's better than the desktop I'm sitting next to. Arch is amazing!
Just a few questions. Do we have basic tab controls yet? I'm looking for, specifically:
Brightness Control
Enable/Disable Touchpad
Volume Control
Sleep/Suspend/Hibernate
Especially that last one! As far as I can tell, if I'm not going to use the tab for more than a couple minutes, it's apparently best to shut it down or reboot back into Android so it can "sleep". Or plug it in. I know we're rough around the edges yet, but is this stuff in, or no?
koiulpoi said:
First off: thank you SO much for your hard work at this! My tab has never browsed the web this well. It's better than the desktop I'm sitting next to. Arch is amazing!
Just a few questions. Do we have basic tab controls yet? I'm looking for, specifically:
Brightness Control
Enable/Disable Touchpad
Volume Control
Sleep/Suspend/Hibernate
Especially that last one! As far as I can tell, if I'm not going to use the tab for more than a couple minutes, it's apparently best to shut it down or reboot back into Android so it can "sleep". Or plug it in. I know we're rough around the edges yet, but is this stuff in, or no?
Click to expand...
Click to collapse
I don't think sleep/suspend/hibernate is implemented at all quite yet. The backlight seems to turn off completely when the screen times out though so you can fake having a low power mode, though obviously true sleep would be nice.
As for volume control, use pavucontrol. You may need to install it with `pacman -S pavucontrol`.
For brightness ... there's no good way to do this as far as I can tell. XFCE has a brightness control applet you can add to the bottom panel but it doesn't seem to work, and most of the usual packages (e.g. xbacklight, etc) don't detect the backlight device. Oddly enough I gave e17 a try and its builtin brightness applet worked fine, I wonder what they do differently ...
At any rate you can control it manually: the file /sys/class/backlight/pwm-backlight/brightness has a 0-255 value which controls the screen brightness. Note that you need to run the echo command as root
Code:
# echo "1" > /sys/class/backlight/pwm-backlight/brightness # minimum brightness
# echo "255" > /sys/class/backlight/pwm-backlight/brightness # maximum brightness
# echo "0" > /sys/class/backlight/pwm-backlight/brightness # completely turns off backlight. use with care
Setting it to zero makes it next to impossible to see the screen. I ended up having to ssh into the device (or reboot) to get it back.
I modified the file through a PC and It works ! Thanks, no problems with wifi
Sleep / Suspend isn't implemented yet.
But, I did a bit of testing, and the TF should last for about ~40 hours with the screen off, and the processor in the Low Power mode (which it does automatically. Obviously, it's still wasteful compared to proper suspend, but it's not too bad.
Really liking this so far, other than managing to break wifi once, which I fixed by doing a quick re(install I guess is the proper term). Any chance of a future release having SLiM or something setup out of the box(I'd do it but looking at some of the guides, we are missing some files(?) :s) either that or is there a way to autologin a new user other than the default one named user?
(edit for more info) I've tried following a guide I found on the arch wiki which had me modify [email protected], but it didn't boot so I had to edit it back to the default.
Thanks for all your work cb22, and thanks for taking my advice and switching file hosts
This may be a dumb question
But I can't for the life of me find out how to flash the hybridkernel.blob, I've already done every other thing, but i'm lost as to what to do there. Can I get a bit of guidance please?
:Nevermind: Silly me forgot to go to fastboot, I was trying to do it with adb, for any others though, reboot to fastboot on your tf300t and then run go to the location of fastboot on your pc and hold shift and right click and select open comand line here. Then move the hybridkernel.blob to the same location as the fastboot and run fastboot -i 0x0B05 flash staging blob
Shingaling said:
But I can't for the life of me find out how to flash the hybridkernel.blob, I've already done every other thing, but i'm lost as to what to do there. Can I get a bit of guidance please?
:Nevermind: Silly me forgot to go to fastboot, I was trying to do it with adb, for any others though, reboot to fastboot on your tf300t and then run go to the location of fastboot on your pc and hold shift and right click and select open comand line here. Then move the hybridkernel.blob to the same location as the fastboot and run fastboot -i 0x0B05 flash staging blob
Click to expand...
Click to collapse
Disregard, didn't see the edit until after you posted essentially the same thing I did.
So, does Adobe Flash support work at all in Chromium? I haven't gotten it to recognize the plugin at all. Any way to get this working, or is it just gonna keep bugging me to install it?
koiulpoi said:
So, does Adobe Flash support work at all in Chromium? I haven't gotten it to recognize the plugin at all. Any way to get this working, or is it just gonna keep bugging me to install it?
Click to expand...
Click to collapse
I don't think it works at all, I've tried every permutation sudo pacman -S flash-plugin that I could think of and I've gotten notwhere.
They is no flash for ARM for pure Linux.
Wysyłane z mojego ASUS Transformer Pad TF300T za pomocą Tapatalk 2
Itege said:
Any chance of a future release having SLiM or something setup out of the box(I'd do it but looking at some of the guides, we are missing some files(?) :s) either that or is there a way to autologin a new user other than the default one named user?
(edit for more info) I've tried following a guide I found on the arch wiki which had me modify [email protected], but it didn't boot so I had to edit it back to the default.
Click to expand...
Click to collapse
In theory you should be able to install a proper display manager without too many issues:
Code:
# pacman -S lightdm lightdm-gtk-greeter
# systemctl enable lightdm
...though when I tried this the DM would never actually be run. I was able to run it manually over SSH without issues (both lightdm and slim worked, more or less). I'm in the process of investigating why it isn't run at startup like it should be, whatever the issue is doesn't seem to be related to the display manager itself.
I have an issue with wifi.
1: The WLAN do not find any Network with Channel 12 or 13.. I think I must change the region in germany, but where?
2. The WLAN do not connect, they search for an network adress and after 30seconds they ask for wlan key again.. the key is correct and my router shows the connection.. but archlinux means the key is wrong.. testet with router und smartphone wlan hotspot..
3. 3G not connecting, i have create a profile for BASE Germany, but they do not connect.
UPDATE:
for 2: Sometimes they connect and I can surf. But the ping are more then 600ms.. After few seconds the connection lost, sometimes they connect again, sometimes say ask for wlan key again.
Maybe you can help me. Sorry for my bad english.
Yours Sincelery
Robert
Could any of you guys find out if you have a process running in "interruptible" state named "kinteractive_lo"?
You can check that using "top" in CLI or installing gnome-system-monitor. I guess the standard xfce task manager works as well.
It's driving me nuts and I believe is one of the reasons why I have to hard-reboot my tablet, since invoking reboot with --force works perfectly.
Thanks in advance!
Hey guys,
I hope you can gibe me a hint how to get my Nexus 4 alive again.
Short intro:
- Phone fell of the desk => display broken
- Sent it to a repair company and received it working again, except the proximity sensor
=> this seems to be a common issue after screen replacements as I found out
- Unfortunately I left my brain at home today and I tried to disable the proximity sensor manually (read in this thread: http://forum.xda-developers.com/showthread.php?t=1626611). Didn't see this was for a Desire S ...
- After adding the line "gsm.proximity.enable=false" to the /system/build.prop file the phone won't boot anymore .... the CM11 boot animation isn't appearing
So, the phone is rooted. I am running CM11 M8 and CWM 6.0.2 (no touch).
So the plan was to alter the file via adb again, but I'm not able to access the phone in any ways.
The Nexus 4 Toolkit however recognizes the phone (with serial Number) and if the phone is in fastboot or ADB Mode. But when ein try to pull files from the device the toolkit says, that I don't have a unsecure boot image ... the adb functions doesn't seem to work either ...
But maybe I'm just not clever enough ...
Have you guys an idea how to get my phone back to life again? I assume wipen the phone will not fix the problem, since there seems to be an important system file corrupted (despite loosing all my data :crying
Hoping for helping words. Thanks in advance.
Gerd
1828
Don't use Nexus Toolkit ... use the native Google Android SDK and everything works fine ....
AntiFanBoy said:
Hey guys,
I hope you can gibe me a hint how to get my Nexus 4 alive again.
Short intro:
- Phone fell of the desk => display broken
- Sent it to a repair company and received it working again, except the proximity sensor
=> this seems to be a common issue after screen replacements as I found out
- Unfortunately I left my brain at home today and I tried to disable the proximity sensor manually (read in this thread: http://forum.xda-developers.com/showthread.php?t=1626611). Didn't see this was for a Desire S ...
- After adding the line "gsm.proximity.enable=false" to the /system/build.prop file the phone won't boot anymore .... the CM11 boot animation isn't appearing
So, the phone is rooted. I am running CM11 M8 and CWM 6.0.2 (no touch).
So the plan was to alter the file via adb again, but I'm not able to access the phone in any ways.
The Nexus 4 Toolkit however recognizes the phone (with serial Number) and if the phone is in fastboot or ADB Mode. But when ein try to pull files from the device the toolkit says, that I don't have a unsecure boot image ... the adb functions doesn't seem to work either ...
But maybe I'm just not clever enough ...
Have you guys an idea how to get my phone back to life again? I assume wipen the phone will not fix the problem, since there seems to be an important system file corrupted (despite loosing all my data :crying
Hoping for helping words. Thanks in advance.
Gerd
Click to expand...
Click to collapse
I don't suppose you made a nandroid and can just restore that.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I don't suppose you made a nandroid and can just restore that.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
due to the lack of free space, I haven't. But as you can read above, the problem was solved.
AntiFanBoy said:
Hi,
due to the lack of free space, I haven't. But as you can read above, the problem was solved.
Click to expand...
Click to collapse
whenever that happens again, just re set the file permission, when you change a file, sometimes it can change it´s permission.
if didnt get to bootanimation after modifying build.prop, the permissions of it are wrong, just set them back to 644 or rw-r-r
Hi,
thanks for you comment. :good:
actually I changed the rights by myself to 666, so I can modify it, but didn't change the permissions back.
So you thinks the permission was the problem and not the content of the file?
I added this line:
gsm.proximity.enable=false
AntiFanBoy said:
Hi,
thanks for you comment. :good:
actually I changed the rights by myself to 666, so I can modify it, but didn't change the permissions back.
So you thinks the permission was the problem and not the content of the file?
I added this line:
gsm.proximity.enable=false
Click to expand...
Click to collapse
Yes, this is a common problem as far as I know
If you use TWRP as your recovery (not sure if it's possible with cwm, too) you can use the built-in file explorer to navigate to the build.prop and set the permissions. Just reboot and it should work fine again
If you can enter recovery do a factory reset
Mashed_Potatoes said:
If you can enter recovery do a factory reset
Click to expand...
Click to collapse
Well, I'd say this would be the last option as he'd lose all his data. Maybe there's another way to fix the problem
no need for factory reset, in case like this refleshing the rom will do the job. there is no need for wipe or anything just flesh the same rom again and everythink will be ok
Hey guys,
looks like I didn't express myself clearly enough
Don't use Nexus Toolkit ... use the native Google Android SDK and everything works fine ....
Click to expand...
Click to collapse
Besides the problemative build.prop file, the nexus 4 toolkit was the problem. After using the standard Android SDK I was able to push a CM Image onto the phone via adb and simply updated the os and everything was fine again. Don't know why the toolkit spun around, always worked fine, but this now thought me a lesson => back to the roots
Resetting the phone to factory defaults/wiping everything wouldn't have solved the problem I assume.
Thanks guys.
Please read:http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
Today I found something really strange about builds LMY47E and LMY47D. I had been running 47D since last week with a DPI of 520, which was adjusted using Root Explorer in the build.prop. After trying to do the same in 47E, rebooting my device would display the "Android is upgrading... Optimizing app 1 of XXX" screen, and make it bootloop after optimizing the last app, displaying the same screen and optimizing my apps again and again.
After many hours trying to isolate the culprit, I found that to properly change DPI In 47E, one has to edit the build.prop lcd density AND use "adb shell wm density XXX". That's the only way I've made sure my device reboots properly.
I think this is really weird, since 47D and 47E are supposed to be identical. Does anybody have any clue about this?
redsmith said:
Today I found something really strange about builds LMY47E and LMY47D. I had been running 47D since last week with a DPI of 520, which was adjusted using Root Explorer in the build.prop. After trying to do the same in 47E, rebooting my device would display the "Android is upgrading... Optimizing app 1 of XXX" screen, and make it bootloop after optimizing the last app, displaying the same screen and optimizing my apps again and again.
After many hours trying to isolate the culprit, I found that to properly change DPI In 47E, one has to edit the build.prop lcd density AND use "adb shell wm density XXX". That's the only way I've made sure my device reboots properly.
I think this is really weird, since 47D and 47E are supposed to be identical. Does anybody have any clue about this?
Click to expand...
Click to collapse
I just changed it with root explorer. I didn't have any issues.
Then again I stayed within the default density's from my past devices.
Nexus 6 is 560, I went to 480.
antiochasylum said:
I just changed it with root explorer. I didn't have any issues.
Then again I stayed within the default density's from my past devices.
Nexus 6 is 560, I went to 480.
Click to expand...
Click to collapse
That's weird. Mine would survive a couple of reboots but after that, bootloop fest.
I'll keep an eye on this issue anyway.
I just went through this on 47E. It was bad but it turns out that you only need to do "adb shell wm density XXX" and not edit the build prop. Editing the build prop sent me through the bootloop
krazekid007 said:
I just went through this on 47E. It was bad but it turns out that you only need to do "adb shell wm density XXX" and not edit the build prop. Editing the build prop sent me through the bootloop
Click to expand...
Click to collapse
The thing is, if you only do "adb shell wm..." you will get weird graphical glitches, especially in the keyboard. So far, I've managed to avoid them by editing build.prop too.
redsmith said:
The thing is, if you only do "adb shell wm..." you will get weird graphical glitches, especially in the keyboard. So far, I've managed to avoid them by editing build.prop too.
Click to expand...
Click to collapse
Still get glitches even after rebooting?
Lol, I'm so glad someone brought this up. Thought I or my phone was going nuts!
All I've ever done is change the build.prop, no adb stuff, never had issues...for all builds
Sent from my Nexus 6 using XDA Free mobile app
A2CKilla said:
All I've ever done is change the build.prop, no adb stuff, never had issues...for all builds
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
It lasts for a few days sometimes.... Usually after a reboot or 2 its gameover.. It'll usually let me reboot 2x before looping .. If I don't reboot it'll just randomly turn off and then..well.. Loop
Not the only ones with this issue... here's what I have found even with "D" & "E" working with the group trying to port the Blinkfeed Launcher from Sense 7 which requires a DPI change to work correctly on the Nexus 6.
532DPI use to work with 5.0.1 & 5.0.2... No longer the case for any 5.1 build (haven't tried "M" build yet) which is the perfect setting for Blinkfeed Sense 7 Launcher....
I am using 520 right now... other experience issues with the bootloop at 520... I have found a way to test:
1. TWRP backup current good DPI setting... Backup up everything cache, efs, system, data, etc.
2. After TWRP backup, boot up and apply the new settings you wish to test. Apply then completely power off.
3. Power on and boot up. If no optimizing apps issues, you have passed step one.
4. Now TWRP backup your new settings, backup everything, reboot system. If no bootloop, then you should be golden
I think it is something in the code to streamline how it handles graphics... however it seems that what is acceptable varies from phone to phone. Most see good results staying with factors of 40 & 80 while others can do even factors of 20....
Don't think anyone has figured out root cause entirely..... I really like to know why I could 532 before and can't now???
Yea 532 was my buttah
redsmith said:
The thing is, if you only do "adb shell wm..." you will get weird graphical glitches, especially in the keyboard. So far, I've managed to avoid them by editing build.prop too.
Click to expand...
Click to collapse
So were you able to successfully change your DPI by editing the build.prop?
I had to do adb shell trick too, otherwise, bootloops.
Build.prop edit LCD_density
redsmith said:
. . . . . I think this is really weird, since 47D and 47E are supposed to be identical. Does anybody have any clue about this?
Click to expand...
Click to collapse
Started with rooting 5.0.1. Then edited build.prop with 'build.prop.editor and changed the LCD-density to 493.
Because the native resolution is of the N6 screen is 493.
After upgrading to LMY47D the DPI value was 520 (0r 560?) again. I edited this value 'ro.sf.lcd_density' and set the value to 384.
With that value the N6 is in tablet mode.
After rebooting the value of 'ro.sf.lcd_density was 384, but the display was not different.
In the Build.Prop editor there is a menu item called Build.Prop Tweaks. In the Tweaks-list the entry 'LCD Density' was missing.
I did not have a backup of the build.prop file so a full restore in recovery was needed to correct this.
The Build.Prop editor has an option to create a backup. Use this option first before editing.
Now for about a week with 47D and DPI 384 and font size to huge, the N6 works fine. (Stock, rooted, encrypted).
Remark.
Because the N6 has a amoled display it's a bit strange that the name 'ro.sf.lcd_density' is used.
NLBeev said:
Started with rooting 5.0.1. Then edited build.prop with 'build.prop.editor and changed the LCD-density to 493.
Because the native resolution is of the N6 screen is 493.
After upgrading to LMY47D the DPI value was 520 (0r 560?) again. I edited this value 'ro.sf.lcd_density' and set the value to 384.
With that value the N6 is in tablet mode.
After rebooting the value of 'ro.sf.lcd_density was 384, but the display was not different.
In the Build.Prop editor there is a menu item called Build.Prop Tweaks. In the Tweaks-list the entry 'LCD Density' was missing.
I did not have a backup of the build.prop file so a full restore in recovery was needed to correct this.
The Build.Prop editor has an option to create a backup. Use this option first before editing.
Now for about a week with 47D and DPI 384 and font size to huge, the N6 works fine. (Stock, rooted, encrypted).
Remark.
Because the N6 has a amoled display it's a bit strange that the name 'ro.sf.lcd_density' is used.
Click to expand...
Click to collapse
whojabacod said:
Yea 532 was my buttah
Click to expand...
Click to collapse
krazekid007 said:
So were you able to successfully change your DPI by editing the build.prop?
Click to expand...
Click to collapse
redsmith said:
I had to do adb shell trick too, otherwise, bootloops.
Click to expand...
Click to collapse
I don't believe there is any rhyme or reason to it bootlooping... something is definitely different in the programming in 5.1... tried everything last night to get 532DPI to stick.... build.prop.... adb command... tried them all... would reboot 1 time ok, second time "op apps" bootloop. this was not the case with 5.0.1 or 5.0.2... I remember tweaking the dpi by 2 up and down to find a perfect dpi for a Blinkfeed launcher port on 5.0.2 and never had this issue. It is either something Google did on purpose for this build or on accident. Either way, we are kind of screwed until someone smarter than I can put a finger on as to what is causing this... I just think 5.1 was rushed to get VoLTE out there for the Verizon release...
When your N6 is bootlooping in 5.1. And you can't find the cause and/or a solution then you could decide to go back to the factory settings including unroot. This can be done easily with the toolkit of Wugfresh.
I did that and I am using now 5.1 (47D) and edited buil.prop. DPI set to 384.
NLBeev said:
When your N6 is bootlooping in 5.1. And you can't find the cause and/or a solution then you could decide to go back to the factory settings including unroot. This can be done easily with the toolkit of Wugfresh.
I did that and I am using now 5.1 (47D) and edited buil.prop. DPI set to 384.
Click to expand...
Click to collapse
Or you can just fastboot flash system.img and save time and your data. It's what I did on a DPI bootloop.
SilkyJohnson said:
Or you can just fastboot flash system.img and save time and your data. It's what I did on a DPI bootloop.
Click to expand...
Click to collapse
Let's hope for him.
NLBeev said:
Let's hope for him.
Click to expand...
Click to collapse
No need to hope - it works. I did it.
Managed to soft brick my Note 4. Set my dpi to 200, and my resolution to 720p. Apparently, it's just too low. Worked great when I set the values, but restarting the phone caused the brick. (It boots, but can't access anything. Unfortunately, I don't have my PC allowed as ADB, so I can't even connect from that state to ADB.)
So.
My idea to prevent full wipe, is to use ADB sideload OR ORS.
- Sideload. Make a "payload" that will replace the build.prop with the stock one.
- ORS. http://wiki.rootzwiki.com/OpenRecoveryScript
How do I actually do this?
Like the RecoveryScript seems to be a great idea, but from TWRP, I could not find a single build.prop file at all. There is a default prop, but it contains no resolution, dpi or whatever.
So I spent another few hours on this. I hate myself. And I hate the app's developer for being so careless.
- Flashed latest Samsung firmware hoping it will kill the software. Nope. It did not.
- Flashed the .zip for build.prop. NO effect.
The system has the correct DPI value so it must not be the issue.
- I think the app auto runs, and sets resolution. So I tried grep, but it cannot find the "1280" string anywher,e and I also removed the app from /data/app and /data/data.
- I cannot get MTP or ADB working in TWRP whatsoever. Huge letdown, but there is just no support. And without seeing what happens on the screen (it must be just my lockscreen there), I can't accept ADB connections either.
Well, so I went YOLO and cleared data. And... behold, NOTHING.
Did this retarded stupid program killed my phone? Holy hell.
Okay, so full entire wipe + reflash + full wipe, and now it works.
This app? Never again. The others are good on the market, so go for it.
App in question: https://play.google.com/store/apps/details?id=com.chornerman.easydpichanger
[ DO NOT USE !!! ]
Instead of wipes at Restore DPI: You can remove only of "com.android.providers.settings" at "/data".
Sorry but I have to resurrect this. I've played with dpi settings and now after reboot I cannot press enter when I type in my password as keyboard is partly off screen. TWRP is not working as it does not support Android 12. Any chance to resolve this beside flash?
Update: Connected keyboard via OTG cable and managed to unlock
Resurrecting this to offer another solution that doesn't involve any wiping/flashing/restoring-to-stock or messing with build.props
I used the same app as OP and feared the worst when I got stuck on recovery after changing DPI
This method allowed me to restore my xiaomi Redmi 9 with android 10
-You need to have a custom recovery installed
-"shell wm" commands don't work in recovery
You need to edit settings_global.xml & settings_secure.xml found in /data/system/users/0
You can do this by pulling&pushing the files to a PC using adb or editing in recovery using nano editor or something similiar.
Search for:
"display_size_forced" in settings_global.xml
"display_density_forced" in settings_secure.xml
Edit those with something close to your default values, then reboot and that's it!
Now that you're no longer stuck in boot you can reset resolution and density with the usual methods like adb or a better app
I hope this helps anyone else stuck in the same problem I was
mrmrva said:
...TWRP is not working as it does not support Android 12. ......
Click to expand...
Click to collapse
Where did you get a A12 version for which Note4?
Owning a N910F=trlte I don't find any higher than A11.
Don't have Samsung but Poco f2 pro and was looking for solution everywhere so posted here.