I don't know how many chefs read this side of the forum, but I know I'll get my hand slapped for posting this in the development side.
But now that Swype beta is available to pretty much everyone, why are we including the stock version anymore? Everyone seems to do it, and it's difficult to remove to install the beta.
It's obvious that the old version doesn't play nice with Gingerbread's text selection process, and the new version has solved that issue.
Can anyone explain why we're still including an almost useless version?
gspitman said:
I don't know how many chefs read this side of the forum, but I know I'll get my hand slapped for posting this in the development side.
But now that Swype beta is available to pretty much everyone, why are we including the stock version anymore? Everyone seems to do it, and it's difficult to remove to install the beta.
It's obvious that the old version doesn't play nice with Gingerbread's text selection process, and the new version has solved that issue.
Can anyone explain why we're still including an almost useless version?
Click to expand...
Click to collapse
I can cook you up a straight stock rom without it. It's only an apk you can uninstall with tb
Sent from my PG86100 using Tapatalk
aray92 said:
I can cook you up a straight stock rom without it. It's only an apk you can uninstall with tb
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Thank you, but that's not really the point. I can remove it from any ROM, just asking why we're bothering to include something that generally doesn't work with our version of the OS.
gspitman said:
I don't know how many chefs read this side of the forum, but I know I'll get my hand slapped for posting this in the development side.
But now that Swype beta is available to pretty much everyone, why are we including the stock version anymore? Everyone seems to do it, and it's difficult to remove to install the beta.
It's obvious that the old version doesn't play nice with Gingerbread's text selection process, and the new version has solved that issue.
Can anyone explain why we're still including an almost useless version?
Click to expand...
Click to collapse
+1 10chars
gspitman said:
Thank you, but that's not really the point. I can remove it from any ROM, just asking why we're bothering to include something that generally doesn't work with our version of the OS.
Click to expand...
Click to collapse
its included because its the only authorized version allowed to be distributed by the manufacturer, if the developer ( the Rom maker ) included it, swype could get pissed and ask for a take down. you need to sign up for an account and be part of the beta to get it.
so in short.. its against Swype's ToS and EULA. in order to avoid complications, rom makers dont include it
Spyderekz said:
its included because its the only authorized version allowed to be distributed by the manufacturer, if the developer ( the Rom maker ) included it, swype could get pissed and ask for a take down. you need to sign up for an account and be part of the beta to get it.
so in short.. its against Swype's ToS and EULA. in order to avoid complications, rom makers dont include it
Click to expand...
Click to collapse
That's just it, I'm not asking to include the new version... just to NOT include the old one.
The old one doesn't really work, and prevents the easy installation of the new one.
So why include broken software?
gspitman said:
Thank you, but that's not really the point. I can remove it from any ROM, just asking why we're bothering to include something that generally doesn't work with our version of the OS.
Click to expand...
Click to collapse
It's not just the APK, there's a file in system/lib that needs to go too. Last paragraph:
http://forum.swype.com/showthread.p...install-Swype-Swype-PreLoad-Production-Device
Edit: Instead of requesting the devs remove, write a quick script that will remove the old. Then you just need run it once whenever you install a new rom.
lyric911 said:
It's not just the APK, there's a file in system/lib that needs to go too. Last paragraph:
http://forum.swype.com/showthread.p...install-Swype-Swype-PreLoad-Production-Device
Edit: Instead of requesting the devs remove, write a quick script that will remove the old. Then you just need run it once whenever you install a new rom.
Click to expand...
Click to collapse
Again, I know how to remove it, I know that it's possible to remove.
The question that no one is answering is WHY INCLUDE SOFTWARE THAT IS NOT COMPATIBLE WITH GINGERBREAD?
Sorry for yelling, but I'm trying to grasp the value of having the original package.
gspitman said:
Again, I know how to remove it, I know that it's possible to remove.
The question that no one is answering is WHY INCLUDE SOFTWARE THAT IS NOT COMPATIBLE WITH GINGERBREAD?
Sorry for yelling, but I'm trying to grasp the value of having the original package.
Click to expand...
Click to collapse
Am I the only one who's seeing the same trend here that happened in the movie "Anger Management"?
He's only asking "Who you are." LOL
gspitman said:
Again, I know how to remove it, I know that it's possible to remove.
The question that no one is answering is WHY INCLUDE SOFTWARE THAT IS NOT COMPATIBLE WITH GINGERBREAD?
Sorry for yelling, but I'm trying to grasp the value of having the original package.
Click to expand...
Click to collapse
Woops. Meant to quote aray92, not you since he/she said only the apk must be removed.
lyric911 said:
It's not just the APK, there's a file in system/lib that needs to go too. Last paragraph:
ht tp://forum.swype.com/showthread.php?2287-Unable-to-uncheck-uninstall-Swype-Swype-PreLoad-Production-Device
Click to expand...
Click to collapse
Thank you for the link. The Swype beta always crashed for me and now I know why. I removed the files and now Swype works. Thanks!
I agree, I want to be able to install the latest swype. If I recall correctly, couldn't they make it so we could uninstall? I think that's how it was with OG Evo custom roms.
It's been removed from mine from day one.
I thoroughly inspect my ROM for every instance of software that I don't want.
gspitman said:
That's just it, I'm not asking to include the new version... just to NOT include the old one.
The old one doesn't really work, and prevents the easy installation of the new one.
So why include broken software?
Click to expand...
Click to collapse
1) It works just fine.
2) It takes 10 seconds to uninstall with TB.
3) Did you ever consider the possibility that some people may not have another version of swype?
nabbed said:
1) It works just fine.
2) It takes 10 seconds to uninstall with TB.
3) Did you ever consider the possibility that some people may not have another version of swype?
Click to expand...
Click to collapse
1. It doesn't work right.
2. Takes longer than that including removal of the lib files and a half dozen reboots to get the beta installed
3. F%#@ them. Majority wins and its a fantastic idea to remove it, let's get rid of car panel, Twitter, footprints, friendstream, stocks, htcfacebook, fm radio too
its not in my rom either
NewZJ said:
1. It doesn't work right.
2. Takes longer than that including removal of the lib files and a half dozen reboots to get the beta installed
3. F%#@ them. Majority wins and its a fantastic idea to remove it, let's get rid of car panel, Twitter, footprints, friendstream, stocks, htcfacebook, fm radio too
Click to expand...
Click to collapse
Done, agreed, done, may not play right, and maybe!
anyone got the new Swype beta? Haven't tried it out yet
Related
Until someone figures out how to cook and upload a custom ROM, here are some cab files for the Titan.
The first is the Home Plug-in used by the Touch. It shows the Weather etc. You
The second is a Music Plug-in
The third is a X-Button program. It's button appears at the top right of the today screen. One can close all programs or any one running program easily.
There's also a streaming video cab which lets one watch YouTube on the Titan. This website would not let me upload it. Search for it elsewhere. It's labeled as follows: RvBCrS_HTC_Streaming_Media
Just put these on your device and click.
Enjoy
out of curiosity, how much memory do you have free on a fresh reboot after installing all of these?
Dishe said:
out of curiosity, how much memory do you have free on a fresh reboot after installing all of these?
Click to expand...
Click to collapse
i have all 3 installed and after soft reset im at like 20-22 max.
hey thanks for the cabs man they are awesome but i had one question about the audio manager, i have a microsoft zune so i get all my songs thru marketplace but i wont let me pay them on my mogul do to licensing is there anyway to bypass that?
Does anyone know how to make the Weather in Fahrenheit and not Celcius?
What is the difference in the X-button cabs. Some are 120kb and some are 240K? I installed version 1 of x-button and had to hard reset my Mogul. I want to make sure the version and size of the Cab are correct.
Larry
sportsfreak2159 said:
Does anyone know how to make the Weather in Fahrenheit and not Celcius?
Click to expand...
Click to collapse
hit where you select you city then go to menu/weather options you will see it.
raidens330ci said:
hey thanks for the cabs man they are awesome but i had one question about the audio manager, i have a microsoft zune so i get all my songs thru marketplace but i wont let me pay them on my mogul do to licensing is there anyway to bypass that?
Click to expand...
Click to collapse
I'm not sure. I've never bought anything from marketplace. Please give me the URL of the site. What file format is the music in .wma?
I downloaded a song from Sprint and was wondering how to play it on my laptop. The .koz files are supposed to be really compact. However, I'd like to play them on my laptop. Sprint's music store's offerings aren't bad. However, after logging in on my PC, I cannot get to their music store. I've talked with two techies who say they'll fix the link between my account and the music store. So far - No go. At one time, Sprint supposed let you download an mp3 or wma to play on your laptop.
DiSephano's Cab Collection
I've tried to upload several neat cabs to this thread but the system would not allow me.
Here's a link to DiStephano's awesome collection of cabs. Most work on the Mogul.
http://forum.xda-developers.com/showthread.php?p=1428673
Enjoy
Schen's 6 Button HTC Home Cab.
Here's a link to Schen's 6 Button Cab. This works good on the Mogul. It has everything in one package. I didn't use the colors but the 6 Button Home is great and makes the device so much more useable. Follow the link and read instructions.
http://www.4winmobile.com/forums/ht...n-all-icons-coloured-clocks-1-package-11.html
Thanks a ton, I have been looking for the Audio Manager Plugin for a while.
tap on the city then menu in the left corner weather optionsthen you can change it.
great cabs
GeLopez said:
great cabs
Click to expand...
Click to collapse
To quote you again from one minute earlier...
GeLopez said:
\
and this thread is old ...why are we reviving it from the death?
Click to expand...
Click to collapse
This one is almost two years old, and I think there are updated versions of each of these programs.
Yea I am starting to think this person is begging for problems.. Here is a post from the Titan/Titan subforum.
He revived yet another post from the grave for no particular reason. What he doesnt realize is that people may actually use the software/information in these old threads and then have to uninstall and install again once locating the newer versions or information. Thats simply not cool.. Even though its not that big of a deal, this place isnt for fooling around.
Please appreciate that this forum has been open that long and prospering. And that XDA still keeps your threads/posts around for years to come. Dont abuse or make fun of the fact that they provide us with those resources.
Cheers XDA
GeLopez said:
yea great job for adding the subforum lol
Click to expand...
Click to collapse
Direct link to which thread/post I am referring to.
http://forum.xda-developers.com/showpost.php?p=3970299&postcount=11
to me these are great cabs. and i can post that if i want to.
OLD is GOLD
GeLopez said:
to me these are great cabs. and i can post that if i want to.
OLD is GOLD
Click to expand...
Click to collapse
Yes you can, but at least practice making usefull posts..
like yours? pleassssseeeeeeee.
now xda has a post moderator who decides what is good and what is not?
then go ahead and delete it if its not good enough
GeLopez said:
to me these are great cabs. and i can post that if i want to.
OLD is GOLD
Click to expand...
Click to collapse
No one is saying that you cannot post that; it is merely a question of advisability of reviving a 2 year old thread and bringing outdated applications back to the foreground of the forums.
New users are attracted to the smartphone/pdaphone scene every day, and this website is one of the more prevalent sources of information. Old apps that may or may not work are just going to create problems for newer users if they do not work; and add more unnecessary questions being asked in the forums. When validating a new configuration, it is best to use the latest components that are available unless there is a specific reason for using older components; weather its on a pda or otherwise. New users don't always think of that, or think to search for a newer version, but instead post complaining that X component does not work and ask how to fix it. Leaving things like this buried saves those problems.
And if you like a application or enhancement that much it is not difficult to look for the most updated version you can find, state that its a great app, state that you have posted the most updated version available to you, and state the relavant revisions of radio firmware or OS rom you have validated the component on.
Food for thought
food for thought...i like that
Swype Voice Input Button Coming Soon – Already Present On Samsung Galaxy S And Motorola Droid X
Is this true? Is there a way to get to voice input from the Swype keyboard? If so.... I can't find it.
Edit: I posted this to the wrong forum. Mods... Please move it to General or Development.
unfortunately the easiest way I found to do it is to press and hold on the input line, click "input mode" and then select the Android KB. Kind of a pain, but it works in a pinch.
I am curious as to where that info came from. Would that function have been removed on the T-Mobile version for some reason?
Its not on the Captivate either. But it IS on the Droid X.
Pneumatic said:
Swype Voice Input Button Coming Soon – Already Present On Samsung Galaxy S And Motorola Droid X
Is this true? Is there a way to get to voice input from the Swype keyboard? If so.... I can't find it.
Edit: I posted this to the wrong forum. Mods... Please move it to General or Development.
Click to expand...
Click to collapse
directly from swype's forum...
http://swype.uservoice.com/forums/55960-swype-for-android-beta/suggestions/530365-voice-input-button
Well, they have it for other phones so you could potentially pull it from another phone (such as the Droid X) and drop it onto yours
If you search, you will find posts by me detailing how to do it. I even fixed some colors to make it easier to use. You pull it from an EVO rom dump and overwrite the one on your phone. Simple. I don't feel like typing it out again.
ttabbal said:
If you search, you will find posts by me detailing how to do it. I even fixed some colors to make it easier to use. You pull it from an EVO rom dump and overwrite the one on your phone. Simple. I don't feel like typing it out again.
Click to expand...
Click to collapse
Yes I been using this for a little while now no issues.
adm1jtg said:
Yes I been using this for a little while now no issues.
Click to expand...
Click to collapse
And you're not gonna link or upload or help at all? Sad..
beckhamsoccerman said:
And you're not gonna link or upload or help at all? Sad..
Click to expand...
Click to collapse
And you're not going to search at all? Also sad.
We can't upload it. XDA has banned all Swype APKs as they got threatened by the Swype company. So you need to find it yourself. It's really not that hard, google will turn it up. It kind of sucks to have to download a ROM dump for a small file, but that's copyright for you. If you look hard enough, you should be able to find a copy of just the APK on Rapidshare or similar. It seems people post them frequently enough.
Ask the Swype people to quit being morons so we can share the files directly. Or to just release a version for the Vibrant. It's not like the phone can't support it, I use it all the time. They probably want TMobile to pay more for that feature or something like that. It would be nice if they would just put it in the Market and let users choose to pay for it themselves if they want to.
http://forum.xda-developers.com/showthread.php?t=742084&highlight=swype+voice
ttabbal said:
And you're not going to search at all? Also sad.
We can't upload it. XDA has banned all Swype APKs as they got threatened by the Swype company. So you need to find it yourself. It's really not that hard, google will turn it up. It kind of sucks to have to download a ROM dump for a small file, but that's copyright for you. If you look hard enough, you should be able to find a copy of just the APK on Rapidshare or similar. It seems people post them frequently enough.
Ask the Swype people to quit being morons so we can share the files directly. Or to just release a version for the Vibrant. It's not like the phone can't support it, I use it all the time. They probably want TMobile to pay more for that feature or something like that. It would be nice if they would just put it in the Market and let users choose to pay for it themselves if they want to.
Click to expand...
Click to collapse
Found it with some digging.. wish you would have said that you cant swype with it.. now I'm stuck with this till I go find the vibrant one. Not compatible wrong screen size, but voice does work..
beckhamsoccerman said:
And you're not gonna link or upload or help at all? Sad..
Click to expand...
Click to collapse
Posting swype is against XDA forum rules. I have used the above mentioned swype with both stock and oc4 kernals and not had issues. What I had to do was change the default keyboard to something other then swype, ADB push the new swype file, run the no yellow metamorph.
Since apparently BN is still changing framework.jar, I'm making a thread to allow separate updates/downloads. framework.jar for 1.0.0 is already in market hack/autonooter/autoconfig
1.0.0 - http://www.mediafire.com/?1wb78ollpb1bd78
1.0.1 - http://www.mediafire.com/?37fugab7xo8s3j3
This framework.jar helps you get an Android ID when you first run the Market. You can replace it with the stock version once your market is working if you want, but leaving it shouldn't cause any issues either.
Um, this thread is remarkably empty.
Thank you for your work!
Not having to generate ID's manually is better than awesome ...
What did you have to change in Framework.jar I know your hacked version works. I'd just like to understand why.
johnopsec said:
What did you have to change in Framework.jar I know your hacked version works. I'd just like to understand why.
Click to expand...
Click to collapse
Google requests a valid phone ID and phone type when assigning an Android ID. Tablets tend to have neither, so Google doesn't assign an ID. It spoofs a valid phone type and ID so that Google is happy and will send you back an ID.
clockworx said:
Google requests a valid phone ID and phone type when assigning an Android ID. Tablets tend to have neither, so Google doesn't assign an ID. It spoofs a valid phone type and ID so that Google is happy and will send you back an ID.
Click to expand...
Click to collapse
Thanks. That makes sense now.
Can somebody post the stock version of either of the two files from the OP? I'm trying to get this working on the eLocity tab and, since I'm no developer, I need to compare the two files to see what Clockworx change... and therefore, what I should try changing in our framework.
Thanks!
Billy
JeepFreak said:
Can somebody post the stock version of either of the two files from the OP? I'm trying to get this working on the eLocity tab and, since I'm no developer, I need to compare the two files to see what Clockworx change... and therefore, what I should try changing in our framework.
Thanks!
Billy
Click to expand...
Click to collapse
If you want to post your framework.jar, it would probably be faster.
clockworx said:
If you want to post your framework.jar, it would probably be faster.
Click to expand...
Click to collapse
Fine by me! I was tying not to be a bother
http://www.slicky.net/android/elocity.a7.framework.jar
Thanks a bunch!
Billy
JeepFreak said:
Fine by me! I was tying not to be a bother
http://www.slicky.net/android/elocity.a7.framework.jar
Thanks a bunch!
Billy
Click to expand...
Click to collapse
Here it is if you want to take a shot.
http://www.mediafire.com/download.php?dd9zif5h89ve7mz
I would back up your stock one and ensure you can restore it, just in case.
This might not be the place or already covered, but is it possible to make the big button in the notification bar not pop up the B&N Soft Buttons? I tend to hit that far too often.
Personally if it was gone, or did nothing, I'd be happy. I can launch the apps from ADW myself, they're all individual apps anyway.
clockworx said:
Here it is if you want to take a shot.
http://www.mediafire.com/download.php?dd9zif5h89ve7mz
I would back up your stock one and ensure you can restore it, just in case.
Click to expand...
Click to collapse
Awesome man! Thanks a bunch!
Billy
clockworx,
can i replace framework.jar from slide_update.zip (BN 1.0.1) with yours
and also what i said in your other thread (supernooter) and then flash the ereader.
I am asking too many questions as i dont want to end up with an over sized 7" ice scraper...
I'm in the same spot as JeepFreak, but mine's a Cruz Reader.
If i upload the framework.jar can you mod it?
P.S. its Eclair-2.0 otherwise i'd try and use an existing copy off the web.
Skwurlsoft said:
I'm in the same spot as JeepFreak, but mine's a Cruz Reader.
If i upload the framework.jar can you mod it?
P.S. its Eclair-2.0 otherwise i'd try and use an existing copy off the web.
Click to expand...
Click to collapse
Are you using a custom firmware for it? I could have sworn someone had already done it for the CR over at Slatedroid. If not, feel free to upload and link.
Skwurlsoft said:
I'm in the same spot as JeepFreak, but mine's a Cruz Reader.
If i upload the framework.jar can you mod it?
P.S. its Eclair-2.0 otherwise i'd try and use an existing copy off the web.
Click to expand...
Click to collapse
We actually ended up getting the eLocity going without using the modified framework.jar.
Billy
clockworx said:
Are you using a custom firmware for it? I could have sworn someone had already done it for the CR over at Slatedroid. If not, feel free to upload and link.
Click to expand...
Click to collapse
nope, stock firmware, I've been trying to re-create the custom firmware that Velocity Micro made for it, but I'm having trouble figuring out exactly what settings they used for the kernel config. I'd like to eventually roll my own firmware image and update the device to either Éclair-2.1 or Froyo-2.2, but that will be awhile.
Until just now I'd never heard of Slatedroid, so i wouldn't know if anyone has succeeded over there or not. I've tried searching using Yahoo, Google and others to no avail, so...
here's the framework.jar, pulled from the most recent firmware update
(version 091257)
'mediafire'/?c76hrb1awmtc4mq
sorry 'bout the link being butchered, I'm a new user and it won't let me post links.
thanks in advance
Edit:I found the post at Slatedroid, but he's using a modded Cruz 102/103 Tablet firmware with Éclair-2.1, and until I get my own rom cooked, I'm going to try and stay as 'stock' as possible. besides, i don't know if the Cruz 103 firmware will work on the reader.
On another note, would it be possible to pre-mod the file in question if you were building from source?
and if so, what modifications would need to be made?
clockworx said:
Google requests a valid phone ID and phone type when assigning an Android ID. Tablets tend to have neither, so Google doesn't assign an ID. It spoofs a valid phone type and ID so that Google is happy and will send you back an ID.
Click to expand...
Click to collapse
I am working with others in another thread to determine why nootering the NC removes the access to B&N instore features.
We have been trying changes to the build.prop file but this does not seem to help. My thought is that something is changed in the framework.jar file that when instore B&N checks to see if the device is a NC. Is this a plausible thought? Can you share what lines in the hacked framework.jar are different that the stock NC framework.jar? Would it be possible to change these lines back to stock after nootering to gain access to the instore features?
Also, could changes in framework.jar also expalin why the market on NC does not have access to some apps?
nikto34 said:
We have been trying changes to the build.prop file but this does not seem to help. My thought is that something is changed in the framework.jar file that when instore B&N checks to see if the device is a NC. Is this a plausible thought?
Click to expand...
Click to collapse
Anything is possible since we don't know what they're doing, but it seems unlikely BN would check phone type and phone ID when on a regular nook they probably both return "invalid". Before you go through the trouble of investigating deeper, I suggest taking the engineering approach and change one variable: push back a stock framework.jar and see if the store works. If it does, then it's the framework.jar. If it doesn't, then it's something else.
nikto34 said:
Also, could changes in framework.jar also expalin why the market on NC does not have access to some apps?
Click to expand...
Click to collapse
No, that would be the fingerprint needed in build.prop, which I thought had already been solved and was part of Autonooter.
clockworx said:
Anything is possible since we don't know what they're doing, but it seems unlikely BN would check phone type and phone ID when on a regular nook they probably both return "invalid". Before you go through the trouble of investigating deeper, I suggest taking the engineering approach and change one variable: push back a stock framework.jar and see if the store works. If it does, then it's the framework.jar. If it doesn't, then it's something else.
No, that would be the fingerprint needed in build.prop, which I thought had already been solved and was part of Autonooter.
Click to expand...
Click to collapse
Thanks for the idea! Do you have or know where to find a stock framework.jar?
As for the fingerprint issue, we have tried returning the rooted NC fingerprint back to the stock fingerprint with no success. When replicating the stock build.prop file on a rooted NC, instore features still do not work and some apps are still not available in the market.
Hello folks
I want to create live wallpapers for sale on the android market. I found a custom creator script and a lwp creator software that does this but I don't think it signs them. Now I am not sure if those could be sold on the market or not. I am still very new to android.
At the moment I am trying to start small, something simple like a looped animation sequence and make that a live wallpaper...just plain, with no settings. So what would be a good way to approach this mission ?
You could try this: http://forum.xda-developers.com/showthread.php?t=739512. You could even try to make them on your phone with this: http://android.ownskin.com/livewallpaper.
Can I sell the apk that I get from custom creator or is there something I need to do before I upload it.
retareq said:
Can I sell the apk that I get from custom creator or is there something I need to do before I upload it.
Click to expand...
Click to collapse
Make sure it's signed.
That's all ? Man thats simple. Here I was readying myself thinking I'm gonna need to brush up my old coding skills. Very nice. Thanks guy.
I would like to pack 2 live wallpapers in one apk. Is this possible ?
No, it's not unless you make an app which will allow selection of whichever one the user wants.
That sucks. I figured I'd provide 2 wallpapers as a pack for $0.99 because they are simple with no settings. There is no other way ?
I suppose I'll start with single ones and then eventually make an app.
Ok so I did some experiments, first apk was 80mb, second was 40mb and the newest one is like 400kb only. But it lags a lot. How do I optimize ?
retareq said:
Ok so I did some experiments, first apk was 80mb, second was 40mb and the newest one is like 400kb only. But it lags a lot. How do I optimize ?
Click to expand...
Click to collapse
Have you tried zipaligning them? See here: http://developer.android.com/resources/articles/zipalign.html.
I am just beginning installing eclipse and the steps that follow. I am still not sure how to open the apk to view what the code is. I was hoping I could see this code and then implement it in eclipse using a fresh project. Main thing I want to find out is how the image sequence loading is implemented. I guess I will post back here in a few days.
Should I code this in ICS or get the sdk files for 2.1 and do it on that ?
retareq said:
Should I code this in ICS or get the sdk files for 2.1 and do it on that ?
Click to expand...
Click to collapse
It depends on what you want. If you only want ICS (and later android versions to come) devices to support your wallpapers, then you can go ahead and code it in ICS. If you want a wider range of support (for now), then your 2nd option is best.
Well ideal case would be its backwards compatible. I've been reading and says ics has new api's...but I'm hoping the wallpaper and related services are backwards compatible. Its okay if its not, I get to learn at least.
retareq said:
Well ideal case would be its backwards compatible. I've been reading and says ics has new api's...but I'm hoping the wallpaper and related services are backwards compatible. Its okay if its not, I get to learn at least.
Click to expand...
Click to collapse
It sure does, but most of them are not backward compatible. Notice only a few (approximately 3) apps built for ICS worked on Gingerbread so the chance is very small that they will support backward compatibility. They may be the same services, etc., but many will still require the ICS+ framework.
Interesting...so that means its safer to start from 2.1 for more than just backwards compatibility reasons. I just tried to grab api7 in sdk manager and it gave me error for file not found. Should I do 2.3.3 ?
Fixed it, 2.1 ready to go. Thanks.
Live wallpapers are now at
http://forum.xda-developers.com/showthread.php?t=1408528
This thread has served its purpose. Request mod to lock it.
hello,
am on miui 11.0.5.0 global and was able to remove the stock mi browser(v10.....etc).
am trying to install an older version of mi browser that had better features than newer versions , it installs but keeps closing everytime i open it!
is there any workaround to make it work?
I know I'm not answering your question.
But why exactly do you prefer to use a browser filled with ads and junk?
Alrich said:
I know I'm not answering your question.
But why exactly do you prefer to use a browser filled with ads and junk?
Click to expand...
Click to collapse
I was wondering that too
Poco launcher gives you a neat way of hiding those bits of xiaomi scurf that you can't uninstall - why not just do that and browse with Iron or something better?
Alrich said:
I know I'm not answering your question.
But why exactly do you prefer to use a browser filled with ads and junk?
Click to expand...
Click to collapse
the older version am talking about has no ads and its the only version that has the feature am lookin for!
thesoupthief said:
I was wondering that too
Poco launcher gives you a neat way of hiding those bits of xiaomi scurf that you can't uninstall - why not just do that and browse with Iron or something better?
Click to expand...
Click to collapse
I never said i cant uninstall it.....read reply #4
Regardless of ads or not, why do you still insist on using a inferior browser when there are so many others out there that do a better job.
Alrich said:
Regardless of ads or not, why do you still insist on using a inferior browser when there are so many others out there that do a better job.
Click to expand...
Click to collapse
i already mentioned the cause above!......the old version am talking about has a certain feature that isnt working anymore in new versions!.
All you mention is "the feature I'm looking for" or the "cause I'm looking for"
There's no direct mention or explanation of what you're looking for. Maybe more people will help you if you choose to explain a bit more rather than shut down every comment that's trying to help you.
Alrich said:
All you mention is "the feature I'm looking for" or the "cause I'm looking for"
There's no direct mention or explanation of what you're looking for. Maybe more people will help you if you choose to explain a bit more rather than shut down every comment that's trying to help you.
Click to expand...
Click to collapse
the reason for posting this topic is to get help regarding running an older version of miui browser that installs but closes everytime i open in oreo/pie/q ......it runs fine on other android phones on nougat!!.
specifying the feature thats working on this old browser and not working on recent versions wont help coz poeple who "try to help" would simply recommend using other newer versions or even different browsers!!
if i wanted to shut comments ....i would have simply ignored any replies without a direct solution!!.
Okay, so you know how it works in the software world. Nobody codes everything from scratch. What we do is build upon the work of others to get what we want. Your previous browser would have been built with various libraries that it hooks into to provide different functionality. Now a new one has come out which was installed on your fone and this is using later versions of the libraries and possibly some APIs may have been dropped. So you're trying to use the old browser with the new libraries and it's entirely possible that the APIs/ABIs it needs are no longer available. So you're SOL. You're going to have to run your browser in debug mode to see what's wrong. I hope it works out for you.
Sent from my Galaxy Tab S5e using XDA Labs
guhvanoh said:
Okay, so you know how it works in the software world. Nobody codes everything from scratch. What we do is build upon the work of others to get what we want. Your previous browser would have been built with various libraries that it hooks into to provide different functionality. Now a new one has come out which was installed on your fone and this is using later versions of the libraries and possibly some APIs may have been dropped. So you're trying to use the old browser with the new libraries and it's entirely possible that the APIs/ABIs it needs are no longer available. So you're SOL. You're going to have to run your browser in debug mode to see what's wrong. I hope it works out for you.
Sent from my Galaxy Tab S5e using XDA Labs
Click to expand...
Click to collapse
ok,this is what i call a helpful reply :good: