Related
im running the latest Drizzys hero and i need to set up my swap can anybody put the commands please and what do i use to set it up?....i'm running it o a G1 thanks in advance!!
Do you already have the third partition? If you do, then you can do this in terminal:
Code:
echo 80 > /proc/sys/vm/swappiness
Where "80" is my value for swappiness
I am M3 said:
Do you already have the third partition? If you do, then you can do this in terminal:
Code:
echo 80 > /proc/sys/vm/swappiness
Where "80" is my value for swappiness
Click to expand...
Click to collapse
how do u do this permanently from terminal?
ok so let's see if i got it....i did open Terminal Emulator and after i put that code i just get a # should i get any confirmation option? what is the code to check my swappiness at the moment?...and one more thing i should this everytime i reboot right?
DKM119 said:
ok so let's see if i got it....i did open Terminal Emulator and after i put that code i just get a # should i get any confirmation option? what is the code to check my swappiness at the moment?...and one more thing i should this everytime i reboot right?
Click to expand...
Click to collapse
You won't get any varification you'll just recieve no errors. If you want to check the swappiness
Code:
su
vi /system/bin/user.conf
look for cc_swappiness= [] <-- That's what you're swappiness is at.
Got it working ^^
ok folks who fancys some performance tweaks for the 7, i dont have one but ill try and do some edits if people wanna test
I told you, he's The Man!
well until the kernel source is out i probly cant do loads, but i can try
And it starts awesome. When mine gets here id be willing to help out.
sent from my Dinc
right if anyone has some free time drop into the #dellstreak irc channel need help testing tweaks on a live device
Please!
Yes, Please!
Is there a recovery for the tablet yet?
Sent from my Dell Streak 7 using XDA App
as far as i no their is not no,
wondering if anyone has time to jump in irc tonight to help test tweaks
DJ_Steve said:
as far as i no their is not no,
wondering if anyone has time to jump in irc tonight to help test tweaks
Click to expand...
Click to collapse
What time , and what's your time zone?
i was thinking now lol, im in uk GMT time so its like nearly 8pm here
DJ_Steve said:
as far as i no their is not no,
wondering if anyone has time to jump in irc tonight to help test tweaks
Click to expand...
Click to collapse
i was gonna try the one that is for the streak 5 recovery but I wanted to know if anyone else thought about it... I would love to change this rom around and use something else... it's limited on video chat uses... ooVoo doesn't switch to front facing... I'm currently using my streak 7 for wifi only and using sipdroid to make calls to other people with the tablet... anyone else know some video chat apps that would be good with this tablet...
I made a post In the app and theme section asking the same thing. Every video chat ive tryed doesnt turn on the front facing camera. Looks like where stuck waiting for skype to update there android app.
Sent from my Dell Streak 7
lol tried fring for a laugh ?
also can anyone with adb please run the following command and upload the outputted file
Code:
cat /dev/block/mmcblk3p2 > /sdcard/boot7.img
DJ_Steve said:
lol tried fring for a laugh ?
also can anyone with adb please run the following command and upload the outputted file
Code:
cat /dev/block/mmcblk3p2 > /sdcard/boot7.img
Click to expand...
Click to collapse
Here you go.
ok p1 & p2 are both recovery related, thats weird, can anyone try and grab me a complete clone of the streak 7 int sd
commands to run:
Code:
cat /dev/block/mmcblk3p1 > /sdcard/p1.img
cat /dev/block/mmcblk3p2 > /sdcard/p2.img
cat /dev/block/mmcblk3p3 > /sdcard/p3.img
cat /dev/block/mmcblk3p4 > /sdcard/p4.img
cat /dev/block/mmcblk3p5 > /sdcard/p5.img
cat /dev/block/mmcblk3p6 > /sdcard/p6.img
cat /dev/block/mmcblk3p7 > /sdcard/p7.img
cat /dev/block/mmcblk3p8 > /sdcard/p8.img
cat /dev/block/mmcblk3p9 > /sdcard/p9.img
cat /dev/block/mmcblk3p10 > /sdcard/p10.img
cat /dev/block/mmcblk3p11 > /sdcard/p11.img
cat /dev/block/mmcblk3p12 > /sdcard/p12.img
cat /dev/block/mmcblk3p13 > /sdcard/p13.img
cat /dev/block/mmcblk3p14 > /sdcard/p14.img
cat /dev/block/mmcblk3p15 > /sdcard/p15.img
cat /dev/block/mmcblk3p16 > /sdcard/p16.img
then up them somewhere, i can provide an ftp if needed for this
DJ_Steve said:
ok p1 & p2 are both recovery related, thats weird, can anyone try and grab me a complete clone of the streak 7 int sd
commands to run:
Code:
cat /dev/block/mmcblk3p1 > /sdcard/p1.img
cat /dev/block/mmcblk3p2 > /sdcard/p2.img
cat /dev/block/mmcblk3p3 > /sdcard/p3.img
cat /dev/block/mmcblk3p4 > /sdcard/p4.img
cat /dev/block/mmcblk3p5 > /sdcard/p5.img
cat /dev/block/mmcblk3p6 > /sdcard/p6.img
cat /dev/block/mmcblk3p7 > /sdcard/p7.img
cat /dev/block/mmcblk3p8 > /sdcard/p8.img
cat /dev/block/mmcblk3p9 > /sdcard/p9.img
cat /dev/block/mmcblk3p10 > /sdcard/p10.img
cat /dev/block/mmcblk3p11 > /sdcard/p11.img
cat /dev/block/mmcblk3p12 > /sdcard/p12.img
cat /dev/block/mmcblk3p13 > /sdcard/p13.img
cat /dev/block/mmcblk3p14 > /sdcard/p14.img
cat /dev/block/mmcblk3p15 > /sdcard/p15.img
cat /dev/block/mmcblk3p16 > /sdcard/p16.img
then up them somewhere, i can provide an ftp if needed for this
Click to expand...
Click to collapse
Is there a way to store a file larger than 4GB, because I have all of these img files except p14 because p14 is larger than 4gb. I would get it if I could. If you have an ftp, I can upload the others.
ok we'll leave that partition 4gb isnt needed for me
ill drop a pm momentarily with ftp info
dumps uploaded
I uploaded all but 7 and 14, which I guess you don't need. Let me know what you find out.
got em, looking through now, anyone who knows how to use fastboot mode wanna play guine pig for me?
also can someone grab /proc/config.gz if it exists
It exists cant seem too find a way to upload from my tab though.
Sent from my Dell Streak 7
possible fix workaround for the DSI errors on Motorola Milestone Froyo on nadlabaks github
http://github.com/nadlabak/android_...mmit/e1bb339b133dd88389a4c3a80bad3a984d12db50
EDIT:
IanTester said:
echo 1 > /sys/devices/omapdss/display0/update_mode
Click to expand...
Click to collapse
should do the same
EDIT:
<nadlabak> it causes slight tearing, visible e.g. when scrolling through email list...
Click to expand...
Click to collapse
but better than reboots or freezes
also fps might drop
EDIT:
for stock 2.2.1, customroms should use their 2nd init (CM7 HowTo):
move original file:
Code:
mv /system/bin/mot_boot_mode /system/bin/mot_boot_mode.bin
create file /system/bin/mot_boot_mode:
Code:
#!/system/bin/sh
export PATH=/system/bin:$PATH
mot_boot_mode.bin
echo 1 > /sys/devices/omapdss/display0/update_mode
set rights:
Code:
chmod 755 /system/bin/mot_boot_mode
EDIT:
made HowTo more clear, hopefully
How to apply this?
Sent from my Milestone using XDA App
to apply this fix you hafe to (as root or in OR)
if /system is readonly:
Code:
mount -o rw,remount /system
then edit /system/etc/rootfs/init.mapphone_umts.rc and add
Code:
# Set OMAP DSS update_mode to 1 (auto) to get rid of the DSI errors
write /sys/devices/omapdss/display0/update_mode 1
after these lines
Code:
# Enable panic on softlockup
write /proc/sys/kernel/softlockup_panic 1
reboot Milestone
Maybe it should be
mount -o ro,remount /dev/block/mtdblock6 /system
Hm, there is no directory rootfs in /system/etc/ ... Have you tried what you are writing here? Maybe "rootfs" refers to the root dir "/" and the file to edit is "/init.mapphone_umts.rc".
You don't need a reboot.
echo 1 > /sys/devices/omapdss/display0/update_mode
Click to expand...
Click to collapse
(I presume that's what that command in the rc file does, right?)
But make the changes to the rc file as well, so the above action is performed on subsequant boots.
as it's on nadlabaks github for cyanogenmod4milestone (CM7) it might differ from the way to do in official froyo. but IanTesters way should do the same
ColdSphinX said:
as it's on nadlabaks github for cyanogenmod4milestone (CM7) it might differ from the way to do in official froyo. but IanTesters way should do the same
Click to expand...
Click to collapse
Seems to be the case. But since I'm not able to edit /init.mapphone_umts.rc (that's the reason why there is an extra dir for this in cyanogenmod), how am I supposed to implement this fix in the official froyo?
Done on CM6.
Yesterday I was browsing the system folders and found this file, full of customizable options, now I know that it's useful.
@tuxor1337: look for the mot_boot_mode hack to run a script as it's used for overclock
IanTester said:
echo 1 > /sys/devices/omapdss/display0/update_mode
Click to expand...
Click to collapse
For stock Froyo roms, i applied VR and then ran AOR, connected phone to pc and used the following commands in command prompt.
adb devices ( should show your device as connected )
adb shell
echo 1 > /sys/devices/omapdss/display0/update_mode
reboot
Upon reboot, i did not find any errors in dmesg which i usually find.
Can someone with more knowledge than me confirm if this is ok?
I know that can be a noobish question but what VR stands for ?
fuggii said:
I know that can be a noobish question but what VR stands for ?
Click to expand...
Click to collapse
VR --> Vulnerable recovery
AOR --> Androidiani openrecovery
I had to do it because adb was not recognising my phone while in the stock recovery menu.
Once i ran AOR, adb recognised my phone to be in recovery mode.
I make this "echo 1 > /sys/devices/omapdss/display0/update_mode" from terminal emulator and after reboot its back to "2" it must be done form adb in AOR ?
it has to be done on or after any boot.
I edited the 1st post to include the changes to do on stock 2.2.1
fuggii said:
I make this "echo 1 > /sys/devices/omapdss/display0/update_mode" from terminal emulator and after reboot its back to "2" it must be done form adb in AOR ?
Click to expand...
Click to collapse
Looks like it loses it during reboot, so it could be added to the init.rc file as well. I am not sure, that's why i asked with someone more knowledge to confirm this.
Anyone?
I have Autostart app and i make autostart.sh with that command and now its start every system boot.
In home i will try that ColdSphinX method and see what happend
@fuggii it's not my method, it's just a mot_boot_mode hack so you don't need any app and the fix get's applyed as early as we can
I think this should work but I copied all of this https://github.com/nadlabak/android...b50/prebuilt/etc/rootfs/init.mapphone_umts.rc
And used that as init.mapphone_umts.rc
Hey the OP needs updating....
It's missing the 1
echo 1 > /sys/devices/omapdss/display0/update_mode 1
zeppelinrox said:
It's missing the 1
echo 1 > /sys/devices/omapdss/display0/update_mode 1
Click to expand...
Click to collapse
no
Code:
echo [B]1[/B] > /sys/devices/omapdss/display0/update_mode
writest the value 1 into file /sys/devices/omapdss/display0/update_mode it's an other syntax then using write in the .rc
HI All,
I just have recieved my Tablet back after it would no longer power up - looks like they had to re flash it and put it into factory mode and left it there, problem with this is that I cannot lock the screen, I have researched and found a temp fix where you put a engineers code in - but as soon as you re-boot it loses this.
I have also found some code
adb shell
su
echo -n ON > /efs/imei/keystr
chown 1001:1001 /efs/imei/keystr
which i have tried using a terminal emulater (on the andriod market) not sure if its me being dumb but i cant get this to work, when it boots now it looks like nvflash is now unlocked. I'm hoping i dont have to send it back again - is there any other things I can try? I have tried other ROMS but because of this factory mode its the same
Thanks in advance
whitehart said:
HI All,
I just have recieved my Tablet back after it would no longer power up - looks like they had to re flash it and put it into factory mode and left it there, problem with this is that I cannot lock the screen, I have researched and found a temp fix where you put a engineers code in - but as soon as you re-boot it loses this.
I have also found some code
adb shell
su
echo -n ON > /efs/imei/keystr
chown 1001:1001 /efs/imei/keystr
which i have tried using a terminal emulater (on the andriod market) not sure if its me being dumb but i cant get this to work, when it boots now it looks like nvflash is now unlocked. I'm hoping i dont have to send it back again - is there any other things I can try? I have tried other ROMS but because of this factory mode its the same
Thanks in advance
Click to expand...
Click to collapse
A friend of mine followed this thread and he made it.i think he has the same issue with factory mode.Did u try?if not u can try and see how it works.Good luck.
http://forum.xda-developers.com/showthread.php?t=1870564
thovu1980 said:
A friend of mine followed this thread and he made it.i think he has the same issue with factory mode.Did u try?if not u can try and see how it works.Good luck.
http://forum.xda-developers.com/showthread.php?t=1870564
Click to expand...
Click to collapse
cheers yes thats what i tried following
I wonder if I'm not doing the
adb shell
su
echo -n ON > /efs/imei/keystr
chown 1001:1001 /efs/imei/keystr
code correctly, whats the best way to enter this code? I think I may need an idiots guide !!
im going to phone the repair place see what they say
Phoned up samsung - they not able to do anything on the phone, sigh!!!!
it has to go back to the repair place - samsung i dont think understood the issue fully - lets hope it gets fixed - i learnt they replaced the motherboard!
Why don't you ask over here? http://forum.xda-developers.com/showthread.php?t=1870561
You can use Terminal Emular and enter:
Code:
su
echo -n ON > /efs/imei/keystr
chown 1001:1001 /efs/imei/keystr
Make sure you are rooted! (SuperSU or Superuser installed)
tracid said:
Why don't you ask over here? http://forum.xda-developers.com/showthread.php?t=1870561
You can use Terminal Emular and enter:
Code:
su
echo -n ON > /efs/imei/keystr
chown 1001:1001 /efs/imei/keystr
Make sure you are rooted! (SuperSU or Superuser installed)
Click to expand...
Click to collapse
just tried teh code again to see if i was going mad - no it doesnt seem to work? the engineers code temp works but the emulator code doesnt
EDITI just did a reset - after doing the code - guess what so far so good I think i have fixed it
Yayyy!!!
i make this thread for the less experienced people that want to make some easy little changes to the kernel or rom and wanna make them permanent. For example lets say i use ondemand governor , i set the up_threshold at 65 so i dont lag but after reboot my changes are reverting back.
Since we dont all know how to edit the kernel to put our values by default, there is an easy way.
We can go to etc/init.d and create a script there.
First line will always be: #!/system/bin/sh
if we want we can write what the script is about at the 2nd line. example: # Set my default values for ondemand governor.
And we write our script. Save it and its ready.
Example:
#!/system/bin/sh
# Set my default values for ondemand governor.
modprobe cpufreq_ondemand
for file in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do echo ondemand > $file; done
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/ignore_nice_load
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias
echo 3 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor
echo 120000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
echo 65 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
Go ahead save it with whatever name u like using 90 infront of the name. 90ondemand
Reboot the phone and go check if that worked. :fingers-crossed: the idea is the same with whatever u wanna change and make it permanent.
This thing has been tested in cm 10.2. propably will work on any rom because android doesnt use a rc.local, instead it uses scripts inside init.d folder. I hope this info helps everyone who wanna do some settings permanent to their phone.
EDIT:
Please be careful what u write and always keep a backup of a script if u gonna change any default script that the phone already uses.
Its critical to be careful. If u mess with voltages for example to make ur battery live longer BE CAREFUL you might "burn" the phone. Do this way and make permanent changes ONLY if u know what u are doing , not to randomly test something.