Hey everyone, right now I am working on a rom for the D2 and I had it all going great and was just about to release it to the community until I came across a pretty major bug with the text color. I fixed that bug with the help of another developer but after fixing the bug I came across a string of other bugs which weren't there before.
Most of the bugs were easily fixable except for a few and one of them I couldn't fix by myself.
The bug is that whenever I am in the settings.apk I cannot access most of the options because it force closes constantly which also results in reboots when I am trying to turn on wifi, gps, etc. It is usable but annoyingly slow. My idea was to just replace the settings.apk and settingsprovider.apk with new/stock ones and I am doing that right now and am going to flash that rom really soon but I am not sure if that will work, any ideas?
Also my logcat looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and just keeps updating the status of the phone position multiple times a second. When I logcat other roms they never constantly update the screen position and I was thinking that this probably sucks the battery dry , does anyone know how to make it update the screen position less often?
Finally I must've misplaced some file in the framework-res.apk and now whenever I try to change the volume of either the ringer or some media the bar that shows how loud it is goes all crazy and turns into a spinner *shown bellow*.
Any help with any of these problems would be great.
Thanks a lot,
ljbaumer
p.s. the rom should be released in a BETA in probably a week once these bugs are fixed and I make a few more changes to the look and speed.
Cool... is this rom based on anouther??? Is it blur or non blur??? Good luck if you need any help hit me up
Sent from my DROIDX using Tapatalk
It's based off of gummyjar but with a lot of changes and tons of stuff from other roms.
It is completely non-blur.
I might include a few pieces of MIUI in it (because I am going to do my best to try and port MIUI over to the D2 from the Droid after this rom).
ljbaumer said:
It's based off of gummyjar but with a lot of changes and tons of stuff from other roms.
It is completely non-blur.
I might include a few pieces of MIUI in it (because I am going to do my best to try and port MIUI over to the D2 from the Droid after this rom).
Click to expand...
Click to collapse
Cool just make sure you give credit to everyones app etc... that you use
If you are really interested in doing this right, I can help you setup your build envirement so you can build your own apps... this is something I have offered since releasing GummyJAR but to date only droid2169 has taken me up on it....
Sent from my DROIDX using Tapatalk
Yeah I definitely will credit everyone!
(I think I PMed you a while back about building my rom from gummyjar but I may have not...)
I hate people who steal work from other people without writing credits.
It would be great if you could help me set up an environment to build apps.
thanks,
ljbaumer
The sound progress issue is linked to progress_horizontal.xml in framework-res/res/drawable. Make sure you have that file edited correctly.
sonnysekhon said:
The sound progress issue is linked to progress_horizontal.xml in framework-res/res/drawable. Make sure you have that file edited correctly.
Click to expand...
Click to collapse
Thanks,
I didn't do any editing to that file.... Should i just replace it with a stock progress_horizontal.xml from a fresh framework-res.apk and see if that fixes it?
ljbaumer said:
Thanks,
I didn't do any editing to that file.... Should i just replace it with a stock progress_horizontal.xml from a fresh framework-res.apk and see if that fixes it?
Click to expand...
Click to collapse
Yes, you can try that. Or use the one from my theme to get the white color.
sonnysekhon said:
Yes, you can try that. Or use the one from my theme to get the white color.
Click to expand...
Click to collapse
thanks, I 'bricked' my phone so I had to SBF and now I am stock again, so I am just rooting over. I'll use the file from your theme so I can get the white one (which looks tight) and then I think I am just going to resync with gummyjar and start over because I just got a new computer for Christmas and I'll just save my system/app and framework-res.apk so that I won't have to do that much editing over again.
thanks,
ljbaumer
Related
Is there a way to get this on the hero?
I like the way it is laid out over the hero phone / dialer.
screen shot perhaps?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i would like that dialer as well...
+1
Would love a larger dialer
looks good, can someone port this?
Been seeing alot of new Roms that have the AOSP Dialer in it and Aloysius 2.0.2 and another one have a version of the dialer?
It would be great it we could just ditch the HTC one and use this one, I am not that good but will look at it this weekend and see what happens. But I am guessing it will not be as easy as pulling one file over to the hero..
chaos67731 said:
It would be great it we could just ditch the HTC one and use this one, I am not that good but will look at it this weekend and see what happens. But I am guessing it will not be as easy as pulling one file over to the hero..
Click to expand...
Click to collapse
I was actually going to create a new dialer based on that Vanilla one. But if you can send me the Droid Phone.apk, I'll see what I can do on porting it.
pseudoremora said:
I was actually going to create a new dialer based on that Vanilla one. But if you can send me the Droid Phone.apk, I'll see what I can do on porting it.
Click to expand...
Click to collapse
someone get this man the dialer.apk
Here is a link to what I think is the ROM I used on my friends Droid. But not to sure. But it is a full Droid ROM.
chaos67731.com/Droid-Rom/ESE53 DesireRemix V.0.1.1.zip
it just looks like a skin for AOSP...
This should be another ROM For The Droid,
chaos67731.com/Droid-Rom/ESimplyStunning-v201.zip
venumx said:
it just looks like a skin for AOSP...
Click to expand...
Click to collapse
I was guessing it is/was a ROM. I can try to find another one latter.
But I know it is one of the two that I flashed over to my friend Rroid, but that was about a month ago so I am not to sure witch it was.
i asked the same question a few weeks back and was told that you can install the aosp dialer but when u make a call or receive a call it reverts back to the sence htc dialer
Just got home... downloaded stuff from the links. I'll be looking into it and see if I can get any successful results. If nothing else, I can always try and skin the phone to have somewhat of the same functionality.
Yeah, if someone can figure this out, that would be awesome. I'm not a big fan of the HTC Sense one as it's really slow due to all the background contact search going on..
I don't know if you guys know.. but there was a AOSP Dialer developed by another member on the forums called NubDialer (Wysie). You can find it in the market by searching NumDial. It's almost identical to the Nexus One/Droid dialer. You guys can have a look at that, while I work on this.
By the way, I've downloaded NubDial, and yes... it does work on our phones. Though, I think the Voicemail button (#1) isn't functioning correctly; I can fix that though.
More info HERE
ill pay $5 for the first dev to get this ported. but id like the dialer buttons to be a dark grey if possible.
I think we should also see if we can find a way to be able to delete the HTC dialer off our phones. Right now, the only way to keep the ability to dial (on any dialer) is to keep the HTC dialer.
OK so you're using adfree or a custom hosts file to block ads.
Great but, now in place of the ads theres an upside down green android and a bunch of crap about the webpage being unavailable!
This isn't always true, but an example is youtube.com
Try going on there with your phone and there should be two or more spots where the frame tries to lead you to a hosts banned location.
This results in a bunch of webpage unavailable errors.
So what I did was I edited the html and optimized the android guy (transparent background) so it only shows him, but no text!
With this update when your browser tries to access an ad that can't be loaded you'll get this.
Heres an example of this on youtube (much more elegant huh?).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Visiting an actual page that doesn't work will give you this.
I think the best part is that this is also true of ads within apps.
Instead of a never-ending load symbol or an actual ad you just get a cute upside down android guy. See below.
Just flash this over your ROM.
Tested only with DC 3.2.3, but should work with most/all roms.
I am not responsible if this causes your phone to explode etcetera.
Note: Replaces framework-res, could kill themes..
Good work! good work! Thank you!
You should add a readme.txt file explaining installation though
Nice idea. I am trying this out most definitely. Much cleaner.
Edit: Hmm, noticed that this replaces framework-res.apk. This will change themes installed on the phone. Maybe a MetaMorph for this would be a better idea?
Good point, hadn't considered that. I have never used metamorph, ill look into it though..
topdnbass said:
Good point, hadn't considered that. I have never used metamorph, ill look into it though..
Click to expand...
Click to collapse
It would play nice with the plethora of customized themes out now.
I simply just looked at what you changed, pulled my framework-res.apk, put your files in, and pushed the framework-res.apk back in. Worked like a charm.
Sorry for the double post, but xda app won't let me edit in attachments. Confirmed, and it is aesthetically awesome. Thanks again.
*Currently Mobile*
Wow man I hope you can get this to work with themes. I would hate to break my custom theme on my evo.
I flashed this over DC 3.2.3 and it didn't work. Did I miss something?
Never mind. I'm a dumb-ass.
I never get the annoying android cannot find image, I always just get a spinning wheel where the ad should be.
If you can't get it working with your theme, link me to it and ill put up a working version.
itmustbejj said:
I never get the annoying android cannot find image, I always just get a spinning wheel where the ad should be.
Click to expand...
Click to collapse
This will replace that with the static green Android image.
I prefer it because the loading sign is distracting and misleading.
Try YouTube. It always gives me those errors.
Also note that this isn't going to work with every ad and its not supposed to.
Only with those which try to access a blocked url
Will this work with CM6?
custom ROM not an option here
niiice
how can this be had on either
Droid X: froyo OTA
or
Droid X: gingerbread .602 OTA
is there perhaps a loopback proxy app that I can run analogous to the windoze application: eDexter (used with hosts adblocking)
proxomitron for android?
eDexter for android?
itmustbejj said:
I never get the annoying android cannot find image, I always just get a spinning wheel where the ad should be.
Click to expand...
Click to collapse
Same here. And it looks like from your screenshots, flash is blocked. I don't get that same screenshot, even on the latest adfree with latest hosts update. My loading of youtube shows everything.
Hi,
Since I've updated to 2.1 that I've been noticing that user interfaces with tabs are not looking so good as they used to.
I don't know if this is just me or everyone using 2.1 ROMs... I want to understand if this is a problem in my ROM (and all other 2.1 ROMs I've tested) or if it's a general problem and if anyone knows of a fix cause they look bad compared to the previous ones.
Here's a screenshot from Cupcake 1.5:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here's a screenshot from Eclair 2.1:
You can clearly see that there's a problem in the separator between the tabs and the rest of the content and also on the tabs labels text color, which is barely readable...
No one else notices this?
I noticed, but I didn't know if they looked better on the old Sense...
But yeah, again, except for the fact that we now have the 2.1 backend, the update really sucked. I don't like the glossy icons with lense flair effect (uagh, that ugly blue guitar player icon in the music player), random crashes (well, sense restarts to be accurate), UI glitches when switching between landscape and portrait mode.
You'd think with over half a year's time and countless delays they should be able to give us some proper software, that at least on the surface looks good.
Have you ever checked adb logcat while sense is running? Oh the plethora of error messages coming form that software...
Sense sucks, really annoying that we had to wait so long for the official 2.1 rom when all I wanted was a clean 2.1 without any of htc's junk. CMH rules period
This really bothered me and I'm the process of fixing the framework graphics...
I'm really close to fixing the graphics, so far so good and everything's working. I'm just not sure where can I change the color of the text labels in the tabs... Any ideas?
EDIT: Nevermind, just found it, I'll post a topic with the a patch in the dev section when I'm finished with this. I'll just a little more thing to try to fix before that...
I know that you have found a patch, but is there a chance you are using basic-Sense ROMs? If you use a full-Sense ROM you should not have this problem...?
Andyt95 said:
I know that you have found a patch, but is there a chance you are using basic-Sense ROMs? If you use a full-Sense ROM you should not have this problem...?
Click to expand...
Click to collapse
I have no idea what you mean by basic/full Sense ROMs...
I'm using my own cooked ROM based on the official RUU and I didn't do any changes for this to happen. But just to make sure, I installed a clean ROM without any changes but root and the problem was still there.
The things I changed for this to look better cannot happen on their own, so I don't understand how can this be a problem for some and not everyone (if that's indeed the case).
Well, I am NOT releasing the theme until I get approval from B-reezy and the original MattedBlues theme creator, but I am stumbling often with what I've worked on already.
I will supply screenshots but I literally changed all of the framework-res.apk files, so I need help finding which ones to restore.
Now, what looks good.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now onto the problems....
After pressing menu, I got this problem.
Anyone know which images they are so I can restore???
Then the next problem, with pop ups...I turned on WiFi (yes, my WiFi network is named after my dog...haha). Then finally text boxes have problems. Teehee
Please please let me know the images I need to work on, the sooner I fix these, the sooner I can release.
Looks great! Can't wait to see finished project! I see you got the color figured out !
*eek*! Is that a matted reds! Yayyyyy
Sent from my SPH-D700 using XDA Premium App
The problems I see right off the bat stem from corrupt/incomplete .9pngs.
theimpaler747 said:
The problems I see right off the bat stem from corrupt/incomplete .9pngs.
Click to expand...
Click to collapse
That's what I jyst told him in pm
Sent from my SPH-D700 using Tapatalk
Personally, I'd make smaller signal bars, add the quicksettings in the notication bar, and don't make the menu in the launcher (that says "add, "settings", "wallpaper") have a transparent background; it's too hard to see.
Otherwise, I really like the idea so far. Maybe get rid of the AM/PM in the notification bar too
Edit: Oh, I see you're having problems with the transparent background thing and quicksettings; Nevermind about that!
But I'd recommend still making the signal bars smaller/getting rid of the AM/PM That's one of the view reasons I don't like mattedblues
acer1096xxx said:
Personally, I'd make smaller signal bars, add the quicksettings in the notication bar, and don't make the menu in the launcher (that says "add, "settings", "wallpaper") have a transparent background; it's too hard to see.
Otherwise, I really like the idea so far. Maybe get rid of the AM/PM in the notification bar too
Edit: Oh, I see you're having problems with the transparent background thing and quicksettings; Nevermind about that!
But I'd recommend still making the signal bars smaller/getting rid of the AM/PM That's one of the view reasons I don't like mattedblues
Click to expand...
Click to collapse
I'll chat with B-reezy later this week and he'll help me out with removing the AM/PM in the status bar. This is built completely off the ported MattedBlues and since I'm new to theming, it may be a bit before this is added to the themes board. Otherwise, I'd say I'm very excited to get this done and hopefully I'll move onto ROMs when I have the experience necessary.
Overstew said:
I'll chat with B-reezy later this week and he'll help me out with removing the AM/PM in the status bar. This is built completely off the ported MattedBlues and since I'm new to theming, it may be a bit before this is added to the themes board. Otherwise, I'd say I'm very excited to get this done and hopefully I'll move onto ROMs when I have the experience necessary.
Click to expand...
Click to collapse
Awesome; nice to see another developer =D
I'm looking forward to your work!
There's not a lot of demand for this but here we go anyway haha!
This has only been tested on dynamickat 4.2 and all credit goes to bri315317 for his awesome rom. Also this will not work well with tw so install a 3rd party launcher that supports navbars.
1. First things first back up your rom incase you mess up something and your phone goes poof.
2. open up your build.prop located in your system folder with a file manager and add qemu.hw.mainkeys=0 as the last line in your build.prop
3. Reboot into recovery and Install the Aosp systemui that bri made for his rom.
If you don't wish to customize the navbar buttons then there's no need to proceed further.
4. Download xposed additions for xposed. This is used to disable the hardware buttons.
5. Download gravity box kk for xposed. This is used to customize the navbar buttons and other parts of the rom.
6. Make sure to install another launcher besides tw launcher because tw doesn't work well with softkeys. I installed nova launcher but Googles launcher works as well.
After you've done all of the above reboot and profit
Actually I've done some fairly serious googling to accomplish what you've outlined here.
Hardware home button has been my biggest issue since buying the device. Thanks a bunch
zhukov_ said:
Actually I've done some fairly serious googling to accomplish what you've outlined here.
Hardware home button has been my biggest issue since buying the device. Thanks a bunch
Click to expand...
Click to collapse
Yw! Glad I could help
Alternatively, you can turn on the navbar in Gravitybox.
adbyerly said:
Alternatively, you can turn on the navbar in Gravitybox.
Click to expand...
Click to collapse
I've always had issues with this method but if it works for you then cool
majortaylor said:
I've always had issues with this method but if it works for you then cool
Click to expand...
Click to collapse
Huh, interesting. Do they show up for you at all? I've only turned it on once to try it out, worked fine but I only used it for a few minutes, so you probably have more insight than I do.
Does anyone else here a problem with the Dialer app? I have an extra bar at the top that is only made for the settings icon and it blocks the first contact.
Edit: Do I need AOSP UI now? I'm on Dynamic Kat 4.2 and was able to get a navbar before, but when I tried to add it just now to get a screen shot of my problem I just get constant UI Crashes.
This happens by editing the build.prop file and with using GB.
Androidi747 said:
Does anyone else here a problem with the Dialer app? I have an extra bar at the top that is only made for the settings icon and it blocks the first contact.
Edit: Do I need AOSP UI now? I'm on Dynamic Kat 4.2 and was able to get a navbar before, but when I tried to add it just now to get a screen shot of my problem I just get constant UI Crashes.
This happens by editing the build.prop file and with using GB.
Click to expand...
Click to collapse
With the Aosp systemui I didn't get any crashes. As far as the dialer I'm not sure. Everything seemed ok to me
majortaylor said:
With the Aosp systemui I didn't get any crashes. As far as the dialer I'm not sure. Everything seemed ok to me
Click to expand...
Click to collapse
Crashing stopped after adding AOSP UI, I'll see how it goes!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what I'm talking about. I thought for sure it covered up part of the contacts but it still takes up quite a bit of space.
That's because it adds the menu button. Which takes up space unfortunately. But shouldn't affect anything other then an eye sore