Related
So, prior to updating to 2.2 I had been testing s couple of things and had my screen set to stay on while plugged in. After the update to Froyo the menu option in "settings" was removed.
However, now I am stuck in screen on mode. (they took the settings control away but didn't change the setting to what they want ) It's pretty annoying because for various reasons the screen chooses to wake up from time to time while charging and I'm a little concerned about burn-in. This makes it so I can't charge the phone unless it is sitting in front of me.
Can someone point me to where this setting might be stored. I'm happy to edit a DB from command line or tweak a settings file... I just don't know where to begin to look.
-p
I'll answer my own question.
In the database
/dbdata/databases/com.android.providers.settings/settings.db
in the table "system" there is an entry "stay_on_while_plugged_in" with a setting of "3" for me..
http://developer.android.com/refere...Settings.System.html#STAY_ON_WHILE_PLUGGED_IN says 0 means off and 1 and 2 have to do with the constants
BATTERY_PLUGGED_AC and
BATTERY_PLUGGED_USB
since these values can be OR-ed together 3 means stay on for USB or AC
I changed it to 0 and am back to normal.
While I as in there I also chose to enable non-market apps since I hadn't done that yet...
Hi,
I'm actually trying to do the opposite. But after modifying it, and rebooting, it comes back with the original values.
I modified the value from 0 to 3 using SQLite Editor. This is after copying the settings.db file to /sdcard, modifying it, writing it back to /dbdata/databases... , and finally changing the permissions and ownership.
I'm running stock Froyo with overstock kernel, rooted (obviously), and voodoo lagfix turned on.
I had sideloading-enabled previously while in Eclair, and after updating it using mini-Kies to stock Froyo, it was still enabled so I didn't bother to do anything with the settings.db file until now.
Any ideas what I'm doing wrong?
Hi I've been doing research and unfortunately I'm not sure if what i have now i rooted my phone with with honey comb installed (Android 3.2)
Now the first part is I've been looking for parts like the outside Belize as I've cracked mine although its 100% still functional just been looking for a replacement part now I've been having trouble finding a replacement part, any help would be great now for my main question
Since i've rooted my phone i've noticed very sluggish performance since installing super user (3.1.3) (46) Su Binary 3.1.1 (17) after installing that its been very sluggish with performance it'll lag or it 'lll just studder a lot now I've done some clean up cleaning up dalvik cache, minor tweaks that i though might have been causing problems and every now and then I've found the Streak 7 will Crash or not power back up it appears its comming back but will just stall and i'll have to use the reset pin hole to restart the hardware. since the rooting
Any help with this would be great, as I am debating on reinstalling the / Doing a factory reset.
Also went through and attempted to fix the file system permissions as well. Any ideas what might be going on....
We need logs to see what is going on. Please go read on how to pull a logcat.
I did a few quick logs with Catlog while running games and doing my normal regime so hopefully this helps out to figure out whats going on..
I'm thinking that i might have a corrupted install as I've noticed errors inside the logs but not really sure how to make heads or tails of them.
also i've noticed my calculator is doing some really strange things only giving 2 digit answers and truncating the rest of the answer only leaving the last 2 digits or being a multiple of 3. very weird hope this helps
Thanks in advance
Does anyone have any ideas whats going on with it i can create another cat log ... but i'm really not sure why this is going on as i've tryed almost all the solutions that is provided part of google.searching.
Your on Android 2.2, thats your problem.
giveen said:
Your on Android 2.2, thatch your problem.
Click to expand...
Click to collapse
Negative I'm running android 3.2 honeycomb ...
it ran wickedly fast before with out super user now that i rooted and installed the SU binary
then it slowed right down so I'm not sure whats going on,
BlackSwoul said:
Negative I'm running android 3.2 honeycomb ...
it ran wickedly fast before with out super user now that i rooted and installed the SU binary
then it slowed right down so I'm not sure whats going on,
Click to expand...
Click to collapse
Fine, you are running stock Honeycomb, there is your problem.
hi.
My Galaxy S1 screen just broke completely today, both LCD and digitizer, so I don't see anything and the phone doesn't respond to touch.
I'm actually using the phone as a security camera, and since it is configured to auto start on boot, I am fine. But I still would like a way to control the phone, maybe something like teamviewer... The problem is, I cannot install anything since I can't control the phone right now. Is there a way to do that? Maybe using some ADB commands? The phone is rooted and running CM 11.
Thanks.
yes you can
romitkin said:
hi.
My Galaxy S1 screen just broke completely today, both LCD and digitizer, so I don't see anything and the phone doesn't respond to touch.
I'm actually using the phone as a security camera, and since it is configured to auto start on boot, I am fine. But I still would like a way to control the phone, maybe something like teamviewer... The problem is, I cannot install anything since I can't control the phone right now. Is there a way to do that? Maybe using some ADB commands? The phone is rooted and running CM 11.
Thanks.
Click to expand...
Click to collapse
https://github.com/yangh/sevensquare i use this
you can also install debian in chroot
debiankit -- google it
midhato said:
https://github.com/yangh/sevensquare i use this
you can also install debian in chroot
debiankit -- google it
Click to expand...
Click to collapse
You can install a kernel which supports USB Host functionality.
I noticed the other day that even with all volume sliders at 100%, my tf701t is significantly quieter than it used to be. I've restored a nandroid, wiped data, even accidentally wiped EVERTHING including all of my files (turns out that the bootloader's wipe option kills your internal SD card contents, too... argh!). Nothing at all seems to increase the sound volume.
I have this feeling I might have caused this with a bit of (perhaps unwise) tinkering. I have ubuntu running in a chroot, and I was poking around and seeing if I could get sound working from the ubuntu side. I saw that with root (or with my user added to the right group) I can run alsamixer and get at all sorts of interesting little sliders. I experimented a fair bit, seeing if raising various sliders and unmuting various channels would let me get sound to play using alsa's aplay command. None of that panned out and I abandoned my effort.
Fast forward to yesterday, days and several reboots after I did the above tinkering, and I noticed that the speaker output was barely audible. I've poked around in alsamixer, and I can get it a BIT louder by unmuting a couple of the channels, but it's nowhere near actually useful volume. I'm not at all sure I caused this by tinkering with alsamixer, but I'm also not at all sure I didn't. I wouldn't have expected any changes I made to survive a reboot, but maybe the tegra chip does things weirdly.
Anyone have any ideas?
If anyone's feeling especially helpful, it would be incredibly useful to me if you could get me the normal alsa mixer channel values. Here's how you can do it with the least amount of fuss (root required of course):
grab "Complete Linux Installer" from the market -- I swear this isn't a plug
Follow the tutorial to grab the "core" version of ubuntu 13.10.
get it all set up and boot it up
when it asks, don't run vnc or sshd
open a second terminal, and run these commands:
su
umount /data/local/mnt/dev/pts
mount -t bind /dev /data/local/mnt/dev
mount -t devpts devpts /data/local/mnt/dev/pts
Now, back in the first terminal, do this:
apt-get install alsa-utils
amixer contents > useful_data_for_lexelby.txt
Grab that file and post it here
I realize that's a lot of effort to ask of you folks -- just hoping someone will have pity on a poor amateur android tinkerer Some linux knowledge would probably be useful, as I've glossed over a few of the setup details. Thanks in advance to any brave souls willing to give this a try.
lexelby said:
I noticed the other day that even with all volume sliders at 100%, my tf701t is significantly quieter than it used to be. I've restored a nandroid, wiped data, even accidentally wiped EVERTHING including all of my files (turns out that the bootloader's wipe option kills your internal SD card contents, too... argh!). Nothing at all seems to increase the sound volume.
I have this feeling I might have caused this with a bit of (perhaps unwise) tinkering. I have ubuntu running in a chroot, and I was poking around and seeing if I could get sound working from the ubuntu side. I saw that with root (or with my user added to the right group) I can run alsamixer and get at all sorts of interesting little sliders. I experimented a fair bit, seeing if raising various sliders and unmuting various channels would let me get sound to play using alsa's aplay command. None of that panned out and I abandoned my effort.
Fast forward to yesterday, days and several reboots after I did the above tinkering, and I noticed that the speaker output was barely audible. I've poked around in alsamixer, and I can get it a BIT louder by unmuting a couple of the channels, but it's nowhere near actually useful volume. I'm not at all sure I caused this by tinkering with alsamixer, but I'm also not at all sure I didn't. I wouldn't have expected any changes I made to survive a reboot, but maybe the tegra chip does things weirdly.
Anyone have any ideas?
If anyone's feeling especially helpful, it would be incredibly useful to me if you could get me the normal alsa mixer channel values. Here's how you can do it with the least amount of fuss (root required of course):
grab "Complete Linux Installer" from the market -- I swear this isn't a plug
Follow the tutorial to grab the "core" version of ubuntu 13.10.
get it all set up and boot it up
when it asks, don't run vnc or sshd
open a second terminal, and run these commands:
su
umount /data/local/mnt/dev/pts
mount -t bind /dev /data/local/mnt/dev
mount -t devpts devpts /data/local/mnt/dev/pts
Now, back in the first terminal, do this:
apt-get install alsa-utils
amixer contents > useful_data_for_lexelby.txt
Grab that file and post it here
I realize that's a lot of effort to ask of you folks -- just hoping someone will have pity on a poor amateur android tinkerer Some linux knowledge would probably be useful, as I've glossed over a few of the setup details. Thanks in advance to any brave souls willing to give this a try.
Click to expand...
Click to collapse
I dont know if this is helpful without mounting things. Ill do the mounts later. I used Linux deploy as well.
numid=1,iface=CARD,name='HDMI/DP,pcm=3 Jack'
; type=BOOLEAN,access=r-------,values=1
: values=off
numid=2,iface=MIXER,name='IEC958 Playback Con Mask'
; type=IEC958,access=r-------,values=1
: values=[AES0=0x0f AES1=0xff AES2=0x00 AES3=0x00]
numid=3,iface=MIXER,name='IEC958 Playback Pro Mask'
; type=IEC958,access=r-------,values=1
: values=[AES0=0x0f AES1=0x00 AES2=0x00 AES3=0x00]
numid=4,iface=MIXER,name='IEC958 Playback Default'
; type=IEC958,access=rw------,values=1
: values=[AES0=0x00 AES1=0x00 AES2=0x00 AES3=0x00]
numid=5,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw------,values=1
: values=on
numid=6,iface=MIXER,name='HDA Decode Capability'
; type=INTEGER,access=rw------,values=1,min=0,max=-1,step=0
: values=0
numid=7,iface=MIXER,name='HDA Maximum PCM Channels'
; type=INTEGER,access=rw------,values=1,min=0,max=-1,step=0
: values=0
numid=8,iface=PCM,name='ELD',device=3
; type=BYTES,access=r-------,values=0
---------- Post added at 08:32 AM ---------- Previous post was at 08:18 AM ----------
Doesnt linux deploy mount all these things anyway? Running the mixer from linux deploy doesnt let me changed volume levels as far as I know. It does show the sound devices. Might it be that some things are read only. Try installing it possibly with Archlinux which im using. Maybe itll fix it for you in some magical way
Oh! That's almost exactly what I need. They only thing is that I forgot to mention that I need the mixer values for card 1 -- it defaults to sound card 0, which is the hdmi output. It looks like your Linux installer did the bind mount of /dev just fine. Not sure why Compete Linux Installer doesn't, but it should. I ended up hacking the startup script to mount /dev properly.
Thanks so much for your help!
lexelby said:
Oh! That's almost exactly what I need. They only thing is that I forgot to mention that I need the mixer values for card 1 -- it defaults to sound card 0, which is the hdmi output. It looks like your Linux installer did the bind mount of /dev just fine. Not sure why Compete Linux Installer doesn't, but it should. I ended up hacking the startup script to mount /dev properly.
Thanks so much for your help!
Click to expand...
Click to collapse
Oh right. Lots more information here.
And with linuxdeploy you can VNC into as if it were some kind of RASPBERRY PI OR BEAGLEBOARD advertised to you for all of eternity!!
Thanks so much for providing that amixer output!
YayYouFixedIt said:
And with linuxdeploy you can VNC into as if it were some kind of RASPBERRY PI OR BEAGLEBOARD advertised to you for all of eternity!!
Click to expand...
Click to collapse
Yeah, the one I used does vnc, but performance is pretty pitiful. I use XSDL from the market, a direct x11 server. Supports more apps (chrome crashes on vnc for me) and it's much faster -- almost like a real Linux box.
lexelby said:
Thanks so much for providing that amixer output!
Yeah, the one I used does vnc, but performance is pretty pitiful. I use XSDL from the market, a direct x11 server. Supports more apps (chrome crashes on vnc for me) and it's much faster -- almost like a real Linux box.
Click to expand...
Click to collapse
Very cool, I see with XSDL you can stream a Linux app directly to the tablet Like intelliJ/android studio for example looks exactly the same. Only thing is I couldnt see the on screen keyboard it mentions in the settings.
EDIT: Oh it looks like you have to use the default keyboard.
How did you fix it?
So, did you ever solve the problem with the internal speaker volume? I'm having a similar issue after rooting and installing a custom ROM. I ended up going back to Jellybean to solve a battery drain issue I was having.
Actually, no, I never did find a fix. I tried various other ROMs, but none fixed it. I think my initial theories that I broke it by tinkering with alsamixer were unfounded, and this is just some weird hardware flaw. I bought a little battery-powered speaker which helps a bit.
I have same problem
Hi, I have same problem with quiet speaker. Today I did my first root of android device by these instructions. Root was successful and then during using my tablet I realized the speaker is very quiet. After root I did only one thing - removed file /system/vendor/lib/mediadrm/libwvdrmengine.so which was the part of solution of battery drain problem described here. Sound via external speakers connected by jack into tablet is ok.
I tried fastboot recovery, wipe data and cold start, but still same problem. Even loading removed file back wasn't helpful.
If you anybody has resolved same problem, thank you for advice, how to repair it. I hope this problem has a solution.
babusek said:
Hi, I have same problem with quiet speaker. Today I did my first root of android device by these instructions. Root was successful and then during using my tablet I realized the speaker is very quiet. After root I did only one thing - removed file /system/vendor/lib/mediadrm/libwvdrmengine.so which was the part of solution of battery drain problem described here. Sound via external speakers connected by jack into tablet is ok.
I tried fastboot recovery, wipe data and cold start, but still same problem. Even loading removed file back wasn't helpful.
If you anybody has resolved same problem, thank you for advice, how to repair it. I hope this problem has a solution.
Click to expand...
Click to collapse
You install the touch recovery?
Hello. I recently stupidly flashed RC29 on my phone. That's how I got out of there.
How to:
1. You realized that you are on RC29. Do not worry. Let's start the escape.
2. Start phone without sim card. Type on the keyboard <ENTER button>setprop persist.service.adb.enable 1<ENTER button>. Reboot with a SIM card (any, not even a valid one)
3. Connect your phone to PC, download ADB and type command: adb shell am start -a android.intent.action.MAIN -n com.android.launcher/.Launcher
4. Download and install telnet: adb install telnet.apk
4.1 Once at the Home screen, open the keyboard and press the Enter key twice.
4.2 Type telnetd & press Enter. The Contacts screen will come up, just ignore it. There will be no indication that you did it right.
4.3 Open Android Telnet Client; type localhost in the large text box and 23 in the smaller text box on the right.
5. Download the recovery to a memory card and type the command in telnet:
flash_image recovery /sdcard/<your recovery>.img
Just type reboot recovery! Now you have a complete Recovery!
6. WARNING! Install 2.22.19.26I and reboot into recovery 2-3 times. Check the radio version in HBOOT. If version 2.22.19.26I install the HBOOT package. Reboot 2-3 times.
7. It's all. Install roms.
Pay attention! Clockworkmod is not recommended by Cyanogen developers. Use AmonRa. (cwm recovery left in the post in case of emergency)
The story of how I installed CyanogenMod 7:
1. Download CyanogenMod 7 build (DM me if rom not downloading)
2. Install HBOOT 1.33.0013d
3. Install ROM. Download the kernel (ezgb_2636_v1.5.1_S.zip). Install kernel.
4. Just restart and wait. Now you have working system!
Notes:
Restart in recovery - HOME + POWER
Restart in HBOOT - PHOTO + POWER
Reset - CALL + MENU + POWER
Safe mode - hold MENU while booting
# sites (not all)
HTC Dream: Rooting - CyanogenMod Wiki
web.archive.org
Google Code Archive - Long-term storage for Google Code Project Hosting.
code.google.com
Please buy the HTC Sensation
I alone am bored in the forum Sensation
It can be found for 500 rubles
Ulumia said:
Please buy the HTC Sensation
I alone am bored in the forum Sensation
It can be found for 500 rubles
Click to expand...
Click to collapse
sorry, even though it costs 500rub, I spent everything on MiPad 2. I don’t have money for it. Sorry((
PS. and notice. I am now trying to bypass android and make my firmware on android 1.0 for dream.
I quote the article on rooting G1 from Cyanogen Wiki "ClockworkMod is not recommended for Dream due to memory shortage and file corruption."
That's why I think it's better to use Amon_RA's
On my Desire Amon_RA 2.0.1 seems better than CWM 2.5.0.7
Below you can find CyanogenMod themed version of Recovery
By the way the new Telnet version is already on Mod edit: 4pda link removed
@russanandres Thanks a lot for the tutorial, you are a real lifesaver! Exactly what I needed to get a custom rom on my G1.
Although now I'm wondering, is android 2.3 perhaps too much for this phone? I was shocked to see that the actual usable ram out of the 192mb is just 96 and out of them ~30mb free. The device itself seems to be somewhat sluggish on 2.3, the default browser can't even load google without crashing. Although I noticed it's kinda inconsistent, sometimes it speeds up a bit and gets pretty close to 1.6 speed. On the stock 1.6 the phone was fairly snappy for what it could do, although it had terrible idle battery drain. The battery on 2.3 seems better from my first impressions.
For daily driver usage in 2022 what would make most sense, if you have experience with more roms on this device? 2.3 just really seems pointless to me, as the device doesn't have enough power to run properly apps that require android 2.3 as minimum, pretty much all apps that I have installed run on 1.5/1.6+. For example, I have my music library in .opus format, tried foobar2000 and gonemad music player(they supposedly support opus) versions that are 2.3+ and they both straight up crashed on startup, perhaps due to the low ram/lack of instructions.
The speed itself doesn't annoy me as much as the soft reboots that happen from time to time when the phone gets too ''tired'', especially after reboot, for me in about 50% of the time the phone just soft reboots again like a half minute after the first reboot.
Edit: The reboots after the bootup happen if I just don't let it idle for 2 minutes or so white it's reading my sdcard, which has quite a lot of files. I doubt it's from the actual speed of the sdcard as it's a 16gb sandisk ultra, should be sufficient for this phone.
A slight overclock option seems to be present in the performance settings but I won't dare to use it, two days ago I had to do a somewhat professional solder reflow+SoC heat revive on 400C for 30 seconds with a bga soldering station and some flux, that brought it back to life, previously it would work only for about an hour after I heated it with a hairdryer. My point is that the processors in these devices haven't aged too well, in terms of wearing out mine is pretty much done for and who knows when it's gonna die again. I also managed to put a copper heat plate over the soc(with thermal paste) to absorb some of the heat in addition to the metal plating and hopefully to increase the remaining lifespan of the silicon.
Back on the topic, maybe android 2.1/2.2 would be more suitable and still with good features(mostly looking at the quick settings), although I have no idea honestly, I haven't played around with android versions this old to know which ones are lighter and heavier. 2.3 definitely seems heavier than 1.6, that is for sure.
Availability in terms of links is another issue but with research and some use of the web archive I suppose we would be able to find at least one rom per android version.
MaRtYy01 said:
@russanandres Thanks a lot for the tutorial, you are a real lifesaver! Exactly what I needed to get a custom rom on my G1.
Although now I'm wondering, is android 2.3 perhaps too much for this phone? I was shocked to see that the actual usable ram out of the 192mb is just 96 and out of them ~30mb free. The device itself seems to be somewhat sluggish on 2.3, the default browser can't even load google without crashing. Although I noticed it's kinda inconsistent, sometimes it speeds up a bit and gets pretty close to 1.6 speed. On the stock 1.6 the phone was fairly snappy for what it could do, although it had terrible idle battery drain. The battery on 2.3 seems better from my first impressions.
For daily driver usage in 2022 what would make most sense, if you have experience with more roms on this device? 2.3 just really seems pointless to me, as the device doesn't have enough power to run properly apps that require android 2.3 as minimum, pretty much all apps that I have installed run on 1.5/1.6+. For example, I have my music library in .opus format, tried foobar2000 and gonemad music player(they supposedly support opus) versions that are 2.3+ and they both straight up crashed on startup, perhaps due to the low ram/lack of instructions.
The speed itself doesn't annoy me as much as the soft reboots that happen from time to time when the phone gets too ''tired'', especially after reboot, for me in about 50% of the time the phone just soft reboots again like a half minute after the first reboot.
Edit: The reboots after the bootup happen if I just don't let it idle for 2 minutes or so white it's reading my sdcard, which has quite a lot of files. I doubt it's from the actual speed of the sdcard as it's a 16gb sandisk ultra, should be sufficient for this phone.
A slight overclock option seems to be present in the performance settings but I won't dare to use it, two days ago I had to do a somewhat professional solder reflow+SoC heat revive on 400C for 30 seconds with a bga soldering station and some flux, that brought it back to life, previously it would work only for about an hour after I heated it with a hairdryer. My point is that the processors in these devices haven't aged too well, in terms of wearing out mine is pretty much done for and who knows when it's gonna die again. I also managed to put a copper heat plate over the soc(with thermal paste) to absorb some of the heat in addition to the metal plating and hopefully to increase the remaining lifespan of the silicon.
Back on the topic, maybe android 2.1/2.2 would be more suitable and still with good features(mostly looking at the quick settings), although I have no idea honestly, I haven't played around with android versions this old to know which ones are lighter and heavier. 2.3 definitely seems heavier than 1.6, that is for sure.
Availability in terms of links is another issue but with research and some use of the web archive I suppose we would be able to find at least one rom per android version.
Click to expand...
Click to collapse
I think a swap of 256 MB or more will save your G1 on 2.3.7
So if 2.3.7 was slow, then any Android 2.x.x will be slow
Within 2.x.x the system showed more and more performance with each version
Ulumia said:
I think a swap of 256 MB or more will save your G1 on 2.3.7
So if 2.3.7 was slow, then any Android 2.x.x will be slow
Within 2.x.x the system showed more and more performance with each version
Click to expand...
Click to collapse
That's a great idea. I have to look into it, as far as I know I have to make a partition for the swap on the sdcard then enable it on boot with some sort of a script. Is that correct?
Guess that's what I'm gonna be doing today after work, apart from transcoding my music library to mp3 unless the music players decide to work with the swap enabled.
Another thing I wanted to mention, is it normal to have such high idle drain on this phone? Even on cm7 in airplane mode it seems to drain ~4-5% per hour or so. Perhaps my battery calibration is off, I charged it overnight and wiped the battery stats hoping to resolve this issue but it seems to persist. I got a nearly brand new vhbw aftermarket battery which should be about 900-950mah capacity from my measurements, so it's not due to an aging battery.
In comparision I also have a galaxy s1 on cm7.2 with a 12 year old battery on ~70% capacity and that phone lasts like 10 days idle with a sim card.
MaRtYy01 said:
That's a great idea. I have to look into it, as far as I know I have to make a partition for the swap on the sdcard then enable it on boot with some sort of a script. Is that correct?
Guess that's what I'm gonna be doing today after work, apart from transcoding my music library to mp3 unless the music players decide to work with the swap enabled.
Another thing I wanted to mention, is it normal to have such high idle drain on this phone? Even on cm7 in airplane mode it seems to drain ~4-5% per hour or so. Perhaps my battery calibration is off, I charged it overnight and wiped the battery stats hoping to resolve this issue but it seems to persist. I got a nearly brand new vhbw aftermarket battery which should be about 900-950mah capacity from my measurements, so it's not due to an aging battery.
In comparision I also have a galaxy s1 on cm7.2 with a 12 year old battery on ~70% capacity and that phone lasts like 10 days idle with a sim card.
Click to expand...
Click to collapse
Swap partition can be done directly in CWM
You need to find Partion SDcard!!! ALL DATA ON THE SD WILL BE REMOVED!!!
For swap you can use this script
Code:
busybox mkswap /dev/block/mmcblk0p3
busybox swapon /dev/block/mmcblk0p3
echo 100 > /proc/sys/vm/swappiness
And about the battery: on all the HTC smartphones that I had (Sensation XE, Desire A8181, Wildfire S) it has been bad since
So try to replace it.
Ulumia said:
Swap partition can be done directly in CWM
You need to find Partion SDcard!!! ALL DATA ON THE SD WILL BE REMOVED!!!
For swap you can use this script
Code:
busybox mkswap /dev/block/mmcblk0p3
busybox swapon /dev/block/mmcblk0p3
echo 100 > /proc/sys/vm/swappiness
And about the battery: on all the HTC smartphones that I had (Sensation XE, Desire A8181, Wildfire S) it has been bad since
So try to replace it.
Click to expand...
Click to collapse
I see, thanks for the explanation.
I'll hold off from getting a new battery for now, hoping that this battery will get better calibrated. I'm also not certain that the problem is in the battery, if I use the device non-stop from full charge it seems to hold on for about 1h45mins SoT before going flat, which for a device with a tiny battert and a 65nm soc doesn't seem unusual.
But I was also wondering about your experience with the battery, do you also get this high idle drain or is it just my unit?
Lastly, I was wondering if multitouch can be enabled somehow. From my quick search it appears that the G1 screen supports it but its purposely disabled, although some people show it off being enabled.
MaRtYy01 said:
I see, thanks for the explanation.
I'll hold off from getting a new battery for now, hoping that this battery will get better calibrated. I'm also not certain that the problem is in the battery, if I use the device non-stop from full charge it seems to hold on for about 1h45mins SoT before going flat, which for a device with a tiny battert and a 65nm soc doesn't seem unusual.
But I was also wondering about your experience with the battery, do you also get this high idle drain or is it just my unit?
Lastly, I was wondering if multitouch can be enabled somehow. From my quick search it appears that the G1 screen supports it but its purposely disabled, although some people show it off being enabled.
Click to expand...
Click to collapse
The G1 supports multi-touch
It's very strange why it's not in CM7
Xperia X8 has multitouch on the custom ROM but no multitouch on the stock ROM
I found a better opmitized gingerbread rom, that still has a working link.
The system runs much smoother than on cm7.
I have to add, something missed in the tutorial is updating the radio to an even newer version that expands the available ram by 15mb. That is like 50%, considering that the phone has 30mb ram free otherwise.
Link for the radio- here
I directly updated to 2.22.28.25_S via recovery and faced no issues. It is recommended to use superwipe first, with a custom configuration file in the root of the sdcard, that will do a full wipe except for the sdcard. (Source) (Source 2)
In the custom config set:
Wipe_Sd_Secure=no
Wipe_Sd_Ext=no
I received a new sdcard that I will use for the phone, a 64gb Patriot EP series that I got for 5€, these are very fast and dirt cheap. Probably faster than the phone's sdcard reader can candle but that is fine. Point is, I ran the partition sdcard option in the recovery, I noticed it doesn't only ask for swap but it also asks for ext2 partition, what capacity should I select for that? Can't find much info for the ext2 parititions other than they are used for moving apps to the sdcard, although I have no clue how to enable that ability in the android os.
As for my battery issues, I'm certain that the culpit isn't software related but rather a failure of the Qualcomm PM7540 power management ic. The easiest way to test that, which I did, turn off the phone and wait, if the chip is fautly it will drain the battery while it is off, which it does for me(there is nearly no difference in discharge speed between the phone being on and off). I actually remember a year ago when the phone was still just sitting as a decoration on my shelf and just turned on with the hairdryer from time to time, that I had to pull out the battery or it would drain it completely while off, so the power ic failure isn't related to the processor failure at all. I don't know what is my luck, to have 2 dying important chips on one board
Perhaps I will try to remedy it the same way I did with the processor, clean it, place some flux and heat it for 30 secs at 400C. Or maybe a bit lower temperature this time. Technically both chips can be replaced and finding a donor isn't hard(especially for the power management ic, it appears that HTC HD2, Touch HD, Nexus One, Touch Pro, Diamond 2, Desire, SE Xperia X10, X10 Mini, BlackBerry Storm are only part of the devices that use this same power ic. But replacing such chips is extremely difficult and beyond my current abilities, giving it to a professional is not worth it either, the entire phone costs 40-50€(as collector's value) so with the cost of such repair I can instead purchase another G1.
Thank, it work fine
MaRtYy01 said:
I found a better opmitized gingerbread rom, that still has a working link.
The system runs much smoother than on cm7.
I have to add, something missed in the tutorial is updating the radio to an even newer version that expands the available ram by 15mb. That is like 50%, considering that the phone has 30mb ram free otherwise.
Link for the radio- here
I directly updated to 2.22.28.25_S via recovery and faced no issues. It is recommended to use superwipe first, with a custom configuration file in the root of the sdcard, that will do a full wipe except for the sdcard. (Source) (Source 2)
In the custom config set:
Wipe_Sd_Secure=no
Wipe_Sd_Ext=no
Click to expand...
Click to collapse
To flash That radio do i need to install the SPL "1.33.0013d"?
or i can keep using Danger SPL (1.33.2005)?
@Ulumia you know anything about this? is the "RAM Hack" SPL required?
jonnyprogamer said:
To flash That radio do i need to install the SPL "1.33.0013d"?
or i can keep using Danger SPL (1.33.2005)?
Click to expand...
Click to collapse
I don't know anything about Dream because I don't have this device.
I think if you need that file, you know what to do to install it.
jonnyprogamer said:
To flash That radio do i need to install the SPL "1.33.0013d"?
or i can keep using Danger SPL (1.33.2005)?
Click to expand...
Click to collapse
Hey sorry for my late response, I just fired up my G1 which to my surprise(or not) failed to cold boot yet again so I had to give it the hair dryer treatment. Guess the hot air station fix worn out at some point after I stopped using the phone 2 weeks after applying it.
I have 1.33.0013d on mine, which appears to be the recommended version. looking at the description of the rom. I would avoid using another one if possible. Unfortunately I don't remember anything specific, so I can't give you more feedback.
MaRtYy01 said:
Hey sorry for my late response, I just fired up my G1 which to my surprise(or not) failed to cold boot yet again so I had to give it the hair dryer treatment. Guess the hot air station fix worn out at some point after I stopped using the phone 2 weeks after applying it.
I have 1.33.0013d on mine, which appears to be the recommended version. looking at the description of the rom. I would avoid using another one if possible. Unfortunately I don't remember anything specific, so I can't give you more feedback.
Click to expand...
Click to collapse
As i found out you need that SPL to get the extra 15MB of Ram, but be aware that SPL is pretty dangerous, because it doesn't support Fastboot flash (and fastboot boot doesn't work, gets stuck when i try to boot recovery), so if you accidentally brick your phone and do not have a custom recovery it's RIP.