Question for Chefs on Album 3 - Touch Pro, Fuze ROM Development

I have this question in the Album 3 thread, but that one's nearly dead -- thought a chef here might be able to offer some insight.
Several posters have noted that when zooming in with Album 3 while the display is in landscape, things go funky. It appears to rotate part of the screen back as it zooms, then it snaps back into place.
It appears to me this only happens with SensorSDK3 -- not SensorSDK4. But I generally prefer to use SensorSDK3 in my own ROM for other reasons.
I'm fairly certain I've seen the zoom work properly with Album 3 on a few other people's ROMs, even when SensorSDK3 is being used. Anyone know how to accomplish this?

Eventually, answered my own question (by taking a closer look at, and borrowing, the files from one of those ROMs (herg's)).
This Album3 (19123021) works exactly as I was hoping.

Related

Mods please close the thread.....

Hi hkwildboy,
Great appreciation to hkwildboy discovering such an solution for quick GPS locking ........ & here is a CAB who find difficulty in editing Reg edit......
Mod's just for an awareness among all members i created new thread as this is a most essential part (GPS locking) most people complain of......
As per the feed back from senior's i came to know that the cab i attached was not working so please forgive me ...this thread will be closed.
Is the cab uninstallable?
aadadams said:
Is the cab uninstallable?
Click to expand...
Click to collapse
Yes it is uninstallable......
I'm trying it out on AT&T Fuze with Shep's 3g. I'm indoors and cannot get a fix with the standard setup. Outdoors I usually get a fix within a minute or so. I will report if this improves my experience later this evening.
Thank you for sharing this.
no feed bscks
With admitted limited use, I would tend to confirm reduced lag. I was not able to get locks indoors at home or at work either with or without the cab installed so no improvement there. The lag reduction alone makes the cab worthy of install however, as I must also admit to seeing no ill/adverse effects from the install. Thanks for the heads up.
aadadams said:
With admitted limited use, I would tend to confirm reduced lag. I was not able to get locks indoors at home or at work either with or without the cab installed so no improvement there. The lag reduction alone makes the cab worthy of install however, as I must also admit to seeing no ill/adverse effects from the install. Thanks for the heads up.
Click to expand...
Click to collapse
the cab does only help in speed lock of gps , would not help at places where you are not exposed to open space to get sat signals also depends on radio as well, i am residing at place where i do not get a proper signal...can't expect gps to work.
Does it also reduce lag or was that my imagination? I didn't think it could do anything for signal, but I know many woould like to see an answer to that question. Thanks again for making us aware.
Well I hate to burst anyone's bubble, but you do realize that both 5.08 and the new 5.10 Raphael drivers have already addressed the lock-on/aGPS issues, right ????
All you need is a newer radio, and those new drivers. Any ROM here on XDA has those drivers implemented by now.
This file/reg tweaks are really only useful if you're still running the stock ROM. In which case, how much use are you REALLY getting out of XDA ????
In any case, this fix is for stock ROM's. if you're running NATF, or Energy, or ROMeo's, or Da_G's custom ROMS, the fix for this has already been done, on the HTC side.
I'm running 6.5, and since aGPS is actually working, I'm getting locks in under 15 secs, in under 5 if I'm already connected to the internet.
mexiken said:
This file/reg tweaks are really only useful if you're still running the stock ROM. In which case, how much use are you REALLY getting out of XDA ????
Click to expand...
Click to collapse
I don't want to get into any theological debate over the good and evil of it, but there's a lot of people who, for various reasons, are stuck using the stock roms or they are too fearful of flashing.
Just an example, a buddy of mine works for AT&T. One of AT&T's policies (like every other major carrier) is to hand out different handsets to the employees so that they can become familiar with them. Next month he's supposed to sample the Fuze. These types of fixes will actually be pretty useful to him for the purpose of making the fuze realistically functional.
speed_pour said:
I don't want to get into any theological debate over the good and evil of it, but there's a lot of people who, for various reasons, are stuck using the stock roms or they are too fearful of flashing.
Just an example, a buddy of mine works for AT&T. One of AT&T's policies (like every other major carrier) is to hand out different handsets to the employees so that they can become familiar with them. Next month he's supposed to sample the Fuze. These types of fixes will actually be pretty useful to him for the purpose of making the fuze realistically functional.
Click to expand...
Click to collapse
I understand where you're coming from. However, most of XDA's fame and notoriety came from ROM's. Nowadays, it has fixes/updates to things, but at its core, its a place for custom ROMs for HTC phones.
BTW, I should have clarified. AT&T released an official, updated ROM for the Fuze. It, among other things, addressed this issue. So if someone is scared to run a custom ROM, they can always just flash to the official update, and still, problem solved with aGPS.
I have worked for AT&T, so I now the specific program you're referring to. By now, all Fuze's should be shipped with latest update. And even if not, its not very hard to flash to something he likes, and then flash it all back to stock when he needs to turn it in....
And btw, not every carrier does that. At least, not the one I work for now....
mexiken said:
BTW, I should have clarified. AT&T released an official, updated ROM for the Fuze. It, among other things, addressed this issue. So if someone is scared to run a custom ROM, they can always just flash to the official update, and still, problem solved with aGPS.
Click to expand...
Click to collapse
I may be mistaken, as I only spent a few minutes looking, but I can't find an officially released rom update for the Fuze anywhere on HTC or AT&T's site. AT&T's support FAQ claims there's no updates yet. Assuming these sites aren't misrepresenting the facts, I'm pretty sure you're mistaking the firmware update with the Leaked version here: A-GPS works in 5.08 leaked AT&T ROM. Keep in mind, that version leaked less than 6 weeks ago and AT&T is famously slow to release.
You're picking at exactly the point I said I didn't want to get into, that we shouldn't be discussing "To Flash or Not To Flash". Fact is that there's some people who can't...or won't...flash their phones, but installing a cab that notably improves GPS performance with minimal (at this point, virtually zero) risk is surely good for them. There's no reason to knock a good solution if it exists. My point is, XDA isn't just about the latest ROMs, and from the reading I've been doing on here for the last couple of years, I don't believe it's ever been just about the roms.
I'd be willing to bet there's going to be a fair number of people getting use out of this fix. Nearly 300 downloads in just the last 3 days, I suspect at least 10% of those downloaders are getting a lot out of XDA without using a custom rom. In other words, cut these guys some slack, they're doing good work even if it doesn't apply to the majority.
Hi krish_nank
This cab works well with my rom : ROMeOS v.1.95.1 WWE.
Regards,
PB
speed_pour and mexiken stay on topic please.
if you both want to discuss certain things that don't concern the meaning of this thread please pm each other or do it on the msn.
you both have installed the cab? if yes, what are the experiences?
thanks and regards
pabcb said:
Hi krish_nank
This cab works well with my rom : ROMeOS v.1.95.1 WWE.
Regards,
PB
Click to expand...
Click to collapse
in which way did it worked well? i know it is for faster gps locks.
But can you be more concrete?
thanks
I dont suppose this also corrects the gps satellite bars for signal not showing does it ?
(IE TomTom , Igo , and a few others dont report the signal strength )
Thanks Much
GSM Raphael owners take note!
pretty funny. Also a good indication of the subjectivity of this problem and the power of the "placebo effect".
Sorry to say, but this cab really doesn't do anything. It sets pollinterval to 500 which is below the 1 second chip update capability. Da_G demonstrated the ineffectiveness of this. Pollinterval should be 1000. Also this cab sets the logs to 32, another setting that has been proven ineffective.
To fix the missing satellite display, TomTom must be upgraded to v7.910.9185.
There is an AT&T test ROM underlying acquisition time fixes to the GPS system. This correctly enables AGPS resulting in consistent 15 second lock times. It has no effect on position lag.
If you really want to understand GPS issues you must patiently read through the entire mammoth thread located in the raphael forum titled "touchpro GPS lag problems". Switch to the forum and sort by views. It is one of the most viewed threads there. It describes in great detail the various GPS issues starting on about post 300. Videos and real cabs containing tested tweaks are there too.
Here is your quiz. Once finished reading you will be able to easily understand and differentiate between these:
what is position lag?
what is speed lag?
what is a cold start, warm start, hot start?
what is ephemeris and how does AGPS affect this?
how does AGPS differ from QuickGPS?
Why does AGPS have no effect on either lags?
More importantly, you will understand exactly what you need to do to turn your Raphael into one of the absolute best handheld GPS devices out there.
Or, you could just load one of the fixed ROMs and run TomTom v7.910.9185 (yes, position lag is partially based on the navigator you are using)
Sleuth255 said:
pretty funny. Also a good indication of the subjectivity of this problem and the power of the "placebo effect".
Sorry to say, but this cab really doesn't do anything. It sets pollinterval to 500 which is below the 1 second chip update capability. Da_G demonstrated the ineffectiveness of this. Pollinterval should be 1000. Also this cab sets the logs to 32, another setting that has been proven ineffective.
To fix the missing satellite display, TomTom must be upgraded to v7.910.9185.
There is an AT&T test ROM underlying acquisition time fixes to the GPS system. This correctly enables AGPS resulting in consistent 15 second lock times. It has no effect on position lag.
If you really want to understand GPS issues you must patiently read through the entire mammoth thread located in the raphael forum titled "touchpro GPS lag problems". Switch to the forum and sort by views. It is one of the most viewed threads there. It describes in great detail the various GPS issues starting on about post 300. Videos and real cabs containing tested tweaks are there too.
Here is your quiz. Once finished reading you will be able to easily understand and differentiate between these:
what is position lag?
what is speed lag?
what is a cold start, warm start, hot start?
what is ephemeris and how does AGPS affect this?
how does AGPS differ from QuickGPS?
Why does AGPS have no effect on either lags?
More importantly, you will understand exactly what you need to do to turn your Raphael into one of the absolute best handheld GPS devices out there.
Or, you could just load one of the fixed ROMs and run TomTom v7.910.9185 (yes, position lag is partially based on the navigator you are using)
Click to expand...
Click to collapse
Hi Sir, May be i was wrong as i am not a technically sound person about the mobile working.....if you really believe this cab doesn't have helped any one or doesn't help any way....please close the thread.....once it is done i will delete the cab too. I don't want to waste many people time & useless long thread with out working fix.........
By the way it is been mentioned that this cab act as an tweak to get quick satellite fix not to correct a lagging problem ....
Please close this thread if possible or delete the thread itself Thank you
Hi Krish,
in the right corner of each post there's a red white triangle.
If you click on that then the mods know that you want to close the thread but use it only for:
Note: This is ONLY to be used to report spam, advertising messages, and problematic (harassment, fighting, or rude) posts.
each forum has his own moderators contact one of them who are availiable

Which Direction should I take my Swype themes?

Ok guys, alot of you have been making various requests on my Galaxy S threads, and I have a huge fork in the road I need to navigate. I have two theme routes to take, and if I take one, then the other must be abandoned without looking back, because there is just so much work involved in either one. I honestly wouldn't mind having someone help me with this, taking the other fork where I take the winning one from this poll. I have all the files you need & instructions, etc. I have a very well organized set up when it comes to these themes, and will make the work process as simple as possible
Ok, the two options I am facing revolve around a very minor difference, but impacts two completely different user bases.
First choice, is to make my current themes international, meaning they will have support for azerty, greek, and other languages.
Second choice, is to modify all the current themes I have to work with the voice input version of Swype (2.2.42.xxxxx). I will continue to fulfill requests as best as I can while maintaining a wide variety of usable, manageable, interchangeable (with Swype trail line colors) themes.
I'm not sure what you think, but my vote is on the Second option, mainly because Swype capability coupled with voice input is the perfect keyboard IMHO, but I am asking this because I DO have so much following wanting both, but I can only do one... I am just one guy
I am allowing 5 days for this poll, and the answer at the end of it will determine what I work on. So, let the voting begin!
I vote for the second as well. I think that it'd be a more efficient method. The first choice would still be on the table but that can be something in the future.
I vote second one also.
Sent from my SGH-T959 using XDA App
I also vote for the second!
Sent from Monnie's Vibrant.. oops, force close.
i can see which ones of you voted for what in the poll... that's what it's there for.
lets leave the thread clear of vote choices so a discussion can be had. this might also be a good place for me to find a partner or a few to help me build a huge Swype theme library, and hopefully in the future, implement it in some sort of convenient Android app-type library that we can distribute to the millions and millions and millions of Android users around the world, and possibly make a few bucks while we're at it.
I have been doing this for quite some time in relation to how long Swype has been available for Android users. Once I have established a solid base for Android, I expect to make a leap into other OS versions of the software, and even further extend my reach. I don't see why the most commonly used software on ANY phone shouldn't have the option to use a touch of some of mine or someone else's style with just the click of a button.
edit: unrelated, but I just noticed, I joined the XDA forums within a few days of the Swype official beta's release date for Android... Scary. My initial experiences with XDA were totally ROM and G1 functionality related, but around my 25th post, I started tinkering with Swype. Fate, anyone?

What User-Interface 'Experience' would you like on Android?

I've been pondering for some time that if Android has the most customization on the earth for a Mobile OS why doesn't the rooted community make a rom? All the current roms out there Whether it be Cyanogenmod, MIUI, Sense, Touchwiz, Motoblur, it's all based and still resembles of what the manufacturers or companies have given us. Even though MIUI has a company behind it, it shows that you can use the rooted community to make something great. We have an abundance of Developers, Themers, Idealists, testers, etc. to do something like this.They could design it, port it, test it, and put more ideas forward. Even though I have nothing of value to offer, I was just wondering why this has not been done, so my pondering can stop.
imagine how many phones you would have to port it to
Not trying to be rude or anything, but think about that statement.
He has a point. A ROM alone doesn't do much if the drivers are missing... and those are not generally available unless you sign a deal with the hardware maker, which isn't exactly trivial for opensource projects. I don't really see any other way than what people are doing now: What other way than grabbing the drivers from the previously installed system is there to get anything to run on the actual hardware?
Cimer said:
Not trying to be rude or anything, but think about that statement.
Click to expand...
Click to collapse
yeah i know your first post says we have a lot of developers to do it, but porting isnt an easy job. each phone has their own specifications. some phones cant handle what other phones can. and even if you manage to port most of the rom, there are bound to be bugs. and maybe you dont know how many phones we have here on xda. we're talking about all the phones here and here
Well since it's off of AOSP...? I don't see where you're getting this whole making deals with manufacturers. How ever since most brands have been ported to Cyanogenmod it's not impossible.
Also you would not need to port it to those devices. Not trying to exclude people but I'm just going to take Cyanogen's stance...It's been two years, most people have updated to new devices. Also most of those are not even Android..cmon
How else do you want to get the drivers... you either have to take them from the device, which means leaving enough of the system in place that they'll function (which is what CyanogenMod is doing now), or make a deal with the people who have the original drivers. I just don't see any other ways, do you?
Cyanogen does not make deals with manufacturers and it's well Cyanogenmod not Cyanogenmod+motoblur or Cyanogenmod + touchwiz.
Look I know you guys are pessimistic about it, but it's a interesting and real possibility.
Drivers, not frontends. What I mean is Cellphone chipsets, battery stats and so on... they're still there when you install Cyanogenmod, since they can't include their own... I thought that was part of what you meant with "Community ROM", that these "leftovers" from the original system should go. I'm not pessimistic, just confused.
Well you're only confusing your self. It's a straight forward idea..The community designs it's own UI and from there it is dependent on specific devices developers. It's not impossible, It's only as possible as the community makes it out to because this community is very talented.
Ah... you just want to change the frontend, not the "bowels" of the system... sorry, simple misunderstanding. I read "community ROM" and thought you wanted to go further than what Cyanogenmod is doing, essentially building a full working ROM instead of what is essentially a kind of patch for the system already in place...
Sort of..Think MIUI but by the community
Hmm... could you be a little more specific what you think should be part of such an alternative main user interface? For example, should it do away with the widgets concept if it feels inadequate? Or remap controls and so on. Or should it be "just" a launcher and a fancy keylock?
Well that's not up to me to be frank. The reason why I can't be specific is because it's a community rom, not a Cimer rom
There always has to be a starting point and you (hopefully) have some thoughts on this, otherwise you wouldn't have created this thread, right?
For me, it's mostly about the launcher and "Task Switcher" or whatever you want to call it ("Recent Applications"). Lock screens for me serve only a single purpose and any more than that usually gets in the way. For example, if you place a lot information on it, you have to keep the screen on for a longer period, which will eventually drain the battery if you keep the phone in your trouser's pockets.
Well yes...I have thought about it. Through thinking about it I came to the conclusion that I don't know what everyone wants, and how it will work out. Now I could be the starting point, but to be realistic I can't do it by myself I would need the previous mentioned people in my first post, and the community to get this rolling. This could either be revolutionary or it could just be lost in XDA's countless topics. It will also be hard because everyone has something they're working on.
You need to give people something to discuss
OK, then I'll start.
As I said, the core functions for me are home screen and task switching.
Let's start with the launcher.
Launchers fall mainly into two categories:
1. Searcher
2. Finder
A "Searcher" allows the user to specify more and more precisely what he wants to do. This can either be key presses, categories/labels or anything really that asks the user for traits of the activity he wants to perform.
A "Finder" on the other hand presents most available functions at once and lets the user pick the one he wants immediately.
There are many shades of gray between those two, but that's the spectrum.
For me one level of "Searcher" functionality has proven the optimal level of traits that I can navigate through without ending up at the wrong point too often. Categories, à la PalmOS are still the best thing I can think of, but obviously that's partly due to my history with mobile devices, which has been dominated by PalmOS. How do other people reach their applications?
P.S. May I suggest a title change for the thread? Something along the lines of "What User-Interface 'Experience' would you like on Android?". The "CustomROM" title still confuses me
Done.
If you think about it All roms basically have icons on their home screen in a grid or on a dock of some sort..How would you change that to have the greatest eye candy and functionality.
Well to be honest you can't get away from icons on the home screen judging from other mobile and computer operating systems. So they next question would be how do you optimize that "dock" to be to the user's liking. ADW, Launcher Pro, and somewhat MIUI has provided a little answer to that. You can theme the dock, put 1 to 5 icons on it..But the trouble is to not make it look iPhoneish yet allow the possibility in case someone want to...we don't want that. So what do you do? Also perhaps we could not get rid of the app drawer, but the app drawer short cut. Like there is a little bar or line (depends what shape your dock is) above the dock and you have to drag that up.
Or perhaps having the notification bar on the bottom (top if you wanted to) and improve the notification system
Cimer said:
The community designs it's own UI and from there it is dependent on specific devices developers.
Click to expand...
Click to collapse
ah i see now, sorry for the misunderstanding
Cimer said:
If you think about it All roms basically have icons on their home screen in a grid or on a dock of some sort..How would you change that to have the greatest eye candy and functionality.
Well to be honest you can't get away from icons on the home screen judging from other mobile and computer operating systems.
Click to expand...
Click to collapse
i came across this...looks pretty interesting to me
I also like this idea, MIUI has done an outstanding job with android, they've added so many things that were never made, but even CM is superior to AOSP or any stock ROM out there. I would like a cool homescreen that's 2D w/ 3D like effect similar to sense 3.0. And the setting menus should resemble honeycomb, it should have extensive theming down to every app. These are just some things I would like to see.

[Q] [devreq]updates on aosp location bug?

Over the past ~2 weeks, many people have been seeing this bug. We often write it off as being the bug that requires you to flash a Sense ROM, get a lock, then flash back to AOSP, but this is something different. Rather than discussing this separated in half a dozen different threads, I'd like for us to tackle this bug here in a thread focused to it.
I've seen what I believe to be this bug manifest with two different symptoms:
Full GPS works fine while network location works in some apps but gives you an obviously bogus location in other apps.
Full GPS works fine while network location works in some apps and simply fails in other apps.
NOTE: If Full GPS fails for you (such as in Google Maps), then go tackle that problem first before discussing here. If full GPS fails, then you probably have the bug that requires you to flash a Sense ROM. Please do NOT confuse that bug with this one!
I have seen this bug reported for all functional AOSP-based ROMs that I've followed, specifically CM7, OMFGB, OMGB, and Liquid Thunderbread. The funny thing is that some people get this bug while others do not, and there is not a clear pattern.
As I said before, this is clearly happening on pretty much every AOSP-based ROM. What is not clear, however, are what causes this. So it sure would be nice to figure this out. I'm not sure exactly what we need to do to find this but since you all are smart cookies, we'll still figure this out...
Click to expand...
Click to collapse
We aosp users have been plagued with the location bug for a VERY long time when it comes to rom dev time. Has anyone even bothered to look into it, or has everyone just excepted that it dosent work?
every thread or mention ive seen on multiple forums all ended in DEAD TOPICS.
rootz wiki has a DEAD 9 page thread on the matter, not one further post.
XDA has... 0 threads?( correct me if im wrong) on this, but ALOT of mentions
can I ask a dev to look into this? Excuse me for making broad assumptions, but it appears to me that all devs are doing right now is working on the bells and whistles for their roms and modding kernels and such while this bug got swept under the rug. I can understand that devs are BUSY and I thank them for that, I just request that we iron out this little bug, so that these AOSP gems are FLAWLESS.

HTC Flyer Touch Buttons after Honeycomb Update

So i've finally got the update, however I really don't like the fact the touch buttons don't work anymore. Surely if you pay for a product with touch buttons you expect them to STAY, rather than the company decide "no, you're not allowed them anymore".
Any way of getting functionality back, or will I have to revert back pre-Honeycomb?
LeeDroids kernel/ROM have HW buttons
I upgraded to HC yesterday and the first thing I did was installing Leedroids ROM and buying Honeybar. The first so I got my buttons back, the second to remove the honeycomb bar when I don't want it. Works perfectly!
Wiley87 said:
So i've finally got the update, however I really don't like the fact the touch buttons don't work anymore. Surely if you pay for a product with touch buttons you expect them to STAY, rather than the company decide "no, you're not allowed them anymore".
Any way of getting functionality back, or will I have to revert back pre-Honeycomb?
Click to expand...
Click to collapse
Why yes, you can have your redundant hard buttons back !
You can send 100,000 Euro to HTC to make a new release , or you can install one of the custom rooted ROMs that give you your redundant buttons back.
Read a bit, you will learn new things.
PS:
for an extra 20K euro I will add a 5th hard button with the very useful function of "REBOOT and CATCH FIRE"
DigitalMD said:
or you can install one of the custom rooted ROMs that give you your redundant buttons back.
Click to expand...
Click to collapse
For those that prefer the capacitive buttons, they can install Honey Bar from the Market, and hide the notification bar. In that case, the buttons are no longer redundant.
True, but you cannot get the reboot and catch fire function with that hack.
While Honeybar works most of the time, do be aware it is a root hack and does cause problems with some games and other apps.
Read the comments on market before thinking you have ROM problems if you install it.
for me its better....however honeybar takes up space..... there is an advantage for me with HC on screen buttons because on GB many a tyms my games were minimised when my finger accidently touched the hardware keys... now software buttons r not clicked when i drag my finger onto them.... this is better for me...
DigitalMD said:
Why yes, you can have your redundant hard buttons back !
You can send 100,000 Euro to HTC to make a new release , or you can install one of the custom rooted ROMs that give you your redundant buttons back.
Read a bit, you will learn new things.
PS:
for an extra 20K euro I will add a 5th hard button with the very useful function of "REBOOT and CATCH FIRE"
Click to expand...
Click to collapse
the funny part about your post was..... actually, there wasn't a funny part. usually, aware me if i'm wrong, an UPDATE means that an existing product is made better through it's ORIGINAL state. buying a product with hardware buttons and then having them removed through a supposed update is like buying a car with a CD player and having the inside fully refurbished with the CD player being turned into a a cassette player.
my point being, I was unaware of such ROM's, so asked a simple question to which I received a perfectly good answer. the only input you have given in the thread is repeating an answer and adding unfunny comments with it.
how ironic, you could say you updated the original reply from Aiden the old fashioned HTC way.
Wiley87 said:
the funny part about your post was..... actually, there wasn't a funny part. usually, aware me if i'm wrong, an UPDATE means that an existing product is made better through it's ORIGINAL state. buying a product with hardware buttons and then having them removed through a supposed update is like buying a car with a CD player and having the inside fully refurbished with the CD player being turned into a a cassette player.
my point being, I was unaware of such ROM's, so asked a simple question to which I received a perfectly good answer. the only input you have given in the thread is repeating an answer and adding unfunny comments with it.
how ironic, you could say you updated the original reply from Aiden the old fashioned HTC way.
Click to expand...
Click to collapse
While DigitalMD is obviously a key member to the community his sarcasm and degrading forum posts do get annoying. (Don't take this the wrong way DigitalMD)
I completely agree with you about the HC update. Why HTC didn't provide the option to remove the lower bar and place the buttons back on the touch buttons on the device is beyond me. They removed a key feature of the device that I liked.
Guess I'll have to look into this LeeDroid rom. I was avoiding bothering with rooting. Kind of sick of messing with stuff as of late. Just causes headaches/complicates things.
Edit:
LeeDroid is only for Flyer... Any View Roms that add the buttons back?
No View Roms to re-add buttons, huh? Or no one knows how to support the other users on this forum....
I do not believe that View has kernel source. Without it I do not believe the HW buttons can be enabled.
Written word on a website can be taken in many ways. I am a sarcastic ass myself and can see how sometimes comments I make can be taken the wrong way. good rule of thumb, try not to take any offense to anything posted on this forum
ORTOX said:
While DigitalMD is obviously a key member to the community his sarcasm and degrading forum posts do get annoying. (Don't take this the wrong way DigitalMD)
I completely agree with you about the HC update. Why HTC didn't provide the option to remove the lower bar and place the buttons back on the touch buttons on the device is beyond me. They removed a key feature of the device that I liked.
Guess I'll have to look into this LeeDroid rom. I was avoiding bothering with rooting. Kind of sick of messing with stuff as of late. Just causes headaches/complicates things.
Edit:
LeeDroid is only for Flyer... Any View Roms that add the buttons back?
Click to expand...
Click to collapse
actually I wasn't being sarcastic,, I'm just extremely funny. And as far as degrading the forum, well we are here to help the newbies, people that run into problems and developers, not necessarily people that obsess about things that realistically cannot be fixed, but I appreciate your humor. While I do my best to answer and help reasonable questions, when people obsess about things that do not have a reasonable solution or do not understand or accept logical business decisions, I tend to point out the facts. Not everyone likes that. That's OK, I've been through several decades of computer and smart device development, you can't please everyone.
HTC didn't remove the HC system bar because Google designed HC that way and left no room for anyone to change that part of the GUI. They intended the system bar to be a center piece and all the moaning in the world won't change Honeycomb. HTC designed the Flyer, per-Honeycomb, before Google decided that future Android devices shalt not have buttons. Google left a little more leeway in ICS and the system bar can be hidden with a system call. They probably wanted it to act like Windows task bar and auto-hide, but were afraid they would have to cough up even more tribute to Microsoft for patent infringement.
I do like to inject some humor , especially with people don't get basic business principles such as Hardware vendors are not in business to fix every little issue you think you have, they are in business to make money. That often means they build a product that is good, but far from perfect because there is a vast amount of cost difference between good enough and perfect.
you tell 'em. seriously though, I see what you are saying and I agree with what you are saying. I am only saying this because I find when there are problems/issues that can be adequately addressed I feel that you (along with various others on this forum) are quite helpful.
mcord11758 said:
I do not believe that View has kernel source. Without it I do not believe the HW buttons can be enabled.
Written word on a website can be taken in many ways. I am a sarcastic ass myself and can see how sometimes comments I make can be taken the wrong way. good rule of thumb, try not to take any offense to anything posted on this forum
Click to expand...
Click to collapse
Here's to hoping I suppose. Maybe if I get ambitious I'll downgrade back to GB. While I understand why HTC released Honeycomb for the tablet, I don't understand why Google made the taskbar mandatory in HC.
The taskbar really gets in the way when using the tablet with handwriting apps and is kind of annoying when using the tablet for reading. It makes it harder to become fully immersed in the book (as corny as this might sound).
I have 3 words for you:
Honeybar
and another three words are: HideBar
and yet another 3 words are:
Honey Hide Widget (incase you want a widget to hide the bar)
vlara said:
and yet another 3 words are:
Honey Hide Widget (incase you want a widget to hide the bar)
Click to expand...
Click to collapse
I must apologize to you vlara because actually Honey Hide Widget is what I meant to refer to as that is what I use on your wonderful Rom HoneyPot. I use leedroid tweaks for the hardware buttons and am able to toggle between the system bar and the hardware buttons depending on my mood/use.
So, I guess the best option for me if I decide to would be, downgrade to GB, and then upgrade to a rooted HC rom, then install one of these toolbar hiders. These all require root access, correct?
AidenM said:
I have 3 words for you:
Honeybar
Click to expand...
Click to collapse
GMAN1722 said:
and another three words are: HideBar
Click to expand...
Click to collapse
vlara said:
and yet another 3 words are:
Honey Hide Widget (incase you want a widget to hide the bar)
Click to expand...
Click to collapse
Hey those make 3 phrases!!
And no, just flash a HC rom.

Categories

Resources