Edit: This fix is defunct as of the current OTA. For a working version of this software (Thanks Steal25!) check out the thread here: http://forum.xda-developers.com/showthread.php?t=1947686
I'll be requesting this thread be closed at this point, though I'll leave the files for anyone still on older software versions. It's served it's purpose. Thanks everyone!
Original post:
There are a number of build.prop edits out there for various fixes. One such edit gives back the ability to make a choice of what program you want for a specific action. This was removed by HTC due to Apple claiming a patent infringement of patent #5,946,647. This patent is what caused the Evo 4G LTE to be stuck in customs.
Due to the nature of build.prop files containing many areas that can be tweaked, ROM devs tend to make different tweaks between ROM's. Until now this could have caused issues.
This script makes a backup of your current build.prop, and then EDITS IT IN PLACE.
What does this mean? It means you can flash THIS file on ANY ROM on this phone and it will not mess up any tweaks your specific ROM dev has put in place.
Why is this important? There are a number of build.props edited with this fix (and others)...some of them are from the stock ROM and some are from various other custom ROMs. Simply copying one over your current build.prop could lose you important optimizations, or custom fixes your dev has set up. By flashing this script you keep those customizations and still get the benefit of having your choices back.
Instructions:
To tell if this edit worked for you, check in settings. If the app associations menu option is gone, then it worked.
You will need to clear defaults for specific programs in order to have a choice pop up.
Example:
If you have selected Chrome for your default browser in app associations, you will need to go to menu/settings/apps/downloaded/Chrome/clear defaults.
The next time you tap a URL you will have a choice of which browser to use.
Credits:
Thanks to iconeo for the original thread found here: http://forum.xda-developers.com/showthread.php?t=1693809
Thanks to Steal25 for the actual build.prop edits.
I am including two zip files. The first one will make the build.prop change to allow you to choose your own defaults.
The second one (HTCLinkify-revert.zip) will allow you to put your build.prop back to its default.
There are other build.prop edits out there and I will be creating ROM agnostic flashable zips for those as well.
Please let me know if there are any issues with this flash.
Edit: I have uploaded a new zip that should work with the latest OTA.
nice man
so people can flash this and still keep their tweaks
loving the support this phone is getting
flex360 said:
nice man
so people can flash this and still keep their tweaks
loving the support this phone is getting
Click to expand...
Click to collapse
Yep, exactly. For people that have a hard time editing build.prop on their own, this will do the trick.
Plus it's the easiest way to re-implement the fix if your ROM dev updates the ROM but doesn't include it by default.
So I'm guessing you can only use this if your phone is rooted right ?
Sent from my Xoom using xda premium
MRFERRARI23 said:
So I'm guessing you can only use this if your phone is rooted right ?
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
You can only manually edit the build.prop if you're rooted to begin with, so even if you choose not to do it this way, you'll still need root to make the change yourself.
To flash the zip requires root and unlocked bootloader since you need a custom recovery to flash zips.
Made a correction to the first post. It was Steal25 who came up with the original build.prop edit, not SteelH. Sorry Steal25!
Mines ready fixed by me. But still, thanks mass for this.
Edit: thinking about this makes me realize just how bad apple effd HTC. I mean, if I was one of the vast majority of users who dont root and just buy a phone and leave it how it is, I would honestly probably return this device and buy something different. And that would be hard because i love HTC and this device. But, removing the 'complete action using' dialog is just not something I could live with. Apple really, really, screwed HTC... and end users. :screwy:
Sent from my EVO using xda premium
It's fantastic, thanks man.
I've been following this issue, and it seems the build.prop fix also works for other HTC ICS phones. I assume this flashable zip would work for those phones as well, correct? Since it's editing in place, seems like it should work for all (One X, One S, Amaze 4G, etc.).
thanks, was looking for this mod
oryan_dunn said:
I've been following this issue, and it seems the build.prop fix also works for other HTC ICS phones. I assume this flashable zip would work for those phones as well, correct? Since it's editing in place, seems like it should work for all (One X, One S, Amaze 4G, etc.).
Click to expand...
Click to collapse
It should, yes. However I only had an Evo 3D and an Evo 4g LTE to test on, so I can't support other phones.
But as long as build.prop is in /system and contains the line ro.da1.enable=true this script should work.
Again though I can't test, so you're on your own.
Edit: One thing though: You'll need a modified updater-script. Right now I have 2 versions of this zip, one for Shooter (Evo3D) and one for Jewel (E4GLTE).
You'll need to modify the line at the top of updater-script to your own phone's model:
getprop("ro.product.device") == "shooter"
Replace "shooter" with "jewel" for the E4GLTE for example. Or you could simply remove the line. Should work fine without it.
Ok, I may be asking a lot...
But I'm not familiar with editing the script lines,
Could you possibly either make a zip with the jewel edit in place?
Thanx
Sent from my LtEvo using XDA
KaptainRandom said:
Ok, I may be asking a lot...
But I'm not familiar with editing the script lines,
Could you possibly either make a zip with the jewel edit in place?
Thanx
Sent from my LtEvo using XDA
Click to expand...
Click to collapse
This one already has jewel. If you want it for another device I can make a quick update for you, just let me know the device name. Or if you want to test it without the device check line I'll pull that for you and you can test it that way.
Many thanks for this. Although i was able to modify fue build prop myself, i did have a hard time. Everytime i edited the build prop with root browser it made a copy of itself . Confusing stuff. Finally sorted it with SM mánager.
Anyways this is much easier for someone with my skills
Thank you
SENT FROM MY EVO LTE USING XDA
corcgaigh said:
Many thanks for this. Although i was able to modify fue build prop myself, i did have a hard time. Everytime i edited the build prop with root browser it made a copy of itself . Confusing stuff. Finally sorted it with SM mánager.
Anyways this is much easier for someone with my skills
Thank you
SENT FROM MY EVO LTE USING XDA
Click to expand...
Click to collapse
Not a problem. It will come in handy later if your ROM dev makes an update. Just flash and go.
This worked flawlessly for me. It's SO nice to have the features back that I was used to on previous devices. Thanks!
OstrichSak said:
This worked flawlessly for me. It's SO nice to have the features back that I was used to on previous devices. Thanks!
Click to expand...
Click to collapse
Glad it did the trick for you.
smw6180 said:
Glad it did the trick for you.
Click to expand...
Click to collapse
No, thank you!
Will we ever be able to long press pics in the browser and have the menu come up with share with (list of programs)
It works now!
Sent from my EVO using xda premium
Related
I compiled my first ROM from source FRF91 for N1 w/root su+busybox+de-odex+gapps. The time of my AOSP -b master sync was around 9:00a pst, 07/10/10. This is not a "kang" of Modaco or CyanogenMod but I credit both and all teamdouche since I regularly need to look into their work to teach myself. Thank you dferreira and jr33 for not flaming my many noob questions and also thanks to dsixda for his reqularly updated android kitchen.
I still can't do much customizing and adding features because I still have to get better at too many things...sorry. Feel free to report bugs and I hope some of you could tell me how to fix simple things or add features by directing me to resources.
I am using themes by micromod777 for FRF91 that do work on this ROM.
Added:
Original Boot Animation (aka Holiday)
APN list
Trackball wake/unlock (crimsondr)
NFL app (jlevy73)
AccuWeather widget (allows multiple locations)
Logger app (michael.novakjr)
If you don't have the new radio installed, fastboot flash radio first.
Flash the ROM .zip after full wipe.
Remember to to do a nandroid backup first.
Radio Download >>> 3321c196d8ec1cf748fd20c3c4068520 32.36.00.28U_4.06.00.12_7 radio.img
(Fastboot flash using "fastboot flash radio radio.img")
ROM Download >>> 6af5516125105c92d8a3d87c6110defc shameless_aosp_frf91_1.0_signed.zip
...saved...
Really had to bump your Rom because no one was using it? nice...
nopenope said:
Really had to bump your Rom because no one was using it? nice...
Click to expand...
Click to collapse
Why this kind of comments? Do u think they help in anyway?
Sent from my Nexus One using Tapatalk
He's also the kind of guy who knows nothing other than wipe & flash and has nothing positive to offer the community... =/
nopenope said:
Really had to bump your Rom because no one was using it? nice...
Click to expand...
Click to collapse
no... i bumped it because i had an old post that i wanted to re-title and use. that post had no replies so i recycled it. why the hate?
Quick84 said:
He's also the kind of guy who knows nothing other than wipe & flash and has nothing positive to offer the community... =/
Click to expand...
Click to collapse
thanks for trying out this rom guys. it is not a cut-n-paste. i really did compile from source. it took 5 alphas to get to this release. it is like a hobby for me to try and solve puzzles and that's how i tackled making the rom. i have zero programming knowledge and have fun relaxing trying to follow steps in a process to accomplish a goal.
When will you work on your desire rom project again? We really need someone to work on desire port beside paul. hopefully you can challenge yourself and make that desire rom perfect.
lpasq said:
no... i bumped it because i had an old post that i wanted to re-title and use. that post had no replies so i recycled it. why the hate?
Click to expand...
Click to collapse
If you added stuff then cool but just the post saying *bump* not added new things to first post makes it seem that you just wanted your post to the top again. And to the guy who says i've never done anything for this community you might wanna change that and then your post well what have you done. my reply is don't worry its more then you'll ever. SO props to the update then
nopenope said:
If you added stuff then cool but just the post saying *bump* not added new things to first post makes it seem that you just wanted your post to the top again. And to the guy who says i've never done anything for this community you might wanna change that and then your post well what have you done. my reply is don't worry its more then you'll ever. SO props to the update then
Click to expand...
Click to collapse
thank you. ...not an update though. it's a source build compile. the post i recycled had a paste-n-bake kang of an early aosp 2.2 that chris soyars put out via a tweet... ...and hundreds of people downloaded it but not one person posted a reply since i made clear i simply was passing it along.
so you know... i think the other flame was also intended for me...not you.
not bad! gonna give this a shot!
How about compiling Stk.apk and extract the dictionaries from the LatinIMEGoogle.apk and putting them in the corresponding locations in your LatinIME source. That will get you more layouts than the Google keyboard and still all the features since they have now been included in the AOSP version. The Stk.apk (SIM Toolkit) is also useful for a lot of people, and only work AOSP based roms, and might possibly drive more people towards this rom if they want the stock experiance.
It should simply be a matter of running 'make -j4 LatinIME' and 'make -j4 Stk' with the -j flagset to your number of cores + 1 or 2.
blunden said:
How about compiling Stk.apk and extract the dictionaries from the LatinIMEGoogle.apk and putting them in the corresponding locations in your LatinIME source. That will get you more layouts than the Google keyboard and still all the features since they have now been included in the AOSP version. The Stk.apk (SIM Toolkit) is also useful for a lot of people, and only work AOSP based roms, and might possibly drive more people towards this rom if they want the stock experiance.
It should simply be a matter of running 'make -j4 LatinIME' and 'make -j4 Stk' with the -j flagset to your number of cores + 1 or 2.
Click to expand...
Click to collapse
I shall pm you prior to attempting so I can get clarification on any questions I may have. Thank you.
Sent from my Nexus One using XDA App
I'm working on the same kind of project you are. The problem I'm running into is that every app that tries to access GPS location FCs on me. Did you ever come across this? Maps won't run at all, and I've had to set my homepage to something other than Google since it FCs the browser when it calls for location. I've got a working build otherwise!
RMGeren said:
I'm working on the same kind of project you are. The problem I'm running into is that every app that tries to access GPS location FCs on me. Did you ever come across this? Maps won't run at all, and I've had to set my homepage to something other than Google since it FCs the browser when it calls for location. I've got a working build otherwise!
Click to expand...
Click to collapse
Very cool that you have a working build environment. What OS are set up in?
I do not get the error you describe. Run a logcat either with ADB or using Logger from Market. Reading the log makes it easier to ask for help based on the specific errors. That is what I do. Ask the pros for advice. Some are helpful. Most ignore us noobs.
I am happy to offer whatever help I can as a rookie. Just PM me.
From N1 via Tapatalk
lpasq said:
thanks for trying out this rom guys. it is not a cut-n-paste. i really did compile from source. it took 5 alphas to get to this release. it is like a hobby for me to try and solve puzzles and that's how i tackled making the rom. i have zero programming knowledge and have fun relaxing trying to follow steps in a process to accomplish a goal.
Click to expand...
Click to collapse
I'm in the exact same boat, just jumped into android about a month or two ago with my nexus (from an iPhone 2g, no less lol), ain't no turning back now
I'm also building a rom from source, more as a side-project to better familiarize myself with Android, but if it turns out well then that's always a plus.
Good luck on your rom!
wdfowty said:
I'm in the exact same boat, just jumped into android about a month or two ago with my nexus (from an iPhone 2g, no less lol), ain't no turning back now
I'm also building a rom from source, more as a side-project to better familiarize myself with Android, but if it turns out well then that's always a plus.
Good luck on your rom!
Click to expand...
Click to collapse
it is nice to know that other "hobbyists" are playing with aosp and the tools used to make roms. much success to you my brother
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.
This post is still working, but has not and will not be updated as I and the other contributors no longer have this device. I welcome questions as always, but without the device in my hand, I may not have your answer.
There are people still actively trying to update the software for this device as of 1/15, and if anyone wishes to take over/update this thread PM me.
It was a great ride with the amaze, and I still feel like the camera puts much newer devices to shame to date.
The ultimate(but now *retired* guide to everything Amaze-ing!
Credits given at the end of this post.
Table of contents - clicking the following links will take you to that specific part of the BIBLE!
1. General Tools
2. General How-to’s: the information needed most commonly- adb, fastboot, bootloaders, etc
3. ICS Specific: How to switch from GB, list of all roms, kernels, how-to’s specific to ICS
4. Gingerbread Specific: An archive of information about everything needed for gingerbread(outdated OS)
5. Battery Tricks: A variety of ways to save on battery, troubleshoot, measure, etc. Updated soon!
6. Misc Apps/Themes, etc Updated soon!
7. Troubleshooting/Miscellaneous: Useful Threads: Useful threads and those for troubleshooting known issues, archived(closed) useful threads, etc
8. Advanced Android 101: So you wanna go to the next level? You’ve read, and read, and read.. how do you do something much more difficult? Compiling/Decompiling, signing, baksmali, misc tools, and more..
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Advanced features of google docs!
Anyone viewing the document can click in the top right hand corner where is says "# other viewers" if anyone else is viewing- there is a chat box there that can me used.
I've allowed people who access from this thread to make COMMENTS in the doc - highlight some text, right click and click add comment - do NOT abuse this, I can turn this off. If you believe you can help clarify information or add a link, that is the best way to!
Contributor have full edit - I will put some advanced functions for you in post #3
Click to expand...
Click to collapse
We can expand upon this at ANY time, if something should be added, please let us know.
You can save or view this doc via the google drive app on your phone!(edited for proper formatting!)
You can ALL be contributors! See something that is missing the link, let us know so we can add it. Want to write something up you feel we have missed, or feel that information is not up to date - write up in this thread and we can directly link to that! Have battery tips, or specific apps, themes.. you name it - this bible is going to eventually cover everything about the amaze and any nooby question ever asked with your help!
We will likely have kernel source drop soon and we will have even more to keep track of, so we will need some serious help from the community to make sure we are all organized as possible!
All future efforts will go into updating the HTC Amaze 4G Wiki:
Amaze General Overview :http://forum.xda-developers.com/wiki/HTC_Amaze_4G This is the page to start updating!
Guides and Tutorials
Tools
Click to expand...
Click to collapse
ROMs, Kernels, Recoveries & Themes- Files for HTC Amaze 4G users and developers including things to cook, flash & customize with.
Stock Roms
Custom Roms
Custom Kernels
Custom Recoveries
Custom Themes
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Initial layout, content, and design by Silentbtdeadly, EclipzeRemix, GlacierGuy- other contributors welcomed!
Thanks to additional contributors: Dark Nightmare
We tried to link to all original work, if we wrote up any information you feel you need credit for or you can provide us to an up to date thread we can link to, just let us know!
Changed not added to wiki yet:
7-12
Added the first 4 posts under the Advanced Android 101 section to reflect some of the new "how to" develop threads.
Click to expand...
Click to collapse
Change log:
5-30-12
Other misc stuff added(instructions for canadian ICS carriers thanks to comment)
Added example of a smali/baksmali edit for advanced android 101 section 8
Added link to posts about "currentwidget" under battery tricks
Removed all tables from the document to make it viewable via the google drive app
Put longer "how-to's" from section 2 and put them at the end of doc to make section 2 more readable(and clickable)
Click to expand...
Click to collapse
5-29-12
Initial post
Everything has been filled out except battery tricks and misc/app themes
Added Dark Nightmare as a contributor
Added comments to sections that need improvement
Corrected links in OP to make sure they take viewer specifically to that part of doc
Added a Troubleshooting/Miscellaneous section for useful threads that don't fall into other categories, updated OP
Formatting of links
Information added to battery tips and General How-to section
What is S-off added
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Chars
Any new contributors added please post in the thread, your first post will be your change log, which I can use to keep change log updated.
Please let's try to stay consistent in formatting - no need to paste the actual XDA or external link, right click highlighted text and add link that way.
Please don't edit the table of contents box in the very beginning of the doc, it will break the links in the OP of this thread.
Let's make sure we only use red text for warnings and the important information that NEEDS to be read.
Clicking insert at the top gives us the ability to add in pictures, links, drawing, etc.. I am not opposed as long as it doesn't take up too much space and isn't confusing.
You CAN create separate docs if you think that posting here would be too difficult - just make sure when you are done with your new doc you click "sharing" in the top right, make it accessible to anyone with a link, but NOT with editing rights! Let's not use other docs unless it is going to be a VERY robust document with images and embedded youtube videos, etc.
You will see at the very end of the doc is an "expanded" version. I put a bookmark in front of each line(insert>bookmark), and then I highlight the text, insert>link and then click the bookmarks tab - choose the text that matches what you are bookmarking.. boom, done.
Easy sharing BBCode links for the Bible.doc and for this thread.
HTC Amaze 4g BIBLE- Google.doc Updated Often
The Ultimate Guide to Everything Amaze-ing!(Amaze 4g BIBLE!)
ChangeLog:
05-29-2012
-Added to General How-To:
How to kill cap key backlights
-Added to battery tricks:
Download Juice Defender app and set it to disable wifi and data when screen is off. Spare Parts Pro works well to monitor what is draining your battery.
Turn off auto brightness and turn down screen brightness
Disable Haptic feedback
Use mod to disable capacitive keys. This also corrects light bleed.
Click to expand...
Click to collapse
Sent from my HTC Ruby using XDA_Premium
HTC Amaze 4g BIBLE- Google.doc Updated Often
The Ultimate Guide to Everything Amaze-ing!(Amaze 4g BIBLE!)
Chanelog:
05-29-2012
-Post on what is s-off added, links added to op.
05-30-2012
-How to install ADB/SDK,
-How to LOGCAT and how to LOGCAT as well via terminal emulator in the Android OS, links to be added to OP
-What is bootloader
-How to boot into bootloader/fastboot/recovery via simple method, hasoon's tool and adb
-How to use fastboot and basic fastboot commands added.
06-01-2012
-How to use ICS OTA files to update devices from GB
-Updated fastboot flash commands with hboot flash command
06-06-2012
-How to restore to stock Telus or T-Mobile ICS via Nandroid or Flashable zip for S-On Users.
-How to change bootanimation/downanimation/sound added.
-T-Mobile ICS OTA flashable zip added to restore to stock tutorial. Credits to R-M-S for this zip.
06-07-2012
-Flashable zips for T-Mobile ICS and Telus ICS to restore to stock via custom recovery, doesn't matter which now since it's flashable and not a nandroid, added to restore post.
06-08-2012
-New to the Amaze 4G? Here's the basics to begin with.
06-13-2012
-added fix to OTA update file tutorial for the ro.cid=00000, 111111 etc error
-How to instal the HQ camera mod for T-Mobile users and a note at the bottom for Telus users
06-14-2012
-How to Edit Build.prop, methods of file pulling and tweaks
06-26-2012
-Added stock recovery.img to restore to stock tutorial.
-Added stock flashable zip for mobilicity ics users
09-06-2012
-Some info added here and there
-Linked how to change font in the theme and apps sections of the bible document.
Coming soon
What do you want added?
Cleaned up my changelog/bookmarks
Click to expand...
Click to collapse
Clickable Bookmarks:
What is s-off/on
How to install adb/sdk and log cat
What is bootloader and how to access it, fastboot and recovery
How to use fastboot and basic fastboot commands
Tutorial to use the ICS OTA files to update from GB when getting the triangle error
Stock via nandroid or flashable zip
How to change bootanimation/downanimation/sound.
New to the Amaze 4G? Here's the basics to begin with.
How to install the HQ camera mod for T-Mobile users and a Note at the bottom for Telus users
How to Edit Build.prop, methods of file pulling and tweaks
Please don't use our work without the appropriate permission, if any of the candy found here is seen in any other basket, we will take steps to have it removed.
glacierguy said:
reserved for me.
Looks awesome SBD... Someone went to bed late
This needs to be stickied
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Oh, I was up till after 4am working on it, and sadly back awake at 6am.. sigh.
I just hope that people will start sending people to this thread when people need help getting started - it still needs some work, but soon this will answer almost every question someone could have when they get an amaze..
And yes, a sticky would be nice - especially since we will have plenty to keep this updated.
Update: Dark Nightmare has been added as a contributor. If you both can post changes you make to your first posts in the thread:
I.E. -
Updated speed rom in ICS roms - 5/29/12
Click to expand...
Click to collapse
Something like that, I'll update the second post based on those so people can see what has been added without going into the doc itself.
I think we finally have a chance at organizing all this knowledge we have floating around these forums!!!
This awesome, when the noobies come around we can just all simply send them this link which will provide everything they need an more good job!!
Sent from my HTC_Amaze_4G using XDA
fuego77 said:
This awesome, when the noobies come around we can just all simply send them this link which will provide everything they need an more good job!!
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
And I'm hoping if the noobies(lol, love the term btw) think there is something we can clarify(that actually would help), we can make the bible even better..
Any other sections you or anyone else can think of? I'm wondering about ways to link to other useful threads - even threads that are closed like the "issues with ICS thread" I had may be useful.. maybe a troubleshooting section perhaps? A misc resources section?
I think forum members will like that they can help with suggestions and hopefully see a useful and well organized final product..
Silentbtdeadly said:
And I'm hoping if the noobies(lol, love the term btw) think there is something we can clarify(that actually would help), we can make the bible even better..
Any other sections you or anyone else can think of? I'm wondering about ways to link to other useful threads - even threads that are closed like the "issues with ICS thread" I had may be useful.. maybe a troubleshooting section perhaps? A misc resources section?
I think forum members will like that they can help with suggestions and hopefully see a useful and well organized final product..
Click to expand...
Click to collapse
I think troubleshooting section would need the most work, most questions usually come from people who aren't really active users and find themselves stuck so then theyll post here.
Example "my phone is stuck on xxx after I xxx" etc
Sent from my HTC_Amaze_4G using XDA
fuego77 said:
I think troubleshooting section would need the most work, most questions usually come from people who aren't really active users and find themselves stuck so then theyll post here.
Example "my phone is stuck on xxx after I xxx" etc
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
Was thinking the same thing...
Sent from my HTC_Amaze_4G using xda premium
fuego77 said:
I think troubleshooting section would need the most work, most questions usually come from people who aren't really active users and find themselves stuck so then theyll post here.
Example "my phone is stuck on xxx after I xxx" etc
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
True, but if we find the answer to their issue, and it is common ENOUGH to be included, we can link directly to the post that fixes it, whether in this thread, or somewhere else.. no, we can't fix EVERY problem, but there are some standard ones that may be useful.. for example, what remix had to do to flash the RUU when his phone wouldn't accept a recovery - we could provide a few different links for anything useful like that for people having issues with the leak..
At the very least that was why I made it a Troubleshooting/Miscellaneous section, perhaps my closed thread on ICS issues may help someone out, even tho it is closed we can link to it.. or any other thread that has been archived but may be useful?
I'm kinda just thinking out loud here, trying to see what bases we can cover..
@SBD
G+ me... u have my email
@Peartfan40
Thanks for the sticky
Sent from my HTC_Amaze_4G using xda premium
glacierguy said:
@SBD
G+ me... u have my email
@Peartfan40
Thanks for the sticky
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Unless you have a totally different name than you do in the google doc, and a lot of tattoos.. I couldn't find you. My G+ is in my contact thing on here, you add me, lol.
And thanks Peartfan!
Silentbtdeadly said:
True, but if we find the answer to their issue, and it is common ENOUGH to be included, we can link directly to the post that fixes it, whether in this thread, or somewhere else.. no, we can't fix EVERY problem, but there are some standard ones that may be useful.. for example, what remix had to do to flash the RUU when his phone wouldn't accept a recovery - we could provide a few different links for anything useful like that for people having issues with the leak..
At the very least that was why I made it a Troubleshooting/Miscellaneous section, perhaps my closed thread on ICS issues may help someone out, even tho it is closed we can link to it.. or any other thread that has been archived but may be useful?
I'm kinda just thinking out loud here, trying to see what bases we can cover..
Click to expand...
Click to collapse
Yeah your right but knowing how noobies can get "I don't have time to be reading through dozens of pages to find my answer, can someone just tell me how to X" we've all seen this plenty of times. But I agree with you. Maybe getting some other threads cleaned up so things are straight to the point ? Idk man
Sent from my HTC_Amaze_4G using XDA
fuego77 said:
Yeah your right but knowing how noobies can get "I don't have time to be reading through dozens of pages to find my answer, can someone just tell me how to X" we've all seen this plenty of times. But I agree with you. Maybe getting some other threads cleaned up so things are straight to the point ? Idk man
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
Sure, there are a few that are like that, but I've dealt with many I like that are pretty sharp, things really are just hard to find at this point - or at least till this point hopefully.
If we give a lazy noob this thread we've already put a ton of time into and he wants more, then I can tell him to get *(#$ with a good conscience. But this should be great for people who aren't noobs, but might be overwhelmed - I remember I was in the beginning, trying to figure out s-off and this and that.. and I was never a noob!(lies.)
What is S-Off?
Well allow me to explain:
In their devices, HTC have installed a sort of security check whose level is determined by S-OFF/S-ON. Essentially, this security level is a flag stored on the device’s radio that checks signature images for any firmware before it is allowed to be written to system memory. This hinders using any custom ROMs, splash images, recovery etc., and also restricts access to the NAND flash memory. However, when security level is set to S-OFF, the signature check is bypassed, allowing a user to upload custom firmware images, unsigned boot, recovery, splash and HBOOT images, as well as official firmware that has been modified, this enabling maximum customization of your HTC Android device.
Furthermore, S-OFF also reduces restrictions on accessing the NAND flash memory on the device, allowing all partitions (including /system) to be mounted in write mode while the operating system is booted.
In simpler terms: s stands for security on and off being it's current status, on restricting your ability to write to certain partitions of the system, example: hboot. Also it usually restricts access to flash kernels while s-on but recoveries such as 4EXT recovery have the ability to bypass this while s-on, hence giving you the ability to flash full custom roms without the need of s-off.
S-Off on the other hand gives you practically full access to system partitions, enabling you to flash radios, hboots, just about everything. It also gives you the option to sim unlock your amaze for free (see general forum), gives you options as well to unbrick your device should you have a slip up while trying to flash a rom/mods to your device(search for the unbricking project in the dev forum).
How to obtain s-off? See JuopunutBear's s-off method in the dev section, super-cid is also recommended if you're a rom flasher who likes to test roms that may not be for your specific device, difference being T-Mobile, Telus and Wind versions of the Amaze 4G.
Source of introduction:
here
Sent from an Amaaaaaazing place :-D
When linking... There shouldn't be a reason why the links have to be listed (i.e. when giving rom links). If you see the first couple of GB roms, u will see I made hyperlinks, but whoever finished it did it differently. We should try to keep this organized and in similar formats from user to user, to make it clean and easier to read. Imho.
Sent from my HTC_Amaze_4G using xda premium
I know, I finished fixing the format of the ics roms that were listed.. some of it was a rush job, but at least most of the info is there until we perfect the format.
Sent from my HTC_Amaze_4G using XDA
We will likely need direction from this point on - someone asked about mobilicity carrier(VIA COMMENT in DOC) and someone else supplied the link, I updated thread-- this is a good way to keep it going.
Productive comments are welcome, as it says in the first post- highlight what you want, click insert then comment to leave us something helpful.. otherwise I hope it is helping people out(I don't see glacierguy, nightmare's, or my thanks button getting super mashed..?)
Anyways, it will never be complete, but we will need some direction to move forward and add more!
Tip for better battery
Current Widget
This is a free app available on the play store, there may be other apps that do the same thing.
See what is causing the most drain while you are actually USING the phone(as opposed to when screen is off- hint, use betterbatterystats for that)..
Steps to see which apps are killing your battery- do this when you get higher than average drain(delete previous log file called currentwidget.log in root of SD)
Put the widget on one of your homescreens, it will go to options screen..
An update interval of 60 seconds should be acceptable
Check(enable) the log file
Go into log options>check(enable) log applications
Use your phone as normal for a few days.. or when you've noticed worse drain.
Go back into the program and click log actions>analyze log,>top processes-- this shows you which app processes are using how much current - for example com.android.chrome(the google chrome app) was using 513MaH(milliampere-hour) - if you have the stock 1730mah battery that means that app alone could kill your battery in a little over 3 hours..
Once you have a list of which apps are causing the most drain turn off logging- that app itself will cause SOME drain, but it is worth using just to find out what is killing your phone!
This has been added to the BATTERY TRICKS section of the original google doc!
First of all - sorry for posting it here, i don't mean to be in your face, it's just all discussions about this topic in other threads or posts went nowhere and i also think it didn't get enough attention from the developers. So, i just wanted to start a new thread dedicated to just this feature, since i believe this is one of the most useful features which is somehow got missed in these devices.
I'm talking about the ability to use GP5 to make calls though and answer calls from other devices through bluetooth. I think it's nuts that Samsung didn't implement this feature in these players, since most if not all top range mp3 and media players from this manufacturer in the last 5-6 years have had this feature (my pretty basic 4 year old samsung mp3 player can do this easily). Some people wonder why i care about this, but in my opinion it is a killer feature, which really opens up so many different possibilities to these devices. Tablets with 3g and 4g are reasonably cheap these days, so more and more people buy them. When you have one of them, you naturally think about a possibility of making calls through it. I'm one of such people, i have a 10" 3g tablet and i would like to be able to call through it using my GP5.
I participate in 5-6 different forums dedicated to these devices (mostly european sites) and i see requests and questions from people about this feature almost on daily basis. I think there are hundreds of people out there who would love to have it in their GPs. What i know is that the new GP 3.6 and 4.2 have it and the older ones 4.0 and 5.0 don't. So, i'm begging you, somebody, please make a ROM with this feature! I have no experience in programming for Android, but i think it should be very easy to take code or a library or whatever it is from one device and put it into another, since all these players have pretty much the same hardware (to my knowledge).
Thank you for your attention.
I you can link to a 3.6 or 4.2 rom that I can pull from (can be stock, custom or whatever), I can possibly integrate it into my next release, although I give no promises. Also, as this is development, and this is slightly off topic, I recommend that you change your post tags to [Discussion][4.0, 5.0 US+INTL]Enabling handsfree calling, so that people understand that this is a discussion, not some random person begging for a feature.
Thanks for your reply, i'll have a look for such rom.
Ok, i've changed the tags of this thread. Thanks.
Thanks! I also meant the tags in the thread name, not the actual thread tags. I never use them, so I forgot .
Right, that's what i thought at first, but i see no way to change the name of the thread, unfortunately.
Right, that's what i thought at first, but i see no way to change the name of the thread, unfortunately.
Click to expand...
Click to collapse
Edit the first post and click on the button called go advanced. Its at the top of the page
Sent by my Robot Butler
ok, Mars11_ on this forum pointed me here ->source codes for samsung players, plus he also offered to get any files from his unrooted GP 3.6. Would any of this be of any help?
Supermaster34 said:
Edit the first post and click on the button called go advanced. Its at the top of the page
Sent by my Robot Butler
Click to expand...
Click to collapse
great, thanks for the tip, done.
Thanks for the link! I will try and play around with some of the stuff included and see if I can come up with something. It may be just as simple as installing an apk...
Or maybe swapping bt libs would be all it takes.
Sent using Tapatalk
hanthesolo said:
Thanks for the link! I will try and play around with some of the stuff included and see if I can come up with something. It may be just as simple as installing an apk...
Click to expand...
Click to collapse
oh, sweet, i'm all itching in anticipation! thanks mate!
this means the phone features also needs to be activated because it goes hand in hand im not a dev but im sure its more than installing an apk. i think this will also require some framework changes. also activating the sip calling feature will be very exciting as our SGP can sync contacts as well this can be done in galaxy note by just adb pushing some files to system dir and activating the hands free profile in htc flyer is as simple as editing the build.prop so im sure this is doable but we need to call in the attention of devs :good:
Bad news guys, the uncompiled image didn't help, and I was unable to open the .img that I pulled from a 3.6 rom. Could someone pull their entire /system directory (apply this terminal command: dd if=/dev/block/systemname of=/sdcard/factoryfs.rfs), and then pull it off their sdcard (internal) and upload it here (tar or zip it if you need to). I do not believe root is required for that, and I am able to access .rfs files to edit them. You can find the name of your system partition by punching in "mount" in the terminal and then finding /system in the output, and recording the partition name that follows (eg. my system partition on my 4.0 is /dev/block/stl9).
I was tinkering with my sgp amd found this if this might be of any help
Sent from my YP-G70 using xda app-developers app
Ok, I've just sent an email to Mars11_, who's recently offered his help with extracting files from his SGP 3.6 in this thread: http://forum.xda-developers.com/showthread.php?p=28558588#post28558588
I asked him to come here and follow your instructions. He's our only hope right now.
Got responce from Mars11_ that's what he said: "Okay, so I've run the commands Hanthesolo had, but I didn't have read access to /dev/block/mmcblk0p8 . So I need root, and second, I can't post in the Android Dev yet, as I don't have 10 or more posts. "
Well, hat pretty much means that I can't pull anything together untilthe 3.6 gets root (I guess I could create a guide for that, but I don't have a 3.6, and I cannot exract anything from it's .img images). Sorry about that, but as soon as a /systm dump is uploaded, I will get on it. A last ditch attempt may be to use adb, but I think that you must have root to get su access from it as well. Perhaps you can boot into stock recovery and adb push the superuser binary and apk, that is, if the stock recovery supports adb, as I believe /system is mounted as rw in recovery. Perhaps a signed update.zip that only has superuser? I dunno, just some theories for 3.6 devs.
Mate, you have absolutely nothing to appologise for, you've done everything you could. I'm grateful for you desire to work on this. I guess we'll just have to be patient and wait for the 3.6 to be rooted Thank you.
Well, thanks for giving me a project to work on, because my sumer has just about fizzled out! I look forward to working on this while I wait for my Nexus 7 to arrive, and with it some more time-consuming hobbies .
hanthesolo said:
Well, hat pretty much means that I can't pull anything together untilthe 3.6 gets root (I guess I could create a guide for that, but I don't have a 3.6, and I cannot exract anything from it's .img images). Sorry about that, but as soon as a /systm dump is uploaded, I will get on it. A last ditch attempt may be to use adb, but I think that you must have root to get su access from it as well. Perhaps you can boot into stock recovery and adb push the superuser binary and apk, that is, if the stock recovery supports adb, as I believe /system is mounted as rw in recovery. Perhaps a signed update.zip that only has superuser? I dunno, just some theories for 3.6 devs.
Click to expand...
Click to collapse
You can always try the korean system dump and see what it gives.
[MOD] [9/7/2012] AOSP Email attachment size 25MB from 5MB & ZIP restriction removed !
This will be my very first MOD I am posting.
After seeing how much cooler the AOSP Mail was over HTC Mail, and not to mention the extra security and certificates upgrades that the Exchange servers are going through. I decided to give it a spin.
My only let down was when i tried to attach a 8MB file, it FAILED and said that the attachment was too large..... WHAT A DEAL BREAKER.
Well, After doing some research I found out that the AOSP mail that has been out will only allow a 5MB attachment size.
I finally fixed the thing to allow up to 25MB of attachment size, b/c i was so frustrated with it, i did something about it and spent a lot of time hunting down things.
Below are three flashable zip files for your flashing pleasure.
AOSPMail_Exchange_25MB.zip is the modified AOSP with 25MB attachment size limit
OrigionalHTC_MAIL.zip will put back the original Mail.apk from HTC that came with the ICS Sense Global 3.6 - 4.03.605.2 update.
This one will assume that you flashed the AOSP mail with the Exchange.apk included in it. It will delete that Exchange.apk and put the original Mail.apk from HTC back in place.
AOSPMail_CM9_25MB.zip is the one for CM9 that was tested by someone to work with Kangs 9CM
Hope everyone enjoys and appreciates this ! I tested this out a couple of times on my Rezound and didn't have any issues using my hotmail account
A note about odex ROMS that are out there: You must delete Mail.odex in the \system\app folder to get this to work or you will get mail force close issues.
Any constructive feedback is appreciated! :good:
Don't forget to hit the thanks button if you like what i have done, and if you use my AOSP Mail.apk mod in your ROM please be sure to mention me.
Finally deciding to give back to the community in a small way at least; maybe a big one...
09/07/2012 - Added Mail for CM9 Kang with 25MB attachment limit.
12/16/2012 - Added the ability to download zip files now; zip restriction removed
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
AOSPMail&Exchange_25MB.zip MD5= dbb284d509ba1b6f5510b0d45eac8cd6
OrigionalHTC_MAIL.zip MD5= af22722cb557d8f8d327bc22926f3d76
AOSPMail_CM9_25MB.zip MD5= ac59315de142f9066df5172ffd58c3ab
this could be extremely useful to those who even use the email app.
Doesn't work on cm9 kang. Force close all mail apps now. Can't open
Sent from my ADR6425LVW using xda app-developers app
Great to have people who are making stuff. But, all I can say is Gmail.
Ohschit said:
Doesn't work on cm9 kang. Force close all mail apps now. Can't open
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Ok, it looks like the email for CM9 was modified in some way ( judging from file sizes, etc ) from the one that I modified,
I pulled out the email.apk from CM9 kang and made the necessary changes.
I need someone to test this for CM9 kang.
If this works I will post it in OP
10/05/2012 - posted in original post
Works! Thx!
Sent from my ADR6425LVW using xda app-developers app
Ohschit said:
Works! Thx!
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Rock! Glad it works. I will put in OP when I get a chance
Sent from my Rezound using xda app-developers app
Hi guys,
I installed the AOSP version through recovery and don't know where to find it. I have InsertCoin 9.6.3 currently. In the apps drawer I have the old Email HTC app.
Sorry for the noob question. Thanks.
nevrozel said:
Hi guys,
I installed the AOSP version through recovery and don't know where to find it. I have InsertCoin 9.6.3 currently. In the apps drawer I have the old Email HTC app.
Sorry for the noob question. Thanks.
Click to expand...
Click to collapse
The version in the zip replaces mail.apk in \system\app in case of NON CM9 roms ( sense base ),
insertcoin uses mail.apk so make sure you used the right one ( AOSPMail&Exchange_25MB.zip )
You could also use a program like root explorer to manually place the modified files in that location in system/app and set the permissions.
12/16/2012 - ZIP restriction removed
The zip restriction for downloading zip files has been removed
ENJOY
awesome email apk
does this bypass the exchange security measures? any or just PIN requirements? tried it and it doesnt but the email patcher does work.
the regular aosp didnt work with my jobs exchange server for whatever reason. i would get an error but the cm9 version did on my razr maxx(xt912)
its not often but when i do send larger files via email the only gripe i had has been relieved by your apk.
thanks a bunch.
soclean said:
does this bypass the exchange security measures? any or just PIN requirements? tried it and it doesnt but the email patcher does work.
the regular aosp didnt work with my jobs exchange server for whatever reason. i would get an error but the cm9 version did on my razr maxx(xt912)
its not often but when i do send larger files via email the only gripe i had has been relieved by your apk.
thanks a bunch.
Click to expand...
Click to collapse
well, i think that might be a little beyond me as far as removing those exchange security measures to be honest. This was/is my first mod.
I will look into it but i think i would require extensive code modification that i am just not familiar with at the moment.
carm01 said:
well, i think that might be a little beyond me as far as removing those exchange security measures to be honest. This was/is my first mod.
I will look into it but i think i would require extensive code modification that i am just not familiar with at the moment.
Click to expand...
Click to collapse
I appreciate the reply and your hard work on this. I've tried to work on apps myself but can't find the time and though you say its out of your depth to do what I'm inquiring about I can't even start to work on this stuff.
So again thanks for the hard work.
kitkat 5mb attachment limit
Hello,
I modified "AttachmentInfo.java" and "AttachmentUtilities.java" from
android 4.4 source code, then I rebuild the "Email.apk" application.
The problem is that after all those source code modifications, the 5MB attachment restriction it is still there.
What other files need to be modified?
I got to look, but it's a smali file and there is literally one one change that needs to be done in the code to get it to go to 25mb attachment size.
For the world of me I don't know who is the fool that keeps building them like this. I don't know off the top of my head atm.
Once I look up my mod notes I will reply to you message so you see it in the notifications. If you would mind reply to my post I would appreciate it as it was a coincidence that I checked this thread.
Best regards
Sent from my HTC6500LVW using xda app-developers app
Hi,
Thank you for the reply!
Quote "For the world of me I don't know who is the fool that keeps building them like this."
I think that the AOSP Email App is crippled because, and I will continue with something I read it somewhere, Google wants the big files to be transferred using its services: Gmail with the Gmail App, Google Drive, etc. and while transferring them back and forth, gain a little insight on their content too.
If you find your old notes, this will ease the required work to make AOSP Email a good daily driver:
- attach as much as you like to your emails (the server knows better how much it wants to accept)
- attach any files, not only jpg and video (I am not such huge multimedia freak, I want normal email use too)
- save any attachment (including the "very dangerous" zip files wich are now forbidden to be saved...)
- maybe delete directly (after confirmation) instead of moving to Trash, and then having to delete them again...
There are only 2 threads on XDA about this problem, and now. thanks to you, I am close to an answer.
carm01 said:
I got to look, but it's a smali file and there is literally one one change that needs to be done in the code to get it to go to 25mb attachment size.
For the world of me I don't know who is the fool that keeps building them like this. I don't know off the top of my head atm.
Once I look up my mod notes I will reply to you message so you see it in the notifications. If you would mind reply to my post I would appreciate it as it was a coincidence that I checked this thread.
Best regards
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
were you ever able to find your notes?
i hate the stupid limits in the default app.
the other thing i noticed is that hyperlinks are no longer highlighted (ie not clickable)
richard
DarkStarMedia said:
were you ever able to find your notes?
i hate the stupid limits in the default app.
the other thing i noticed is that hyperlinks are no longer highlighted (ie not clickable)
richard
Click to expand...
Click to collapse
I know what i did however the files were uncompiled source which i do not work off of. Furthermore, you will need to provide me with a deodexed version of the APK file in question.