i had to take some shots of these while i can, it looked pretty freakin cool
As weird as it sounds... I like that method... wish we could change where the pull bar was on the phone. I would totally put mine on the side. And if we could change the notificiation bar to the bottom that would be a nother neat little tweak.
nice, looks pretty good on the side. would it be possible to mod it in someway to always be on the side?
I had ADP1 installed and my topbar icons were having a seizure. They kept flashing and moving really fast. I wonder if its a problem with ADP1. I went back to RC30 and no more problems.
Reveal your secrets!!!
That's pretty sweet. Wish we could do something like that on purpose..lol
I got those same effects with that one program I can't remember what it was. O yeah I think its called PHOTOSHOP. Nah I'm just jokin around. I was just surprised I was the first person to call shenanigans. That's pretty cool, I'm sure we'll have the option to do that soon. Thanks for the screenies. Please no flaming, as I said I was joking = D
sWuRv said:
I got those same effects with that one program I can't remember what it was. O yeah I think its called PHOTOSHOP. Nah I'm just jokin around. I was just surprised I was the first person to call shenanigans. That's pretty cool, I'm sure we'll have the option to do that soon. Thanks for the screenies. Please no flaming, as I said I was joking = D
Click to expand...
Click to collapse
lol its ok i dont kno how to photoshop anyway lol n i do wish there was a way to puposely move the tab and notification around
well im gonna say that this will happen with time! it looks as if the ui is all xml files which means as we start talking the android code more we will see some pretty trick stuff! this began to happen with my t mobile shadow! we could edit just about anything! so with time comes custom android! just remember thats android itself is fairly young! and it takes time to hack the sheezie out of these things! open source or not
Here are the XML files in question:
For landscape view:
http://android.git.kernel.org/?p=pl...her.git;a=blob;f=res/layout-land/launcher.xml
Line 63:
launcher:direction="vertical" />
For portrait view:
http://android.git.kernel.org/?p=pl...her.git;a=blob;f=res/layout-port/launcher.xml
Line 63:
launcher:direction="horizontal" />
my phone did that before. it happened when i first got it(stock rc30). a program was causing it to happen. i cant remember which one right now.. but it would force close and when i'd close the keyboard the screen would rotate with the apps bar.
Related
Does anyone on this forum know how to change the sms background screen from white to black? Im am currently running the rogers rom, but i will be switching to cyanogens 1.5r2 which will have the white background in sms
Considering your name i can see why this is so important to you. But ive never seen an option for background menu modification in the g1 settings.
just take all the .xml's out of the framework-res/res/layout directory of the mms.apk you have with the black background and copy them over to the mms.apk in the build you are going to flash to prior to flashing...MAKE A NANDROID BACKUP FIRST!!!! If you do this and it messes up your phone IT IS NOT MY FAULT. This is the method i used to get the 5x5 and 6x3 row app trays from the dudes build onto Cyanogen's 3.6, and it worked just fine with no adverse affects to my knowledge. I CANNOT GUARANTEE YOU THE SAME RESULTS, AND I AM NOT RESPONSIBLE FOR ANY PROBLEMS THAT ARISE IF YOU MESS THIS UP. Hope it works for ya...DONT FORGET TO MAKE A NANDROID BACKUP!!!!
-BMFC
bmfc187 said:
just take all the .xml's out of the framework-res/res/layout directory of the mms.apk you have with the black background and copy them over to the mms.apk in the build you are going to flash to prior to flashing...MAKE A NANDROID BACKUP FIRST!!!! If you do this and it messes up your phone IT IS NOT MY FAULT. This is the method i used to get the 5x5 and 6x3 row app trays from the dudes build onto Cyanogen's 3.6, and it worked just fine with no adverse affects to my knowledge. I CANNOT GUARANTEE YOU THE SAME RESULTS, AND I AM NOT RESPONSIBLE FOR ANY PROBLEMS THAT ARISE IF YOU MESS THIS UP. Hope it works for ya...DONT FORGET TO MAKE A NANDROID BACKUP!!!!
-BMFC
Click to expand...
Click to collapse
Thanks alot for the response chief! Yeah i know it wouldnt be your fault, this kind of stuff is always "do at your own risk" lol.. i decided to go back to the rogers rom instead tho... i just cant part with the htc dialer that it comes with
droid01 said:
Considering your name i can see why this is so important to you. But ive never seen an option for background menu modification in the g1 settings.
Click to expand...
Click to collapse
LMFAO!!!! i like the black backgroudn because it looks more flush with the black phone as opposed 2 the white backgorund. And i really hate that bright **** in my face when texting at night lol
bbbblack said:
LMFAO!!!! i like the black backgroudn because it looks more flush with the black phone as opposed 2 the white backgorund. And i really hate that bright **** in my face when texting at night lol
Click to expand...
Click to collapse
Yeah here in California you'll get a huge ticket if a cop sees you driving with a bright light in your hand.
Binary100100 said:
Yeah here in California you'll get a huge ticket if a cop sees you driving with a bright light in your hand.
Click to expand...
Click to collapse
That's why you alway keep Google Maps running - GPSes are perfectly legal.
-bZj
I posted this in Cyanogen's main thread but it got pretty much overlooked. So I'm posting here
So I've been using Cyanogen builds for quite a while now and absolutely love them them. One problem I've had consistently with every build since the beginning is that window animations are pretty much non-existent. The transitions are fine though. Animations are enabled in settings and in spare parts, any setting i put it on other than very slow makes it seem like window animations are off. The very slow setting just makes it super choppy. I've searched and not found anybody else having this problem or at least not like me. I don't have apps2sd or swap going. Just the straight fat32. Tried it with the three partitions and same thing. Transitions are fine but window animations are crap. Other non Cyanogen builds work fine. If anybody can point me in the right direction or help me out that would be awesome. Fortunately the Cyan builds are so awesome that I can look past crappy window animations but it would be nice Thanks guys
anybody?
So no one has had or has even heard of this happening? Surely its something simple that can just be fixed through the terminal or something...
I remeber seeing ur post in his main thread. It works for me on normal speed. Have u tryed wiping and reflashing?
pistol4413 said:
I remeber seeing ur post in his main thread. It works for me on normal speed. Have u tryed wiping and reflashing?
Click to expand...
Click to collapse
Oh yeah for sure. Countless times. I've used tons of different roms and wiped almost everytime I switch. I always end up coming back cyanogen though. The more I think about it though its not all window animations that are bad. Like when a menu pops up from the bottom or when the volume fades in and out. Its really only when I press and hold that whichever window it pulls up doesn't animate well. Such as pressing and holding the home screen.
Have u posted this on cyanogenmod.com under the issues tab, its worth a shot. If cyanogen can reproduce it he will most likely fix it.
pistol4413 said:
Have u posted this on cyanogenmod.com under the issues tab, its worth a shot. If cyanogen can reproduce it he will most likely fix it.
Click to expand...
Click to collapse
Hmm. Good idea. I'll give it a shot and see what happens. Thanks for your help
Any devs out there wanna give this a go?
I would love to be able to rotate my phone in any direction and have the screen flip like on my omnia... I know sense doesn't flip to landscape, thats not a prob, what I really want is to be able to flip the phone upside down and still use it as the correct rotation.
Reason I want to be able to do this is so I can use my phone in the cup holder of my car again, and to do this it must be upside down because of the charger placement... (same as on my Omnia)
Seems a pretty simple request, would be nice if it could auto run and run in the background without using up to much resources to.
If anyone is able to do this, would be awesome.
Thanks
Seconded ... but
I too would like to be able to rotate at least the other way; when showing off the Incredible, people rotate to landscape the other way and nothing happens, so they figure it doesn't rotate. I have to say "no turn it the other way" but it would be great to just not have to think about it.
BUT ... regarding the OP ... I simply took a dremel to the dash mount I bought (the beanbag, since California law doesn't allow sticking to the window in the middle). Carved out enough for a charger, and am done with it
I'd also like to see this. Anyone know the reasoning behind only allowing landscape mode by rotating to the left, and not the right? Even my old BB storm could handle rotation in both directions.
Agreed. This would be useful.
mattwood2000 said:
I'd also like to see this. Anyone know the reasoning behind only allowing landscape mode by rotating to the left, and not the right? Even my old BB storm could handle rotation in both directions.
Click to expand...
Click to collapse
I would think it's because the majority of the world is right-handed and by rotating to the left, the optical track button is on the right side. I could complain because I'm left-handed, but hey at least my phone still has a signal when I hold it in my left hand, unlike other phones out there
This is an option in the cyanogen rom available in the rom manager. If you can look past the few bugs in the rom you can enjoy the 360 degree rotation you are looking for.
br125 said:
This is an option in the cyanogen rom available in the rom manager. If you can look past the few bugs in the rom you can enjoy the 360 degree rotation you are looking for.
Click to expand...
Click to collapse
I've been running this cyanogen ROM since it came out and this is the 2nd thing you have pointed out to me in the settings that i didn't know about. I need to look through all the settings much more thoroughly.
br125 said:
This is an option in the cyanogen rom available in the rom manager. If you can look past the few bugs in the rom you can enjoy the 360 degree rotation you are looking for.
Click to expand...
Click to collapse
My phone aint even rooted yet, for some reason I've tried everything and won't allow me to get into adb recovery... anyways, if it's in another rom, it must be possible, if someone could make this an app!! it would be awesome.
Then we wouldn't have limits as to which rom we would have to use.
...just a thought...
JustinD2473 said:
I've been running this cyanogen ROM since it came out and this is the 2nd thing you have pointed out to me in the settings that i didn't know about. I need to look through all the settings much more thoroughly.
Click to expand...
Click to collapse
Yeah you should hes got a lot of good stuff.
So will this be possible as an App?
forgot to reopen
Thanks Mikey for re-opening this thread , you can delete the Why thread now if you like...
So anyone know if any of this is possible?
Found this looking around the forums runs smooth on the bionix 2.2 build...install then reboot for smooth runnings...enjoy.
Might need some minor tweaks but looks clean.
http://forum.xda-developers.com/showthread.php?t=831144
Sent from this mobile thinggy...
Nice, I'll try this. Downloading now. Thanks for the heads up.
Yea I'm running it now...thinking of some tweaks needed for memory and style on the widgets but other than that running like silk.
Sent from this mobile thinggy...
Did you have to rename the file to install?
EDIT: nm, didn't read.
Phone icon on launcher does NOT work
I was just gonna say that. Dialer shortcut not working.
I can't log on to FB from the widget. But so far I like it. Looking good.
looks good... Thanks.
wow looks nice i may try this in a few days still thinking about going obsidian so this may be my launcher of choice for the new build
Yea dialer is broken but ill see what I can come up with...at work now ill see what I can fix after I get home and get the kids in bed...haven't had time to look at it too much yet
Sent from this mobile thinggy...
I tried it yesterday and it was a pretty cool concept. You are right about needing some tweaking though. It would be awesome if this could take the place of Touchwiz in a 2.2 ROM. I might have to get out the good old Rom Chef handbook...
The launcher needs to look different imo, everything else looks good. I like how swiping up brings up the tray that's pretty slick. I'd be happy with the stock TW launcher look to be honest.
has anybody found a work around for the Phone button?
I when into Super Task Manager and I see the Phone.apk, because on the original Thread said to rename it to that in case it didn't work but it is already Phone.apk.
Phone Button is like Froyo launcher2.
You will need to smali it & edit to according.
eugene373 said:
Phone Button is like Froyo launcher2.
You will need to smali it & edit to according.
Click to expand...
Click to collapse
At work right now so I cant dig into it, is it looing for the wrong named apk?
jellette said:
At work right now so I cant dig into it, is it looing for the wrong named apk?
Click to expand...
Click to collapse
yes sir.
Just got home and kids refuse to sleep atm...yea a simple rename is all it is calling for a simple rename of the phone.apk should fix the issue I just haven't torn apart the launcher apk yet so I'm unsure of the name if the kids crash out soon I can start the digging...lol...gotta love kids...they are like living with full time drunks....you never know what they are going to do next or where they hid you power supply for the laptop at...
Sent from this mobile thinggy...
Just digging into it myself - 614,165,225 files in there - any hints where it is in there?
Edit - Are there apps or system files that rely on "Phone.apk"? Will it be easier to change the name that dell looks for rather than changing the name of the apk?
Edit 2 - No luck here...
Been digging threw lines of code in the launcher looking for all the files and apks it calls for might be a day or so before I have this fixed...back to 18 hour days at work do this will have to be spare time project...
Sent from this mobile thinggy...
Running this now. Phone icon works. All widgets besides music, which gets immediate force close when trying and facebook not login are working. Pretty smooth. Im getting some force close on miuui music player, could be unrelated. Fairly useable on my superfast vibrant, froyo of course : )
p.s. Ill try to dial this in some more.
Sent from my SGH-T959 using XDA App
Alright. Well. This is interesting.
I've fixed the original HTC touchscreen driver for use in ICS. I'm assuming it will work on other HTC phones as well, since the fix is FAR less intrusive in terms of changing existing code, or trying to port other drivers.
I was working on trying to map out the Samsung and HTC drivers in terms of data they let the system see as they are running. Getting no where fast, I remembered a couple days ago when I was attempting to get the touch keys working with the Samsung driver. Originally, I had added this code to the mxt224 driver above the line 'set_bit(EV_ABS, ts->input_dev->evbit);':
added to mxt224.c
Code:
set_bit(EV_SYN, ts->input_dev->evbit);
set_bit(EV_KEY, ts->input_dev->evbit);
set_bit(BTN_TOUCH, ts->input_dev->keybit);
set_bit(BTN_2, ts->input_dev->keybit);
I assumed this may have something to do with the softkeys, since it was present in the HTC driver with all four lines. By this I mean that in the HTC driver, that section looked like this:
atmel.c
Code:
set_bit(EV_SYN, ts->input_dev->evbit);
set_bit(EV_KEY, ts->input_dev->evbit);
set_bit(BTN_TOUCH, ts->input_dev->keybit);
set_bit(BTN_2, ts->input_dev->keybit);
set_bit(EV_ABS, ts->input_dev->evbit);
It worked fine in CM7 after doing this, but I lost all touchscreen in ICS, with it not even registering touch data anymore.
Back to my main point, I decided to see what would happen if I totally removed those four lines from the atmel.c file (HTC driver) and see what happens in ICS. Long story short, it works. Apparently ICS doesn't use or absolutely hates one or all four of those input preprocessors. So yeah I kinda **** bricks that it was that simple.
I'm going to try to see if its one or just all of these keybits that's causing the problem and I'll report back.
Instructions
If you want to try this, follow along:
Get rid of build settings for the Samsung driver if you've been messing with that
open up our favorite driver driver/input/touchscreen/atmel.c
CRTL+F, search for EV_SYN
Comment or delete all of the set_bit() lines except for the last one, EV_ABS
Your atmel.c should only have this line now, where all five were before:
Code:
set_bit(EV_ABS, ts->input_dev->evbit);
Clean your make environment and make sure your config files are set to use atmel-touchscreen
**** bricks
so it should look like:
Code:
ts->input_dev->name = "atmel-touchscreen";
// set_bit(EV_SYN, ts->input_dev->evbit);
// set_bit(EV_KEY, ts->input_dev->evbit);
// set_bit(BTN_TOUCH, ts->input_dev->keybit);
// set_bit(BTN_2, ts->input_dev->keybit);
set_bit(EV_ABS, ts->input_dev->evbit);
?
twistedumbrella said:
so it should look like:
Code:
ts->input_dev->name = "atmel-touchscreen";
// set_bit(EV_SYN, ts->input_dev->evbit);
// set_bit(EV_KEY, ts->input_dev->evbit);
// set_bit(BTN_TOUCH, ts->input_dev->keybit);
// set_bit(BTN_2, ts->input_dev->keybit);
set_bit(EV_ABS, ts->input_dev->evbit);
?
Click to expand...
Click to collapse
Yeah try that. I've run into something though, which must be something stupid I'm doing but I can't figure out what the hell it is.
I've gone through each of those that I commented out to see if it was just one of the set_bits that was making it not work. But even with them all on now it's still working in ICS. I've cleaned my builds between each time. I think I'm going crazy! Because it didn't work before!
swm5126 said:
Yeah try that. I've run into something though, which must be something stupid I'm doing but I can't figure out what the hell it is.
I've gone through each of those that I commented out to see if it was just one of the set_bits that was making it not work. But even with them all on now it's still working in ICS. I've cleaned my builds between each time. I think I'm going crazy! Because it didn't work before!
Click to expand...
Click to collapse
I'm building now and I will see what I can find out. It might be as simple as it forced the build to refresh in some way? Ill see what happens and let you know.
I'm already engaged, but I think she will understand... Will you marry me? haha, it worked!
And then I see this : http://android.modaco.com/topic/348194-04-nov-icl23d-galaxy-nexus-boot-recovery-system-dump/
Can you post the zip with it working? Please
w9jds said:
Can you post the zip with it working?
Click to expand...
Click to collapse
http://dl.dropbox.com/u/11023553/imoseyon_leanKernel_184Mhz_vAOSP.zip
That is the Thunderbolt version
swm5126, I cannot than you enough for all the help. I really wouldn't have gotten anywhere without it. Least we can toast to a success!
But I am still looking into what needs to be commented, just a little excited to actually touch ICS. lol.
twistedumbrella said:
I'm already engaged, but I think she will understand... Will you marry me? haha, it worked!
And then I see this : http://android.modaco.com/topic/348194-04-nov-icl23d-galaxy-nexus-boot-recovery-system-dump/
Click to expand...
Click to collapse
Unfortunately I'm engaged too, so no dice!
Can't wait to take a look at those
Quick question, does your pointer in ICS seem to go back up to the top left hand corner of the screen? Or aren't you in pointer mode?
for me it does!!
but I still can't unlock the F screen...
LorD ClockaN said:
for me it does!!
but I still can't unlock the F screen...
Click to expand...
Click to collapse
Awesome! Glad I'm not crazy and this works. They must have deprecated some of the input preprocessors. I'm just surprised using them in the driver basically made the touchscreen inoperable in ICS.
One step closer...to something! Now to figure out those pesky idc files to get this to work without the pointers.
maybe better to focus on Paul's dump.. could be different regarding TS
My post for the stuff inside the new idc configurations system is here http://forum.xda-developers.com/showthread.php?t=1320170&page=16
hope it helps
swm5126 said:
Awesome! Glad I'm not crazy and this works. They must have deprecated some of the input preprocessors. I'm just surprised using them in the driver basically made the touchscreen inoperable in ICS.
One step closer...to something! Now to figure out those pesky idc files to get this to work without the pointers.
Click to expand...
Click to collapse
It reverts to the corner. I am working on a fix for that right now. Congrats, btw.
w9jds said:
My post for the stuff inside the new idc configurations system is here http://forum.xda-developers.com/showthread.php?t=1320170&page=16
hope it helps
Click to expand...
Click to collapse
What he said, lol
Sent from my ADR6400L using Tapatalk
LorD ClockaN said:
maybe better to focus on Paul's dump.. could be different regarding TS
Click to expand...
Click to collapse
Trying to haha filesonic is only letting me get one file at a time *sigh*
I already downloaded those.. I have a paid acount for filesonic
I posted this in DHD thread also:
my Touchscreen works, but it doesn't unlock anything... I mean, I pull the ring to unlock icon, it vibrates and it doesn't change screen..
so I unlock screen with adb shell, and when it gets unlocked I'm welcomed with SystemUi FC.. and every time like that.. if I turn off screen and back ON after trying to unlock screen, my touches are not working.. it must be because systemui already crashed... but it doesn't show it..
LorD ClockaN said:
I already downloaded those.. I have a paid acount for filesonic
I posted this in DHD thread also:
my Touchscreen works, but it doesn't unlock anything... I mean, I pull the ring to unlock icon, it vibrates and it doesn't change screen..
so I unlock screen with adb shell, and when it gets unlocked I'm welcomed with SystemUi FC.. and every time like that.. if I turn off screen and back ON after trying to unlock screen, my touches are not working.. it must be because systemui already crashed... but it doesn't show it..
Click to expand...
Click to collapse
With the fix from here for the driver? Or without anything?
with your fix here
Awesome! Now if only I could find someone to reverse engineer the 3D camera and Gallery for the HTC Evo 3D, I would be fat from all the Ice Cream Goodness I would be devouring! Good job guys
I got money for whomever gets a decent working (radio, touch screen, texts) ICS DINC build by the end of this weekend.....
wetbo529 said:
I got money for whomever gets a decent working (radio, touch screen, texts) ICS DINC build by the end of this weekend.....
Click to expand...
Click to collapse
Can we not do that? That's how things get sloppy. Just donate it to swm, he deserves it.
Sent from my ADR6400L using Tapatalk