I have installed IceComb's rom on the A500, everything works, it just keeps asking me for a SIM card and other phone related stuff, I understand he developed on the a501, is there a way to disable the Telephony/Phone services since they don't really do anything on my A500 except run my battery down???
EDIT: Just to expand on the magnitude of the problem, Cell Standby is currently using about 10% of my battery at present
You can just add the following lines in your build.prop file, located in the system folder:
ro.carrier=wifi-only
Look all the way at the bottom of the file. You may already see it there, but with a "#" symbol at the beginning. Remove the symbol, save, double check to make sure it saved, then reboot.
Moscow Desire said:
You can just add the following lines in your build.prop file, located in the system folder:
ro.carrier=wifi-only
Look all the way at the bottom of the file. You may already see it there, but with a "#" symbol at the beginning. Remove the symbol, save, double check to make sure it saved, then reboot.
Click to expand...
Click to collapse
in settings under device info the product sku will still list it as 3G, will that be an issue or is it something fixable? didn't see anything related in build.prop
sent from my Acer Iconia A500 beast of a tablet via XDA app
Unfortunately, the rom was built on an a501, so I will guess you'll just have to ignore what is listed in the settings. Doesn't hurt anything.
Basically, the 500 and 501 share identical hardware, with the exception of the 501's internal 3g. So thus, they share the same Honeycomb code.
The mod in the build.prop, usually allows or hides the 3g wireless menu's. In theory, it should also stop the old "cell.standby" usage as well (sometimes I think it still runs, just hidden from the rom's battery report)
There are several methods to stop this for the a500, as the issue is rather old. If you run a 3rd party battery app (after changing the build.prop), and the 3rd party battery app still reports cell standby, then some of the old methods were to "freeze" the telephoney apk, (get a couple errors), reboot, and I believe things will be ok. You should probably get a second opinion here on this, as I run a 501 so I can't freeze my phone apk's.
Moscow Desire said:
Unfortunately, the rom was built on an a501, so I will guess you'll just have to ignore what is listed in the settings. Doesn't hurt anything.
Basically, the 500 and 501 share identical hardware, with the exception of the 501's internal 3g. So thus, they share the same Honeycomb code.
The mod in the build.prop, usually allows or hides the 3g wireless menu's. In theory, it should also stop the old "cell.standby" usage as well (sometimes I think it still runs, just hidden from the rom's battery report)
There are several methods to stop this for the a500, as the issue is rather old. If you run a 3rd party battery app (after changing the build.prop), and the 3rd party battery app still reports cell standby, then some of the old methods were to "freeze" the telephoney apk, (get a couple errors), reboot, and I believe things will be ok. You should probably get a second opinion here on this, as I run a 501 so I can't freeze my phone apk's.
Click to expand...
Click to collapse
good to know, I'll look into it and take care of it
sent from my Acer Iconia A500 beast of a tablet via XDA app
Oh, I wanted to add one more thing. Because of the sharing of the same code, you may occessionally, get the "please insert sim card" For 500 users, ignore this message.
I run a 501, so I have a sim card, and guess what? I occassionally get the same message. Usually, if I don't see my 3g status, I reboot. Everythings fine. And it only happens about once every couple of weeks.
Again, this is because of the close sharing of the same code, and the same hardware.
But when you run "cooked" roms and kernels, we expect these things. A way of life.
Related
I just traded up from an HTC Legend to a Desire Z but unfortunately I have two gripes which are both due to Bell:
1) Preinstalled games and apps. Asphalt 5; Cyberon Voice; GPS Navigator; Kobo; Let's Golf!; Remote PVR; SoundHound; Tunes & Apps; TV & Radio; UNO; Zoompass. 11 apps that I don't need. 11!
2) HTC Locations is missing. Instead they want you to use GPS Navigator which is $10 a month. No thanks!
Anyway my questions are:
1) Is there any way to remove the excess apps without a full root? Ex: with VISIONary + another apps?
2) Is there any way to get HTC Locations back? I see it in some of the system settings, but can't actually launch it.
not too sure about htc places, but to remove those waste of space third party Apps all you need to do is run visionary. once you've done that, load up Root Explorer application and navigate to /system/app/ directory. here you will find those pesky Apps and games, but be careful with what you delete. some of these apk's are critical to htc sense. good luck... let me know how it turns out.
Sent from my HTC Desire Z using Tapatalk
Thanks for the reply but as with my Legend, it's all back after reboot. :-(
Sorry, I currently just experienced the same thing. I think this occurs due to the apk remaining in /data/Dalvik-cache/ files. I would suggest deleting the files corresponding to the .apks you remove and repeat the first process as well.
Sent from my HTC Desire Z
That seemed to have solve the problem. I just rebooted and they did not return. Let me know if it works for you.
Sent from my HTC Desire Z
No go. I deleted from /system/app and /data/dalvik-cache but after reboot, everything is back.
Maybe you did a power down and then turned it on again - since they have quick-boot now (aka sleep mode) it doesn't actually power down or restart the phone, causing it to appear as if the changes stuck when they didn't.
I remember reading that you need a true root to get rid of sys apps on HTC phones, but I also thought I saw something about doing it from command line on a PC somehow.
The practice of preloading uninstallable demos and useless apps is unacceptable.. ugh
have you checked the G2 forums ??
This same Q for this same device has been previously asked and discussed there
They are lightyears away form us
I still think both forums should be merged...
.
gtrab said:
have you checked the G2 forums ??
This same Q for this same device has been previously asked and discussed there
They are lightyears away form us
I still think both forums should be merged...
.
Click to expand...
Click to collapse
Agreed, it's going to be kinda silly have the two sets of forums. On the G2 they've figured out loads of things like this already.
The new HTC phones have a good system protection thing going on.
Basically each time you reboot the phone it checks to see if the contents of /system has been edited (apps added or removed etc etc) then if it has changed it will reflash it back to stock.
Basically you can root using "visionary" and make any changes you want, but as soon as you reboot it will all change back.
That being said Modaco has now come up with a method for removing apps permanently but not adding them.
Lennyuk said:
The new HTC phones have a good system protection thing going on.
Basically each time you reboot the phone it checks to see if the contents of /system has been edited (apps added or removed etc etc) then if it has changed it will reflash it back to stock.
Basically you can root using "visionary" and make any changes you want, but as soon as you reboot it will all change back.
Click to expand...
Click to collapse
That was the original story, but I think it's been debunked now, hasn't it ? It doesn't revert things to normal once you reboot (as proved by Paul's program which can delete built-in apps), but merely prevents you from writing to the on-board storage.
steviewevie said:
That was the original story, but I think it's been debunked now, hasn't it ? It doesn't revert things to normal once you reboot (as proved by Paul's program which can delete built-in apps), but merely prevents you from writing to the on-board storage.
Click to expand...
Click to collapse
not quite
Pauls method basically tricks the phone into thinking the app was legitimately removed therefore it doesn't think there is an issue so won't reflash it.
Lennyuk said:
not quite
Pauls method basically tricks the phone into thinking the app was legitimately removed therefore it doesn't think there is an issue so won't reflash it.
Click to expand...
Click to collapse
I don't think that's right though. Paul's method just fools the phone into deleting the app as part of a supposed update.
There is no check to see if anything's been changed when the phone boots, as far as I can tell from the G2 forums.
steviewevie said:
I don't think that's right though. Paul's method just fools the phone into deleting the app as part of a supposed update.
There is no check to see if anything's been changed when the phone boots, as far as I can tell from the G2 forums.
Click to expand...
Click to collapse
Well it has to check something otherwise it would not know to erase anything you change like Overclock levels etc.....
Lennyuk said:
Well it has to check something otherwise it would not know to erase anything you change like Overclock levels etc.....
Click to expand...
Click to collapse
It doesn't erase those though, it's just that when you "change" them via the tools, it doesn't write to the internal storage, it's just caching the changes in RAM. So it reads the cache and uses the changes. When you reboot, of course the cache is flushed, so the changes disappear.
They used to think there was a "revert to stock on reboot" thing on the G2 too, a few weeks back. No disrespect, but this is an example of how out of date "we" are here on the DZ forums, compared to the G2 which has been out a few weeks now.
steviewevie said:
It doesn't erase those though, it's just that when you "change" them via the tools, it doesn't write to the internal storage, it's just caching the changes in RAM. So it reads the cache and uses the changes. When you reboot, of course the cache is flushed, so the changes disappear.
They used to think there was a "revert to stock on reboot" thing on the G2 too, a few weeks back. No disrespect, but this is an example of how out of date "we" are here on the DZ forums, compared to the G2 which has been out a few weeks now.
Click to expand...
Click to collapse
hmm, I am still not convinced caching would hold it without significantly lowering perfomance, plus why the very very long boot times when you do make a change and then reboot?
Lennyuk said:
hmm, I am still not convinced caching would hold it without significantly lowering perfomance, plus why the very very long boot times when you do make a change and then reboot?
Click to expand...
Click to collapse
Try asking about this on the G2 forum if you like ...
On the caching thing, there's more in the Wiki - http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Intro . Specifically :
For anyone interested-- despite what the blogs are saying-- THERE IS NO "ROOTKIT" and THERE IS NO "RESTORE ON REBOOT". What *is* happening is that Android thinks it's writing to the eMMC (memory card), but it is not. What you are seeing as a successful write is just the cache
Click to expand...
Click to collapse
And here's the proof - http://pastebin.com/cm75Z9UA
Lennyuk said:
hmm, I am still not convinced caching would hold it without significantly lowering perfomance, plus why the very very long boot times when you do make a change and then reboot?
Click to expand...
Click to collapse
Because that's a REAL reboot
The fabulous fake "5 seconds boot time" is just a hibernation trick, a feature called "HTC Fast Boot" (= power off hybernates instead of really "powering off").
Check the G2 forums, this has been confirmed by HTC.
When you press "power off", the phone DOESN'T power off, it just "hibernates", then when you power the phone on again, you see the "amazing 5 seconds boot up"
If you want REAL power off you have to REMOVE THE BATTERY
.
gtrab said:
Because that's a REAL reboot
The fabulous fake "5 seconds boot time" is just a hibernation trick, a feature called "HTC Fast Boot" (= power off hybernates instead of really "powering off").
Check the G2 forums, this has been confirmed by HTC.
When you press "power off", the phone DOESN'T power off, it just "hibernates", then when you power the phone on again, you see the "amazing 5 seconds boot up"
If you want REAL power off you have to REMOVE THE BATTERY
.
Click to expand...
Click to collapse
So how long are these very very long boot times??? Have had android 2.1 take about 1 minute to load up normally on a 600mhz processor, so surely 2.2 wouldn't take much longer than this?! ???
Anyway, back to the question (in a way)...
Is TomTom actually available as standard on the Desire Z? As I'm sure I read somewhere that it was Route66 or some other software with a similar name, not TomTom...
gtrab said:
Because that's a REAL reboot
The fabulous fake "5 seconds boot time" is just a hibernation trick, a feature called "HTC Fast Boot" (= power off hybernates instead of really "powering off").
Check the G2 forums, this has been confirmed by HTC.
When you press "power off", the phone DOESN'T power off, it just "hibernates", then when you power the phone on again, you see the "amazing 5 seconds boot up"
If you want REAL power off you have to REMOVE THE BATTERY
.
Click to expand...
Click to collapse
yes thanks but I knew this already, I knew this from the moment I heard of the new "fast boot" its the same as blackberry have been using for years
I don't have data to spare to test things myself until next month, and have a fairly stable PPP setup anyway.
But I figured if someone wants to experiment the following might be worth a shot.
What I've done is attach a zip with 4 sample options files for pppd that attempt to address issues I've seen with pppd. Specifically the crash with memory issues due to compression, and pppd dying when disconnected and needing to be restarted (eg by LeTama's v0.3 wrapper). If you want to try these out I would suggest using them in conjunction with his wrapper as I'm unsure how other versions may work: http://forum.xda-developers.com/showthread.php?t=824413
The 4 versions for testing are as follows:
option1
- Makes the buffer size used for compression as small as possible.
- Tries to make the connection persistant.
option2
- Disables compression.
- Tries to make the connection persistant.
option3
- Makes the buffer size used for compression as small as possible.
option4
- Disables compression.
To use them they will need to be copied to your /etc/ppp/ folder as "options" and you'll need to ensure it's readable.
If you don't know what I mean I suggest you don't bother trying this.
If you do know what you're doing then you can try experimenting with the different options and see if they make things better/worse.
option3 is probably the safest, option4 may be needed if things still crash due to memory issues with option3.
option1 would be the ideal, but I can't guarantee the persist option is possible.
If option1 or option3 prove to improve things and prevent the crash, then the values used could be slowly increased (to a max of 15) to see if crashes start happening again.
Anyway, just something else the more adventurous and tech savvy users out there with PPP issues can try.
Can I copy these over via ADB push while Android is running, or do I need to put them in the Android root folder so they'll get copied into place on reboot?
Well with Option 1 the data connections drops almost instantly, Option 2 is doing without drops for 10 min now, but it is too early to say if it's an improvement over the old options.
Does compression influence the connection speed? Option 2 works as fast as possible on HSDPA... Option 2 dropped after about 15 minutes when downloading from the market, but downloading from the market was much faster than before.
Should we be copying it as "options" with no file extension or "options.smd"?
Probably as options.smd, that's what I did and it seemed to have some effect...
Now testing option3, will mess with it for the rest of the day and see what happens. At first glance, it seems a bit slow, but that's anecdotal at best.
MAsterokki said:
Well with Option 1 the data connections drops almost instantly, Option 2 is doing without drops for 10 min now, but it is too early to say if it's an improvement over the old options.
Does compression influence the connection speed? Option 2 works as fast as possible on HSDPA... Option 2 dropped after about 15 minutes when downloading from the market, but downloading from the market was much faster than before.
Click to expand...
Click to collapse
Seems like I drew my conclusion from Option 1 too early, after a reboot it works great, I have been downloading MDJ newest rom for 10 min now which resulted 20% of 170mb (from multiupload). No drops untill now, definitely a huge improvement over the old options.smd. Thanks alot Hastarin!
question when i get to the ppp file in i see options.smd and a options.smd1 do i just add this new option to it or delete the old ones and replace with this one?
imphoking said:
question when i get to the ppp file in i see options.smd and a options.smd1 do i just add this new option to it or delete the old ones and replace with this one?
Click to expand...
Click to collapse
I would backup your original files first, although the orig options.smd is probably blank anyhow.
Replace the options.smd with the renamed options from hastarin.
Hastarin, do you happen to know the default options when we were using the default "blank" options.smd? Does it use compression etc. Thanks for your efforts!
noellenchris said:
Hastarin, do you happen to know the default options when we were using the default "blank" options.smd? Does it use compression etc. Thanks for your efforts!
Click to expand...
Click to collapse
The wrapper supplies nodetach, debug and something I can't recall atm (should be in IRC logs).
Compression will be used by pppd by default but I couldn't find information on what size buffer it uses by default.
Google pppd man page for more information.
You are right about options.smd being the safest option. Using options file may affect other things that use pppd if there are any.
Sent from my HTC HD2
Option1 seems to be working fine for me right now. I will report more in a few hours while I'm out.
Hey just wanted to say that I am checking out these options also. So far using option1 and I haven't had any data drops or freezes. Haven't been able to test it extensively yet but will over the next few hours.
With option 1 can you make sure you can switch between WiFi and data and back again? And that you can turn mobile data off and on? And perhaps airplane mode and back to be thorough?
Thanks
Sent from my HTC HD2
It seems after some time options.smd gets reset to blank by itself? Anyone noticed?
Sent from my HTC HD2 using XDA App
memin1857 said:
It seems after some time options.smd gets reset to blank by itself? Anyone noticed?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
I haven't rebooted yet, but mine is still there and not blank. I will try to toggle wifi etc next. Otherwise it's still rolling well, no disconnects yet or hangs.
memin1857 said:
It seems after some time options.smd gets reset to blank by itself? Anyone noticed?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
I set mine to read only in case this actually happens lol.
noellenchris said:
I haven't rebooted yet, but mine is still there and not blank. I will try to toggle wifi etc next. Otherwise it's still rolling well, no disconnects yet or hangs.
Click to expand...
Click to collapse
Lucky.. I still can't get mine to last longer than 5 seconds.
Ok with option1 I started experiencing some data freeze again. It happened while downloading a large file and then again when I switched to wifi tethering. The freeze actually freezes my entire system and then my phone runs really really slow. It may be the build that I am using so I am going to try an older build that did not seem to have this problem. I will run option1 for a while again and then try the others.
Option 1 is no good - I think the persist option keeps 3g "connected" even though I'm getting timeouts, instead of dropping and reestablishing data connection.
Will test the other options once I upgrade to 0.4 ril wrapper and S4 mdeejay kernel.
EDIT: oh yeah, I noticed though the default options.smd is blank, when pppd is running it creates a options1.smd in /etc/ and it has the words "user dummy" in it?
Its stops the tablet from searching for a cell phone signal that eats up some of the battery.
Acer Iconia Phone Disabler (strange name)
zanetti2000 said:
Its stops the tablet from searching for a cell phone signal that eats up some of the battery.
Acer Iconia Phone Disabler (strange name)
Click to expand...
Click to collapse
Please provide a link when posting info in future for reference
here's the reference :
http://forum.xda-developers.com/showthread.php?p=14053121
I went ahead and downloaded the app..but becuase of differing opinions on the feasibility and safety in removing or changing those 2 .apk files...im a bit reluctant to actually use it. Anyone have any wordds of wisdom one way or another?
Chlballi
It's a good app but i worry cannot update to 3.1 after root it. So wait for Honeycomb 3.1. Thanks for sharing
is thera any other way to disable cell stanby? not buying this app?
i've deleted phone.apk and telephonyprovider.apk through system apps remover but cell standby is still draining my battery
Glebaka said:
is thera any other way to disable cell stanby? now buying this app?
Click to expand...
Click to collapse
Well, I did the same thing - downloaded then changed my mind and uninstalled. It's nothing more than renaming the telephony.provider and phone apk's so why pay - you need to be rooted to use it anyway so why not just rename them?
BUT - there's a big issue if you need to do a hard reset and also, you will not be able to get the update because as we know, the updating procedure checks for completeness of all the apps - if any are missing, it won't install.
I'm waiting for Acer to fix this (actually it's a Google problem since many other tablets have this issue).
Convenience, maybe?
It's quick, don't have to mess with remounting /system to read/write. And when it's time to take that update, just run it again and click "Enable" and they are back to normal. After an update, you can disable them again, if they haven't fixed the battery drain issue.
docfreed said:
Well, I did the same thing - downloaded then changed my mind and uninstalled. It's nothing more than renaming the telephony.provider and phone apk's so why pay - you need to be rooted to use it anyway so why not just rename them?
BUT - there's a big issue if you need to do a hard reset and also, you will not be able to get the update because as we know, the updating procedure checks for completeness of all the apps - if any are missing, it won't install.
I'm waiting for Acer to fix this (actually it's a Google problem since many other tablets have this issue).
Click to expand...
Click to collapse
I have a way that seems to work for me... I downloaded power widget, made 2g/3g toggle, clicked it, then unchecked everything. (Doesn't delete or rename anything) and my tablet no longer wastes battery on cell standby
First off, I cannot take credit for finding this, I was referred to a bug report thread on the Google Android site by XDA user aweaver33, who I thank VERY much for pointing me on the right direction.
So, several of us have had this issue with various custom kernels, where after typically 24-48 hours, the phone would slow to a crawl. If you were to open an app like System Panel, you would see that the CPU load was pegged at 95%+, and speed would be maxed out. You would also see that the process using all the CPU is Android System.
The problem has to do with the file "time_in_state", which literally keeps track of how much time the CPU spends at any given speed in MHz. There is a limit to the size this file is supposed to reach, 256 bytes. Once it exceeds this size, the next time Android tries to access it, it flips out and gets stuck trying, and pegs the CPU. A lot of devs and users blamed SetCPU, and it is true that SetCPU does have an EFFECT on this issue, it does NOT cause it, and indeed the issue can occur whether SetCPU is installed or not.
The issue is brought on by custom kernels that add additional frequency steps for the CPU to choose from, which causes that log file to grow. Which is why older or stock kernels will not cause this. Some ROMS incorporate a workaround so you may not have this issue.
Anyways, the issue is explained better in the link aweaver33 gave me. I will link to the original thread I posted with the conversation we had and the link he gave. I can confirm that, using the info he gave me, the issue has been fixed. I am currently just over 120 hours of uptime with no problems.
Here is the link: http://forum.xda-developers.com/showthread.php?t=1082363&highlight=stock+kernel+gpu+
EDIT: attached the script files for those who want them. You can drop one or the other (NOT BOTH) in /etc/init.d if your rom has this folder already (creating the folder and adding it won't work), or you can download Autostart (root) from the market for free, and drop the file in /data/opt (create the opt folder). This difference between the two is one runs only once at boot, the other runs every five minutes. If you use SetCPU, you need the one that runs every five mins, as every time you open SetCPU it resets permissions on the time_in_state file.
flashable zip? not everyone is comfortable with code and scripts
If I knew how, I would. I wasn't even comfortable with it. But I was so tired of the locking up, I was willing to try anything (after a Nandroid of course). I'm not sure you *could* do this in a flashable zip. I can post the script I'm using. It only runs once after reboot, unlike aweaver's, which runs every five mins (good if you're using SetCPU, as opening SetCPU resets the permissions of the time in state file).
This script should work if dropped into /etc/init.d. *If* your ROM has that folder by default. Mine does not, so I had to download a free app from the market called Autostart which is free and very small. For that app you create a folder in /data/ and drop the script in there.
Sorry guys but I'm no dev so this is the best I can do, maybe someone else can make it flashable?
would it also be fixed by simply deleteing the log file as well rather than setting it to unreadable
It can't be deleted. System instantly replaces it.
bast525 said:
It can't be deleted. System instantly replaces it.
Click to expand...
Click to collapse
:/ i suppose when it is replaced it would be with a fresh one deleting would fix it for 24-48 hours till it got filled again humm i wonder if a script could be auto executed every 12 hours to delete it rather than just make it unreadable.
Do you know if it is a problem in gingerbread as well?
mirrin said:
:/ i suppose when it is replaced it would be with a fresh one deleting would fix it for 24-48 hours till it got filled again humm i wonder if a script could be auto executed every 12 hours to delete it rather than just make it unreadable.
Click to expand...
Click to collapse
I don't think you can delete it. I can't figure out how to.
mirrin said:
Do you know if it is a problem in gingerbread as well?
Click to expand...
Click to collapse
Issue 9733 is still listed as New, so either Google hasn't fixed it in Gingerbread or they just don't bother statusing their bug reports.
Why do you feel the need to delete it? If you are trying to delete it, you are likely using Root Explorer. Why not just use that to change the permissions of the file? Tap and hold, select permissions, and unchecked all permissions except for the top left one. This will stop the bug, but the permissions will be reset after a reboot, or after opening SetCPU.
I imagine that deleting the file might actually cause FC's or may cause the same bug but I dunno since it wont delete.
dyetheskin said:
flashable zip? not everyone is comfortable with code and scripts
Click to expand...
Click to collapse
I've never created a flashable zip before, but I'd be willing to look into it if the demand is really there. The problem I see is that I'd have to make certain assumptions about how everybody's ROMs are configured. It looks like the most portable approach would be to append a line to the end of /bootcomplete.inc.rc. Do people really find it easier to boot into recovery and flash a zip than to add one line to a file themselves? Personally, I'm always hesitant to flash a zip other than a full ROM because I'd be uncertain how it interacts with other changes I've made to my system.
Inc is
not bad
But. 48hours?
Sent overrow from my Optimized Inc using XDA App
Hi can't post yet in development threads.
But I'd like to know why there is an issue for ICS either not seeing or mis-reporting an empty sdcard. Even though it shows a 'used' value.
I've searched about and read a few Q's about the issue and even claims of apparent fixes.
But I can't find any, but I can't figure why the problem in the first place.
I just 'zed's an empty card.
there is no problem with the sd card it was located in emmc.
go get io file manager or es file manager and go to directory /mnt/emmc.
cheers
Format
Is the card formated? Could be the problem.
Yes it is half full (16gb) and used daily Before flashing.
So is there a reason the card is. 'hidden' in eec?
and how do apps know where it is assuming I can remember as well.
I also don't see the root in stock FM, I wonder what its doing when it does a media scan.
So anyway how do I make it normal?
Many thanks
Also got a say luving this ice (slim)
But a couple of issues with wifi.
First someone like me might not know on the settings page, you have the regular switch, but to configure and choose a network, press the txt liable to the same switch.
Not exactly obvious
And 2nd wifi absolutely eats battery. maybe there's a way to reduce power etc?
cleverdicky said:
Also got a say luving this ice (slim)
And 2nd wifi absolutely eats battery. maybe there's a way to reduce power etc?
Click to expand...
Click to collapse
Change the Modem File. Different Modemfiles have different battery drain´s.
Also you can change the Kernel, the is a relationship ( right Word ?) between Modem & Kernel.
Thanks, yes I agree but was a struggle to get this working as it was for UK. (Do all devs live in the us or Poland)
I use the jpy modem & busy box but even that was taxing for my poor brain.
One other thing I found using ics is appalling sms.
Terrible button layout that doesn't show contacts and a tiny type area again A bad point for android anyway.
But if you go through phone button to see contacts, if you select a mobile no and start typing, it changes to home number.
Also if your not carefull, it just dials and hard to cancel.
Annoying and quite a disappointment .
I'm just going to see if go SMS does a better job.
Shame to have to though.