Advantages of Digital workerbees

Digital workerbees, refer to software-based agents or bots that automate various tasks and processes in the digital realm. Here are some top reasons to highlight the importance and benefits of digital workerbees:

1. Efficiency and Productivity: Digital workerbees can handle repetitive, mundane, and time-consuming tasks, allowing human workers to focus on more strategic and value-added activities. They work tirelessly and can perform tasks faster and with higher accuracy, leading to increased productivity and efficiency.

2. Cost Savings: By automating routine tasks, digital workerbees can help reduce labor costs and minimize errors that can lead to financial losses. Once set up, they can operate 24/7 without requiring breaks or benefits, resulting in significant cost savings for businesses.

3. Scalability and Flexibility: Digital workerbees can be easily scaled up or down based on workload demands. They can handle increased volumes of work without the need for additional human resources, allowing businesses to adapt quickly to changing business needs and scale operations efficiently.

4. Enhanced Customer Experience: By automating certain customer-facing tasks, such as responding to inquiries, processing orders, or providing basic support, digital workerbees can improve response times and ensure consistent service delivery. This leads to a better customer experience and higher satisfaction levels.

5. Reduced Errors and Increased Accuracy: Digital workerbees follow predefined rules and workflows, which minimizes the chances of human errors and inconsistencies. They can perform repetitive tasks with high accuracy, ensuring consistency and quality in operations.

6. Workflow Streamlining: Digital workerbees can integrate with various systems, applications, and databases, allowing for seamless data exchange and process integration. They can streamline workflows by automating data entry, data validation, report generation, and other manual tasks, reducing bottlenecks and improving overall workflow efficiency.

7. Compliance and Auditability: Digital workerbees can be programmed to adhere to specific rules, regulations, and compliance requirements. They can accurately track and log all activities, providing a clear audit trail and facilitating compliance reporting, which is crucial in regulated industries.

8. Employee Empowerment: By taking over repetitive tasks, digital workerbees free up human workers to focus on more creative, complex, and strategic aspects of their roles. This can lead to increased job satisfaction, skill development, and employee empowerment.

9. Data Insights and Analytics: Digital workerbees can process and analyze large volumes of data quickly, enabling businesses to gain valuable insights and make data-driven decisions. They can perform data mining, pattern recognition, and predictive analysis, helping identify trends, optimize processes, and uncover business opportunities.

10. Continuous Operations: Digital workerbees are not limited by factors like working hours, holidays, or geographical locations. They can operate round-the-clock, ensuring continuous operations and minimizing downtime.

Overall, digital workerbees offer numerous advantages, ranging from improved efficiency and cost savings to enhanced customer experience and data-driven insights. By harnessing their capabilities, organizations can optimize operations, drive innovation, and stay competitive in the digital era.

Read More

Strategic Scaling: Achieving Growth With a Limited Budget

Scaling a small business with limited financial resources can be challenging, but it's not impossible. Here are some strategies to help you scale your small business on a shoestring budget:

1. Focus on profitable activities: Identify the products, services, or activities that generate the most profit for your business. Concentrate your efforts and resources on these areas to maximize your returns and generate additional revenue.

2. Optimize your operations: Look for ways to streamline and optimize your business processes to reduce costs and improve efficiency. Automate repetitive tasks, negotiate better deals with suppliers, and implement lean practices to eliminate waste and maximize productivity.

3. Leverage technology: Take advantage of affordable and accessible technology solutions to enhance your business operations. Use cloud-based software for accounting, project management, and customer relationship management. Leverage social media and digital marketing to reach a wider audience without a significant financial investment.

4. Build strategic partnerships: Seek mutually beneficial partnerships with other businesses that complement your products or services. Look for opportunities to collaborate on marketing campaigns, share resources, or cross-promote each other's offerings. This can help you expand your reach and customer base without a hefty financial commitment.

5. Focus on customer retention and referrals: Satisfied customers can be a valuable asset for scaling your business. Invest in exceptional customer service and create a positive customer experience to encourage repeat business and generate referrals. Word-of-mouth marketing is often highly effective and cost-efficient.

6. Explore alternative funding options: While you may have limited funds, consider exploring alternative financing options. Look for grants, loans, or crowdfunding opportunities specific to small businesses. Additionally, micro-loans and peer-to-peer lending platforms can provide accessible funding options with favorable terms.

7. Seek free or low-cost marketing channels: Utilize low-cost or free marketing channels to promote your business. Leverage social media platforms, create engaging content, and participate in online communities or industry forums. This allows you to increase your brand visibility and reach a broader audience without significant financial investments.

8. Prioritize customer feedback and iterate: Actively seek feedback from your customers and use it to improve your products or services. By continuously iterating and making improvements based on customer needs, you can enhance customer satisfaction and loyalty, leading to organic growth and positive word-of-mouth.

Remember, scaling a business requires careful planning, resourcefulness, and adaptability. By leveraging your existing resources effectively, making strategic choices, and focusing on sustainable growth, you can scale your small business even with limited financial investment.

Join us today and earn $0.50 Welcome bonus.

Read More

Leaked Android "Q" Code Reveals Apple-Inspired Security Secret (Face recognization)

It has been reported that Google is developing native support for a secure biometric authentication feature similar to Apple's Face ID in the forthcoming Android Q smartphone operating system release. Writing on the XDA-Developers Portal site, Mishaal Rahman points to "dozens of strings and multiple methods, classes and fields related to facial recognition in the framework, SystemUI and Settings APKs" of a leaked Android Q build that is up-to-date as far as Google's Android Open Source Project (AOSP) internal master version is concerned.

This AOSP Android Q build included lots of features that are sure to get Android fans fired up. A dark mode theme that's system-wide and works with apps that don't come with a dark mode built-in, a whole bunch of changes to the way Android Q handles app permissions especially those concerning location and a 'force desktop mode' developer option that hints at something similar to Samsung DeX according to the XDA-Developers Portal report.

However, it's the discovery of code that relates to a new facial recognition authentication system which could bring Face ID-like security to handset unlocking, app logins and for payments that is the most interesting. This will be a major step forward for Android devices in my never humble opinion. Sure, some handset vendors already have their own versions of Face ID operating in Android smartphones already. The Mate 20 Pro from Huawei springs immediately to mind. The problem here is that Huawei has had to work hard on tweaking and customizing Android in order to bolt on the necessary operating system support for that facial recognition hardware.

While there is nothing to suggest that the Huawei implementation is in any way insecure, bolting-on and OS-tweaking are never going to be as inherently secure as native support within Android itself. As we have seen from numerous Internet of Things examples, the cost and complexity implications of security that isn't baked in can often lead to less than secure results. Native support for facial recognition in Android-powered devices should reduce both the cost and the complexity that bespoke biometrics introduce, which has to be a good thing. Or is it?

"Facial recognition in Android? Wow so exciting, but not really so helpful for security in my opinion" Ian Trump, head of cybersecurity for AmTrust International told me. There are two main reasons for his caution regarding facial recognition on smartphones: firstly, Trump wonders how accurate it will be and also worries it has more the feel of a convenience mechanism rather than a security win about it. Not that it's all bad of course, as Trump points out "I'm a passcode person; will always be a passcode person, but I get that a feature like facial recognition may be a way to encourage folks to secure their Android device."

Read More

Android Pie: Everything you need to know about Android 9

From new gestures to extending battery life, here's everything you need to know about Android Pie!

Following last year's Oreo release, 2018 is the year of Android 9 Pie.

Google's latest flavor of Android is jam-packed with all sorts of new features, including a brand-new gesture navigation system, new UI elements, and a heap of under-the-hood tweaks that aim to make this the best version of Android to date.

Without further ado, here's everything you need to know about Pie!

The latest Android Pie news

December 28, 2018 — Adoptable storage is missing with Samsung's final Pie update

Just before Samsung's open beta of its One UI/Pie update was released, one of the most exciting things we saw was the addition of adoptable storage in a leaked build of the new software — something Samsung phones have been missing since the feature's introduction back in 2015. Adoptable storage wasn't actually functional during the beta, but we expected that this would change once the final build of Pie started rolling out to Samsung devices.

Unfortunately, that doesn't seem to be the case.

As noted by SamMobile, Samsung's final and official Pie update doesn't show any sign of adoptable storage anywhere at all.

My guess is that it'll be added at some point down the road since it's apparent that it's something Samsung is working on, but maybe the feature wasn't ready for primetime quite yet.

November 13, 2018 — Samsung phones may finally get adoptable storage with Android Pie

Back in 2015 with the release of Android Marshmallow, one of the highlight features was the introduction of adoptable storage — the ability to choose if you want to use Micro SD cards as extra phone storage or portable storage. It's proven to be extremely helpful over the years, but for whatever reason, Samsung phones have never supported it.

The folks at SamMobile recently got their hands on an early build of Android Pie for the Note 9, and as you can see from the screenshots above, adoptable storage is finally enabled.

Adoptable storage doesn't actually work in this early build, but it's expected that it'll be fully functional once the final release comes about in January.

All the big details

Android P is officially Android 9 Pie

No Popsicles or Pineapples here. On August 6, 2018, Google revealed that its next version of Android is Android 9 Pie.

Along with the name change, the number this year is also slightly different. Rather than following the trend of 7.0, 8.0, etc., Pie is referred to as 9. This probably doesn't mean much in the grand scheme of things, but it's still an interesting move on Google's part.

Every new Android version builds upon the previous one, meaning that each new update is better than the last.

However, in day-to-day use, how does really Pie hold up? What's it like using the new gestures instead of the traditional navigation buttons? How do the subtle UI tweaks compare to Oreo? What's performance like?

Read More

Android O will be revealed during Monday’s solar eclipse – and it’s probably Oreo

Monday’s total solar eclipse is nearly here… and so is Android O, apparently. Google invited the press to an event on Monday for the official reveal for the next version of Android – and by this point we’re fairly convinced it’ll be called Oreo.

For everyone else, Google will be livestreaming the Android O reveal starting at 2:40PM EST, just a few minutes before peak eclipse time. Considering most people won’t be in the path of totality, Google will let you experience the eclipse in VR via Google Earth as well. You can head over to Android.com/o to find out more and watch the livestream come Monday.

As usual, Google will be naming the next version of Android after a dessert. Oreo was always the obvious choice, and rightfully so. But given the disappointment of Nougat (which should have been Nutella, of course), we’ve been a little worried.

But Earlier today 9to5Google caught a Google+ post teasing Android O with the filename GoogleOreo_Teaser_0817_noDroids (1).mp4. The post has since been replaced with the more innocuous OctopusTeaser.mp4, but the damage was done.

Read More

How can I build an app like Instagram using Java? What languages are used for the front end and database?

Why do people use your application?

Find your target people and How will you attract them on your application.

So designs and functionality matter! You need below points for Design & functionality.

• It is easy to use.
• It has the simple but beautiful design.
• It has many little and nice features.

For this, create some key features in your mind and choose better interface in which you are expert.

I found some modules as provided by Instagram.

Easy registration and authorization : Users can use email or phone number. You can also use social logins which are available on their developer sites(Ex,Social Facebook signup-login API visit Facebook for Developers, Google API visit Google Developers)

Profiles Module : That’s obvious, Every one want to know each other on social media, and another reason is to Identify user from their description or profile photo.You can Keep it simple: Name, avatar, small description and general information or website link. Allow your users to edit, add and remove information in one click (We call it CRUD functionality).

Communication : Most important part of any development. This kinda apps , which shares photo and feelings, you can tell it “social network”. You should add something like Follow or Unfollow, so Users can communicate with each other. You can add submodules like Like, Comment, Share, Direct Message(For chat), Follow etc.

Image customization and filters : Main heart of Instagram. You can put some best and rare filters which can be appreciated by users. No need to put 150–200 filters :)

Posting: purpose of posting is for users, they can share picture(s) from their local directory. So upload module is needed to achieve this functionality. You can also add these as a submodules : post description, mentioning people and adding people on photo (tag in terms of Facebook), Hashtags (Optional), searching (Filter by post,hashtags), so they are necessary.

Push notifications : Its optional for starting level, but you can take permission from users to allow notification, If user allows, you can show blinking notification like Facebook.

I would say, Instagram was made with Python - Django, but if you want to create such an app, you can use any you would like to do!

You need to keep in mind that…

If you are going to make application like Instagram you should have to care about,

Hosting,

Data storage,

Load Balancing,

Monitoring servers

Bingo… You have some basic planning about how to create such applications.

Let me know first when you will create one!

[Source] : Quora

Read More

Android O: After Nougat Will Google Call it Android Oreo?

Sorry Guys, After a long time, Finally We are back !

If not Oreo, the guys at Google will really have to think hard for a sweet name of Android O. Here are four other possible names of Android O (or version 8.0) which Google might consider. (Image: Google)

Google has just the released the developer preview of Android version 8.0 and more importantly confirming that there will be something called Android O after N. The preview hasn’t offered much to confirm the features but have already tickled the interests of Android fanbois as to what will Google name Android O.

Of course, it will not be called omelette as the name has to something sweet and the next obvious hint that comes to our mind has to be Oreo. However, Google has always managed to surprise us.

Recalling the name KitKat, it was widely expected that Google would name Android N as Nutella but to everyone’s surprise it was called Nougat. Most Android based out of India had to Google to know Nougat actually is. This time chances are very less that Android O would be named after any Indian sweet dish.

If not Oreo, the guys at Google will really have to think hard for a sweet name of Android O. Here are four other possible names of Android O (or version 8.0) which Google might consider.

1) Android Oatmeal Cookie: With so much focus on the health benefits of oats in India, oatmeal cookie could be a possible name. The Android mascot-shaped cookie could be covered with a lot of oats to highlight the sweetness of Android O.

2) Android Orange: While it can use sweet or sour depending on the source of the fruit, orange can be a simple name for Android O. Google might also think of making it further sweet by calling it Orange Candy or Crush.

3) Android Orellete: You might find it very difficult to taste one in India but orellete is a sweet pastry found in Spain. While the name rhymes well very few knows about it.

4) Android Oregano: Of course, oregano is not sweet but it is widely used with pizzas across the globe. And its medicinal herb with loads of health benefits. Google might consider something healthy this time.

What do you think about Android O ? Please Comment Below ... 

Read More

Tutorial 2:- How To Build A Android Linux Kernel For your Custom ROM?

Adding features to your kernel

Adding features to your kernel
The kernel is probably one of the most important parts of the Android system, the whole system relies on the kernel, the performance, stability, smoothness, etc.
Considering the kernel as the most important part, you want it to be optimized, making your system run smooth and performing above standards, also the battery life may not suffer when gaining these improvements. In this tutorial I will explain how to add CPU Governors,  how to add I/O Schedulers and a global sight on how to add Overclocking support for your kernel.

Chapters:
1. Github
2. Governors
3. I/O Schedulers
4. Overclocking 

Chapter 1. GithubI will not explain how to use Github in general, also I’m not trying to advertise for Github. I just want to say that you really “need” to use Github in order to get a clear overview of the changes you made.
Believe me, without a commit system and thousands of changes in your source, you will definitely forget what you actually did to the source.
Github helps you keeping track of the changes you made. Easily done by commits added by the developer.
If you want to build a (custom) kernel form source and you want to customize it,you must use Github! Not just for the overview of changes but also to make sure you don’t  violate the GPL law!
Since the android kernels are open source and protected by the GPL law, youneed to share your source with the world. (same thing counts for manufacturers!)
Enough about Github, let’s start with customizing.

Chapter 2. GovernorsWhat is a governor, why is it important to have custom governors and how to add governors to your kernel? These 3 questions are very important to know.
What is a governor:  A governor is actually nothing more then a behavior profile for your CPU, the governor will tell the CPU exactly what to do in what situation. The term ‘governor’ has nothing to do with it’s function, imagine it was called CPU Presidents! sounds strange but it’s as normal as using the word Governor.
Why is it important to have custom governors: The default governors added to kernels are “ondemand, powersave, performance, conservative” and optionally “userspace”, all these governors are pretty basic and not optimized for usage/battery whatsoever. a list of default governors with a small description:
- ondemand, the overall default CPU governor worldwide. Basically just ramps up your CPU speed to max freq when just pushing the screen once, then lowering it back to the minimal cpu freq (somewhat smart, but not optimized at all).
- performance just stays at the max CPU freq all the time (horrible for your battery).
- powersave stays at the min CPU freq all the time (resulting over the top lag).
- conservative is somewhat adjusted to use less power, but that’s also very notable in performance.
- userspace is a governor that needs to be completely configured manually, the default setting is the same as powersave, it will stay at your min CPU freq when not configured. (this governor is rarely used)
Because the stock CPU Governors are just plain boring and do not improve your device whatsoever, you want to add custom CPU Governors, making your device smoother, more stable and less battery consuming.
How to add a CPU Governor:
The CPU governor itself is just 1 C file, which is located in  kernel_source/drivers/cpufreq/,  for example: cpufreq_smartass2.c. You are responsible yourself for find the governor (look in an existing kernel repo for your device)
But in order to successfully call and compile this file into your kernel you will have to make the following changes:
1. Copy your governor file (cpufreq_govname.c) and browse to  kernel_source/drivers/cpufreq, now paste it.
2.  and open Kconfig (this is the interface of the config menu layout) when adding a kernel, you want it to show up in your config. You can do that by adding the choice of governor.

1 2 3 4 5

config CPU_FREQ_GOV_GOVNAMEHERE tristate "'gov_name_lowercase' cpufreq governor" depends on CPU_FREQ help governor' - a custom governor!

for example, for smartassV2.

1 2 3 4 5

config CPU_FREQ_GOV_SMARTASS2 tristate "'smartassV2' cpufreq governor" depends on CPU_FREQ help 'smartassV2' - a "smart" optimized governor!

next to adding the choice, you also must declare the possibility that the governor gets chosen as default governor.

1 2 3 4 5

config CPU_FREQ_DEFAULT_GOV_GOVNAMEHERE bool "gov_name_lowercase" select CPU_FREQ_GOV_GOVNAMEHERE help Use the CPUFreq governor 'govname' as default.

for example, for smartassV2.

1 2 3 4 5

config CPU_FREQ_DEFAULT_GOV_SMARTASS2 bool "smartass2" select CPU_FREQ_GOV_SMARTASS2 help Use the CPUFreq governor 'smartassV2' as default.

- can’t find the right place to put it? Just search for  “CPU_FREQ_GOV_CONSERVATIVE”,  and place the code beneath, same thing counts for “CPU_FREQ_DEFAULT_GOV_CONSERVATIVE”
Now that Kconfig is finished you can save and close the file.
3. While still in the /drivers/cpufreq folder, open Makefile.
In Makefile, add the line corresponding to your CPU Governor. for example:

1	obj-$(CONFIG_CPU_FREQ_GOV_SMARTASS2)    += cpufreq_smartass2.o

Be ware that you do not call the native C file, but the O file! which is the compiled C file. Save the file.
4. Move to:  kernel_source/includes/linux.  now open cpufreq.h
Scroll down until you see something like:

1 2 3

#elif defined(CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND) extern struct cpufreq_governor cpufreq_gov_ondemand; #define CPUFREQ_DEFAULT_GOVERNOR    (&cpufreq_gov_ondemand)

(other cpu governors are also listed there)
Now add your entry with the selected CPU Governor, example:

1 2 3

#elif defined(CONFIG_CPU_FREQ_DEFAULT_GOV_SMARTASS2) extern struct cpufreq_governor cpufreq_gov_smartass2; #define CPUFREQ_DEFAULT_GOVERNOR (&cpufreq_gov_smartass2)

Save the file and close it.
The initial CPU Governor setup is now complete. when you’ve done all steps successfully, you should be able to choose your governor from the menu (menuconfig, xconfig, gconfig, nconfig). Once checked in the menu it will be included to the kernel.
Commit that is nearly the same as above instructions:  “add smartassV2 and lulzactive governor commit”


Chapter 3.  I/O SchedulersNext to adding custom CPU governors, you can also enhance your kernel by adding new I/O Schedulers if needed. Globally Governors and Schedulers are the same, they both provide a way how the system should work. but on Schedulers it’s all about the Input/Output datastream except the CPU settings. the I/O Schedulers decide how the upcoming I/O activity is being scheduled.
The standard schedulers such as “noop” or “cfq” are pretty decent actually. They perform very reasonable.
Anyways, you can add more I/O Schedulers if you like to, think of “deadline/sio/row/vr”  for example
I will explain how to add a I/O Scheduler, it’s just a bit easier then adding a CPU Governor.
I/O Schedulers can be found in kernel_source/block.
1. Copy your I/O Scheduler file (example sio-iosched.c)  and browse to kernel_source/block, now paste it.
2. Now open Kconfig.iosched, and add the choice to the Kconfig, example for SIO

1 2 3 4 5 6 7 8 9

config IOSCHED_SIO tristate "Simple I/O scheduler" default y ---help--- The Simple I/O scheduler is an extremely simple scheduler, based on noop and deadline, that relies on deadlines to ensure fairness. The algorithm does not do any sorting but basic merging, trying to keep a minimum overhead. It is aimed mainly for aleatory access devices (eg: flash devices).

3. and the default choice option:

1	default "sio" if DEFAULT_SIO

Save the file, and move on to the Makefile of kernel_source/block/
4. Simply add this line, for SIO:

1	obj-$(CONFIG_IOSCHED_SIO)    += sio-iosched.o

Save the file and you’re done! The I/O Schedulers should now popup at the menu config.
Commit that is nearly the same as above instructions:  “add simple I/O scheduler commit”
Chapter 4. Adding OverclockingUnfortunately there is no solution ALL-IN-ONE solution available regarding overclocking, every device has a different OC, making it very important to use the right one!
The target file depends on your chipset type and chipset revision.
for example: on the Galaxy S Plus (which has a QualComm MSM Chipset, (msm7x30) the target file would be:
kernel_source/arch/arm/mach-msm/acpuclock-7×30.c
Once you got your acpuclock file, it’s time to take a look at how overclocking actually works.
Basically overclocking is nothing more then extending an array of frequencies and matching voltages.
Example show’n below is only an example, please find existing kernel with OC for your phone on Github, and study the changes that are made to OC the kernel!
Stock Settings:

1 2 3 4 5 6

static struct pll pll2_tbl[] = { { 42, 0, 1, 0 }, /* 806 MHz */ { 53, 1, 3, 0 }, /* 1024 MHz */ { 125, 0, 1, 1 }, /* 1200 MHz */ { 73, 0, 1, 0 }, /* 1401 MHz */ };

Along with:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

static struct clkctl_acpu_speed acpu_freq_tbl[] = {     { 0, 24576,  LPXO, 0, 0,  30720000,  900, VDD_RAW(900) },     { 0, 61440,  PLL_3,    5, 11, 61440000,  900, VDD_RAW(900) },     { 1, 122880, PLL_3,    5, 5,  61440000,  900, VDD_RAW(900) },     { 0, 184320, PLL_3,    5, 4,  61440000,  900, VDD_RAW(900) },     { 0, MAX_AXI_KHZ, AXI, 1, 0, 61440000, 900, VDD_RAW(900) },     { 1, 245760, PLL_3,    5, 2,  61440000,  900, VDD_RAW(900) },     { 1, 368640, PLL_3,    5, 1,  122800000, 900, VDD_RAW(900) },     /* AXI has MSMC1 implications. See above. */     { 1, 768000, PLL_1,    2, 0,  153600000, 1050, VDD_RAW(1050) },     /*      * AXI has MSMC1 implications. See above.      */     { 1, 806400,  PLL_2, 3, 0, UINT_MAX, 1100, VDD_RAW(1100),&pll2_tbl[0]},     { 1, 1024000, PLL_2, 3, 0, UINT_MAX, 1200, VDD_RAW(1200),&pll2_tbl[1]},     { 1, 1200000, PLL_2, 3, 0, UINT_MAX, 1200, VDD_RAW(1200),&pll2_tbl[2]},     { 1, 1401600, PLL_2, 3, 0, UINT_MAX, 1250, VDD_RAW(1250),&pll2_tbl[3]},     { 0 } };

OC Settings:

1 2 3 4 5 6 7 8 9 10 11 12 13

static struct pll pll2_tbl[] = {     {42, 0, 1, 0 },        /*  806 MHz */     {53, 1, 3, 0 },        /* 1024 MHz */     {58, 1, 3, 0 },     /* 1113 MHz */ /*    {125,0, 1, 1 },     /  1200 MHz */     {63, 1, 3, 0 },     /* 1209 MHz */       {68, 1, 3, 0 },     /* 1305 MHz */     {73, 0, 1, 0 },     /* 1401 MHz */     {78, 1, 3, 0 },        /* 1516 MHz */     {83, 1, 3, 0 },        /* 1612 MHz */     {88, 1, 3, 0 },        /* 1708 MHz */     {93, 1, 3, 0 },        /* 1804 MHz */ };

along with:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

static struct clkctl_acpu_speed acpu_freq_tbl[] = {     { 0, 24576,  LPXO,       0, 0,  30720000,  800, VDD_RAW(800) },     { 0, 61440,  PLL_3,    5, 11, 61440000,  800, VDD_RAW(800) },     { 1, 122880, PLL_3,    5, 5,  61440000,  800, VDD_RAW(800) },     { 0, 184320, PLL_3,    5, 4,  61440000,  800, VDD_RAW(800) },     { 1, 192000, PLL_3,    5, 3,  61440000,  800, VDD_RAW(800) },     { 1, 245760, PLL_3,    5, 2,  61440000,  800, VDD_RAW(800) },     { 1, 368640, PLL_3,    5, 1,  122800000, 850, VDD_RAW(850) },     { 1, 568000, PLL_3,    5, 1,  137800000, 900, VDD_RAW(900) },     /* AXI has MSMC1 implications. See above. */     { 1, 768000, PLL_1,    2, 0,  153600000, 1000, VDD_RAW(1000) },     /*      * AXI has MSMC1 implications. See above.      */     { 1, 806400,  PLL_2, 3, 0, UINT_MAX, 1025, VDD_RAW(1025),&pll2_tbl[0]},     { 1, 1024000, PLL_2, 3, 0, UINT_MAX, 1100, VDD_RAW(1100),&pll2_tbl[1]},     { 1, 1113600, PLL_2, 3, 0, UINT_MAX, 1125, VDD_RAW(1125),&pll2_tbl[2]},     { 1, 1209600, PLL_2, 3, 0, UINT_MAX, 1150, VDD_RAW(1150),&pll2_tbl[3]},     { 1, 1305600, PLL_2, 3, 0, UINT_MAX, 1175, VDD_RAW(1175),&pll2_tbl[4]},     { 1, 1401600, PLL_2, 3, 0, UINT_MAX, 1200, VDD_RAW(1200),&pll2_tbl[5]},     { 1, 1516800, PLL_2, 3, 0, UINT_MAX, 1250, VDD_RAW(1250),&pll2_tbl[6]},     { 1, 1612800, PLL_2, 3, 0, UINT_MAX, 1275, VDD_RAW(1275),&pll2_tbl[7]},     { 1, 1708800, PLL_2, 3, 0, UINT_MAX, 1300, VDD_RAW(1300),&pll2_tbl[8]},     { 1, 1804800, PLL_2, 3, 0, UINT_MAX, 1325, VDD_RAW(1325),&pll2_tbl[9]},     { 0 } };

Handle the CPU with care! Keep in mention that you’re playing with the voltages of your phone. Only raise the voltages by 25 max per try. When your phone doesn’t get enough power when requested it will turn off.
No big deal luckily, but a WARNING to you that you shouldn’t raise the voltage anymore (in the matter of fact you need to lower it by 25 when your device goes off)

Read More