Related
So, I just grabbed the Hero port from here - http://forum.xda-developers.com/showthread.php?t=722122. And then, I did the following -
1) loaded into dsixda's kitchen and selected 'Advanced' and 'port'
2) used freshly compiled AOSP ROM with freshly compiled kernel as base for device (using Android Builder - link in sig)
3) replaced 'heroc' with 'desirec' in updater-script & build.prop
4) changed several lines in build.prop to change 'Sprint' into 'Verizon' & 'Hero CDMA' into 'Eris'
5) renamed 'init.heroc.rc' in ramdisk to 'init.desirec.rc'
6) copied 'desirec-keypad.kcm.bin' & 'desirec-keypad.kl' from planejane into appropriate locations
7) copied 'sensors.desirec.so' from planejane to appropriate location
Seriously. That's all that I did.
What works:
wifi
camera (no preview)
bluetooth (well it turns on, I don't have anything to test)
Market (after the Google bits are installed)
phone calls
3G
touch screen
buttons
lights
SMS
What doesn't work:
MMS (couldn't send)
OC won't work because the kernel I used doesn't have it.
This is really nice for no more work than it takes to port. It kind of hurts me, because I like the idea of compiling from source so much better...
I don't want to step on any toes of people who are doing real work, since I don't plan on maintaining this ROM. (Well, I didn't really do much of anything anyway!) So, hence the instructions above. Roll your own, if you want.
nice work has anybody tried this yet? i can guinea pig if not.
Edit:
Nevermind
gnarlyc said:
So, I just grabbed the Hero port from here - http://forum.xda-developers.com/showthread.php?t=722122. And then, I did the following -
1) loaded into dsixda's kitchen and selected 'Advanced' and 'port'
2) used freshly compiled AOSP ROM with freshly compiled kernel as base for device (using Android Builder - link in sig)
3) replaced 'heroc' with 'desirec' in updater-script & build.prop
4) changed several lines in build.prop to change 'Sprint' into 'Verizon' & 'Hero CDMA' into 'Eris'
5) renamed 'init.heroc.rc' in ramdisk to 'init.desirec.rc'
6) copied 'desirec-keypad.kcm.bin' & 'desirec-keypad.kl' from planejane into appropriate locations
7) copied 'sensors.desirec.so' from planejane to appropriate location
Seriously. That's all that I did.
What works:
wifi
camera (no preview)
bluetooth (well it turns on, I don't have anything to test)
Market (after the Google bits are installed)
phone calls
3G
touch screen
buttons
lights
SMS
What doesn't work:
MMS (couldn't send)
OC won't work because the kernel I used doesn't have it.
This is really nice for no more work than it takes to port. It kind of hurts me, because I like the idea of compiling from source so much better...
I don't want to step on any toes of people who are doing real work, since I don't plan on maintaining this ROM. (Well, I didn't really do much of anything anyway!) So, hence the instructions above. Roll your own, if you want.
Click to expand...
Click to collapse
am i missing the download link ?
rvpartsguy said:
am i missing the download link ?
Click to expand...
Click to collapse
He is just giving instructions if you want to try and port your own...Hence, the last sentence.
rvpartsguy said:
am i missing the download link ?
Click to expand...
Click to collapse
lol i ported this too .. if anyone wants to check it out ,, let me know
Team edward
tazzpatriot said:
lol i ported this too .. if anyone wants to check it out ,, let me know
Click to expand...
Click to collapse
lol nope there just isn't one up . . .
by the way gnarlyc for your own good, you should put a link up or edit the title before the heathens start chewing on your neck =)
Sjflowerhorn said:
lol nope there just isn't one up . . .
by the way gnarlyc for your own good, you should put a link up or edit the title before the heathens start chewing on your neck =)
Click to expand...
Click to collapse
Yeah, I thought that NOT putting [ROM] in the title would take care of it. Maybe not...
gnarlyc said:
Yeah, I thought that NOT putting [ROM] in the title would take care of it. Maybe not...
Click to expand...
Click to collapse
if ur not gunna upload it , i have a copy that i will , if ur cool with that ?
tazzpatriot said:
if ur not gunna upload it , i have a copy that i will , if ur cool with that ?
Click to expand...
Click to collapse
Hey, I just provided the instructions... If I were going to post the ROM, I would make sure it's ok with darchstar. That's just me though. Since it's all open source, it may not matter one way or another.
So, yeah, it's ok with me! I haven't sent my build to anyone yet, so if you ported it, well, you ported it!
Thanks for asking. That's the way to be.
I do have one request though... If you make any more changes, can you post them too? And not just - "v53 - fixed thingy". I really like to see what people are doing, so I can learn how they did it. That's purely a request. You are in no way obligated.
gnarlyc said:
Hey, I just provided the instructions... If I were going to post the ROM, I would make sure it's ok with darchstar. That's just me though. Since it's all open source, it may not matter one way or another.
So, yeah, it's ok with me! I haven't sent my build to anyone yet, so if you ported it, well, you ported it!
Thanks for asking. That's the way to be.
I do have one request though... If you make any more changes, can you post them too? And not just - "v53 - fixed thingy". I really like to see what people are doing, so I can learn how they did it. That's purely a request. You are in no way obligated.[/QUOTE
he knows i ported it over ,he has let me b4 and there shouldnt be a problem
and yes i will
Click to expand...
Click to collapse
tazzpatriot said:
he knows i ported it over ,he has let me b4 and there shouldnt be a problem
and yes i will
Click to expand...
Click to collapse
Cool deal then. The next thing that I was going to do was change the "Sprint" in res/xml/eri.xml in the framework-res.apk to say Verizon. I had no idea of where to do that until last night when it was mentioned in the irc channel by andrew8806 & conap.
This is really good build. I'm using it right now as my everyday ROM. It will be good for this to be an option for people. It's just not a part of my plan... Muhahaha.
Rock on.
very informative, thanks for editing the title accordingly. =) don't need anymore flames rising. And also thanks for making sure to add the ASK DARCHSTAR part in the OP beings that there was already almost a issue between him the heroc community and one of the eris forum members(you already know who) due to a mixup.
I'm feeling like an idiot but I can't find ramdisk to make the necessary changes, othwise great info as always.
listyb01 said:
I'm feeling like an idiot but I can't find ramdisk to make the necessary changes, othwise great info as always.
Click to expand...
Click to collapse
If you are using dsixda's Kitchen, you can go to Advanced and then '15'. It will expand the boot.img out into a folder called BOOT-EXTRACTED, and there's a folder in there that is the contents of the ramdisk and the kernel. Be sure to build the boot.img back after making changes and before building the ROM.
This explains it -
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Thanks for the info and the link. I am new to Linux and android development so I am reading every bit of info I can get my hands on.
Sent from my KaosFroyoEris
listyb01 said:
Thanks for the info and the link. I am new to Linux and android development so I am reading every bit of info I can get my hands on.
Sent from my KaosFroyoEris
Click to expand...
Click to collapse
Oh, ok. Me too. I just got this thing in March and started learning then. Here are more links that you might find helpful.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://forum.androidcentral.com/hacking/6037-general-rom-faq.html
http://forum.xda-developers.com/showthread.php?t=633246
http://blog.coralic.nl/2010/01/28/build-eclair-aka-android-2-1-for-hero-from-source/
http://forum.xda-developers.com/showthread.php?t=622916
http://forum.androidcentral.com/htc...how-build-your-own-kernel-package-source.html
http://forum.xda-developers.com/showpost.php?p=6738713&postcount=1
http://www.kandroid.org/android_pdk/index.html
http://android-dls.com/wiki/index.php?title=Main_Page
https://docs.google.com/Doc?docid=0AcdxIJRSH9ypZGZzc2pxNDlfMjdnazk4OHNxZA&hl=en
http://forum.xda-developers.com/showthread.php?t=641223
http://adrianvintu.com/blogengine/post/Colored-Logcat-Script-for-Windows.aspx
http://www.androidenea.com/2009/08/init-process-and-initrc.html
http://forum.xda-developers.com/showthread.php?t=623976
http://lukasz.szmit.eu/2009/12/making-your-own-rooted-android-rom.html
http://groups.google.com/group/android-kernel
http://groups.google.com/group/android-building
http://groups.google.com/group/android-porting
http://groups.google.com/group/android-developers
http://groups.google.com/group/android-ndk
http://groups.google.com/group/android-platform
I also find the G1 Android Development forum quite interesting. Start at the oldest posts and come forward. There's a lot of good stuff in there, and there's no telling how much I've missed by just skimming the subjects for interesting things.
There's a lot to learn. It takes time.
Thanks for the info and the link. I am new to Linux and android development so I am reading every bit of info I can get my hands on.
Sent from my KaosFroyoEris
Click to expand...
Click to collapse
Oh, ok. Me too. I just got this thing in March and started learning then. Here are more links that you might find helpful.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://forum.androidcentral.com/hacking/6037-general-rom-faq.html
http://forum.xda-developers.com/showthread.php?t=633246
http://blog.coralic.nl/2010/01/28/build-eclair-aka-android-2-1-for-hero-from-source/
http://forum.xda-developers.com/showthread.php?t=622916
http://forum.androidcentral.com/htc...how-build-your-own-kernel-package-source.html
http://forum.xda-developers.com/showpost.php?p=6738713&postcount=1
http://www.kandroid.org/android_pdk/index.html
http://android-dls.com/wiki/index.php?title=Main_Page
https://docs.google.com/Doc?docid=0AcdxIJRSH9ypZGZzc2pxNDlfMjdnazk4OHNxZA&hl=en
http://forum.xda-developers.com/showthread.php?t=641223
http://adrianvintu.com/blogengine/post/Colored-Logcat-Script-for-Windows.aspx
http://www.androidenea.com/2009/08/init-process-and-initrc.html
http://forum.xda-developers.com/showthread.php?t=623976
http://lukasz.szmit.eu/2009/12/making-your-own-rooted-android-rom.html
http://groups.google.com/group/android-kernel
http://groups.google.com/group/android-building
http://groups.google.com/group/android-porting
http://groups.google.com/group/android-developers
http://groups.google.com/group/android-ndk
http://groups.google.com/group/android-platform
I also find the G1 Android Development forum quite interesting. Start at the oldest posts and come forward. There's a lot of good stuff in there, and there's no telling how much I've missed by just skimming the subjects for interesting things.
There's a lot to learn. It takes time.
Click to expand...
Click to collapse
+ 1 on the G1 forum thanks for the post!
Sent from my Eris using XDA App
First successful port done!
listyb01 said:
First successful port done!
Click to expand...
Click to collapse
Well done! Did you have to do anything that I did not list in the instructions in this thread? Share?
Honestly, it's real tempting to take yet another detour and make a plugin for the kitchen that will do the steps in the OP (CDMA Hero --> Eris) and maybe another one that's Eris --> CDMA Hero.
I don't think it will take much time to do, and it will make Hero ports even easier for people who don't have the time to dig into things as well as they probably should if they are going to be a dev. (There is a downside to making all of this easier to do...)
Can anyone help me figure out how to change keyboard background?
I have looked through everything and must be missing it somehow...
Well we found the files, edited one to test but now when we reflashed the swype.apk, no virtual keyboard is installed. ADB pushed it, reflashed it, moved it to system/app... no keyboard shows up after only changing one image...
I am confused...
I basically need to figure out how to resign the apk after customizing and I am pretty noob right now..
You'll be better off asking this in the theming subforum.
I figured it out finally. It was me being dumb is all...
jkrough0728 said:
I figured it out finally. It was me being dumb is all...
Click to expand...
Click to collapse
Would you mind contributing to the community and sharing the solution?
Sent from my mind using telepathitalk
Let me get it completely figured out first but then of course!!
To change it, you have to edit swype.apk and I have had to reflash 3 times now because I keep making little errors. It is kind of a painful process!
Well I finally got most of the editing done... I kept it pretty simple as far as the letters and I didn't really try hard with the placements on things because to be honest I wanted to throw the phone after awhile !
But here is a sample of what I did, if there is actually a demand for people wanting to do this then I will write a "how to" but I have to warn you it is painful and you will need experience with photo editing...
I changed the flame color in the background to be different for each mode.
And yes, Swype still works!
Consider this your first demand for a how-to.
Ha.. I will go ahead and get started on it then and post under themes/apps for everyone! I am not taking credit for doing it but I will write the how to for somebody to try.
Maddog and Illinois08 were the biggest help during the process so I will include them in the walk through.
Pointless816 said:
Consider this your first demand for a how-to.
Click to expand...
Click to collapse
I have placed the how to under themes section.
Let me know if you have any questions...
I recently got my hands on a Kindle Fire HD 7" and have been playing around with it a bit. I wasn't a fan of the ads found in the lockscreen and initially set out to modify the smali to remove the ads or at least not display them. While playing around with the build.prop, I decided to change the density to 213 (the same as the Nexus 7) and upon rebooting I was greeted with the standard ICS lockscreen. So I no longer needed to mess with smali since this is much easier and others can do it just as easily.
I have tried this on the 7.2.3 firmware but it may work on older versions just the same. If it does, please post and let others know that it worked.
Prerequisites
Rooted device
ES File Explorer
local.prop - download link
Although I did this via ADB and manually mounted /system as RW and used vi from busybox, I'm going to explain how to do this without any command line usage.
I'm using ES File Explorer but if you are familiar with an alternative which allows you to write a file to /data then please feel free to use that.
Copy the downloaded local.prop file to your device's SD card
Install ES File Explorer if you have not done so. This is available in the Amazon Appstore.
Open ES File Explorer and go to the settings by pressing the menu button in the navbar.
Select Root Settings
Check Root Explorer
Check Up to Root
Press the back button a few times until you are back at the main app
Navigate to the SD card where local.prop is located, long press the local.prop file and select Copy to
Press the Up icon at the top right of the dialog that appears
Select the / folder (should be above SD Card)
Select data folder and press OK
If you'd like, you can navigate to the /data folder and verify that local.prop does exist in there now. If so, then it's time to reboot.
Reboot the device. You'll have to shut down and then power back on since the amazon firmware does not provide a reboot option.
Caveats
Black background on lockscreen.
Auto brightness toggle no longer shows up when adjusting brightness.
For those that would like to see what's in the local.prop file in advance, here you go.
Code:
# override ro.sf.lcd_density found in build.prop
qemu.sf.lcd_density=213
Before I forget, please do not ask how to root or how to accomplish things outside the scope of this thread. This information is intended for those that have already rooted their device and are on stock firmware but don't want the ads and would rather have the ICS lockscreen.
0xD34D said:
Before I forget, please do not ask how to root or how to accomplish things outside the scope of this thread. This information is intended for those that have already rooted their device and are on stock firmware but don't want the ads and would rather have the ICS lockscreen.
Click to expand...
Click to collapse
And the keyboard?
Sent From My Super Modded KFHD
persano said:
And the keyboard?
Sent From My Super Modded KFHD
Click to expand...
Click to collapse
What about it? Works fine at this density if that's what you are getting at.
0xD34D said:
What about it? Works fine at this density if that's what you are getting at.
Click to expand...
Click to collapse
Yes, in landscape and portrait is well?
Sent From My Super Modded KFHD
persano said:
Yes, in landscape and portrait is well?
Sent From My Super Modded KFHD
Click to expand...
Click to collapse
Yep, no problem in either orientation. Been using it with this density setting since last night. I wanted to put it through some normal usage before posting about it. Besides the caveats listed in the OP, I have not noticed anything else.
This works great! Anyway to change background though?
Sent from my KFTT using XDA Premium HD app
ICS Lockscreen the easy way
0xD34D,
Thank you for the post.
This is a nice option.
prokennexusa said:
0xD34D,
Thank you for the post, we had this tweak under Post #2 in http://forum.xda-developers.com/showthread.php?t=2101564 but as you will see we revoked the post since we had over 27 people Brick there Kindle in one week of posting the How To. We plan to add a new post to #2 that allows you to change the lock screen in 5 steps and no chance of Bricking the Kindle. We prefer this idea, it is just a little more dangerous and we did not like the idea of loosing the brightness toggle.
It is still nice to offer people options.
Click to expand...
Click to collapse
Actually if they follow the steps I have outlined, there is very little danger involved. Like many modifications, there is always the chance that something can go wrong. I've made far more sever changes to this device without problems.
I could probably bring this down to 3 steps if I really wanted to but that's no fun. Please don't jack threads so you can promote your own. The Android community is about choices and they deserve to have this information and do with as they please.
prokennexusa said:
0xD34D,
Thank you for the post, we had this tweak under Post #2 in http://forum.xda-developers.com/showthread.php?t=2101564 but as you will see we revoked the post since we had over 27 people Brick there Kindle in one week of posting the How To. We plan to add a new post to #2 that allows you to change the lock screen in 5 steps and no chance of Bricking the Kindle. We prefer this idea, it is just a little more dangerous and we did not like the idea of loosing the brightness toggle.
It is still nice to offer people options.
Click to expand...
Click to collapse
you gon and did it now
meddle70 said:
This works great! Anyway to change background though?
Sent from my KFTT using XDA Premium HD app
Click to expand...
Click to collapse
Right now there does not seem to be an easy way to set the background (wallpaper). Amazon seems to have disabled the WallpaperManager which apps use to set the wallpaper. I was playing with a test app and on the KFHD I get a null value for the manager so an alternative method will need to be found for that.
0xD34D said:
Right now there does not seem to be an easy way to set the background (wallpaper). Amazon seems to have disabled the WallpaperManager which apps use to set the wallpaper. I was playing with a test app and on the KFHD I get a null value for the manager so an alternative method will need to be found for that.
Click to expand...
Click to collapse
Ah. Well ill tell you what doing that mod makes it feel much more responsive. I tried the third party lockscreens, and they were just too slow for my taste. I dont really mind the black screen and i didnt like autobrightness. Gives me a headache when playing solitare lol
0xD34D said:
Actually if they follow the steps I have outlined, there is very little danger involved. Like many modifications, there is always the chance that something can go wrong. I've made far more sever changes to this device without problems.
I could probably bring this down to 3 steps if I really wanted to but that's no fun. Please don't jack threads so you can promote your own. The Android community is about choices and they deserve to have this information and do with as they please.
Click to expand...
Click to collapse
0xD34D,
Very nice tutorial 0xD34D!
prokennexusa said:
0xD34D,
I am sure it was the ways we setup the steps. Anyways options are great for the end user. Very nice tutorial 0xD34D!
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
0xD34D,
Ahhhh, actually there is a way, easy too. Monitor that like I gave you tomorrow AM. We will have the instructions posted.
Click to expand...
Click to collapse
You might want to monitor my OP since I deprecated the original method in favor of a simple local.prop. And once again, let me thank you for jacking this thread to promote your own. Top notch XDA sh!t right there!
To anyone following this thread. I have been following Ox for quite some time now and he has never led me astray. If you follow the instructions as posted in the OP you'll be fine. People brick because of their own stupidity and lack of reading or knowing exactly what they are doing with their device. Not because a developer led them astray.
Sent from my GT-N7105 using Tapatalk 2
Method update
For those that may have already made this modification. I have updated the procedure which does not require any modifications in /system. If you want to use the new method just revert your changes to build.prop so that the density is back at 240 and then follow the steps to get local.prop onto /data
Any screen shots man
Sent from my Nexus 7 using Tapatalk 2
esema1o said:
Any screen shots man
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I've updated the OP with a couple screenshots. As you can see there is no background but it is indeed the standard ICS lockscreen.
0xD34D said:
You might want to monitor my OP since I deprecated the original method in favor of a simple local.prop. And once again, let me thank you for jacking this thread to promote your own. Top notch XDA sh!t right there!
Click to expand...
Click to collapse
0xD34D,
Wow, what was not my intention, I am quite surprised I have never had someone say I was jacking there thread. We do not need to jack threads since our reason for being here is not for personal gratification or kudos, it is to serve people and a community which we love and have been a part of since 1978. If I offended you, I am sorry, that was not my intention. I was just sharing my concern around a build.prop and I came back to since I saw your edit, I was going to say "impressive idea using a local.prop edit" which it is impressive - I also was going to send you a PM on how to inject the code through two keystrokes. Sorry, I will remove the link. Wow..........
prokennexusa said:
0xD34D,
Wow, what was not my intention, I am quite surprised I have never had someone say I was jacking there thread. We do not need to jack threads since our reason for being here is not for personal gratification or kudos, it is to serve people and a community which we love and have been a part of since 1978. If I offended you, I am sorry, that was not my intention. I was just sharing my concern around a build.prop and I came back to since I saw your edit, I was going to say "impressive idea using a local.prop edit" which it is impressive - I also was going to send you a PM on how to inject the code through two keystrokes. Sorry, I will remove the link. Wow..........
Click to expand...
Click to collapse
One thing I found funny was you said you originally had this in your #2 post of the link you provided but the only thing in that #2 post was "Reserved for new tutorial" and that was the original post since it did not show that it was ever edited. If you had people bricking due to a simple build.prop edit then you must have provided some incorrect directions or the users simply did something else that was out of the scope of the tutorial. Commenting on another thread with a link back to your tutorial and then providing FUD is not really good forum etiquette. Whether that was your intention or not, that is how it was perceived by myself and others I showed the comment to.
And on a side note, this particular community has been around for about 4.5 years. I'm not aware of any Android devices from the late 70's.
If you had been living under a rock, then get out of there and take a look here
http://aokp.co/blog/aokp-boot-animation-contest-read-this-right-now
I am not going to rewrite everything that is written there
The gist is :
AOKP wants you to submit a bootanimation for the contest. The last date is 7th February. First prize involves a Nexus device. For more details visit the above link.
For any queries/doubts/clarfications, please post below in the thread, and we'll try out best to help you out.
~ Championswimmer (Team Kang)
I'm just wondering, how is the best boot animation going to be decided? Maybe an open blog poll?
pandasa123 said:
I'm just wondering, how is the best boot animation going to be decided? Maybe an open blog poll?
Click to expand...
Click to collapse
Read the blog post.
Not sure if it's planned or not, but it would be awesome if the entries were posted here so that we can check them out!
DaMadOne said:
Not sure if it's planned or not, but it would be awesome if the entries were posted here so that we can check them out!
Click to expand...
Click to collapse
Counterproductive. AOKP clearly stated that entries for the contest shall be UNIQUE - posting these here will make people copy ideas. AOKP will draw the winner in a secret election, just participate and drink a tea.
Little update,
The last date is now Feb 7 (postponed by a day)
Non-USA participants are allowed (and if selected, we will try to get them that nexus definitely)
aaaanndd.. if you check back on the blog posts, vector format logo of aokp is uploaded, in case anyone of you wants it
can we send more than one entry ? or single entry with 2 or more projects?
cisza said:
can we send more than one entry ? or single entry with 2 or more projects?
Click to expand...
Click to collapse
Hi there. You can submit as many as you want. Just remember, it's quality over quantity. Look forward to yours and everyone else's submissions. ^^
If I were more artistic I would've had a unicorn dancing on a disco dance floor a la John Travolta in Saturday Night Fever, sadly I'm not
Already started working on some sexy bootanimations here, but just had a few questions :
1- How am supposed to send a second bootanimations, just by submitting another entry with the same name & email ?!
2- what is that 'Haiku' field !? what does that mean ?
ahmedelhofy said:
Already started working on some sexy bootanimations here, but just had a few questions :
1- How am supposed to send a second bootanimations, just by submitting another entry with the same name & email ?!
2- what is that 'Haiku' field !? what does that mean ?
Click to expand...
Click to collapse
and
1) Open stock camera
2) Stay on Image mode not Video mode
3) Click on the 'settings' gear icon
4) Keep on clicking/tapping on 'redeye reduction' continuously
Advanced features is now unlocked (camera developer options)
5) Switch to video mode
6) Click on the 'settings' gear icon
7) Go to 'Image Stabilization' option
8) Turn 'ON'
**Note Video stabilization will work for videos resolutions 1080p/720p. It will be disabled for video resolutions higher than 1080p.
To disable 'Camera developer options' clear the data of the camera app.
StoneSpider said:
1) Open stock camera
2) Stay on Image mode not Video mode
3) Click on the 'settings' gear icon
4) Keep on clicking/tapping on 'redeye reduction' continuously
Advanced features is now unlocked (camera developer options)
5) Switch to video mode
6) Click on the 'settings' gear icon
7) Go to 'Image Stabilization' option
8) Turn 'ON'
**Note Video stabilization will work for videos resolutions 1080p/720p. It will be disabled for video resolutions higher than 1080p.
To disable 'Camera developer options' clear the data of the camera app.
Click to expand...
Click to collapse
Give credits to the guy who actually found it.
Don't post it as your own.
akshmau5 said:
Give credits to the guy who actually found it.
Don't post it as your own.
Click to expand...
Click to collapse
I Own an Asus Zenfone Max Pro M1 and I tried it on my phone. I haven't downloaded any files that was created/shared by anyone or anywhere. Neither did I copy and paste the text from any article or post.
What do you have to say about this?
There are multiple tips n tricks on Youtube about Asus Max Pro M1, almost every video contains the same tips and tricks. Is everyone stealing?
StoneSpider said:
I Own an Asus Zenfone Max Pro M1 and I tried it on my phone. I haven't downloaded any files that was created/shared by anyone or anywhere. Neither did I copy and paste the text from any article or post.
What do you have to say about this?
There are multiple tips n tricks on Youtube about Asus Max Pro M1, almost every video contains the same tips and tricks. Is everyone stealing?
Click to expand...
Click to collapse
Buddy have you checked XDA portal and this device section ? The guy who posted this first (check the date ) is the one who will get the credit. While your intentions may be noble (about informing everybody of this workaround) posting a new thread about the same thing/duplicity is not helping it and it may seem like you are not giving credit where it's due.
Tianhe said:
Buddy have you checked XDA portal and this device section ? The guy who posted this first (check the date ) is the one who will get the credit. While your intentions may be noble (about informing everybody of this workaround) posting a new thread about the same thing/duplicity is not helping it and it may seem like you are not giving credit where it's due.
Click to expand...
Click to collapse
I'm not aware of his post And how can you jump to conclusions? I didn't get any of the info or idea from his post. Pls go ahead and make complaints on the other 100 of sites who have made videos and articles on the same subject.
You can ask me to delete the post on the grounds of similar post being published in this community, making it double posts. But u can't ask me to give credit to someone who I'm not even aware of.
StoneSpider said:
I'm not aware of his post And how can you jump to conclusions? I didn't get any of the info or idea from his post. Pls go ahead and make complaints on the other 100 of sites who have made videos and articles on the same subject.
You can ask me to delete the post on the grounds of similar post being published in this community, making it double posts. But u can't ask me to give credit to someone who I'm not even aware of.
Click to expand...
Click to collapse
Now you are the one jumping about. Did I say that you got the idea from his post? Read my post carefully, especially the intention part. I have neither visited those 100s of sites you mention nor do I intend to for the simple reason that XDA is place where usually things happen first and for the best as can be seen in this case itself.
It is your fault that you are unaware of the original thread posted on XDA itself and that too in this device section + being featured on XDA Portal. Ignorance in this case is not bliss. And you should be smart enough to atleast edit the post for giving credits if not deleting it altogether. Rather you seem hell bent on not even acknowledging it, let alone take corrective action. To each, his own I guess...
Tianhe said:
Now you are the one jumping about. Did I say that you got the idea from his post? Read my post carefully, especially the intention part. I have neither visited those 100s of sites you mention nor do I intend to for the simple reason that XDA is place where usually things happen first and for the best as can be seen in this case itself.
It is your fault that you are unaware of the original thread posted on XDA itself and that too in this device section + being featured on XDA Portal. Ignorance in this case is not bliss. And you should be smart enough to atleast edit the post for giving credits if not deleting it altogether. Rather you seem hell bent on not even acknowledging it, let alone take corrective action. To each, his own I guess...
Click to expand...
Click to collapse
Do you even read what you type?
It's my fault if I'm unaware of whatever thread/forum/post that you are following? And I'm ignorant for not following the same feed that you follow? You reply on my thread and dictate me to credit someone that you have been following! You are being so adamant on making me acknowledge someone that I didn't even get any ideas from!
Dude Relax, waste your time on the other sites go around forcefully insisting people to credit someone as per your liking. If they don't oblige then be insulting to them and call out names(may be ignorant). :good:
I don't mind deleting this post on the basis of it being a similar post to someone else (thus making mine a duplicate) and so to avoid double postings. But don't play the blame game and insult others.
StoneSpider said:
I Own an Asus Zenfone Max Pro M1 and I tried it on my phone. I haven't downloaded any files that was created/shared by anyone or anywhere. Neither did I copy and paste the text from any article or post.
What do you have to say about this?
There are multiple tips n tricks on Youtube about Asus Max Pro M1, almost every video contains the same tips and tricks. Is everyone stealing?
Click to expand...
Click to collapse
Umm.. The senior editor of XDA has given credits to the guy so its suffice to say that it's a general rule at Xda and in comparison your post/thread doesn't even count.
Regarding your rhetorical/condescending question - There is this nice saying "monkey see monkey do".
Is that adequate enough for you!!
The rant comes after reading all your posts in the thread.
akshmau5 said:
Umm.. The senior editor of XDA has given credits to the guy so its suffice to say that it's a general rule at Xda and in comparison your post/thread doesn't even count.
Regarding your rhetorical/condescending question - There is this nice saying "monkey see monkey do".
Is that adequate enough for you!!
The rant comes after reading all your posts in the thread.
Click to expand...
Click to collapse
The irony 'monkey see monkey do'.
Btw Your argument 'XYZ gave credit to ABC' so why aren't you giving credit to ABC'? ? Logic overboard
akshmau5 said:
Umm.. The senior editor of XDA has given credits to the guy so its suffice to say that it's a general rule at Xda and in comparison your post/thread doesn't even count.
Regarding your rhetorical/condescending question - There is this nice saying "monkey see monkey do".
Is that adequate enough for you!!
The rant comes after reading all your posts in the thread.
Click to expand...
Click to collapse
Leave it buddy, the guy's got his head buried in the sand and logic has gone for a toss. It's like "I pointed out America on the map, what do I care who Columbus is or what he did much before me".
Tianhe said:
Leave it buddy, the guy's got his head buried in the sand and logic has gone for a toss. It's like "I pointed out America on the map, what do I care who Columbus is or what he did much before me".
Click to expand...
Click to collapse
I found your nose, it was in my business. So, please take it and keep it to yourself.
MJ wasn't the one who invented the moonwalk, he was the one who popularized it. Do you know the person who should be actually credited for the moonwalk? Or is it that you are 'ignorant' because you are 'unaware' about it, or perhaps didn't follow other guy.