Database Users

[Q] Note Edge's Curve screen features through software emulation?

Has anyone thought about it already? I'm no developer myself but I think it would be a cool inclusion to have it on my Note 3 (Exynos) . What i mean by this question is that, could we emulate the software of the edge screen,by taking up a part of the Note's screen which acts like the actual curve on the Note edge and displays notifications and important stuff. Any comments? If anyone is willing to try, I'll be a tester. Thank you

Sir,
Please wait until mods will move this thread to the device specific forum.
Stand by
Good luck

R_a_z_v_a_n said:
Sir,
Please wait until mods will move this thread to the device specific forum.
Stand by
Good luck
Click to expand...
Click to collapse
Seems like it currently is in the Note 3 section. My bad for posting it on the wrong section. I hope the devs give a shot about this feature

There's no question that it could be done, but frankly, I don't see it happening. An overlay or sidebar or widget or something with the same sort of features would probably be doable, but true 1:1 'emulation' seems like it would involve a ton of modification to the framework.

Oh well. I wish some widget sort of a fully functional thing can be made possible by the devs. (Hopefully). Thank you

Tell Samsung to include Camera 2 in its Lollipop update

Not sure if this type of thing is permitted, but here goes.
I've posted a note to Samsung on my blog to try and get them to include support for the new Camera 2 API in the Lollipop update for, at least, the Note 4 and S5. Sharing on FB, Twitter and tagging Samsung is the easiest way to try to get them to hear users.
An Open Letter to Samsung

It is too late for the S5 as updates have already been release...same thing for the Note 4. I didn't fully look at your letter, but perhaps state for future updates because the current is already done.

I don't have my Lollipop update yet. Regardless of whether it's the first update to Android 5 or subsequent is irrelevant. The point is that Samsung should support the Camera 2 API.

There are companies that do listen to their customers. And it's not unheard of for a company to change direction if enough of its customers express a desire for (or against) something.

I have seen it posted in the International Forum that "it's there but switched off". I'm sure we will see it in a future update.

I dont get all the negativity. If you don't want to help, don't reply and move on.

KingBeef said:
I have seen it posted in the International Forum that "it's there but switched off". I'm sure we will see it in a future update.
Click to expand...
Click to collapse
It's not there because Samsung doesn't use camera2 api. They made their own because Google still sucks at it.
Sent from my SM-N910T using XDA Free mobile app

From the Moderator
To all in this thread, post respectfully... Or Do Not Post.......easy
To the OP, Trying to use the camera2 is not as easy as it sounds, Remember, updates also need to be downwardly compatible, that makes enacting something much harder, or buggier.
So, couple that with then having all supporting app devs to adjust or modify their apps to work with it...... just not as simple as releasing a new feature or update.....
Ok people, please be kind when posting, be respectful thanks ~~~ oka1

[Great News] [Official] [CM12.1][Coming Soon]

Hello Everyone
I have come across device tree for Hima M9/CyanogenMod 12.1 with a custom Kernel. (If I'll tell you the name of either , you'd Google in a second)
The developer is a genius and trust me you'd see both of these within a month. Stay tuned for updates.
I can attach screenshots but I'd not post links as previous experiences that I had meant that people started troubling the developer and he quit the project all together. Respect the developers and read in my signature about development process and what it is actually like to be one.
This is just a confirmation and I can actually prove it to everyone who are interested.
I see many device tree updates every day so I am sure once CM12.1 is available officially, it'd open gates for all sorts of custom ROMs!
Attachments coming in few hours as I'm heading out

wow that would be awesome! cant wait to run a pure android rom on this beast
*all f***** fingers crossed*

Yay!
Sent from my LG-H811 using Tapatalk

Hnk1 said:
Hello Everyone
I have come across device tree for Hima M9/CyanogenMod 12.1 with a custom Kernel. (If I'll tell you the name of either , you'd Google in a second)
The developer is a genius and trust me you'd see both of these within a month. Stay tuned for updates.
I can attach screenshots but I'd not post links as previous experiences that I had meant that people started troubling the developer and he quit the project all together. Respect the developers and read in my signature about development process and what it is actually like to be one.
This is just a confirmation and I can actually prove it to everyone who are interested.
I see many device tree updates every day so I am sure once CM12.1 is available officially, it'd open gates for all sorts of custom ROMs!
Attachments coming in few hours as I'm heading out
Click to expand...
Click to collapse
The link below is to the thread which its being discussed in within m9 Q&A section. Rashid97 is the dev working on the project
http://forum.xda-developers.com/one-m9/help/cyanogenmod-12-12-1-htc-one-m9-t3069920

v1rk said:
The link below is to the thread which its being discussed in within m9 Q&A section. Rashid97 is the dev working on the project
http://forum.xda-developers.com/one-m9/help/cyanogenmod-12-12-1-htc-one-m9-t3069920
Click to expand...
Click to collapse
aaronrw said:
Yay!
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
sweetrobot said:
about ****ing time!!! so sick of the nonSense...
cm / aosp / aokp ftw.
paperweight for the last couple of months. tried a bunch of the existing roms, just not my cup of tea.
Click to expand...
Click to collapse
k1moe said:
wow that would be awesome! cant wait to run a pure android rom on this beast
*all f***** fingers crossed*
Click to expand...
Click to collapse
I am afraid that is not it what you are pointing out.
Here are the screenshots.
You can clearly see that how much commits are posted daily and it is going on at a very brisk rate. Cheer up everyone!
Request :
Just please do not trouble the developer if you find out who is he.
READ THIS HERE
Alternatively you can see more information in my signature!
Hnk1 said:
DEVELOPMENT PROCESS
INTRODUCTION
I am starting this forum in hope of educating my readers about ROM development according to my experiences. Further, I will highlight what is the usual developers' thought process before they decide to build a ROM for a specific device. The reasons why they usually choose a certain device or why they prefer one device over another would also be stated briefly. I also have intention of looking into ways how we can speed up ROM productions for any device and what you can do to play your part.
I UNDERSTAND YOUR FRUSTRATION FOR NO CUSTOM ROMS EVEN AFTER SOME MONTHS BUT THIS DOESNOT GIVE YOU THE RIGHT TO SPAM
I am sure many of you must be really disappointed by the lack of development for your device and I know this must be frustrating when we see other devices are getting ROMS so quickly. I know many are too excited when they find a little about any OTA/ Custom ROM and sharing such news is fully justified. However, it's beyond my logic & thinking why the forums are SPAMMED for any little information they might find anywhere regardless of their sources or if it has been ALREADY POSTED. I reckon many of these threads could have been avoided by simply searching in the forum.
ROM DEVELOPMENT
I can assure you that many develoeprs are working very hard to PORT and develop different ROMS for a device. However, the reason we can not see any CUSTOM roms till yet is due to complicated nature of a device itself.
Usually developers prefer a device which is :
1. Easy to work with, less complicated to code with or in other terms DEVELOPER friendly. For example, for a while I had a real issue with HTC phones as they have too many things to work with like Bootloader, S Lock, Radios, Hboot version etc while in Nexus devices you only need to unlock your device with one fastboot command. That's all and you are ready to flash ROMs.
2. Personal preference of Device. This simply means that we all have different tastes and thus we choose different devices. A certain developer might only work for a certain brand while other might work with few brands. This has nothing to do with anything but a personal choice.
3. A device that promises reward in terms of money/self satisfaction. Developers usually go for devices which have most active users so if their intention is also to get some money out of it in terms of donation, this will work well with devices which are more in number.
4. Knowledge about a certain brand more than another.
5. MONEY TO BUY A CERTAIN DEVICE/DEVICES. Suppose a developer wants to make ROMS for Xperia L/ SP/Z and Xperia U. Yet he only has 500 dollars to choose from. He then will have to make a choice between devices and this will eventually mean that not all of the devices get the same treatment. Money is the most decisive factor why a developer doesnot chose your device but rather another. For example purpose only, if I have to choose between devices, I might prefer SP over Xperia L as I can see more future of SP than Xperia L(I might be wrong).
6. Simply he bought a device or it is gifted/donated to him
SOME REQUESTS
Please STOP bugging developers by trivial questions. Just think how many other people ask the same question and it gets very frustrating to actually work on the device itself.
Every developer has a LIFE apart from developing ROMs. They also have a family, school, work, hobbies, bad days and so much like us. So they will do it when they feel like doing it. Just sit back and relax. Enjoy your device until developer releases the ROM for your device. Asking a REASONABLE question seems plausible but asking same questions/useless questions without using brains is just STUPID. Kindly refrain from that.
If you have seen a developer who has taken the initiative to work on your device , the best thing to do is to be patient. Let him concentrate. Spamming and spamming again won't help really.Yet some users start SPAMMING developers, their twitters, blogs and accounts. That's really sad. You can discuss on the forum what you think about it but IRKING developers isnot really cool.
WHAT CAN YOU DO TO HELP DEVELOPERS AND SEE CUSTOM ROMS.
1. Search the form first and look for answers. DON'T start new posts/questions/threads when it is ALREADY mentioned in some other section.
2. STOP PMing/SPAMING developers but rather ask a question WHICH havenot been asked before in the forum. Do not engage in the habit of making a new forum for everything. Try to keep threads as little as possible.
3. Follow developers and see what they have updated about on their official twitter,facebook,etc rather than bugging them on different forums/social websites.
4 DONATE THEM. DONATE THEM . DONATE THEM!
The amount of efforts they put, sitting for hours in front of their PCs and I know how frustrating it gets when you try to run commands and everything seems to work yet you can not boot up your ROM. And worse, you can not find WHY really. Just a change in line in build.prop results in failure of ROM to boot up and specially working from source to build ROM is really really tough. The best thing you can do is being supportive and patient !
A ROM development requires not just EXCESSIVE amount of hardwork, time, energy and dedication but also they need MONEY to actually buy devices and try it on. They are happy and encouraged to keep on developing ROMs when they see their efforts are not wasted and they are rewarded and respected for what they do.
SOME BASICS OF ROM DEVELOPMENT
Usually this is required to make a full custom ROM
Blobs which contain hardware information which comes from hardware manufacturer like Qualcomm in case of Snapdragon processors
A fully functional device tree
Latest Android source (Or the android version source you want to build for)
Specific Custom ROM coding which is based on Android Source
Usually a device tree and kernel tree is needed before custom roms can be made available. This is a long trial and error process in which every component of hardware is made functional as usually manufacturers do not provide any code for their devices and thus new code is to be written which is very frustrating and long process!
Click to expand...
Click to collapse

Hnk1 said:
I am afraid that is not it what you are pointing out.
Here are the screenshots.
You can clearly see that how much commits are posted daily and it is going on at a very brisk rate. Cheer up everyone!
Request :
Just please do not trouble the developer if you find out who is he.
READ THIS HERE
Alternatively you can see more information in my signature!
Click to expand...
Click to collapse
What i pointed is where the developer actually mentioned he his working on it and the link can be sourced by anyone, and people in that thread have been checking the github as mentioned. Theres now two threads on the discussion of cm12.1 which talk similar. All you are doing is not mentioning the dev based someone who used his work without his permission. Also to add the dev replied that thread to have to say they having working booting img just some features aren't working.
Link to his github for the current work
https://github.com/Hima-Dev/android_device_htc_hima-common

Thank GOD
---------- Post added at 01:33 PM ---------- Previous post was at 01:32 PM ----------
I'll be happy to donate

I'm really excited about this, because the person doing this is making amazing progress and at last count I want to say it was only Wi-Fi and one other thing not working with said developer already pretty certain that they know how to change that, it's just a lot of trial and error (any dev knows how frustrating it can be having to compile the source all over again to test a tiny change)
What this means for me, personally, is that I can do what I've done on past htc devices and knock out a fairly complete port of miui (some default miui stuff doesn't play nice during flash, like the camera app, so I'll likely include the stock m9 camera app as packaged for other phones so it doesn't rely on sense)
Anyway... ?

v1rk said:
What i pointed is where the developer actually mentioned he his working on it and the link can be sourced by anyone, and people in that thread have been checking the github as mentioned. Theres now two threads on the discussion of cm12.1 which talk similar. All you are doing is not mentioning the dev based someone who used his work without his permission. Also to add the dev replied that thread to have to say they having working booting img just some features aren't working.
Link to his github for the current work
https://github.com/Hima-Dev/android_device_htc_hima-common
Click to expand...
Click to collapse
Cheers for side information. I know the developer and I'm pretty sure you'd get a kernel and Cm12.1 pretty soon.
Actually I Would let the developers sort out their differences themselves, for me it is Cm12.1 coming pretty soon.

agentfusion said:
I'm really excited about this, because the person doing this is making amazing progress and at last count I want to say it was only Wi-Fi and one other thing not working with said developer already pretty certain that they know how to change that, it's just a lot of trial and error (any dev knows how frustrating it can be having to compile the source all over again to test a tiny change)
What this means for me, personally, is that I can do what I've done on past htc devices and knock out a fairly complete port of miui (some default miui stuff doesn't play nice during flash, like the camera app, so I'll likely include the stock m9 camera app as packaged for other phones so it doesn't rely on sense)
Anyway... ?
Click to expand...
Click to collapse
Whhhaaatttttt?!?!?! Miui?!?!?

Wait

Galaxysm said:
Whhhaaatttttt?!?!?! Miui?!?!?
Click to expand...
Click to collapse
Yeah. Once we have a reliable port of CM12, then porting other stuff is pretty easy. All I have to do is find a device that already has miui with the same resolution and dpi/ppi and port the assets over to the m9.
Preferably I'd like to port the miui patchrom so I can setup an automated build system to build a fresh copy every time aosp and miui are updated, but I don't have anywhere near enough time for that.

agentfusion said:
Yeah. Once we have a reliable port of CM12, then porting other stuff is pretty easy. All I have to do is find a device that already has miui with the same resolution and dpi/ppi and port the assets over to the m9.
Preferably I'd like to port the miui patchrom so I can setup an automated build system to build a fresh copy every time aosp and miui are updated, but I don't have anywhere near enough time for that.
Click to expand...
Click to collapse
Nice I can't wait!!

Nice to see this coming ... And for MIUI I haven't been able to use it since I change my original EVO ... It would be great to have it as an option ...

Great news

Daily reminder that CM12 is a desperately needed and coveted thingy for the m8+1.

Is it lollipop 5.1?
Sent from my HTC One M9 using XDA Free mobile app

vegetaleb said:
Is it lollipop 5.1?
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
Cm12.1 is lolipop 5.1

Anyone knows the progress on this...

epedrosa said:
Anyone knows the progress on this...
Click to expand...
Click to collapse
Be patient. The OP says "within a month" and it has only been roughly 2 weeks

Are DEVs working on a third-party fingerprint reader solution?

I hate to be the one to ask, but does anyone know of any DEVs that are working on making their own source code for the fingerprint reader? I don't want custom ROMs without a fingerprint reader and I don't really want this phone without custom ROMs. A large factor of me buying this phone was due to OnePlus having excellent community support, which this one does, but that is all null and void for me with broken fingerprint on third-party ROMs. Guess I joined team OnePlus at a bad time -.-

Yes many people are working on it recently a omni dev had a breakthrough and almost got it working give it some time and it'll be working...

Good things come to those who wait. Rome wasn't built in a day my friend.

Looks at top thread ... Wonders why this one was started.

Bear in mind that this is one of the first phones with an ud fp scanner. Give it some time, we really got super devs behind the scene working on it. Be glad that this phone has allready sow many custom roms waiting for the fp solution.

garretts228 said:
I hate to be the one to ask, but does anyone know of any DEVs that are working on making their own source code for the fingerprint reader? I don't want custom ROMs without a fingerprint reader and I don't really want this phone without custom ROMs. A large factor of me buying this phone was due to OnePlus having excellent community support, which this one does, but that is all null and void for me with broken fingerprint on third-party ROMs. Guess I joined team OnePlus at a bad time -.-
Click to expand...
Click to collapse
If you want it so badly, then learn how to develop so others can ask YOU for ETA's..
Asking for an ETA on anything is frowned upon here...keep that in mind

garretts228 said:
I hate to be the one to ask, but does anyone know of any DEVs that are working on making their own source code for the fingerprint reader? I don't want custom ROMs without a fingerprint reader and I don't really want this phone without custom ROMs. A large factor of me buying this phone was due to OnePlus having excellent community support, which this one does, but that is all null and void for me with broken fingerprint on third-party ROMs. Guess I joined team OnePlus at a bad time -.-
Click to expand...
Click to collapse
It says you hate to be the one to ask but if you went through the forums you would have seen that it's being worked on.
This thead shouldn't even still be here as there is no purpose

Wow the forum police are out in full force today...

liam_davenport said:
Yes many people are working on it recently a omni dev had a breakthrough and almost got it working give it some time and it'll be working...
Click to expand...
Click to collapse
Awesome. I have seen threads of people talking about it but couldn't find any talk of actual progress. Thank you!

wase4711 said:
If you want it so badly, then learn how to develop so others can ask YOU for ETA's..
Asking for an ETA on anything is frowned upon here...keep that in mind
Click to expand...
Click to collapse
I don't see OP asking for ETA... just a casual question to see if anyone is working...

Dollyllama said:
Wow the forum police are out in full force today...
Click to expand...
Click to collapse
Pssss , watch your back ... They will come for you.... ETA. ETA. ETA. ETA. ETA. ETA.ETA..........

This is no ETA question!

He did not asked for eta.
Why people?why? For few likes you guys will impose anything.?
If it bothers sooo much. You can simply ignore and move on.
And to all those who answered politely you guys are the real mvp, xda needs more people like you.
Sent from my ONEPLUS A6010 using Tapatalk

Thread closed
Question has been answered, No further reason for this thread to live on.

Fingerprint Reader not usable after Bootloader Unlock

So this thread is intended to discuss the issue of the fingerprint reader being deactivated by Realme after unlocking the bootloader. As well as possible solutions, and ways of requesting a fix from Realme.
Realme is a company that belongs to the same group as Oneplus and Oppo, namely BBK Electronics. Since it is possible to use the Fingerprint Reader on the Onplus devices after bootloader unlocking and the Oneplus 7T being quite similar in hardware to the Realme X2 Pro, it would only make sense that it should be possible to use the sensor on the X2 pro as well after unlocking.
So this seems to be more a political decision rather than a hardware limitation. :good:
Ways for you to request a fix for the issue are ideally via the Realme Forum, that is the Indian Forum (as they speak English, that more easy for most of us, than using the Chinese forum. And the Indian version being basically the same as the European version as well).
You can comment in this thread:
https://c.realme.com/in/post-details/1201215999353815040?comment=1201237884766519296
As well in this one:
https://c.realme.com/in/post-details/1199644629624946688
Additionally, you can contact Realme Europe via twitter here:
https://twitter.com/realmeeurope
As I already did, as you can see here:
https://twitter.com/realmeeurope/status/1201485228428210181
So let's make this Realme great again

The first thread seems to be deleted.
Dont know if its intended, but deleting threads with suggestions/reports of issue feels some kind of strange...

That was a thread about a recap of the introduction events. Where you could share issues and make queries.
Ther is also this thread, where a Moderator replied and wants to forward the issue:
https://c.realme.com/in/post-detail...64863306907648&subForumId=1197159778845982720
I attached a screenshot, just incase it gets deleted.

there's another one on their forum. Maybe it helps if we bump up the like/comment counter?
they can't ignore us if we can get enough noise.
https://c.realme.com/in/post-detail...64863306907648&subForumId=1197159778845982720

I think fp is disabled in color os only. May be in custom roms it will be available to use.

Sadly it seems that nobody is interested in this issue. Neither customers nor moderators/developers in the realme forums...

May be if some developers start developing a custom rom, then we will get to know. I think the unusability of fp sensor will be limited to color os after unlock. But it probably might work with custom roms

hi all , please go and hit "i am facing this issue too" button on the below link ,
I have created a bug report for the finger print sensor issue after unlocking the bootloader
https://c.realme.com/in/post-details/1200373166703116288

Well You guys should also bump your issue in the flipkart product page so that their sales will get a hit and then realme will take some steps to fix this .

I spoke to a senior developer at XDA FOR THe FINGERPRINT ISSUE AFTER BOOTLOADER UNLOCK ......HELP IS ON ITS WAY !!!!!
ENJOY GUYS !!!!!!!!!?

Lets hope for the best

bharat.bkj said:
I spoke to a senior developer at XDA FOR THe FINGERPRINT ISSUE AFTER BOOTLOADER UNLOCK ......HELP IS ON ITS WAY !!!!!
ENJOY GUYS !!!!!!!!!
Click to expand...
Click to collapse
Do you have more information?

It doesn't work on any roms (EU, India, China)?

HTCDevil said:
It doesn't work on any roms (EU, India, China)?
Click to expand...
Click to collapse
nope

I guess if it's disabled after the bootrom unlock it will have to be a fix or an custom change for the bootrom to allow the finger print

natedogg20050 said:
I guess if it's disabled after the bootrom unlock it will have to be a fix or an custom change for the bootrom to allow the finger print
Click to expand...
Click to collapse
At first we should hope there will be custom roms for this amazing device. Realme's official support seems extremely poor. And without it's support I don't know if there will be any bug solutions or custom roms...:crying:

asusgarb said:
At first we should hope there will be custom roms for this amazing device. Realme's official support seems extremely poor. And without it's support I don't know if there will be any bug solutions or custom roms...:crying:
Click to expand...
Click to collapse
They released a bootloader unlock tool and released kernel resource so I think that they're supporting custom development. But let's hope that they will fix this problem ASAP.

In the latest episode of #AskMadhav for the month, the company’s CEO, Madhav Sheth has answered some questions
The company already said that bootloader unlocking will disable fingerprint scanner, but this will be fixed in the upcoming update said the CEO. It will also release a separate flash tool in Q1 2020.
Lets wait now.

He was talking about the realme x2

sareer007 said:
In the latest episode of #AskMadhav for the month, the company’s CEO, Madhav Sheth has answered some questions
The company already said that bootloader unlocking will disable fingerprint scanner, but this will be fixed in the upcoming update said the CEO. It will also release a separate flash tool in Q1 2020.
Lets wait now.
Click to expand...
Click to collapse
Are you talking about X2 or X2 Pro device?
Thanks...