Database Users

Development Q&A - Ask Development Questions Here!

After looking into what another moderator said , I thought it would be a good idea to have a place for development related questions. If you have any questions feel free to post em in here and we will answer them. Please do not make a new thread!
-CK

Can one of the smart developers around here make this dialer T9 capable for looking up contacts?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
aTakephone comes very close to this dialer but is missing the contacts tab that this one has.
http://htc-phones.net/category/htc-phones/htc-dream/page/5

I can use someone's nandroid backup for droid eris?
i brick my phone and i need a nandroi backup but i dont have one
so.. i can use another nandroid backup of another droid eris?

So how to make our own ROMs ?

cant i put a nand from one htc eris to other eris "?

l3nytm said:
I can use someone's nandroid backup for droid eris?
i brick my phone and i need a nandroi backup but i dont have one
so.. i can use another nandroid backup of another droid eris?
Click to expand...
Click to collapse
acidburned; said:
cant i put a nand from one htc eris to other eris "?
Click to expand...
Click to collapse
Same question, sort of the same answer.
For the Eris, "system.img", and "boot.img" files in the Nandroid backup contain no personal information, nor anything which is "customized" to a particular handset; they are generic.
So, yes, you can restore a Nandroid backup from one phone to another. You only need to copy the BDS-YYMMDD-HHMM backup folder from the source phone into the correctly named folder on the target phone. (The easiest way to create that folder on the target phone is to do a dummy Nandroid backup on that phone, and Nandroid will create it for you).
The person that makes the Nandroid backup for you should do it this way:
- reboot into Amon_RA
- make a Nandroid Backup (let's call this one "#1")
- wipe data/factory reset
- make a 2nd Nandroid Backup (let's call this one "#2").
- perform a Nandroid Restore of backup #1
- boot up the phone and copy the backup #2 to the target phone (and delete it from the source phone)
That way, all the personal info, market apps, are wiped from the #2 backup, and it can be freely handed out to someone else without worry.
l3nytm : Unfortunately, Nandroid restore works by "mounting" the /system and /data yaffs2 filesystem(s). There are certain pathologies that can occur where mounting fails and the "nandroid-mobile.sh" script bombs out - in which case, no Nandroid restore will help you, no matter what they contain.
I had it happen to me a long time ago, and I could not even manually mount them using adb - the only thing which saved my butt from a "live brick" was re-application of the Root PB00IMG.zip file. No guarantees that that will work for your phone - and you might have to perform the jcase "Flash any RUU" procedure before you try the HBOOT + PB00IMG.zip flashing procedure.
Lastly, this question isn't a development question; but oh well.
bftb0

Captainkrtek said:
After looking into what another moderator said , I thought it would be a good idea to have a place for development related questions. If you have any questions feel free to post em in here and we will answer them. Please do not make a new thread!
-CK
Click to expand...
Click to collapse
aye aye captain great idea for this thread i promise to never bring out........
THE KRAKEN lol
but seriously i would love to help others out here

prj71 said:
Can one of the smart developers around here make this dialer T9 capable for looking up contacts?
aTakephone comes very close to this dialer but is missing the contacts tab that this one has.
http://htc-phones.net/category/htc-phones/htc-dream/page/5
Click to expand...
Click to collapse
Look for "Dialer One" in the Android Market. It's the closest you can find that has T9 capable dialing aka smart dial. You can also press Menu > Contacts to get to your contacts.

jsuh said:
Look for "Dialer One" in the Android Market. It's the closest you can find that has T9 capable dialing aka smart dial. You can also press Menu > Contacts to get to your contacts.
Click to expand...
Click to collapse
Don't like dialer one. Ive tried it. I want the tabs across the top like the Froyo dialer shown above with T9 capability.

I hope this is a development question. I am trying to make a theme for 2.1 roms does anyone know how I can change the font for the clock in the status bar. Ideally a way to do it via MetaMorph

need sum 1 to make androd 1 rom!

Could we port iphone to the android? Im being completely serious

While figuring out what was causing my widgets to reload every time I hit the back button from an app, I got to thinking about cache. I have CacheCleaner installed and it works great at freeing up space. I also noticed that when I clean the cache, the phone seems a bit more responsive. So here's the question, and feel free to correct me or whatever you feel, but can something be developed like AutoKiller, but that focuses on Cache? Say, it clears the cache when it reaches a certain level like 10mb per say, or whatever you choose. Again, any and all ideas are appreciated.
Thanks everyone for everything that we have here at XDA

DS36 said:
aye aye captain great idea for this thread i promise to never bring out........
THE KRAKEN lol
but seriously i would love to help others out here
Click to expand...
Click to collapse
I think this is good too

Word has it that an hot update for the market is out for certain <2.2 devices.. 'twill supposedly make it resemble the Froyo market a bit more.. Forgive my gall for posting a link, but like some have said, provide screen caps, or it didn't happen..
h ttp://phandroid.com/2010/10/10/android-market-gets-a-hot-update-to-add-froyos-once-exclusive-features/
*bracing for teh flamez, in case my xda google skillz failed me*
Edit: arrgh.. forgot to clarify my dev question.. are there any plans, or is it possible to turn this update into an .apk or a flash-able .zip?

I have an AOSP 2.1 build i'm working on and the video recorder does not work. The logcat shows
E/MediaRecorder( 587): prepare failed: -17
E/videocamera( 587): prepare failed for /sdcard/DCIM/Camera/video-2010-10-05-13
-05-42.3gp
V/videocamera( 587): Releasing media recorder.
V/videocamera( 587): Empty video file deleted: /sdcard/DCIM/Camera/video-2010-1
0-05-13-05-42.3gp
E/CameraInput( 59): Unsupported parameter(x-pvmf/media-input-node/cap-config-i
nterface;valtype=key_specific_value)
E/CameraInput( 59): VerifiyAndSetParameter failed on parameter #0
E/audio_input( 59): unsupported parameter: x-pvmf/media-input-node/cap-config-
interface;valtype=key_specific_value
E/audio_input( 59): VerifyAndSetParameter failed
Can anyone help me with this? i tried using different camera apks all with the same issue.

stingbliss said:
Word has it that an hot update for the market is out for certain <2.2 devices.. 'twill supposedly make it resemble the Froyo market a bit more.. Forgive my gall for posting a link, but like some have said, provide screen caps, or it didn't happen..
h ttp://phandroid.com/2010/10/10/android-market-gets-a-hot-update-to-add-froyos-once-exclusive-features/
*bracing for teh flamez, in case my xda google skillz failed me*
Edit: arrgh.. forgot to clarify my dev question.. are there any plans, or is it possible to turn this update into an .apk or a flash-able .zip?
Click to expand...
Click to collapse
well yes you could either install the .apk like the normal way or just install it via and update.zip to /system/app didnt check link so im not sure.

Guess my question wasn't clear.
There's a new update to the Market for Androids running versions prior to 2.2. It makes the market on those devices resemble the 2.2 market, i.e., tabbed app pages (comments on separate tab), and more importantly, the auto-update feature..
Considering that a lot of us dislike the inherent instability of Froyo, I like the idea of getting this update.. unfortunately, I haven't seen any evidence that my phone is getting it.. (running the Droid Does ROM, even though it hasn't been updated since July)..
Has anyone looked into this market update, and whether or not it could be applied to any of the ROMs for the Eris? (obviously prior to Froyo)

I'd like to try out the Shadow Rom but don't have Clockwork (and wont get it). I've read that I can sign it with test keys so Amon Ra will accept it. Where do I find the program to sign it?
Sent from my Froyo Tazz using XDA App

joshw0000 said:
I'd like to try out the Shadow Rom but don't have Clockwork (and wont get it). I've read that I can sign it with test keys so Amon Ra will accept it. Where do I find the program to sign it?
Sent from my Froyo Tazz using XDA App
Click to expand...
Click to collapse
EasySign --> http://android.grdlock.net/index.php?&direction=0&order=&directory=HTC Droid Eris/Extras
dsixda's kitchen --> http://forum.xda-developers.com/showthread.php?t=633246
I've used both of those to sign ROMs.

Got Viper4Android working! Survives hard reboot

Update: Successfully working atm, survives a hard reboot.
Status: In testing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Congrats!! Hard work surely pays off.

Thanks bud. I'm gonna run it for a bit and make sure there isn't any issue that are gonna come about but I doubt it. I could release a IMG out also for people to flash, but I removed a ton of apps I don't ever use, but unsure about the user who will download it.
Sent from my XT1254 using XDA Free mobile app

savagebunny said:
Thanks bud. I'm gonna run it for a bit and make sure there isn't any issue that are gonna come about but I doubt it. I could release a IMG out also for people to flash, but I removed a ton of apps I don't ever use, but unsure about the user who will download it.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah run it all this weekend and hopefully all is well. Dont hesitate About making the IMG but just specify which apps you have removed and what not beforehand on the op when you make the post. Remember there are all types of users out there so don't question who would be interested dont question that who would be interested.

wadamean said:
Yeah run it all this weekend and hopefully all is well. Dont hesitate About making the IMG but just specify which apps you have removed and what not beforehand on the op when you make the post. Remember there are all types of users out there so don't question who would be interested dont question that who would be interested.
Click to expand...
Click to collapse
Well.. Right when I thought I got it, already ran into a issue. What I did BEFORE was I made sure was the V4A .apk in priv-app had 0755 permissions. I installed the driver and worked, but then i did a SOFT reboot. Driver was successful and no issue. I just now did a hard reboot, and the driver gets uninstalled, and the permissions get set to 0666. Whats weird though is in the img in linux, I made sure priv-app folder is 0755 and I just checked and V4A apk is 0755 in the image. Some how along the line it gets changed to 0666 by the system.
tl;dr only way for it to work is set apk to 0755 via root browser, install driver, Do a soft reboot and it works. Doesn't survive hard reboot. unsure why

savagebunny said:
Well.. Right when I thought I got it, already ran into a issue. What I did BEFORE was I made sure was the V4A .apk in priv-app had 0755 permissions. I installed the driver and worked, but then i did a SOFT reboot. Driver was successful and no issue. I just now did a hard reboot, and the driver gets uninstalled, and the permissions get set to 0666. Whats weird though is in the img in linux, I made sure priv-app folder is 0755 and I just checked and V4A apk is 0755 in the image. Some how along the line it gets changed to 0666 by the system.
tl;dr only way for it to work is set apk to 0755 via root browser, install driver, Do a soft reboot and it works. Doesn't survive hard reboot. unsure why
Click to expand...
Click to collapse
Figure out where the apk installs the driver and manually insert the driver in that location with the proper permissions in the IMG then flash. Should work then I'd think
Edit: looks like you may have to add some lines to the build.prop as well

viper
brennam7 said:
Figure out where the apk installs the driver and manually insert the driver in that location with the proper permissions in the IMG then flash. Should work then I'd think
Click to expand...
Click to collapse
hello. am a lover viper. I had on other cell. there is a way to install without root on droid turbo? thank you. greetings: P

brennam7 said:
Figure out where the apk installs the driver and manually insert the driver in that location with the proper permissions in the IMG then flash. Should work then I'd think
Edit: looks like you may have to add some lines to the build.prop as well
Click to expand...
Click to collapse
Ya I'm thinking that too. It's a new day so I'm gonna start digging into it today and see what's up. The only down fall is that I gotta keep sending over that 3.5GB img each time which takes a lot of time into work.
Already added the lines to build.prop also. There may be a few extra ones that could be lingering
pialletti said:
hello. am a lover viper. I had on other cell. there is a way to install without root on droid turbo? thank you. greetings: P
Click to expand...
Click to collapse
Nope, gotta have root due to dependencies needed by the V4A and various other files that need to be written in /system/

Sign me up!
Sent from my XT1254 using XDA Free mobile app

Hello guys, I may have figured out the issue. In V4A options, we can choose High Quality (HQ) and Super High Quality (SQ). From what I've read SQ doesn't use too much battery more than HQ, and we are using quite a powerful CPU. Should I make a image with HQ or SQ driver installed?

savagebunny said:
Hello guys, I may have figured out the issue. In V4A options, we can choose High Quality (HQ) and Super High Quality (SQ). From what I've read SQ doesn't use too much battery more than HQ, and we are using quite a powerful CPU. Should I make a image with HQ or SQ driver installed?
Click to expand...
Click to collapse
SQ! Did you get it figured out so that it survives a reboot?

PerCompLLC said:
SQ! Did you get it figured out so that it survives a reboot?
Click to expand...
Click to collapse
I'm gonna find out once the image flashes over. I'm crossing my fingers I figured it out... only can hope. I'll update this post if it survives a hard reboot
EDIT: Nope, didn't stick. Now during a soft-reboot it doesn't even work now.. Man this is a struggle

Quick updated, with some mind boosting affect from computerfreek274, I was digging into V4A why it wouldn't stay after hard reboot. I've done 3 hard reboots so far and the driver is sticking without the driver install loop. Can't believe it's taken me this long, but its finally done

Have computerfreek274 add it to the IMG he's been uploading! Could be a fantastic addition! Congrats on getting it to work. No better feeling in the world

JakeDHS07 said:
Have computerfreek274 add it to the IMG he's been uploading! Could be a fantastic addition! Congrats on getting it to work. No better feeling in the world
Click to expand...
Click to collapse
Ya me and him have been talking about it. He is in testing phase atm also
Sent from my XT1254 using XDA Free mobile app

savagebunny said:
Ya me and him have been talking about it. He is in testing phase atm also
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Awesome thanks for your work

@savagebunny It sucks how long it takes to flash each time you need to test something. I hope one day we get an unlocked boot loader and some custom recovery so we can just flash shot as we need it.
Thanks @savagebunny for keeping me going this. I am testing now the changes we just talked about we will see if it works. I also did the same things but when I do a full clean wipe and flash it asked for the driver. I am doing a clean and wipe and fresh install if all works good I will post 1.5.2a with ad blocking and V4A.
Thanks buddy now we will need to work on something new after this. lol.
PS 46% like wet paint.

Ya I feel ya. Made some good progress, although it took us longer than usual, seems like there is only a handful of us working on things. Like you said, gotta think of something else good to bake into the images until we get unlocked boot-loader and we can flash all day

[Guide][EASY][Marshmallow] Disable Force Encryption - No Ugly Corrupt on Boot

I seen a lot of Discussion On this topic, and found a really simple way to disable Forced Encryption and it also removes the warning at boot. This in NO WAY is my work at all. I am sharing this [FIX] FED-Patcher v7 (ForceEncrypt Disable Patcher) which was posted by @gladiac. Absolutely make sure you head over to his forum and hit the Thanks button. This works great
Screenshots Below
I have the option to encrypt the phone as you can see circled. I went into system with Root Explorer and was prompted for R/W access and obviously I granted it. Everything is working great!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Preparation
Before proceeding, enable Developer options and MAKE SURE USB DEBUGGING IS ENABLED!!!
1. Download fed_patcher_v7-signed.zip and check here to verify the latest version
2. Download [BETA][2015.10.10] SuperSU v2.52 by @Chainfire
3. Download Whatever ROM you are going to use. I am currently running [ROM]【6.0】LightROM - Marshmallow【MRA58K】- 10/08/15
Instructions
1. Backup your SD Card, during this process, everything will be erased during the process
2. Reboot into TWRP, this is important that you actually have TWRP
3. Perform a Full Wipe by doing the following:
Press Wipe
[*] Press Advanced
[*] Click every check Box
[*] Wipe 3x for good measure
[*] Press Home button
[*] Press Wipe
[*] Press Format Data
[*] Type yes in the box to perform the format
[*] Perform this 3x for a good full wipe
4. Reboot TWRP (Do Not Install Super Su Yet)
5. Once Back In Recovery, On the computer, open My computer
6. Navigate to and open the Nexus 6 Drive
7. Drag the Zip files below to your Phone -
1) fed_patcher_v7-signed.zip
2) BETA-SuperSU-v2.50.zip
3) ROM Zip
If You are Having Trouble, take a look at the screen shots below
You Want to make sure you mount data if it is not, and make sure MTP is not disabled! Thanks @jamiejames and @aliasferno
8. Flash your ROM 1st (DO NOT BOOT AFTER FLASHING)
9. Wipe Dalvick Cache/Cache 3x
10. Flash fed_patcher_v7-signed.zip
11. Wipe Dalvick Cache/Cache 3x
12. Flash BETA-SuperSU-v2.52.zip
13. Reboot and Enjoy with no more red error sign during boot and no encryptionhttps://source.android.com/devices/tech/security/verifiedboot/verified-boot.html#user_experience
Supported Devices
Motorola Nexus 6 (shamu)
Version History
v1 - Initial version with HTC Nexus 9 WiFi (flounder) support
[*]v2 - Added Motorola Nexus 6 (shamu) support
[*]v3 - Added support for HTC Nexus 9 LTE (flounder_lte)
[*]v4 - Added support for signed boot-images
[*]v5 - Changed error handling to compensate for missing fstab files. Some roms seem not to ship with the complete set of boot-files from AOSP.
[*]v6 - FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
[*]v7 - FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
What Do I need To Make This Work?
A supported device (Your nexus 6)
[*]An unlocked bootloader
[*]An already installed ROM with forceencrypt flag. (like cyanogenmod CM12.1)
[*]A recovery that includes busybox (TWRP, CWM)
How Do I Use it?
Follow Instructions above - This is the basic need to know information
[*]Make a thorough, conservative backup of your data if there is any on your device
[*]Go into your recovery (TWRP, CWM)
[*]Flash fed_patcher-signed.zip
[*]If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before. If you don't do a backup and want to restore your data... well... Call obama.
IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on CM12.1 for example and you used my patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.
Is It Dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.
All Thanks To:
@gladiac - For Putting the OP together for the Nexus 9 and sharing this
[*]@rovo89 - for his xposed framework - I used some of his ideas by reading the source of his xposed installer flashable ZIP for FED-Patcher.
[*]@pbatard - for making (un)mkbootimg (dunno if he is on xda)

good work mate

Danvdh said:
good work mate
Click to expand...
Click to collapse
Thanks Bro...Thanks for the ROM, I saw it's already updating. Thanks

Thanks for this! :good:

Herk718 said:
Thanks for this! :good:
Click to expand...
Click to collapse
No Problem...

@gladiac mentioned he wasn't able to get system R/W access with v7. I'm not sure which SuperSU he was using earlier in the day but can you confirm? I'd like to make a couple edits to build.prop. thanks!

TY you for this info. Exactly what I was looking for. Thanks a milion

spunks3 said:
@gladiac mentioned he wasn't able to get system R/W access with v7. I'm not sure which SuperSU he was using earlier in the day but can you confirm? I'd like to make a couple edits to build.prop. thanks!
Click to expand...
Click to collapse
I am decrypted, I have super user ...I was able to restore with titanium backup, I will see if I can edit the build.prop or just mount rw
edit: I was able to mount rw successfully in root explorer no issues
simunovic said:
TY you for this info. Exactly what I was looking for. Thanks a milion
Click to expand...
Click to collapse
No problem
Sent from my Nexus 6 using Tapatalk

spunks3 said:
@gladiac mentioned he wasn't able to get system R/W access with v7. I'm not sure which SuperSU he was using earlier in the day but can you confirm? I'd like to make a couple edits to build.prop. thanks!
Click to expand...
Click to collapse
I posted a few screenshots in post# 1, I could mount R/W from the system folder in Root Explorer, everything is working great for me

bdorr1105 said:
I posted a few screenshots in post# 1, I could mount R/W from the system folder in Root Explorer, everything is working great for me
Click to expand...
Click to collapse
Very much appreciated!!! Now I wonder if Android pay works.. Something I'll test out later this week I suppose

spunks3 said:
Very much appreciated!!! Now I wonder if Android pay works.. Something I'll test out later this week I suppose
Click to expand...
Click to collapse
It won't work unless you remove root
Sent from my Nexus 6 using Tapatalk

Moved this from the development forum as there is no development, this is not your work, and it is a guide for this; this is better suited to a General forum.
Thread reopened on the basis that this is a guided collection of work.

Ok, this OP is more of a guide on how to use this tool, I am going to edit the OP and redirect it to the Forum that was in the Nexus 6...There was a mis-understanding on my part, I did not realize this was in the Nexus 6 Android Development already, this is just how to run it, and the steps to successfully flash and get rid of the warning before booting Android 6.0 and having a force decrypted set up form boot...

bdorr1105 said:
QUOTE]
As per Light Rom description it says Forced encryption is disabled. So If I install Light ROM, them there is no encryption right? or am I missing something?
Click to expand...
Click to collapse

atrix4nag said:
bdorr1105 said:
QUOTE]
As per Light Rom description it says Forced encryption is disabled. So If I install Light ROM, them there is no encryption right? or am I missing something?
Click to expand...
Click to collapse
There is no encryption, this is just an extra layer, if you flash kernels to make sure it doesn't force encryp, but you should be fine and not have to do this. This gets rid of the warning message at boot
Click to expand...
Click to collapse

bdorr1105 said:
atrix4nag said:
There is no encryption, this is just an extra layer, if you flash kernels to make sure it doesn't force encryp, but you should be fine and not have to do this. This gets rid of the warning message at boot
Click to expand...
Click to collapse
Just now installed light rom, installed custom ROM, and format data. so no more encryption on my phone, but I have the warning message at boot.
so following this method, I wont be having warning message, is that right?
Click to expand...
Click to collapse

atrix4nag said:
bdorr1105 said:
Just now installed light rom, installed custom ROM, and format data. so no more encryption on my phone, but I have the warning message at boot.
so following this method, I wont be having warning message, is that right?
Click to expand...
Click to collapse
I do not have the warning at boot doing this method. So yes, you should no longer have the warning
Click to expand...
Click to collapse

If i follow the steps correctly and change my kernel will the corrupt boot screen return?
my plan is to use Xtrasmooth rom with Elite kernel.

Hucklebury said:
If i follow the steps correctly and change my kernel will the corrupt boot screen return?
my plan is to use Xtrasmooth rom with Elite kernel.
Click to expand...
Click to collapse
I am not 100% sure if it will or not, with the kernel there is a chance it will, but I think you will be ok.. The splash screen is really more of an annoyance than anything else, but I think it will be ok.
At any rate, all you would have to do is flash just the fed_patcher_v7-signed.zip again

bdorr1105 said:
I am not 100% sure if it will or not, with the kernel there is a chance it will, but I think you will be ok.. The splash screen is really more of an annoyance than anything else, but I think it will be ok.
At any rate, all you would have to do is flash just the fed_patcher_v7-signed.zip again
Click to expand...
Click to collapse
ok, thanks for the reply. i have tried many times to get rid of that ugly screen without success, ended up going completely stock M.

[HELP THREAD] [Q&A] [NOOB FRIENDLY] Ask any question here, don't be shy!

A thread for everyone from everyone! Noob friendly and a home for every newcomer!​
Thread rules:
1. Respect xda rules regarding conduct. (Rule no. 2 here)
2. All questions allowed by xda rules are welcomed.
3. Your questions must show that you want to learn. No one will criticize you because you are trying to learn.
4. Ask politely no matter how desperate you might be.
5. Do not post or request warez. XDA rule 6 here.
6. There are no bad questions, but only bad intentions and bad answers.
7. Don't use this thread as an excuse to ask all kinds of questions everywhere in the forums, especially in development threads. This is why this thread is for.
8. For all who want to help, do that kindly according to the rule 2.3 of xda
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Work In Progress
Android related questions
Q: What is a smartphone?
A: ... just kidding, you are way past that!
Q: What is an android ROM?
A: Android Read-Only Memory. A file containing the Android operating system and its apps. The "stock ROM" comes preinstalled on the phone.
Q: What is a custom ROM?
A: A custom ROM replaces your device's preinstalled Android operating system (or Stock ROM), normally stored in read-only memory, with a new version of the Android operating system.
Q: What is a kernel in android?
A: A kernel is the component that helps the applications communicate with the hardware. It manages the system resources, communicates with external devices when needed, and so on. Android uses a variation of the Linux kernel. The kernel is the bridge between the ROM and hardware.
Q: Rooting-What is it?
A: Rooting is the process of allowing users to attain privileged control (root access) over various Android subsystems. As Android uses the Linux kernel, rooting an Android device gives similar access to administrative (superuser) permissions as on Linux. Rooting gives the ability (or permission) to alter or replace system applications and settings, run specialized applications that require administrator-level permissions, or perform other operations that are otherwise inaccessible to a normal Android user.
Q: What is a recovery in android?
A: In Android, recovery refers to the dedicated, bootable partition that has the recovery console installed. It is accessible with a combination of key presses, or instructions from a command line.
Q: What is Stock Recovery?
A: The Recovery that comes with your Android Device from the manufacturer is called Stock Recovery. Stock recovery can be used to flash updates from an update.zip file, OTA Updates, for factory reset etc.
Q: What is a Custom Recovery?
A: From stock recovery, we cannot flash Custom ROMs, Modules etc. For this, you need to flash custom recoveries like TWRP. Flashing a custom recovery overwrites the system recovery. Custom Recoveries have been coded to allow for backup and restore functions, selective deletion of data so you don't have to wipe everything, and modified to allow update packages that have not been digitally signed by official sources.
Q: What does TWRP stand for?
A: Team Win Recovery Project.
Q: What does OTA stand for?
A: Over The Air Update. An OTA Update is a software update that is distributed via Wi-Fi or broadband network, making use of functions built into the operating system itself.​
Note:
Noobs and newcomers: If someone answers you and the answer is helpful to you, press the "thanks" button for that person. It's a polite thing to do in the forums and saves you from creating a post just to say "thanks".
And remember: there are those that are noobs and those that were noobs!
Credit: Google.com for helping me to search, select, format and prepare some of the answers for easy reading.

Thanks for doing this. Been thinking of making one myself but you beat me to it. I'll help you out with answering whenever I can.

joeyhuab said:
Thanks for doing this. Been thinking of making one myself but you beat me to it. I'll help you out with answering whenever I can.
Click to expand...
Click to collapse
Welcome on board!

Now that is a good thread, I do really hope people would ask here now instead of making separate threads.

Xadus said:
Now that is a good thread, I do really hope people would ask here now instead of making separate threads.
Click to expand...
Click to collapse
We can ask the moderators to make this thread a sticky. So it will be always visible.

My device is rooted. I m use substratum in my device.. I m using a theme in substratum for 2 week ago but today I try to install & apply a new one but once I did that my device itself restart & Showing me a message " Android system load failed.. Your Data maybe corrupted , Please do a reset factory " but I want to back my device without loosing my data... What can I do. Please anyone help me..This is error

shafayetsabbir3 said:
My device is rooted. I m use substratum in my device.. I m using a theme in substratum for 2 week ago but today I try to install & apply a new one but once I did that my device itself restart & Showing me a message " Android system load failed.. Your Data maybe corrupted , Please do a reset factory " but I want to back my device without loosing my data... What can I do. Please anyone help me..This is error
Click to expand...
Click to collapse
Substratum creates a folder in your internal sd card with a flashable file that you can rescue your system.
Boot your phone into twrp if you have one and flash that file.
If you don't have a recovery installed, than just boot into a recovery and again flash that file.

Is there any way to resolve this issue of feb patch not getting installed

ragav_lithun said:
Is there any way to resolve this issue of feb patch not getting installed
Click to expand...
Click to collapse
Can you please give some more details? How are you installing the february patch?
Did you root your phone? Can you take a screenshot of the problem and upload it here?

varben said:
Substratum creates a folder in your internal sd card with a flashable file that you can rescue your system.
Boot your phone into twrp if you have one and flash that file.
If you don't have a recovery installed, than just boot into a recovery and again flash that file.
Click to expand...
Click to collapse
I have twrp installed bro.. What to do now?

shafayetsabbir3 said:
I have twrp installed bro.. What to do now?
Click to expand...
Click to collapse
Boot into twrp, find the folder substratum in your internal sd card and flash the rescue zip file. (Or uninstall, can't remember the exact name of the file)

I've bought a dux ducis flip cover. Any advice on how to turn on/off screen when open/close cover?

edgardurao said:
I've bought a dux ducis flip cover. Any advice on how to turn on/off screen when open/close cover?
Click to expand...
Click to collapse
Is it a smart flip cover? Link to the product details?

Hello..
I love xperia sound enhancement instead of viper or atmos.
my question are:
1. have you try installing such as mod on Mia1? is it applicable on oreo?
2. do you have any mod version recommended for mia1?
3. i'd love if it's magisk friendly any suggest?
thanks in advance for the answer..

varben said:
Is it a smart flip cover? Link to the product details?
Click to expand...
Click to collapse
Well I think it is: https://m.pt.aliexpress.com/item/32...32835263750&shortkey=bUvYjAfQ&addresstype=600
Any ideas?

varben said:
Boot into twrp, find the folder substratum in your internal sd card and flash the rescue zip file. (Or uninstall, can't remember the exact name of the file)
Click to expand...
Click to collapse
bro r u sure it will work?
For now I don't have twrp install in my device but I will boot twrp but if I found no rescue file in substratum folder then?

edgardurao said:
Well I think it is: https://m.pt.aliexpress.com/item/32...32835263750&shortkey=bUvYjAfQ&addresstype=600
Any ideas?
Click to expand...
Click to collapse
That doesn't look like a smart cover. So you can't use it to turn screen on/off by opening and closing the cover.
Sorry!

shafayetsabbir3 said:
bro r u sure it will work?
Click to expand...
Click to collapse
Can you try it? It's safe to do it.

varben said:
Can you try it? It's safe to do it.
Click to expand...
Click to collapse
Ok bro... I will try that tomorrow.. If it work then u save my life.. Actually there is lots of important data which I don't wants lose..

many people have faced with proximity sensor issue on devices such as redmi 3s, redmi note 3, note 4, redmi 4x, mi a1 and others ... the problem occurs when incoming calls, but xiaomi does not respond ... can someone look at the logs and fix this? Can someone help?
http://c.mi.com/thread-517279-1-1.html
http://c.mi.com/thread-294939-1-1.html
http://en.miui.com/thread-1341151-1-1.html
there's so many proximity sensor bug reports. Why does no one want to solve this problem? I have two devices (Mi a1, Redmy note 3 pro) with an incorrectly working proximity sensor.

proximity sensor - screen not turning off during calls

Hello forum,
after digging around in plenty of places:
the screen of my S10+ (G975F) does not turn off, during phone calls. it used to work for a while, when i bought it, but one day it stopped.
testing with *#77692# shows a working sensor.
installing Lineage OS 17, i find it working normally. but Lineage is no go, as with the poor coverage here at home, i depend on Voice over WiFi.
so i assume, it's software, not hardware.
i tried about all updates from Samsung, until now, apart from G975FXXU4CTC9. As i read, that there are some quirks with TWRP, i hesitate to install this, as the downgrade isn't possible, after my understanding.
i found out that deactivating google playstore and everything xy.setup keeps the sensor working. it stops, after connecting to playstore and doing updates. so i still think it is definitely not hardware. but what else could be the cause ?
did someone else come across this problem and eventually really solve it ?
thanks for Your help
roland

blackspy_ said:
Hello forum,
after digging around in plenty of places:
the screen of my S10+ (G975F) does not turn off, during phone calls. it used to work for a while, when i bought it, but one day it stopped.
testing with *#77692# shows a working sensor.
installing Lineage OS 17, i find it working normally. but Lineage is no go, as with the poor coverage here at home, i depend on Voice over WiFi.
so i assume, it's software, not hardware.
i tried about all updates from Samsung, until now, apart from G975FXXU4CTC9. As i read, that there are some quirks with TWRP, i hesitate to install this, as the downgrade isn't possible, after my understanding.
i found out that deactivating google playstore and everything xy.setup keeps the sensor working. it stops, after connecting to playstore and doing updates. so i still think it is definitely not hardware. but what else could be the cause ?
did someone else come across this problem and eventually really solve it ?
thanks for Your help
roland
Click to expand...
Click to collapse
Check in setting/running apps,
some apps are using the sensor so you are getting this problem.
If you cannot fix this problem then try wiping cache only not data.
Sent from my P5 mini using premium XDA app

PrashannaGP said:
Check in setting/running apps,
some apps are using the sensor so you are getting this problem.
If you cannot fix this problem then try wiping cache only not data.
Click to expand...
Click to collapse
I wiped everything about a dozen times. it happens after fresh install, when google is doing its first setups and updating the playstore/framework. and also in safe mode, where no apps should be involved.
the only way not to have it, is to deactivate everything "google" and "setup" without SIM and WLAN. re-activating them, later, leads to the same problem again. no additional apps installed.

blackspy_ said:
I wiped everything about a dozen times. it happens after fresh install, when google is doing its first setups and updating the playstore/framework. and also in safe mode, where no apps should be involved.
the only way not to have it, is to deactivate everything "google" and "setup" without SIM and WLAN. re-activating them, later, leads to the same problem again. no additional apps installed.
Click to expand...
Click to collapse
What could be the problem then! I never had this problem ever with same device and same rom too
Check your hardware using
HTML:
CPU-Z apk

PrashannaGP said:
:
Check your hardware using
HTML:
CPU-Z apk
Click to expand...
Click to collapse
as mentioned before: the hardware is ok, otherwise it would not work with *#77692#, nor in lineage OS. an other way to have it working is: re-lock bootloader and unrooted stock. so definitely not hardware

blackspy_ said:
as mentioned before: the hardware is ok, otherwise it would not work with *#77692#, nor in lineage OS. an other way to have it working is: re-lock bootloader and unrooted stock. so definitely not hardware
Click to expand...
Click to collapse
I got the solution
If you have a perfectly working custom ROM or stock ROM then from that rom get
system/lib/hw/sensor.so file something like that and replace the folder that you currently have
And make sure you put the permission as rw-r-r
Use es file explorer
System/lib/hw/sensor....so file
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my P5 mini using XDA-Developers Legacy app

PrashannaGP said:
I got the solution
If you have a perfectly working custom ROM or stock ROM then from that rom get
system/lib/hw/sensor.so file something like that and replace the folder that you currently have
Click to expand...
Click to collapse
so, i assume that i grab the file when the phone is still working properly and then replace it, once the problem showed up again - correct ?

blackspy_ said:
so, i assume that i grab the file when the phone is still working properly and then replace it, once the problem showed up again - correct ?
Click to expand...
Click to collapse
grab that sensor.so file and paste in to the /system/lib/hw/..........paste....here
it is not correct because when you replace the file your device will reboot but no worries
when your device restarts
and go to the place where you replace the file /system/lib/hw/........sensor.so.....may be...
and change the permission of the file to
rw-r-r
Click to expand...
Click to collapse
and only this will work.
once you change the permission using ES file EXPLORER or ROOT Explorer
you have to reboot twice.

PrashannaGP said:
and go to the place where you replace the file /system/lib/hw/........sensor.so.....may be....
Click to expand...
Click to collapse
"sensor.so" does not exist, neither in the above path, nor anywhere else on the device
i attached the searchresults for "sensor.so" and just "sensor". the only thing that comes close to what you wrote, is sensors.exynos9820.so. but that is in /vendor/lib/hw.
i'm a bit lost there

blackspy_ said:
"sensor.so" does not exist, neither in the above path, nor anywhere else on the device
i attached the searchresults for "sensor.so" and just "sensor". the only thing that comes close to what you wrote, is sensors.exynos9820.so. but that is in /vendor/lib/hw.
i'm a bit lost there
Click to expand...
Click to collapse
Yes what I am telling you is to replace the sensor file not necessarily it should be in other folder with .....name.....
Only the thing is to change the file carefully and change permission to
rw-r-r
That's all its not necessary where the location is.
Sent from my [device_name] using XDA-Developers Legacy app

PrashannaGP said:
grab that sensor.so file and paste in to the /system/lib/hw/..........paste....here
.
Click to expand...
Click to collapse
unfortunately, replacing
/vendor/lib/hw/sensors.exynos9820.so
and
/vendor/lib64/hw/sensors.exynos9820.so
with the ones from when it was working, did not help.
and yes, i did change to rwx rxx rxx
interesting is, that it works the whole day, until ... 05:20 in the morning - then it stops. after that the problem stays permanently

blackspy_ said:
unfortunately
and yes, i did change to rwx rxx rxx
Click to expand...
Click to collapse
I told you to change from rwx rxx rxx to rw r r
you did this??
rwx rxx rxx
Click to expand...
Click to collapse
which is incorrect
should be this
Code:
rw r r

PrashannaGP said:
I told you to change from rwx rxx rxx to rw r r
you did this??
Click to expand...
Click to collapse
just wrote it wrong: rw- r-- r-- like all the other files.
i'll do some testing now, how to restore to working again. apart from installng from scratch ...

PrashannaGP said:
Code:
rw r r
Click to expand...
Click to collapse
blackspy_ said:
i'll do some testing now, how to restore to working again. apart from installng from scratch ...
Click to expand...
Click to collapse
in fact, it is very hard to get rid of it. resetting the phone, wiping whatever, reflashing, changing version or region of OS don't help at all, custom ROMs neither. aborting a flash, or flashing the wrong firmware neither. the only thing that helped this time, was to insert another simcard.
but after installing two more apps this morning (3C Toolbox and Nova Launcher) the problem is there again.
but this time the SIM-card trick doesn't help. uninstalling the two apps neither. this seems to work only once.
i think i will start from scratch i.e. re-lock/unlock bootloader ...

blackspy_ said:
i think i will start from scratch i.e. re-lock/unlock bootloader ...
Click to expand...
Click to collapse
yes rooting and flashing custom roms means having too many bugs.
And Even sometimes the official software updates have bugs.
No one except the rom developer can fix the problem.
The method that i told you was for fixing general bugs of sensors and camera.
The android is a complex coded Operating System and is attached to every files and empty folder and also if the empty folders are deleted then it will start many proplems.

PrashannaGP said:
The method that i told you was for fixing general bugs of sensors and camera.
Click to expand...
Click to collapse
this and nothing else does help right now. even going to stock with locked bootloader. the phone screen stays on. it only works in lineage OS.
update:
got it working again, by 1st doing an improper rooting i.e. flash stock and then not let it boot up
2nd try to flash the patched AP which aborts 3. flash stock again and root it properly.
then delete all the settings from what's called "setup", "update" and so on - all what is being done at 1st. start. then deactivate all those apps, do another reset from menu, but not boot to TWRP, where the reset will be completed. all this was done without network and playstore and with no simcard.
i don't know at what point it started working again, but right know, it does. will set it up properly now, as i expect it to be working after setup. it will only stop tonite around 05:20 CET --- i hope.
don't know if all this clarifies anything ...