How to screen record on nexus 5

How to screen record on nexus 5 - Nexus 5 General

screen-record-adb
One of the newer features in Android 4.4 – KitKat includes the ability to record your screen. Which is something I’m in love with right now. It definitely helps when I’m doing tutorials, like this one. Instead of recording it with a separate camera and having to worry about lighting and such. This way is much easier and preferred in my opinion. To record your screen, it’s actually quite simple. You do need to have the Android SDK installed to be able to do this. Once it’s installed, just navigate to the platform-tools folder and open up a command prompt window. Then enter the following command:
adb shell screenrecord /sdcard/filename.mp4
As you can see in the image above, I named it screenrecord-sample.mp4. I actually have a quick sample of a screen recording down below that you can check out. The quality may not be that great, but you can change that. By default it does it at 4mb bit rate. But luckily you can change that. The preferred bit rate for me is 8mb, which you add into the command so it looks like this:
adb shell screenrecord — bit rate 8000000 sdcard/filename.mp4
That allows you to record at a higher bit rate which is always good, and better for viewers. The screen recording has a limit of 3 minutes. So you can’t go longer than 3 minutes, and it’ll actually disconnect shortly before then. Which kinda sucks, but I’m sure there’s a reason behind it. It’ll continue to record your screen until you go into the command prompt and press Ctrl+C to stop it. Then you’ll find the screen record in your gallery under the name that you made for it.
It’s actually really simple, and we’ll definitely be using this for some tutorials and how to’s in the future here at Android Headlines. Stay tuned for plenty more Nexus 5 and KitKat coverage.
Sent from my Nexus 5 using Tapatalk

Related

[APP] Call recorder (ROOT access needed) [Nov 24 update]

I wrote this program because I was unable to find a good app capable of recording the other side of the call properly.
Except for AirVoice, all such apps record the speaker rather than the line, and you barely hear the other side in the recordings.
The guy who wrote AirVoice knew the trick but seemed to be very annoyed by the negative feedback from Android Market, where the users of various devices (with the list of supported ones clearly stated!) tried to install that program. Because it wasn't open source, I had to disassemble it in order to write what I wanted exactly.
So the app uses an esoteric HTC driver, and NEEDS THE ROOT ACCESS just to open the device. If you do "adb shell chmod 666 '/dev/voc*' ", it'll never ask you for root access (but you have to be ROOT to execute that command).
It writes the calls in either WAV (recommended) or MP3 format (not tested much; needs some time to encode the file after the call, but the size is about 4 times smaller), stereo (left ear is your voice, right is that of the other party), to "/sdcard/voix" directory.
The kernel driver itself is kinda buggy. Actually, the auto-answer mode is non-functional for kendon's & ninpo's kernels (others not tested). Do NOT select it in Settings unless you've got such ROM and particularly need to reboot your phone on each incoming call . It'd be nice if somebody try to fix that.
If you select "Ask each time" for any incoming calls, be sure to wait half a mo until the confirmation dialog appears. The "Foreground service" (default) setting is also recommended because Android may otherwise kill it if memory is low.
Any comments are welcome. I'm not sure that I'll ever add something to this program because I'm too lazy for that, but any bugs will reasonably be fixed. The code is open source, PM me if you're a programmer and have any ideas how to improve it.
=======================
NOV 24 UPDATE
Numerous improvements/corrections/bugfixes (I'm not removing the previous version as this one haven't been much tested).
Enjoy!

Thanks dude. Great job

avs333 said:
I wrote this program because I was unable to find a good app capable of recording the other side of the call properly.
Except for AirVoice, all such apps record the speaker rather than the line, and you barely hear the other side in the recordings.
The guy who wrote AirVoice knew the trick but seemed to be very annoyed by the negative feedback from Android Market, where the users of various devices (with the list of supported ones clearly stated!) tried to install that program. Because it wasn't open source, I had to disassemble it in order to write what I wanted exactly.
So the app uses an esoteric HTC driver, and NEEDS THE ROOT ACCESS just to open the device. If you do "adb shell chmod 666 '/dev/voc*' ", it'll never ask you for root access (but you have to be ROOT to execute that command).
It writes the calls in either WAV (recommended) or MP3 format (not tested much; needs some time to encode the file after the call, but the size is about 4 times smaller), stereo (left ear is your voice, right is that of the other party), to "/sdcard/voix" directory.
The kernel driver itself is kinda buggy. Actually, the auto-answer mode is non-functional for kendon's & ninpo's kernels (others not tested). Do NOT select it in Settings unless you've got such ROM and particularly need to reboot your phone on each incoming call . It'd be nice if somebody try to fix that.
If you select "Ask each time" for any incoming calls, be sure to wait half a mo until the confirmation dialog appears. The "Foreground service" (default) setting is also recommended because Android may otherwise kill it if memory is low.
Any comments are welcome. I'm not sure that I'll ever add something to this program because I'm too lazy for that, but any bugs will reasonably be fixed. The code is open source, PM me if you're a programmer and have any ideas how to improve it.
Click to expand...
Click to collapse
thanks, good job
but recorded sound a lit low, any chance to make it loud

Aha Thats Great Now i can prove my prank calls

no auto start, please add (i mean after re-boot)

Hi-Fi said:
but recorded sound a lit low, any chance to make it loud
Click to expand...
Click to collapse
No problems with sound volume here, but I'll see if I can add some basic volume normalisation...
Hi-Fi said:
no auto start, please add (i mean after re-boot)
Click to expand...
Click to collapse
Added as an option in Settings. Also fixed a triffle UI bug (forgetting to set proper dialog attributes).

Just tried this, works great on my Hero (Vanilla Eclair 4.0). Thank you very much for this one!

Interesting software. Could you possibly add a new feature: The app saves all calls, but deletes them, if you don't move them to another folder/to your PC.
This because I could record all of my calls, without the risk of making a huge 1Gt folder to fill up my memory. So if the user could choose how many recent calls (2,5,10) the app saves before deleting them I'd be great!

What about battery draining?
This great app is also tiny enough not to reduce drastically battery duration?
TIA

I'd love to see this generalized to not require the HTC driver. Do you think that would be possible?

cool app. anyone know if it would be possible to play an audio file directly to the caller? would come in handy rickrolling damn telemarketers

Very good work. Handy app, for sure.
Can you enable recording mid call?

Works in all Androis Devices? I have a Milestone.

Awesome idea, I've been looking for exactly this sort of software.
I'm having a bug I hope someone can help me with. When I start the program I get a prompt that says "Device does not exist, or its permissions cannot be changed." When I click "OK" it takes me to the screen to uninstall the program.
I'm running an Evo, fully rooted, NAND unlocked, running Virus Airbourne ROM and King #11 kernel.
I never get the prompt from the SuperUser app to give the app root access.
I tried the adb command but it gave me the error:
Unable to chmod dev/voc*: No such file or directory

Having same issue on rooted G2.
Sent from my T-Mobile G2 using XDA App

MercuryTangent said:
Awesome idea, I've been looking for exactly this sort of software.
I'm having a bug I hope someone can help me with. When I start the program I get a prompt that says "Device does not exist, or its permissions cannot be changed." When I click "OK" it takes me to the screen to uninstall the program.
I'm running an Evo, fully rooted, NAND unlocked, running Virus Airbourne ROM and King #11 kernel.
I never get the prompt from the SuperUser app to give the app root access.
I tried the adb command but it gave me the error:
Unable to chmod dev/voc*: No such file or directory
Click to expand...
Click to collapse
I experience the same problems on my rooted DINC. ROM and kernel are in sig.

Am I right to assume that this is a HTC Hero exclusive?

bemymonkey said:
Am I right to assume that this is a HTC Hero exclusive?
Click to expand...
Click to collapse
Likely so, but I'm hoping the dev will extend it or I can find a way to make it work

This is amazing app. The only thing I would beg the author to consider a white status bar icon for normal running service as colored icons there usually break the aestetics of Android UI. The icon can change or become colored while recording, but when only running in the background it should remain white.

I have the same problem (link to uninstall) on my Nexus One. Everything works fine on Hero

[APP] AudiobookMark [R] 2011-01-13 [V]1.0

Name: AudiobookMark
I was frustrated by the lack of built-in support for mp3-based audiobooks so I wrote this app. It lets you load as many audiobooks as you have memory for. It remembers where you are in each file of each book (and of course, which file you are listening to for each book).
It has standard transport keys plus the ability to enter HH:MM:SS to skip directly to.
Download Link: social.zune.net/redirect?type=phoneApp&id=b1cab14b-e91d-e011-9264-00237de2db9e

Is this a free app?

Its a 0.99 app, with a free trial that basically let's you use it without limitation, but pops up a message box occasionally...

Can you add support for a sleep timer? So you need to shake the phone every 15 mins or it will pause the audio book.

That sounds like a useful addition. Let me think through how best to implement it, and I'll try to add it in with "run under locked screen" update I'm working on...

elmstrom said:
Can you add support for a sleep timer? So you need to shake the phone every 15 mins or it will pause the audio book.
Click to expand...
Click to collapse
I would also really like this.

Hey dbroome, this sounds like it has the potential to be an awesome app. I'm so used to the Mortplayer audiobook app on Android and really enjoy using it (great alternative to music btw).
So by mention of "remembers where you are" you mean bookmarks are automatically placed for us? I ask because a cool feature of the mortplayer app was the bookmark feature where you can tag certain spots on demand and go back to wherever you tagged. I hope you go far with this app, it really does sound promising.
The UI looks good too!

I had not heard of Mortplayer, I'll have to check it out, though I don't have an Android device to be able to get a good look at it.
You are correct in that the app places the bookmark for you. It basically remembers where you were in each file.
How do you use the "tag different places in a file" type feature in your audiobook listening? I generally am just listening to novels, and don't have any real need to jump to various spots in the same file.
The reason I ask is that I'd like to implement features users would use, but don't want to overly complicate it with feature bloat.
As an update, I have implemented and am testing three new features. Once I make sure it is working as expected, I'll submit the update to the marketplace:
1) Configurable port on the loader (8001 might not be convenient for everyone. Should have thought of this before)
2) Run under locked screen. Now you can lock the screen to save battery power
3) Configureable sleep timer (with optional shake to reset).
I hope to submit it in the next day or so...

Thanks / Volume / File Corruption
First I love the app. I have been writing down my numbers until this app came along. Thank you dbroome.
Second, I noticed the volume is weaker than the default music player; has any one else notice this?
Third, I received a file corruption error message saying it couldn't determine the file lengths and displays all .MP3s as being 00:00:00 in running time. The files didn't play, but after a reboot they started too but still display the zero length; anyone have any thoughts?
Thanks!

Also needs skip forward/skip back button that just goes 30 sec back/fprward. The current skip to a location is not usable when driving.
Bonus points for a ui redesign with bigger buttons.
Additional bonus points for a fast play (i.e. play back at 150% speed with no pitch shift).
For me to purchase, I need:
Play under lock screen
Uploader program to work (changing ports might help)

In order to determine the length of the mp3, the player has to actually open the file and then close it. The Zune software interferes with the player opening the file after upload, and as such you have to unplug the phone from the computer after uploading before closing the "I'm done" pop up box. I'm guessing that the 0-length issue might have been due to that. Try deleting that book and re-loading it to the phone, making sure to unplug the phone before continuing (or, alternatively, using the SDK's WPConnect.exe which doesn't interfere with the media being opened).
It might be useful to add a "determine durations" type button on the load screen that would let you try to determine them again at a later time instead of re-loading them. What do you think?
30 second skip could definitely be useful. I'll see if I can find a good way to incorporate it in the next update.
I really want fast play as well. Unfortunately the MediaElement player I have to use to be able to set positions doesn't support it. I'll definitely be watching the updates as they come out for supporting that.
I'm dreadful at UI stuff, but I have a friend who I can probably rope into giving it some love.
Play under lock and the configureable port are in the next update, which I will finish testing and submit tonight...

Cool. Bought it as an encourgement.
For UI ideas look at audiobook player 2. It is much easier to use while driving.
Suggestions
Your [skip to a time] section shouldn't be on the main page, but off a toolbar option.
Your play/pause button should swap between play/pause depending on state rather than changing the background colour.
Use images rather than text in the buttons [|<] [<<] etc

v1.1 has been approved and should show up in the marketplace shortly. This adds a sleep timer (with optional shake to reset), play under lock, and configureable port on the loader and phone.
Next update will hopefully be a ui re-do, possibly adding the "skip xx seconds" idea.

Downloaded the update for the app, re-uploaded the audio book, followed instructions on the pop up (after upload completed) and the software recognized the full lengths. Very nice! Thanks dbroome!! The mp3s seem to have uploaded a little quicker too or is it this just me?
FYI, using a colon within the name of a book crashes the app (at least it does for me).

Good find. I'll correct that.
Waiting on a friend with some design skills. If he doesn't come back to me soon, I'll go looking for free images to include on the buttons and do a general usability re-skin of the ui...

Is this the correct website: http://davidbroome.com/AudiobookMark
I am just getting Bad Request (Invalid Hostname) when I try to goto it. Also the volume seems low on my Samsung Focus. Good work though, I am going to buy it.

Thanks!
The website had a temporary issue and should be resolved.
I'm looking into the lower volume and should have at least an answer soon if not a fix...

it's a very nice little app and I'm using it now for a few weeks.
But I've found when you have to many audiobooks or when the aaudio-files are very big (about 6 MB's) the program can't determine the length of the audio-files any longer...
Maybe we can get an update for that?

The only time I have been able to load an audio file the program could not determine the length of was when I forgot to unplug the phone from the Zune software when prompted. I have tested files up to 50 mb. Of course, it could be file dependent. Did the file play even after the length failed to update?
Fortunately I am almost done with the next update that includes code to re-check for the length of files if it fails the first time. I need to finish the "Load from DropBox" functionality that I am implementing and then I can submit it. Hopefully this week!

Yes - I can start the player and I can play the file even when it says the length is 00:00:00.
This morning I've transferred some 300 MB audiobook-files to my HD7. After that I disconnected the device and it started "determining length of..." and it immediately started playing the first file (10.7 MBs) but even after 20 minutes it just couldn't find the length of the first audio-file so I stopped the program.

[UT]Ubuntu Touch First Look - a personal Review

Hey guys! I’m doing a personal review of Ubuntu Touch on the Nexus4 device, and I thought I could share it with you.
It’s kind of a “Pros and cons” thing, but since I tend to get off-topic easily and babble a lot I’ve divided things in sections,
so you don’t have to read everything should you not want to.
Here it goes - Ubuntu Touch on the Google Nexus 4 (mako).
Installing Ubuntu has always been a pleasant experience for me. It feels open. Feels different. Feels fresh. Feels UBUNTU.
Installing any linux distribution on any PC makes mu blood run like crazy and Ubuntu Touch makes no difference.
It’s exciting to see something new and beautiful done for phones. And it’s even more exciting when you see it’s done with taste.
Now just to be clear – when it comes to Pros and Cons I guess the “Cons” section would be obviously much larger,
but hey: it’s a developers preview of what we should be expecting so I’m willing to suck some things up.
Pros:
1. Design.
Ubuntu Touch feels like Ubuntu in your hand. I just have to say this. I’m not sure if it’s the fonts or the wallpapers or the
transitions or the launch pad on the left or something else that I couldn’t quite grasp and understand,
but the fact is UT feels right. Feels Ubuntu.
2. Screen usage
Almost every other mobile OS has some buttons be it hardware or software (eg. Android’s software buttons on the screen + the 3-dot thingy).
Ubuntu gives you the whole screen to have for yourself and your app. It’s amazing how even the “Contacts” app feels bigger and more open.
3. Docking
I haven’t had the chance to go through the UT docking experience yet. I don’t even know if it’s quite baked yet, but what
I’ve seen on videos and ads is pretty awesome. The very idea of it makes it way cool. Chuck Norris cool.
The vision that one can have his PC in his pocket at all times is nothing but genius.
4. Compatibility
Ubuntu aims to be compatible with lots of devices. Which is good, I guess. I just hope compatibility doesn’t come
at the expense of stability or power management or something else that might come along and present itself as an issue.
5. Stability
I am yet to witness an app to crash or force-close or just close or anything like that.
I do get some strange freezes for a few seconds every now and then though.
Cons:
1. Installation
Installation can present itself to be harsh on someone who know nothing about using the terminal. There was a small step
missing in the installation tutorial which can cause some people to get confused. Mainly people with no
prior unlocking/rooting/flashing ROMs experience.
2. Boot
No boot animation. First time the phone booted it needed quite some time and there wasn’t even a splash screen indicating
something was working. The screen had the backlight on and that was it. No shutdown animation as well. And while we’re
still on the subject: there is no shutdown menu, which was kind of strange – I mean when you hold the power button the
phone just shuts down – no questions asked. I guess that might be good in some situations, but I’d rather have the shutdown menu.
3. Overall performance
Overall performance is laggy. The “use-of-edge” design is pretty neatly thought of, but in real life it need polishing. A LOT of polishing.
Swipes act strange, I move from app to app by accident.. My personal guess is that one can get used to it in a couple days
but the swipes should take a step towards being more intuitive as well.
I didn’t like the fact that the music page doesn’t stream anything, but takes you to the browser and when you hit play on some
hit you’re supposed to hear you get a message that flash is not supported or crashed or something like that. It’s kind of frustrating.
I think a native app should be replacing that page on the home screen real soon.
4. Social media
Neither Facebook nor Twitter have native apps. All you get is a mobile version in the browser. I don’t think it needs further explanation.
I hope both Facebook and Twitter do something about this. I don’t think it’s up to Canonical to make apps for those… or up to the
community for that matter. Anyway. I didn’t see a LinkedIn, Pinterest or any other social platform on the suggested apps, so
I guess I’ll just stop here.
5. Graphical glitches
Sometimes things will shift aside or up and down and text would overlap. It’s not something you can’t live with – a simple swipe one
way or another – fixes it, but I think all would agree it’s not an eye-candy feature. There are a few of these throughout the system.
It’s nothing serious in my opinion, but I couldn’t bring myself to put it in the “Pros” section.
The clock disappeared form everywhere except the clock app. I mean it – everywhere. It’s not on the homescreen,
it’s not in the “notification bar”, it’s nowhere. It happened after I rebooted the device for the first time. Also alarms don’t
seem to be working at all.
//* after a second reboot clock reappeared. Alarms still don’t work though.
Another thing is after picking up a call and finishing it – when you put the phone away from your ear the screen won’t turn on by itself.
That’s kind of odd if you ask me. It’s like it knows I’m saying “goodbye” and saves my battery or something. It’s a minor setback,
but still. I noticed that during the dialing process screen lights up if you take the phone away from your ear. I haven’t read a lot of
UT documentation, so it might be on purpose – I’m just stating what I’ve experienced.
6. Navitagion
Navigation is bad right now, I think. It looks like the OS isn’t sure how to respond to your swipe. Transitions are slow in my opinion.
They should be a tad faster. A major setback is the back button. I mean seriously – how many times do you misclick on something
and want to go right back. Think about it. It’s at least a few times a day. I think the back button should be visible the first few seconds
along with the rest of the app menu – should there be one. Or maybe just put it in the top left corner next to the search. If you think there
is no space – the search can always morph into “just a button” ... Other than that I can’t complain about navigation – it’s pretty neat,
actually. Menus are simple and understandable.
7. Hardware glitches
Everytime I wake my device up my Bluetooth is ON and I need to turn it off manually.
I can’t say I like that at all but considering that is all I have to say about hardware glitches I think it's not that bad.
8. 3G
3G is really important. AND it works! There’s just now way to shut it off.
I mean sure – you can turn off the mobile data, but when it comes to choosing whether to use 3G or 2G Networks Only – you don’t really have a choice.
You’re stuck with 3G and all the disadvantages that come with it as well as the advantages.
//* We all know what happens to your battery when using 3G and I’m the kind of guy that doesn’t like to turn his mobile data ON and OFF all the time – it just stays enabled all the time and saves me whole lotta thinking. Not having the choice of switching back to “2G networks only” sends you straight in hell in terms of battery life.
9. Syncing
Since I’m obviously new to Ubuntu Touch I just recently started using Ubuntu One, but my gosh! Syncing contacts with Google is a
real pain in the ass. Since the Gmail app is not a native app, but a HTML5 client instead, syncing appears to be impossible at this point.
Users are forced to hook their devices up to a PC running Ubuntu and write a bunch of commands in the terminal over and over again,
since syncing only works for no more than 50 contacts at a time. That being said I have over 600 so I had to run the damn thing 12 times
in a row. Aside from that should you choose to add a new contact it won’t sync with Google automatically and upload your new contact
into the cloud where you can have access to it at anytime.
//*Note: AFAIK: iOS, WM and Android have pretty easy ways to sync contacts with Google. I think this is one of the things the guys at Canonical should focus on. Slick mail application and neat contacts syncing is vital to a lot of people and is a major reason why they never switch phones.
Final thoughts:
Ubuntu Touch aims to deliver something different and really special to consumers: a PC inside a phone. I think what they are truly
missing here is an app store of some kind. The OS suggests apps but I couldn't see an app for that and I'm guessing that is somewhat of a
setback as well. They’ve been doing really well and while for now the “Cons” section is significantly larger than the “Pros”
I have hope and faith that Canonical will pull this off eventually.
Aside from the hard installation and the lack of an eye-candy boot animation… and maybe some other minor tickles - the OS looks
and feels nice and really pretty in the palm of one’s hand. They still have a lot of work to do if they ever want to catch up with Android or iOS
in terms of usability, syncing, MTP and other stuff that average consumers don’t know and don’t need to worry about but would miss a lot.
If you don’t don't mind the fact it’s a developers preview and the camera doesn’t always start off properly and you have to shut it down and run it again it’s pretty impressive!
Conclusion:
There are a lot of words one can use to describe Ubuntu Touch, but in my opinion the high order bid is “Inspiring”.
Yes, there are some glitches here and there. There is a lot to do. But after seeing it and touching it with my own eyes and fingers well…
I have to say this – I am thrilled and I can’t hardly wait to see what will they make of it.

littlegreen said:
Yes, there are some glitches here and there. There is a lot to do. But after seeing it and touching it with my own eyes and fingers well…
I have to say this – I am thrilled and I can’t hardly wait to see what will they make of it.
[/I]
Click to expand...
Click to collapse
Honestly, i think this is nothing new and nothing special ;/.
UPD: The problem is your article is too generalised, viewing stuff too objectively. Your article must show your personal opinion and vision on stuff, more than boring facts.
And don't use Pros/Cons style, when it's all about cons, not pros. Just don't.
Sent from my Nexus 4 using Tapatalk

reqmon said:
Honestly, i think this is nothing new and nothing special ;/.
UPD: The problem is your article is too generalised, viewing stuff too objectively. Your article must show your personal opinion and vision on stuff, more than boring facts.
And don't use Pros/Cons style, when it's all about cons, not pros. Just don't.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Well since I only have a few hours of experiencing the OS I don't think generalising is an option per say.
Besides - I am an optimist. I try to see the good in everything and that is why I have the "Pros" list. Thanks for the advice though.

well i find your review interesting to learn about the basics of ubuntu
Can you report about the battery performance?

OEM skin/software

Are you comfortable in your own skin? Is your phone comfortable in its skin? Rate this thread to express how you deem the skin on the Google Pixel 2. A higher rating indicates that you love it: it adds just the right amount of features, it's visually pleasing, and overall it's additive to the experience. If this is a Nexus phone (you didn't think we hand-wrote all of these prompts, did you?) then use this rating to indicate how the latest version of Android looks to you.
Then, drop a comment if you have anything to add!

I'm annoyed at being a beta tester for Oreo. There are clearly bugs that cause stuttering on my device.

As simple as it can be. Every phone should start this way.

No complaints here. I'm glad this phone wasn't load with bloatware or unnecessary apps.

Honestly, it's too basic. I appreciate how light it is, but it could really use more features built in to make the phone more customizable.

PuffDaddy_d said:
Honestly, it's too basic. I appreciate how light it is, but it could really use more features built in to make the phone more customizable.
Click to expand...
Click to collapse
Could you make some concrete example of important missing features in android 8.1 stock?
I'd like to buy it, but I need more info first.

Could benefit from being able to make folders in the app drawer, also be able to hide apps to keep the app drawer tidy.

isaak said:
Could you make some concrete example of important missing features in android 8.1 stock?
I'd like to buy it, but I need more info first.
Click to expand...
Click to collapse
Cannot program hardware buttons to launch custom quick actions like flashlight or calculator.
No native theme support.
Cannot take a scrolling screen capture or edit the screenshot immediately before sharing or saving.
No support for advanced gestures to launch shortcuts.
Basically, you can't do anything that most other manufactures bake into their skins. I know the XDA community has historically hated skinned versions of Android, but the hardware couldn't keep up with the software in years past. Now, it's no longer an issue for most mid range and higher devices and the additional features of those skins are sorely missed in the Google Pixel line.
I had to root just to do half of what is listed above.

linkisoc said:
Could benefit from being able to make folders in the app drawer, also be able to hide apps to keep the app drawer tidy.
Click to expand...
Click to collapse
Why not just use a custom home launcher like Nova? It's fast anyhow

PuffDaddy_d said:
Cannot ... edit the screenshot immediately before sharing or saving.
Click to expand...
Click to collapse
.............uh....yeah, You can. Just took a screenshot. Opened up the screenshot and hey look, an edit option.
The only feature i'm interested in, though, is a Private Mode. I loved it on my Galaxy S6. Any pictures I took while it was turned on were completely hidden as soon as I turned it off. I know there are apps out there for hiding pictures but
A. do I really trust them that much?
B. You have to take a picture, open the app, enter your password, select "import", select you image(s), select enter. It was nice just being able to tap "Private Mode" and enter my pin and BOOM. Done. From there, just take a picture and it automatically saves to the private folder.

matrix0886 said:
.............uh....yeah, You can. Just took a screenshot. Opened up the screenshot and hey look, an edit option.
The only feature i'm interested in, though, is a Private Mode. I loved it on my Galaxy S6. Any pictures I took while it was turned on were completely hidden as soon as I turned it off. I know there are apps out there for hiding pictures but
A. do I really trust them that much?
B. You have to take a picture, open the app, enter your password, select "import", select you image(s), select enter. It was nice just being able to tap "Private Mode" and enter my pin and BOOM. Done. From there, just take a picture and it automatically saves to the private folder.
Click to expand...
Click to collapse
That's not what I mean. The screen shot of already saved; therefore, as you said, you have to open the saved file and then edit and then save again. I'm taking about doing it right from the screenshot menu that many other Android devices have. Even the crappy iPhone has it.

Great , i want to try it next time

How To Guide Enable Native Call Recording + OP Stock Dialer on OnePlus 10 Pro

Hi guys,
Just upgraded from OP7T to OP10 Pro as a European user.
Call recording functionality does not come with the device here.
Had native call recording enabled on my OP7T through jOnePlus Tools and the likes.
Jtools Oneplus does not install on our device.
Don't want to give up this very important functionality.
I'm sure there's a bunch of peeps here just like me.
To be clear, I haven't succeeded yet and I'm not a developer.
Hoping someone smarter than me can appreciate what a wonderful breakthrough it would be to make this work on the OP10 Pro.
I made some progress and have some clues which I'll share in summary below:
OP10 Pro comes with Google Dialer, not OnePlus dialer.
Google dialer natively either prohibits call recording or when succesfully enabled transmits a voice message to the other party disclosing the call is being recorded.
Enabled developer options by tapping build number 7 times in software version details (About Phone section in Settings)
In Developer Options: enabled USB debugging & OEM unlocking
jOnePlus Tools app (Play Store) does not install on our device.
Dev replied to a review in Play Store he discontinued further development of the app.
Following page lists what adb shell commands need to be executed to enable native call recording:
Enable Call Recorder on any OnePlus Device [Android 12]
In this comprehensive guide, we will show various methods (both root and non-root) to to enable Call Recorder on OnePlus devices.
www.droidwin.com
Commands on the previous page do not execute, but come back with an error stating "android.permission.GRANT_RUNTIME_PERMISSIONS" must preceed.
"pm grant <android app package name> android.permission.GRANT_RUNTIME_PERMISSIONS" is useless if there's no particular app available you want to do the writing
A YouTube video pointed to the following page providing links to download oos12 working OnePlus Dialer & Contacts app along with instructions to change the default dialer app:
Oneplus Stock Dialer for Oneplus Smartphones running OxygenOS 12
Oneplus Stock Dialer for Oneplus Smartphones running OxygenOS 12. Join Techibee Telegram Channel Join Now WhatsApp Group Join Now Along with the launch of Oneplus 8T, Oneplus started to Include a few google applications like Google Dialer & Google Messaging app as default communication...
techibee.in
The apps work as advertised albeit there's a floating balloon from the Google Dialer appearing overlayed on the OP Dialer when in a call.
After installation, settings of these apps still do not show the option for call recording in the settings options list
I vaguely remember there's a file, that I think needs root access to get to, that can be opened as a text file, in which you can change how your device interprets the region your device is used in, that afterward allows for the otherwise hidden native call recording function to be revealed. But it's been too long since I performed such an operation and can't even remember the name of this file. Maybe the way I explained it triggers someone's understanding here. I'm wondering if this could be a lead to a remaining thing to do to get that call recording function activated.
I fiddled a bit with different ways of writing the cmd adb commands, by for example using the app package names of the installed OP dialer and contacts apps within a pm grant command, but I'm too dumb to get it right, so no luck with that.
Hoping a smarter person here is willing to give it a go and make history
Cheers and godspeed !

Have you tried SKVALEX call recording app? Not sure if it works on Android 12 though. It needs root/magisk to work.

Macke93 said:
Have you tried SKVALEX call recording app? Not sure if it works on Android 12 though. It needs root/magisk to work.
Click to expand...
Click to collapse
Thank you for the suggestion. I am mainly interested in re-acquiring native call recording functionality. I was also informed that Android 12 indeed does not permit any third party call recording apps to function properly. Asides from that, a non-root method is what I pursue as primary objective. But thank you for suggesting, I appreciate it

Got my OP10Pro today too, waiting to see if someone comes up with turning recording on! Such a great feature, would be a waste to miss it!

So for those interested in knowing what the error in adb is that comes back:
Exception occurred while executing 'put':
java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:2663)
at com.android.providers.settings.SettingsProvider.mutateGlobalSetting(SettingsProvider.java:1635)
at com.android.providers.settings.SettingsProvider.insertGlobalSetting(SettingsProvider.java:1589)
at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:591)
at android.content.ContentProvider.call(ContentProvider.java:2473)
at android.content.ContentProvider$Transport.call(ContentProvider.java:521)
at com.android.providers.settings.SettingsService$MyShellCommand.putForUser(SettingsService.java:382)
at com.android.providers.settings.SettingsService$MyShellCommand.onCommand(SettingsService.java:278)
at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
at android.os.ShellCommand.exec(ShellCommand.java:38)
at com.android.providers.settings.SettingsService.onShellCommand(SettingsService.java:50)
at android.os.Binder.shellCommand(Binder.java:970)
at android.os.Binder.onTransact(Binder.java:854)
at android.os.Binder.execTransactInternal(Binder.java:1226)
at android.os.Binder.execTransact(Binder.java:1163)

Hi guys,
Found a solution !
Go to Developer Options.
Scroll to an option near the end of the list called Disable Permission Monitoring --> Enable it & the command ./adb shell settings put global op_voice_recording_supported_by_mcc 1 is now executing.
Make a call from your OnePlus Dialer and behold the native call recording button in all its glory !
Review the call recording from the call log of the number from which you recorded the call OR go to folder Music>Recordings>Call Recordings to find your entire list of call recordings
Please note that as I understand it, this call recording function will not survive a reboot. We need to re-execute this command in adb upon each reboot for the time being.
I also tried disabling the Google Dialer to get rid of that annoying floating bubble overlay on the OnePlus in-call UI, but that simply destroys the in-call UI alltogether by no longer revealing it! So the person who created those OP apps that work on our devices succeeded at making it work by accepting that floating bubble as part of the workaround.
I noticed that on few occasions the OnePlus dialer does not hijack the call in time and the call goes through the Google Dialer in-call UI instead. Anyway, not complaining now that I found it to work at least.
Going to fiddle around with Tasker or some other app that allows me to automate the above adb command to execute upon each reboot.
Edit: Think I'm way to dumb to figure out how I'm gonna be writing this task. If someone savvy can chime in, that'd be great !
Edit 2: Used the following page tutorial to get a paid app called LADB to work on my device that allows me to execute adb commands OTG:
How to Send ADB Commands to Your Own Phone Without a Computer or Root
There are three tiers to Android customization: things you can do by default, things you can do with ADB, and things you can do with root. While root is still pretty tricky to get, ADB mods just got a lot easier. Back in Android 9, Google added a feature that allowed you to wirelessly send ADB...
android.gadgethacks.com
So for now, upon each reboot, I'll just open up this app (you'll need access to wifi every time) and copy/paste the adb command in there without the ./ adb shell part added at the start. So use just settings put global op_voice_recording_supported_by_mcc 1 and tap enter. Boom ! You got call recording back in case you had to reboot OTG.
Still looking forward to find a savvy chap on this thread that can help with automating that adb command upon each reboot

Seems that incoming calls still run through the Google dialer and disables the call recording function again. Needed to execute the command again several times now, whilst I didn't perform any reboots throughout that time that could have invoked that otherwise.
Oberserved if it deactivated after an incoming call, once I noticed that this has happened before. Strangely, last incoming call that went through Google dialer didn't disable it. I may be completely wrong. Something else might be causing that deactivation. Maybe the system's automated security measures baked in are reverting it, idk.
I keep thinking about the build.prop file. I remember something was in there referring to how your device interprets the region it is used in. Supporting/unsupporting region sensitive functionalities. Like call recording..

This is really annoying.
I really liked OP stock dialler and contacts.
Hopefully there will be a way to bring it back without having to root the phone.

Just found this workaround...

No need to root or download all kind of developers apps, I uses on my oneplus 10 pro - oneplus call recorder app from the play store, it records - regular calls, skype, whatsapp, and more...

I tried to use OnePlus Call Recorder but It's renamed app Travis Call Recorder from same developer. The app works like most others, records only silence when using an external handsfree or headphones. the app doesn't replace the native call recorder. Recordings with using OnePlus dialer truly works from guide TechiBee.

Installing the previous version of Joneplus Tools from apkmirror works. Granted adb permissions to the app through LADB (read above) and it seems to work fine.
Also check Techibee's latest video if you want to learn how to properly handle the OP Dialer sometimes not being revealed as the primary Dialer on screen. He also explains how you can access the OP Dialer on incoming calls.
It's a welcome addition to the above advised steps for those who are not in Call Recording native activated regions (Europe, other?...)

I have android 12, on my oneplus joneplus doesn't work on this version any more. And as for the oneplus call recorder, it is available on play store, i have Chinese oneplus 10 pro version ne2210 with European rom ne2215. Its working and recording any call. For the old os i guess joneplus still works, it was working on my previous phone.
Who really wants it, i mean, you need to use adb with developer option to make it work.
But if thats the only option you have, so use it.
Another thing, on the new os, i dont have the phone app from oneplus, its google phone app so i dont think we can add the joneplus and the native call recorder unless you install the phone app from oneplus, but again, you will have to use adb and install updates for the new app by your own, and who knows if that will even work.

I think for you to download the app oneplus call recorder or joneplus, it depends on the os version and also maybe the region that you are in.

I found this link to the app https://www.google.com/amp/s/apkpremier.com/amp/com-travis-callrecorder-oneplus

shhuhs said:
I have android 12, on my oneplus joneplus doesn't work on this version any more. And as for the oneplus call recorder, it is available on play store, i have Chinese oneplus 10 pro version ne2210 with European rom ne2215. Its working and recording any call. For the old os i guess joneplus still works, it was working on my previous phone.
Who really wants it, i mean, you need to use adb with developer option to make it work.
But if thats the only option you have, so use it.
Another thing, on the new os, i dont have the phone app from oneplus, its google phone app so i dont think we can add the joneplus and the native call recorder unless you install the phone app from oneplus, but again, you will have to use adb and install updates for the new app by your own, and who knows if that will even work.
Click to expand...
Click to collapse
Thank you, but what you propose is completely different than what I've created this thread for.
The idea was to find a workable solution in obtaining native call recording inside OnePlus Dialer, whilst Joneplus Tools seemed to no longer install on android 12.
All these things have been RESOLVED and shared above to the extent that it is possible at this time of writing.
In my posts above I've shared links to where the OP Dialer can be downloaded along with a link on how to install it and make it default. I explained how to get the adb command to execute.
I provided a solution for adb OTG (LADB), given the adb command needs to be re-executed at times.
In my last post I also shared that the second to last version of Joneplus Tools DOES INSTALL on our device that comes with Android 12 pre-installed.

anarche_diver said:
Hi guys,
Found a solution !
Go to Developer Options.
Scroll to an option near the end of the list called Disable Permission Monitoring --> Enable it & the command ./adb shell settings put global op_voice_recording_supported_by_mcc 1 is now executing.
Make a call from your OnePlus Dialer and behold the native call recording button in all its glory !
Review the call recording from the call log of the number from which you recorded the call OR go to folder Music>Recordings>Call Recordings to find your entire list of call recordings
Please note that as I understand it, this call recording function will not survive a reboot. We need to re-execute this command in adb upon each reboot for the time being.
I also tried disabling the Google Dialer to get rid of that annoying floating bubble overlay on the OnePlus in-call UI, but that simply destroys the in-call UI alltogether by no longer revealing it! So the person who created those OP apps that work on our devices succeeded at making it work by accepting that floating bubble as part of the workaround.
I noticed that on few occasions the OnePlus dialer does not hijack the call in time and the call goes through the Google Dialer in-call UI instead. Anyway, not complaining now that I found it to work at least.
Going to fiddle around with Tasker or some other app that allows me to automate the above adb command to execute upon each reboot.
Edit: Think I'm way to dumb to figure out how I'm gonna be writing this task. If someone savvy can chime in, that'd be great !
Edit 2: Used the following page tutorial to get a paid app called LADB to work on my device that allows me to execute adb commands OTG:
How to Send ADB Commands to Your Own Phone Without a Computer or Root
There are three tiers to Android customization: things you can do by default, things you can do with ADB, and things you can do with root. While root is still pretty tricky to get, ADB mods just got a lot easier. Back in Android 9, Google added a feature that allowed you to wirelessly send ADB...
android.gadgethacks.com
So for now, upon each reboot, I'll just open up this app (you'll need access to wifi every time) and copy/paste the adb command in there without the ./ adb shell part added at the start. So use just settings put global op_voice_recording_supported_by_mcc 1 and tap enter. Boom ! You got call recording back in case you had to reboot OTG.
Still looking forward to find a savvy chap on this thread that can help with automating that adb command upon each reboot
Click to expand...
Click to collapse
anarche_diver said:
Hi guys,
Found a solution !
Go to Developer Options.
Scroll to an option near the end of the list called Disable Permission Monitoring --> Enable it & the command ./adb shell settings put global op_voice_recording_supported_by_mcc 1 is now executing.
Make a call from your OnePlus Dialer and behold the native call recording button in all its glory !
Review the call recording from the call log of the number from which you recorded the call OR go to folder Music>Recordings>Call Recordings to find your entire list of call recordings
Please note that as I understand it, this call recording function will not survive a reboot. We need to re-execute this command in adb upon each reboot for the time being.
I also tried disabling the Google Dialer to get rid of that annoying floating bubble overlay on the OnePlus in-call UI, but that simply destroys the in-call UI alltogether by no longer revealing it! So the person who created those OP apps that work on our devices succeeded at making it work by accepting that floating bubble as part of the workaround.
I noticed that on few occasions the OnePlus dialer does not hijack the call in time and the call goes through the Google Dialer in-call UI instead. Anyway, not complaining now that I found it to work at least.
Going to fiddle around with Tasker or some other app that allows me to automate the above adb command to execute upon each reboot.
Edit: Think I'm way to dumb to figure out how I'm gonna be writing this task. If someone savvy can chime in, that'd be great !
Edit 2: Used the following page tutorial to get a paid app called LADB to work on my device that allows me to execute adb commands OTG:
How to Send ADB Commands to Your Own Phone Without a Computer or Root
There are three tiers to Android customization: things you can do by default, things you can do with ADB, and things you can do with root. While root is still pretty tricky to get, ADB mods just got a lot easier. Back in Android 9, Google added a feature that allowed you to wirelessly send ADB...
android.gadgethacks.com
So for now, upon each reboot, I'll just open up this app (you'll need access to wifi every time) and copy/paste the adb command in there without the ./ adb shell part added at the start. So use just settings put global op_voice_recording_supported_by_mcc 1 and tap enter. Boom ! You got call recording back in case you had to reboot OTG.
Still looking forward to find a savvy chap on this thread that can help with automating that adb command upon each reboot
Click to expand...
Click to collapse
@anarche_diver Hello, thank you for the detailed post. I just switched from 7Pro to 10Pro (NE2213) as well and was looking to get native call recording. Firstly, you shouldn't be selling yourself short as you are definitely smart enough to have put in the efforts at the right places it seems, a special thanks for that
However, I am stuck at LADB. After I have plugged in the command (copy pasted from your post), it shows the following error. Could you maybe help me figure out what I did wrong ? Thanks in advance & below is a screenshot from LADB.
Edit : Please note that one way or another, I would love to get the native call recording feature. And I don't mind even if the voice announcement of call recording is issued

has anyone found a very good stock dialer for root my device?

Database Develop

welcome