Related
Hi All,
as you may see, I'm new to XDA and even though I'm familiar with linux, I'm new to the whole Android thing. I successfully flashed VillainROM onto my SGA and noticed that I don't like the stock gingerbread launcher. So I tried to get any TouchWiz-Style launcher on my phone:
I tried the "TouchWiz Launcher for Gingerbread [V4]":
http://forum.xda-developers.com/showthread.php?t=1049501
I had to replace the "update-binary", but finally it doesn't match the screen size of the sga and moreover it always crashes when I'm trying to start any app.
I also tried the "Honeycomb" theme:
http://forum.xda-developers.com/showthread.php?t=1104335
Some icons and the general menu style changed, but the launcher didn't change - could that be because I couldn't figure out how to install that "minimal.zip"-file?
I somewhere grabbed "TW4_for_Tab - 182dpi.zip" of which I thought it was made for the sga, but it failed to install.
Besides, I tried some other TouchWiz (4) mods of which I can't find the reference anymore. Some of them didn't install (the well-known "error in /tmp/sideload/package.zip") even with a replaced "update-binary", so that wasn't a success either.
I figured out how to mount the unmodified 2.3.3 Samsung-ROM and could access the TouchWiz30Launcher.apk - but I didn't try to move it to my system folder because it isn't de-odexed - is it a problem to put a non-de-odexed apk (and it's .odex) onto a generally de-odexed phone?
Now I'd like to know if there is any easily usable TouchWiz I could use. Some enhanced version of TouchWiz with additional features would be nice, but I think I would also be satisfied with the unmodded Samsung TouchWiz.
Thanks in advance!
I have tried this with a few different framework & system apks. Im on power_rom evergreen. I tried this with stock evergreen apks, the older power_rom apk, the stock deodexed 407 apks, and even the theme Vantastic glow apks.
The vantastic glow theme flashes on my phone and works great. I dont know why my theme wont work.
Heres the problem, everything changes even the icons, BUT when the phone is not using any data the signal icon changes back to the stock one from that framework & system apk that I used. And when data is used it changes back to the theme icon.
How do I make it so it stays on the theme icon I picked.
In the kitchen I changed to this- "Amend scripting. Old scripting, compatible with old recoveries. Use this if you having problem with flashing (no changes, error 0) or have not HTC Desire phone"
everything else I left alone,
I uploaded both files frame & system
it cooks & flashes fine.
I wiped the dilvak & catch partitions.
WHAT AM I MISSING?????
about phone: I have a aws, with power rom evergreen, kernel=2.6.35.14-gxkernel1.0, baseband= gausb1a140514-aws, android version 2.3.3
Please help..
Attached is the latest theme I made. based off the deodexed 407.
You probably aren't doing anything wrong. I had that problem when I used Kalagas animated (I think that was the name) for icons. It didn't have icons for that particular data state, so the stock ones were used. I fixed it manually in my theme.
Take a look at this theme:
http://www.multiupload.com/1V0DU6AD2S
It's one I made for gingerbread roms. If these are the icons you are talking about, rebuild your theme on UOT and use my framework-res and systemui as your base. The icons are already fixed in it and your changes will overwrite whatever I had in there.
Thanks I will
Sorry just seen this post I will try that
Thank-you
I don't know if they are all like this or not. I only recall having three problem with this pack. I don't remember the exact process i used, but basically i unpacked the mdpi and hdpi folders out of the apk's, found the offending png files and noted their names. I found other icons that could take their place (in this case it was one of the animated icons), copied them and gave them the same name as the offending icons. I overwrote the offending icons with the new ones and everything was good to go.
Sent from my Dell Streak using xda premium
Cooking it right now, I think I used your theme in the past, Thats why I like these icons. Ill post how it turns out.
Works flawlessly
Thank you again
Ryan
Sent from my Dell Streak using XDA App
No problem, glad it worked out for you.
Sent from my Dell Streak using xda premium
Have a cleaner stock ROM that is best suited for your needs
Install the ROM then flash the optional parts that you want
ROM download (backup made on ClockworkMod Recovery v5.0.2.0):
http://www.mediafire.com/?4a2fnfg8j902b74
Optional parts (flashable ZIPs):
Car Home: http://www.mediafire.com/?4f7hsq05rck3mjz
LG Keyboard: http://www.mediafire.com/?clduteothoarey5
LG PC Suite: http://www.mediafire.com/?1lxa9bz707j5and
LG widgets: http://www.mediafire.com/?445vzwsmiogvj30
In case you're interested, toxicro shared his RingNoFade patch for those wanting to test it.
http://forum.xda-developers.com/showpost.php?p=25024287&postcount=34
NOTE: It started as a personal backup that later I decided to share with everybody. It's not a tweaked/themed ROM. It's a stock ROM with an easier start (already rooted, cleaned up and updated), so you're free to use it as a base to all the changes you like (kernels, tweaks, scripts, themes, etc).
Here is the story of this ROM
Or should I say "backup"?
klaudyuxxx pointed out here that the stock ROM V20I from T-Mobile UK doesn't have the problem of wakelocks caused by fast dormancy.
Then toxicro posted the link to download the *.KDZ of this ROM here.
Huge thanks to both of them!
I installed the stock ROM V20I, made some modifications and then made a backup. Here's what I changed:
- Rooted it;
- Removed all the apps that were put by T-Mobile UK;
- Removed all the apps that can be found on Google Play Store (the only ones I didn't remove were Google Search, Superuser and Voice Search);
- Removed the ringtone, the notification and the alarm sounds that were put by T-Mobile UK (they were excessively high).
- Made Car Home, LG Keyboard, LG PC Suite and LG widgets available to download as optional parts (removed them from the ROM).
- Updated Google Play Store to 3.5.16, Google Search to 1.3.3.247963, Superuser to 3.0.7 (with binary 3.0.3.2) and Voice Search to 2.1.4;
Advantages:
- The superb and well known quality of the camera on stock ROMs;
- If you like Lg's keyboard, it's there. If you like LG's widgets, they're there. LG's launcher is also there;
- CPU sleeps just fine (no wakelocks from fast dormancy);
- All the other things you like on the stock ROMs.
Drawbacks:
- T-Mobile UK boot animation with sound in the very beginning (instead of the mute and coloured LG's animation);
- Couldn't remove T-Mobile UK APN and MMS settings from the list, but I was able to select another APN, having no problem with mobile data. But having two MMS settings seems to be a problem for people who sends and receives MMS.
Enjoy!
Does anyone know how to remove the APN and MMS settings on this ROM?
As I said, mobile data has no problems with another APN selected, but two MMS settings seems to be a problem.
I tried a different /system/etc/apns-conf.xml, removing telephony *.db files and rebooting, but I think this ROM simply ignores the entries in that file.
Also took a look at the framework-res.apk, but the apns.xml looks the same as on other ROMs.
Am I missing some trick here? Please help!
Thanks in advance!
Check system/etc/flex and remove flex.db or edit it with some sqlite editor
Keep up the good work...I was waiting for something like this, being to lazy myself to start cooking ROMs.
You are my hero...and Roqu3 - I adopted your kernel over franco's.
Roqu3 said:
Check system/etc/flex and remove flex.db or edit it with some sqlite editor
Click to expand...
Click to collapse
Thanks man!!! Very, very much!
I replaced both files for the ones of brazilian ROM and I have now only the corerct APNs listed and selected.
I even made a ZIP to flash during the installation of this backup with the proper brazilian configuration.
http://dl.dropbox.com/u/47227133/Brazil-signed.zip
In case anyone wants the same, just send me the following three files from a stock ROM of your country.
/system/etc/apns-conf.xml
/system/etc/flex/flex.db
/system/etc/flex/flex.xml
Click to expand...
Click to collapse
The phone won't sleep again if you do this.
Is it mandatory to edit the files?
yuripg1 said:
In case anyone wants the same, just send me the following three files from a stock ROM of your country.
/system/etc/apns-conf.xml
/system/etc/flex/flex.db
/system/etc/flex/flex.xml
Click to expand...
Click to collapse
So are you saying the a new APN cannot be created without d!cking around with the files? I'm asking because with V20G (which is Romanian version) I had no problems creating a Canadian APN.
Please keep us updated on your work...as I said, I've been waiting for something like this since I first read about V2oi and the wakelocks fix.
Ipse_Tase said:
So are you saying the a new APN cannot be created without d!cking around with the files? I'm asking because with V20G (which is Romanian version) I had no problems creating a Canadian APN.
Please keep us updated on your work...as I said, I've been waiting for something like this since I first read about V2oi and the wakelocks fix.
Click to expand...
Click to collapse
No, as I've said, I had no problem setting and selecting another APN (because you can select the right one). It's just that you can't remove the T-Mobile entries from the list, meaning that it may be a problem for MMS only (because you can't select a specific MMS setting like you can do with APNs, and I don't know how smart Android is dealing with two different MMS settings).
By the way, you can change the mentioned files by yourself with just a file manager with permission to write on /system partition, like ES File Explorer (enabling the root functionalities of it). I created a ZIP to myself only to make my life easier when installing the backup, eliminating the entries from T-Mobile without having to use a file manager to do it afterwards.
Long story short: I did use the ROM before without this change, only with additional APN and MMS settings and I had no problem with mobile data. It worked just fine!
yuripg1 said:
In case anyone wants the same, just send me the following three files from a stock ROM of your country.
/system/etc/apns-conf.xml
/system/etc/flex/flex.db
/system/etc/flex/flex.xml
Click to expand...
Click to collapse
These are the files I replaced in my custom rom to give me a T-Mobile 2.3.3 ROM base of the 20G Open Europe KDZ. Fixes a few issues if you do it this way.
techhead0 said:
These are the files I replaced in my custom rom to give me a T-Mobile 2.3.3 ROM base of the 20G Open Europe KDZ. Fixes a few issues if you do it this way.
Click to expand...
Click to collapse
Interesting...when I touched the files (replaced the v20i ones with the V20g files) my phone would not boot. I had to recover the ROM.
How do I get rid of the T-Mobile APNs ...and why are they read-only?
/EDIT I can edit the optable.db (to leave only my provider) but you guys did not mention this file. apns-conf.xml can also be trimmed to one provider...flex.xml is still giving me trouble (still looking for the correct codes in flexinfo) and I kind of see what can be edited in flex.db.
If anyone can help sort this mess out, I'd appreciate it
Scared of having to recover the phone again if I mess with it.
Ipse_Tase said:
Interesting...when I touched the files (replaced the v20i ones with the V20g files) my phone would not boot. I had to recover the ROM.
How do I get rid of the T-Mobile APNs ...and why are they read-only?
/EDIT I can edit the optable.db (to leave only my provider) but as far as flex.db goes, I have no idea what to keep. apns-conf.xml can also be trimmed to one provider...flex.xml is still giving me trouble (still looking for the correct codes).
If anyone can help sort this mess out, I'd appreciate it
Click to expand...
Click to collapse
I installed the flex.* and apns-conf.xml on a clean installation, so I had no problem. I think you had problems because you didn't delete telephony *.db files after changing the files (I suppose you changed the files manually using the phone, so you had data left from previous configuration).
If you can, try the same thing but deleting the *.db files in /data/data/com.android.providers.telephony/databases/
They will be generated again on reboot.
Of course, it's good to have a backup in case it goes wrong again.
By the way, if your flex.xml has FLEX_AUTOPROFILE="true", you will have the problem of fast dormancy (Mine has and I'm suffering from it after disabling mobile data. I suspect that's the case. I'll take a look at the same file of stock T-Mobile setup to see if it's lacking or set as false - which may indicate the way to solve it)
Click to expand...
Click to collapse
I was wrong saying that.
yuripg1 said:
IBy the way, if your flex.xml has FLEX_AUTOPROFILE="true", you will have the problem of fast dormancy (Mine has and I'm suffering from it after disabling mobile data. I suspect that's the case. I'll take a look at the same file of stock T-Mobile setup to see if it's lacking or set as false - which may indicate the way to solve it)
Click to expand...
Click to collapse
WHAT?????? You're killing me...the whole reason I moved to V20i was to get rid of that stupid bug
How did you determine it's related to fast dormancy?
Last night my phone was NOT awake at all (unlike V20G) and drained <0.5% /hr
BTW: it is the telephony.db that has the APN list...I see my APN added there. One would think if I edit that db I should get rid of the T-Mobile entries. But then there is the preferred-apn.xml that points to the db....
Ipse_Tase said:
WHAT?????? You're killing me...the whole reason I moved to V20i was to get rid of that stupid bug
Click to expand...
Click to collapse
You misunderstood me. The stock V20I on post #1 has a flex.xml without this entry, so I think it won't keep your phone awake as it was promised.
It was my fault to push the brazilian files containing that entry (the reason why I experienced FD bug even on this ROM).
Ipse_Tase said:
How did you determine it's related to fast dormancy?
Click to expand...
Click to collapse
For a reason I can't remember confused I searched for FLEX_AUTOPROFILE and found this page. It's from another LG phone.
And comparing both flex.xml from V20B_00 (Brazil unbranded) and V20I_00 (T-Mobile UK), the latter doesn't have the FLEX_AUTOPROFILE declared.
Don't know if any other ROM without this thing would start to behave fine or not (I don't even know if it's needed to edit also the flex.db file)
Ipse_Tase said:
Last night my phone was NOT awake at all (unlike V20G) and drained <0.5% /hr
Click to expand...
Click to collapse
I hope it stay that way!
yuripg1 said:
And comparing both flex.xml from V20B_00 (Brazil unbranded) and V20I_00 (T-Mobile UK), the latter doesn't have the FLEX_AUTOPROFILE declared.
Don't know if any other ROM without this thing would start to behave fine or not (I don't even know if it's needed to edit also the flex.db file)
I hope it stay that way!
Click to expand...
Click to collapse
Thanks for the clarification...for a moment I had shivers down my spine that I'll be in the same boat with wakelocks...
If I have any luck editing telephony.db without crashing, I'll be happy. Not that I have any problems at the moment (just annoying that the T-Mobile APN is R/O).
/EDIT I changed my telephony.db on PC and uploaded it to the phone...got only one APN now, and it's mine. Hope it stays that way.
BTW: deleting the telephony.db database only caused the default one to be re-created...not what we needed.
APN Global Pack (CyanogenMod's APNs - Thanks to them)
Removed - Have to fix behavior on clean installation
APN Brazil Pack (Brazilian V20B_00 APNs)
Removed - Have to fix behavior on clean installation
READ BEFORE INSTALL
If you are flashing one of these packs on the ROM you are currently running, I would recommend you to first delete all content of /data/data/com.android.providers.telephony/detabases/ then reboot to recovery to flash the pack you want.
If you are flashing one of these packs on a clean installation (no /data yet), there's no problem in flashing it.
If you are going to flash the APN Global Pack, containing a huge list, it can take you a fair amount of time to "Reset to default" the APNs list (it took me almost 48 seconds when I tested it), but it works just fine.
However, the best part is that, after applying the APN Global Pack, any apns-conf.xml that you push from another stock ROM to /system/etc/ will be fully understood. So you can have APNs list you want, not forgeting to delete the directory mentioned above before the change.
----------edit----------
Haven't tested if it invokes the problem of fast dormancy (I personally think it's very unlikely, but...)
I'm going to try later
Click to expand...
Click to collapse
Haven't figured out how to make it work without flex.db (or how to create a flex.db containing all needed APNs)
yuripg1 said:
You misunderstood me. The stock V20I on post #1 has a flex.xml without this entry, so I think it won't keep your phone awake as it was promised.
It was my fault to push the brazilian files containing that entry (the reason why I experienced FD bug even on this ROM).
For a reason I can't remember confused I searched for FLEX_AUTOPROFILE and found this page. It's from another LG phone.
And comparing both flex.xml from V20B_00 (Brazil unbranded) and V20I_00 (T-Mobile UK), the latter doesn't have the FLEX_AUTOPROFILE declared.
Don't know if any other ROM without this thing would start to behave fine or not (I don't even know if it's needed to edit also the flex.db file)
I hope it stay that way!
Click to expand...
Click to collapse
Romanian v20h doesnt have that line on flex.xml and that ROM have data tracker-fd problem, so i think it's not that line
Roqu3 said:
Romanian v20h doesnt have that line on flex.xml and that ROM have data tracker-fd problem, so i think it's not that line
Click to expand...
Click to collapse
Does it have a space before the closing /> ? Could be a parsing problem.
It is somehow related to those files, because when I pushed the files from my stock ROM it started to suffer wakelocks caused by fast dormancy.
----------edit----------
Compared the flex.db files and, despite each one having some some different fields, both have the same values related to fast dormancy (10).
yuripg1 said:
Does it have a space before the closing /> ? Could be a parsing problem.
It is somehow related to those files, because when I pushed the files from my stock ROM it started to suffer wakelocks caused by fast dormancy.
----------edit----------
Compared the flex.db files and, despite each one having some some different fields, both have the same values related to fast dormancy (10).
Click to expand...
Click to collapse
yeah but changing that value to 0 or deleting the line had no effect on dtfd-fd bug, you can also delete the whole db file and no effect on that
Happy camper
After a couple of days on V20i with Roq IX (notouch) I can happily reports all's well, good battery life and no FCs.
THANK YOU both yuripg1 and Roqu3 for your work - now the O1 is worth keeping a little longer.
Only issue I have is that Clockworkmod 5.0.2.7 does NOT backup my ext2 partition that I use for apps...I have to back it up manually from Root Explorer.
where can i find the Roq IX kernel? i searched all the forum without luck.. thanks in advance..
answer for Roq kernel
where can i find the Roq IX kernel? i searched all the forum without luck.. thanks in advance..
you can find it here:
mioptimusone.com/foros/viewtopic.php?f=11&t=684
latest is Kernel-X.
Click on [Descargar Kernel-X] and download latest Roq version.
I can't seem to change DPI on any of these new ICS roms..
I have to! I'm not blind!
So it's stuck at 240 dpi.. I've tried DPI changer apps, but on every reboot my phone hangs at boot logo (splash screen, logo.jpg)
Maybe changing DPI on these roms doesn't work?
I feel you mate!
Last I checked It worked on LP6, from LPH onwards it doesnt work!
I dont know the reason but yeah hasnt been working for me too.
Damn this is unbearable! Even blind people can see these huge icons. Someone must know of a fix..
Look here http://forum.xda-developers.com/showpost.php?p=23438841&postcount=11877
edit the build.prop file in system folder and change the value from 240 to 160 or some other value you like.
Done that, same effect..
I done that, except deleting the backup build.prop.bak. I don't see why that'd help so I'll exclude it for now..
Got stuck at splash screen still!
I know on LPH and a few other ICS roms that the build prop has two locations you need to set the LCD Density. If you changed one already, look for the other one as there should be two locations within build prop.
Ok I've confirmed it by installing LPQ, rooting and changing LCD density. As mentioned, there are two 'ro.sf.lcd_density=240 locations in build prop. Change both of them to desired density level. I changed both of mine to 210 and after a reboot, the LCD changed without issue and a lot smaller.
blue265 said:
Ok I've confirmed it by installing LPQ, rooting and changing LCD density. As mentioned, there are two 'ro.sf.lcd_density=240 locations in build prop. Change both of them to desired density level. I changed both of mine to 210 and after a reboot, the LCD changed without issue and a lot smaller.
Click to expand...
Click to collapse
just tried by changing both 'ro.sf.lcd_densities' to 160 with root tools and am stuck with bootloops...
I am a bit of a noob when it came to editting the build.prot but i changed both values and rebooted ,, everything is lots smaller now...
Now to learn how to size the desktop to fit the smaller writing/icons..
This method worked perfectly for me.
I went 192. After some tweaking apex got the desktop to look far less.. Err.. Big.
The email app and dialer are a bit skewed though.
Sent from my GT-I9100 using XDA
tried every other way suggested here and came up with bootloops.
so i did this instead, using 7zip for the PC,
1. opened the cwm flashable custom rom's zip in the PC,
2. opened the build.prop with notepad where i had already set the *.prop to open with notepad
2. changed both locations from 240 to whatever i desired.
3. updated the build.prop back to the zip (it'll prompt when you close the build.prop)
4. Copied back to the SD card
5. and flashed
and voila, no worries, no bootloops
i hope this helps
I tried everything (changing on phone directly, flashing changed boot.prop, changing through the app), but in each case phone will not boot after change. I would really like to know what is the factor influencing this.
Did anyone succeed to change dpi on stock LPQ (rooted with CF and reverted to original kernel)?
vandric said:
I tried everything (changing on phone directly, flashing changed boot.prop, changing through the app), but in each case phone will not boot after change. I would really like to know what is the factor influencing this.
Did anyone succeed to change dpi on stock LPQ (rooted with CF and reverted to original kernel)?
Click to expand...
Click to collapse
I can only get dpi to 182 in criskelo ics rom and litening ics rom all other ics rom dont work.
shanume said:
I can only get dpi to 182 in criskelo ics rom and litening ics rom all other ics rom dont work.
Click to expand...
Click to collapse
Changing DPI on these roms work
ROM - (16 March 2012) TurkbeyRom Ics V1 4.0.3 Blue-Black Themed XXLPQ
Manually set your desired DPI : edit build.prop
078gregory said:
Look here http://forum.xda-developers.com/showpost.php?p=23438841&postcount=11877
Click to expand...
Click to collapse
I tried, but it doen't work. After change the file, it saves successfully, but i cannot find build.prop.bak.
I used root explorer and worked fine for me.a few fred weeks ago
Sent from my GT-I9100 using Tapatalk
i have LPG, tried density modders and manually changing build.prop, every time tje phone wont boot !!!!
I've but the omega rom on my SG2 and would like to know i editing the file to change my resolution will work? Since there seems to be mixed results. On Gingerbread used LCD density changer to get this done and would like to recreate the resolution on my ICS rom now.
thanx guy
[Solved]
I'm running cm 10.1 rc2. I went ahead and changed the MMS.apk because I prefer the black theme or the stock white/grey. I overwrited the current mms.apk located in system/apps/ and changed the permissions to match the other apks in this folder. After I rebooted and noticed the icon for the mms on my homescreen dock was gone. I added it back through the app drawer. I then went ahead and did the same with the contacts.apk after changing the permissions I noticed both the contacts/phone icons were gone from the dock. I rebooted as usual and replaced the missing contact icon.
Now here is the issue the phone icon isn't located in my app drawer. I went to make sure it was still installed and in the system/apps/ and it was. I didn't touch this file at all. I tried to access the dialer through my lockscreen shortcut when I highlighted it nothing happened it just unlocked my phone. I'm unsure how to get my dialer to work and the icon back.
reinstall
I think you can use Root Explorer, go system/app/ then install file Dialer.apk.
deaddead said:
I think you can use Root Explorer, go system/app/ then install file Dialer.apk.
Click to expand...
Click to collapse
I just reverted the contacts.apk to the default that comes with cm 10.1 and it fixed it thanks anyway
RoRo1990 said:
I just reverted the contacts.apk to the default that comes with cm 10.1 and it fixed it thanks anyway
Click to expand...
Click to collapse
Good for you!
Please add [SOLVED] to the title of your post then.