Q&A for [TabZ][TWRP][PhilZ Touch][CWM] XZDualRecovery Q&A
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [TabZ][TWRP][PhilZ Touch][CWM] XZDualRecovery Q&A. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
where am i?
Just wanted to say thanks for the great software for free! It's working great!
I did have a little trouble installing. I get this message
./install.sh: line 74: ./adb.linux: No such file or directory
./install.sh: line 75: ./adb.linux: No such file or directory
./install.sh: line 76: ./adb.linux: No such file or directory
and so on. Apparently my linux is a different build? 32 bit vs 64 bit?
anyway using my os's adb solves the problem. Use sed on the install.sh
sed 's/.\/${ADBBINARY}/\/sbin\/adb/' install.sh > newinstall.sh
If any other noobs are scrathing their heads... But i cant post in the thread... so...
Related
Q&A for [ROM][UB][4.4.4] Unofficial SlimKat [Slim Build 8.2]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][UB][4.4.4] Unofficial SlimKat [Slim Build 8.2]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
SlimKat - two questions
Hi,
Great work on the SlimKat build, it looks really slick and doesn't CTD as much as the JB ROM I was running previously.
Two questions:
I saw mention of a ROM to get the LED illumination bar working. Can someone point me to it?
My phone doesn't recognise my headphones any more. Anyone else seen this?
Anticipated Android L?
why everything got so big in last ota update?
its just not normal.
its even worse in nova luancher!
just look at these screen shot
You need to edit your build.prop file, as mentioned in the main thread. When I tried this, I ended up breaking the boot for a while, until I figured out it was a permissions problem; so be careful. The following process works for me.
Connect your phone, with USB debugging on. You'll be using
Code:
adb
to fiddle with the files. At a command prompt, type:
Code:
adb shell
That will give you a shell prompt in your phone. Now type:
Code:
cd /system
cp build.prop build.propbak
sed -i s/ro.sf.lcd_density=.*/ro.sf.lcd_density=180/ build.prop
exit
The second line is backing up the existing build.prop, so you can put it back if you get into trouble. The third line edits the build.prop in place, replacing the line that sets the display density with one set to 180. That makes it look right for me. Values between 180 and 280 should definitely work; larger number, larger icons.
Then reboot, and you should be back to a good size.
Asilano said:
You need to edit your build.prop file, as mentioned in the main thread. When I tried this, I ended up breaking the boot for a while, until I figured out it was a permissions problem; so be careful. The following process works for me.
Connect your phone, with USB debugging on. You'll be using
Code:
adb
to fiddle with the files. At a command prompt, type:
Code:
adb shell
That will give you a shell prompt in your phone. Now type:
Code:
cd /system
cp build.prop build.propbak
sed -i s/ro.sf.lcd_density=.*/ro.sf.lcd_density=180/ build.prop
exit
The second line is backing up the existing build.prop, so you can put it back if you get into trouble. The third line edits the build.prop in place, replacing the line that sets the display density with one set to 180. That makes it look right for me. Values between 180 and 280 should definitely work; larger number, larger icons.
Then reboot, and you should be back to a good size.
Click to expand...
Click to collapse
tnx man.
worked like a charm
No mantiene varias apps abiertas.
Muy buen ROM con perfecto rendimiento pero aun no consigo manera de escuchar musica respondiendo en BBM o mientras chateo por el Whatsapp,no mantiene dos procesos a la vez.
Someone knows when will the Stable 9.0??
Q&A for [ROM][UB][5.0.1] Unofficial SlimLP [Alpha 0.8]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][UB][5.0.1] Unofficial SlimLP [Alpha 0.8]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
How to?
he guys.....i did not get the adb shell part???
can anyone plz tell me how to do that part.....????
after connecting my phone to the pc then what will i do???
and what should i copy or paste the line ??? thnx in advance
Yasin Abir said:
he guys.....i did not get the adb shell part???
can anyone plz tell me how to do that part.....????
after connecting my phone to the pc then what will i do???
and what should i copy or paste the line ??? thnx in advance
Click to expand...
Click to collapse
You have to download adb into your computer first. http://forum.xda-developers.com/showthread.php?t=2588979
Then connect your phone with Android Debugging was on (Developer options in Settings)
Open cmd (Command Prompt) and type in these line:
Code:
adb shell
echo "512,768,2880,4160,6080,10560" > /sys/module/lowmemorykiller/parameters/minfree
This will make the keyboard more usable.
I was wrong to post, I can not delete the comment sorry. Detele it please.
automatically reboot
I need help now, after installing rom, my sola sometimes reboot by itself even when I do not use it.
please help, i really like this rom
rndy_Chaniago said:
I need help now, after installing rom, my sola sometimes reboot by itself even when I do not use it.
please help, i really like this rom
Click to expand...
Click to collapse
I had the same problem. Uncheck automatic brightness in settings>display. It helped me.
Here is logcat:
Code:
I/DEBUG (28191): pid: 28697, tid: 29145, name: RenderThread >>> com.android.systemui <<<
I/DEBUG (28191): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
I/DEBUG (28191): Abort message: 'Encountered EGL error 12291 EGL_BAD_ALLOC during rendering'
Q&A for [TABUNTU] Galaxy Tab 10.1 NATIVE Ubuntu WIFI now with a video
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [TABUNTU] Galaxy Tab 10.1 NATIVE Ubuntu WIFI now with a video. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
tabuntu install on Android problem
I have some problems, when I type bootubuntu I get this message :
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at AndroLinux.com ,G2Hacks.com and NexusOneHacks.net
To enter the Ubuntu Linux console just type 'bootubuntu'
[email protected]:/sdcard/ubuntu # bootubuntu
tmp-mksh: bootubuntu: can't execute: Permission denied
126|[email protected]:/sdcard/ubuntu #
anyone can help me???
Q&A for RegawMOD Bootloader Customizer | Full Application | Updated 10.09.13
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for RegawMOD Bootloader Customizer | Full Application | Updated 10.09.13. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
hi.
Is there anyway through adb or otherwise to 'pull' the original hboot file from the phone ?
I used this
$ adb shell
shell:/ $ su
shell:/ # dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
shell:/ # exit
$ adb pull /sdcard/hboot.img C:\AndroidSDK\tools
but when i want to open it with a hex editor, it is just all Zero
Hello everyone,
Glad to be here! This is my first time posting on the forum, I apologise in advance if I inadvertently break any rules.
I have installed Android x86 9.0_r2 in a virtual machine using the virt-manager application (QEMU/KVM connection) on Ubuntu 22.04, and I installed it using the ISO and manually selecting the OS as Android x86 9.0. Upon booting, I see a Trusted GRUB 1.1.5 menu and I am able to boot Android x86.
However, my resolution is stuck in 1024x768, and I have to manually edit the GRUB entry and add 'vga=914' after the kernel option to boot with a resolution of 1920x1080.
I read some forum posts stating that the GRUB boot options are located in either a 'menu.lst' file or an 'Android.cfg' file, so I opened the terminal emulator and ran the following commands to find these files in the root directory or sub directories. I also searched for the GRUB directory directly.
su
find / -iname menu.lst -type file -mindepth 100
find / -iname android.cfg -type file -mindepth 100
find / -iname grub -type directory -mindepth 100
However, these commands did not yield any results. So I decided to use grep to try and find the statements present in the boot commands in any of the files present in the system. I decided to search for the statement "root=/dev/ram0", so I ran the following commands to run grep recursively and print the filename where the given text occurs, ignoring errors and binary files:
su
grep --exclude-dir /proc -sIrl "root=/dev/ram0" /
This search took too long, so I narrowed my search to the term "ram0" and checked individual directories instead. However, there were no readable text files containing the boot menu configuration.
Am I making a mistake in any of these commands? Where is the GRUB configuration file located? Please feel free to ask for any additional information to troubleshoot this problem.
Thank you in advance for your help and have a nice day.
kb_android_x86 said:
Hello everyone,
Glad to be here! This is my first time posting on the forum, I apologise in advance if I inadvertently break any rules.
Click to expand...
Click to collapse
Hello and good morning, @kb_android_x86
Welcome to XDA. I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
[Read Before Posting]QUESTIONS DO NOT BELONG IN GENERAL
Hello Everybody, In order to attempt to keep this forum neat and tidy the moderation team is asking you to post your questions into the Questions and Answers (Q&A) forum and not into the General section. You can find the Q&A forum by clicking...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
Hello everyone,
I have found the solution to this problem.
To access the GRUB configuration files, you must boot Android x86 in Debug mode, and then type the following commands into the terminal:
mount -o remount rw /mnt
cd /mnt/grub
vi menu.lst
Then you can edit the GRUB configuration permanently. I am unsure why these files are hidden when booting Android x86 normally, even when I browse the filesystem with root privileges enables.