Android one xda forum

[Index][Roms]Android one All Roms And Gapps

Breadcrumb

Ashish0077

Senior Member

Hii Guys.
Here Are all the custom Roms available for android one

Android 5.1.x Lollipop Based Roms

For Android 5.1 or 5.1.1, you will need a compatible Gapps for your custom ROM. The following Android 5.1 Lollipop Gapp
s includes:

Android 5.1 and 5.1.1 support
Google Play Services 7.3.26
Google Play Store 5.4.12
Google Search App/”OK Google” everywhere feature
FaceLock for SmartLock
Fully compatible with CM12 and CM12.1 ROM
Fully compatible with any Android 5.1 or Android 5.1.1 custom ROM

These are minimal Gapps so you don’t get all the extra Google bloatware you don’t need, you can download any other Google apps using Play Store after installing! You can install apps like Google+, GMail, Google Maps, etc… on the Play Store after installation.

Android 4.4.4 Kitkat Based Roms

This is micro Gapps Package this includes:-

Google Play Store
Google Bookmarks Sync
Gmail
Google Calendar (replaces stock AOSP Calendar)
Google Now Launcher
Google Play services
Google Search
Google Text-to-Speech

NOTE:- These Stock Roms Are only Flashable By SP Flash Tool(Pc Required)

Flashable Stock Rom (Kitkat 4.4.4)

The Given links will redirect You to the flashable stock rom thread. These rom package are flashable by recovery no need of Sp flash tool.
Thread 1 ==> http://forum.xda-developers.com/cro. -stock-rom-android-one-flashable-zip-t3031400

All GAPPS (5.1.1 LP & 4.4.4 KK)

You Guys Must be thinking Why I m giving two Gapps Links/Whats the difference
The Above given Gapps are micro packages that only includes essential Google apps u need to run ur android device perfectly.
Here are all packages available full, stock, normal, micro etc etc. so download according to ur usage

This Link will redirect U to the Xda Thread Of Gapps where u can find Gapps According to your Usage.

Pls Hit Thanks If U Like My work

ARAVIND_PAVAN

Senior Member

nice could you copy paste this on questions thread by me

SENT FROM PIECE OF GLOWING GLASS MADE BY MICROMAX

Ashish0077

Senior Member

nice could you copy paste this on questions thread by me

SENT FROM PIECE OF GLOWING GLASS MADE BY MICROMAX

ghpranav

Senior Member

It would be great if you even include the custom kernels & also if you add the current versions of the roms in the post.

Ashish0077

Senior Member

ghpranav

Senior Member

asifboss00

Senior Member

Thanks for this thread. You’ve done a noble job

the_prodigal_coder

Senior Member

Ashish0077

Senior Member

the_prodigal_coder

Senior Member

Let me clarify
Stock Lollipop builds have face unlock feature.
Custom roms which require separate gapps files do not seem to support face unlock
Face unlock (which uses the front camera) has nothing to do with «on body detection» that has been recently added as a separate smart lock feature on newer gapps packages, since it uses the on-board accelerometer and gyroscope.
So no, on body detection cant replace face unlock. I am still confused as to why face unlock doesn’t work on custom roms

———- Post added at 12:07 AM ———- Previous post was at 12:01 AM ———-

PS. Face unlock was one of lollipop’s key release features (it was present since 4.0.4, but very slow and insecure) that Google showed off in i/o 2014, so your statement that «face unlock doesn’t work on lollipop» is absurd.
PPS. Great thread though, I hope you continue maintaining it, then I’ll talk to the mods to make this a sticky thread.

Источник

Android One

Breadcrumb

avoup

New member

I was searching for Android One topics here and unfortunately found nothing ( probably because of the confusing name)

So can someone explain what’s up with this Android One software overlay.
I read some info on wiki but still have some questions:

Is it like normal firmware that only comes with certain smartphones, or you can flash it yourself?

It’s a near stock android but, which version is it based on,
does it come out every time new android version rolls out, or it just gets updated to the new one.

and lastly let’s say I have android one phone, and after three years they stopped regular updates,
it’s still android one compatible phone right, so I can update to the new version myself?

Forum Moderator

I was searching for Android One topics here and unfortunately found nothing ( probably because of the confusing name)
.
and lastly let’s say I have android one phone, and after three years they stopped regular updates,
it’s still android one compatible phone right, so I can update to the new version myself?

Hi, Android One are phones that run a lite weight version of Android for budget phones with small specs (under 2Go of RAM, entry level processor. ) called Android Go. It’s supposed to give a fluid experience to phones with limited capacity. Each Android Go version (for each Android One device) is in consequences very specific to the device, in order to use efficiently all of what the different specs has to offer.
You can still build ROMs/TWRP for those devices, and use it as a normal device, but the experience will be much slower. So to answer your 3 questions:
1)It’s firmware that only comes with certain phones, it’s build to use perfectly the SoC and memory, so it’s very specific (not generic like GSI)
2) Android One are phones, Android Go is the Android version. Your phone may or may not receive an update to the Next Android version, on that side it’s the same as other phones. If it receives an update, you’ll run (for example) Android 10 Go Version. So update exists for Android One phones, they won’t stay for ever at the same Android version they had at the beginning.
3) when your phone won’t be supported anymore, you won’t be able to update your phone to another version of Android Go. You’ll still be able to flash ROMs or stuff like that, but since Android Go builds are very specific to each devices, you can’t flash them «cross devices».

PS: at the moment I’ve not heard of Android 10 Go Edition, it’s still at Android 9 if I’m correct. But it will be updated, the goal of Android one is to support cheap and often not long lasting phone over time.

Источник

[ROM][8.1][STOCK][MONTANA] Android 8.1.0 Oreo — Stock Firmware (Fastboot & TWRP)

Breadcrumb

DoctorStrange96

Senior Member

This is a guide on how to install official Android 8.1.0 «Oreo» on our beloved, forgotten, poor Moto G5s (montana). As you all may know, Lenovorola still hasn’t released Oreo for everyone worldwide. Only a few Latin American countries are receiving the update, with Brazil due to receive it Soon™, since we’ve already received the August security patch (still Nougat though :/).
Update 2018.09.29: Brazil and India have also started receiving Oreo, but with a different build (OPP28.65-37-2).
However, this is Lenovorola we’re dealing with, so I went ahead, captured the OTA and created a TWRP flashable zip, by patching the June firmware (NPPS26.102-49-11) with said OTA. And also, there’s the standard .xml.zip to be used with fastboot, directly from Moto.
For those of you who want to keep everything stock, locked bootloader and all, I recommend going with the fastboot zip. For those who already have unlocked their phone’s bootloaders and have TWRP installed, or are coming from a custom ROM but don’t want to fiddle around with fastboot, you should use the TWRP flashable zip.

I can’t stress this enough. ALWAYS BACK UP YOUR STUFF. Do a TWRP backup (data, system, boot). I recommend backing up the contents of your internal storage as well. And for those willing to downgrade at some point, back up your persist and efs partitions, otherwise you’ll lose IMEI!

Oh, and I assume you already have adb, fastboot and the Motorola USB drivers installed. In case you don’t.
Motorola USB Drivers
Android SDK Platform Tools (includes adb & fastboot)
If you use Linux, you don’t need to install any drivers, but you may have to configure udev to allow fastboot to detect your device. But that, along with telling how to configure adb and fastboot, is beyond the scope of this thread.
I don’t know how things work in the Apple side, so kindly don’t ask me how to do that on macOS.

This firmware should work on all Moto G5s models (XT1791/2/3/4/5/7). I can’t tell if it works on model XT1799-2 (aka Green Pomelo / Qingyou).

A few warnings:
1. Forced encryption has not been disabled. So, if your phone is not encrypted, it will be encrypted again upon the very first boot. Don’t interrupt the process, otherwise you’ll lose ALL of your data! (You can flash @Zackptg5’s dm-verity / forced encryption disabler if you want to)
2. Xposed doesn’t work, whether it’s installed to /system or via Magisk (systemless). I’ve already opened an issue on GitHub and am awaiting a reply.
3. (Fastboot only) Updating to this firmware will also update your bootloader and partition table. If you’re unsure about that and/or afraid of a possible hard brick, skip the gpt and bootloader lines.
4. Please install the proper build for your software channel. For retbr and retin, use OPP28.65-37-2. For the other channels, go with OPP28.65-37.
5. If your phone’s software channel is retbr or retin and you have already flashed the -37 build, you can simply dirty flash the -37-2 build over it. No need to factory reset / fastboot erase userdata.

With that out of the way, let’s get to what matters most.

Источник

[INFO] Android One Overclocking

Breadcrumb

F4uzan

Inactive Recognized Contributor

Hi guys !
I’ve been trying to add overclocking to Android One, I’m able to add another frequency (both Overclock and Underclock) but I’m able to test it, the 1391 MHz was the stablest overclock frequency I could get. Decreasing frequency lower than 590 MHz makes booting slower (I don’t know why).

Check the screenshot, I’ll report more news once I get things finished.

I have attached the mt_cpufreq.c just in case anyone have a kernel source and want to try the overclock.

EDIT3: I found this in mt_cpufreq.c :

Which is defined in the same file, the DVFS_F0 is :

The DVFS_F0 is 1.3 GHz, this might explain why the max frequency keeps jumping to 1.3 GHz when screen off. But this is just an assumption.

I’ve added mt_ptp.c just in case anyone want to checkout and help the development.

Attachments

• 

the_prodigal_coder

Senior Member

I had given up all hopes of low level modifications such as over clocking /underclocking/under volting and kernel level wake gestures like double tap to wake etc. This gives me something to look at. Thank you

F4uzan

Inactive Recognized Contributor

It seems that max freq can’t be set to other than 1300 MHz / 1.3 GHz.
Can anyone here using CM12.1 confirm this bug ? Since it might be because of the ROM but I’m unsure here, it can be either ROM or my custom built kernel.

BTW, 470 MHz isn’t fully implemented, the kernel refuses to use it. It might be because I haven’t defined it in the volt switch function.

EDIT: Another possibility, it seems on mt_ptp, the clock are either hardcoded or defined in other file. So I have to say that overclocking might be still far away to be achieved.

Saurabh K

Senior Member

F4uzan

Inactive Recognized Contributor

hstinscdln

Member

F4uzan

Inactive Recognized Contributor

hstinscdln

Member

Can it be used on a 5″ screen and MT6582M?

Sent from my Lenovo A536 using XDA Free mobile app

F4uzan

Inactive Recognized Contributor

Can it be used on a 5″ screen and MT6582M?

Sent from my Lenovo A536 using XDA Free mobile app

Depends, does your phone kernel source exist ? If yes, then you’re free to try. If not, then don’t.

BTW, please don’t think this is just a ‘install the .c file and get overclock’. It needs many work, and such, I advise you to have at least some advanced knowledge of Linux Kernel.

Mr.trololol

Senior Member

It seems that max freq can’t be set to other than 1300 MHz / 1.3 GHz.
Can anyone here using CM12.1 confirm this bug ? Since it might be because of the ROM but I’m unsure here, it can be either ROM or my custom built kernel.

BTW, 470 MHz isn’t fully implemented, the kernel refuses to use it. It might be because I haven’t defined it in the volt switch function.

EDIT: Another possibility, it seems on mt_ptp, the clock are either hardcoded or defined in other file. So I have to say that overclocking might be still far away to be achieved.

Источник