[ROM][Stock] Stock Android 6.0 ROM for Lenovo Tab 3 8/TB3-850F (Root, BusyBox, Zipali - Thinkpad Tablet Android Development

Lenovo Tab 3 8/TB3-850F
Stock Android 6.0 Marshmallow ROM
Rooted, BusyBox, Zipaligned
TWRP Flashable Installer
DISCLAIMER:
By proceeding further, please take note that your warranty will be null and void. You hereby take full responsibility for any positive or negative consequences which may incur by installing this ROM and, in doing so, you are absolving me from any liability in the event that your device gets bricked or is otherwise rendered inoperable. This ROM has been thoroughly tested. Follow the instructions carefully and pay attention to detail and things should go smoothly and without incident.
Note:
For members interested, I should note that I have compiled a build of this ROM with up-to-date security patches (June 1, 2018) and several custom features, which I will be posting in the next couple of days.
DESCRIPTION:
This is a Stock Android 6.0 ROM for the Lenovo Tab 3 8/TB3-850F. This ROM should also be compatible with the LTE variant of this device (TB3-850M), but such compatibility has not been confirmed. This ROM is the most current stock build available for the TB3-850F.
SPECIFICATIONS & FEATURES:
•Android Version: 6.0 Marshmallow
•Build No. TB3-850F_S100031_171010_ROW
•Software Version: TB3-850F_160412
•Kernel Version: 3.18.19
•Android SDK: 23
•Security Patch Level: September 5, 2017
•Build ID: MRA58K
•Build Date: October 10, 2017
•Root: Magisk v16.7-beta (Systemless)
•SafetyNet Pass (ctsProfile & basic integrity)
•BusyBox: v1.28.4 (Static Binaries) /system/bin/
•Zipaligned: /system/app & /system/framework
•Force Encryption Disabled
•dm-verity Disabled
•Init.d & su.d Support
•Optimized for Low RAM
•TWRP Flashable Installer
INSTRUCTIONS/REQUIREMENTS:
First and foremost, your device must have an unlocked bootloader and you must have TWRP custom recovery installed. If you need instructions on doing this, please see my thread here: https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786 Also, because installation requires the /userdata partition to be formatted, an external microSD card is needed.
1. Download the ROM zip from the below download link and save it to external storage;
2. Boot your device into TWRP recovery mode;
3. On TWRP's main screen, select Wipe>>Advanced Wipe and select Cache & Dalvik, then swipe to commence wiping;
4. Again, on the main screen, select Wipe and then select Format Data in the lower right of your screen. Swipe to commence formatting (this step is crucial for the disabling of force encryption);
5. Select Install, navigate to the location of the ROM zip, select it and swipe to commence installation (takes 3 to 4 minutes);
6. Reboot System;
BUGS:
No known or reported bugs...Please report any bugs or instabilities in comments.
Open Source Code: https://pcsupport.lenovo.com/us/en/...ies/tab3-8/za17/za170001us/downloads/ds112711
Mentions/Thanks:
•Thanks to @pndwal for his support on this device and assistance in my absence.
•Thanks to @osm0sis for his static BusyBox installer and Magisk Module.
•Thanks to @topjohnwu for his legendary and world famous Magisk Systemless Interface.
•Thanks and credit to the brilliant coder, @SuperR., for his superb Windows version Kitchen.
•Thanks to @Hemphiz for breaking ground on the Tab 3 8" and for his guidance.
Download Links:
TB3-850F_S100031_171010_ROW: https://drive.google.com/file/d/1pKu1If-9Y9adeigUe5-HEBbqmFej5zYB/view?usp=drivesdk
Lenovo Tab 3 8/TB3-850F
User Manual (English) PDF: https://drive.google.com/file/d/18gCTfuZecJnlB0ddBIN02YPaDpuvmzov/view

Installing now, will report after review!
Sent from my Redmi Note 5 using Tapatalk

LineageOS and RR ports for this device are coming along decent. The trick is not the ROM itself on /system, but rather the kernel/ramdisk, which was specifically compiled for the TB3-850M chipset. Soon as I get a bootable kernel, we are in business with Nougat for TB3-850F.

MotoJunkie01 said:
LineageOS and RR ports for this device are coming along decent. The trick is not the ROM itself on /system, but rather the kernel/ramdisk, which was specifically compiled for the TB3-850M chipset. Soon as I get a bootable kernel, we are in business with Nougat for TB3-850F.
Click to expand...
Click to collapse
That's good news. Look forward to trying.
If it helps, I kept the original Lenovo box sticker for TB3-850F. It says: CPU:MT8161P QC 1.0GHZ 64BIT. (So it seems on-line information, Kernel Auditor, Phone Tester and CPU-Z etc, are in fact reporting CPU / Vendor correctly as MT8161P.)
I was interested in this for overclocking potential, but it may help streamlining kernel for chipset. (I guess CPU speed may still be crippled by MT6735 hardware / SoC.)
Hope you get it booting. PW.

The rom works great, much better then stock!
Battery life is very good and speed is much better!!
Thank you!
Sent from my Redmi Note 5 using Tapatalk

pndwal said:
That's good news. Look forward to trying.
If it helps, I kept the original Lenovo box sticker for TB3-850F. It says: CPU:MT8161P QC 1.0GHZ 64BIT. (So it seems on-line information, Kernel Auditor, Phone Tester and CPU-Z etc, are in fact reporting CPU / Vendor correctly as MT8161P.)
I was interested in this for overclocking potential, but it may help streamlining kernel for chipset. (I guess CPU speed may still be crippled by MT6735 hardware / SoC.)
Hope you get it booting. PW.
Click to expand...
Click to collapse
This is still quite perplexing. It does appear there are two variants of the TB3-850F -- an MT8161P variant and an MT6735M variant. Although SP Flash Tool and the scatter file both indicate that my chipset is the MT6735M, I went as far as to disassemble my device to check the nomenclatures on my logic board -- which, to no surprise, is the MT6735M. Since the MT6735M and the MT8161P are in fact two entirely different chipsets, the only logical conclusion is that there are two variants to the TB3-850F. Curiously however, both chipsets are listed under MediaTek's specs as being arm64 architecture with a max clock of 1.0 GHz and 1GB RAM. My RCA Voyager tablet runs on the MT8161P and performs nearly exactly like my Tab 3 8.

MotoJunkie01 said:
This is still quite perplexing. It does appear there are two variants of the TB3-850F -- an MT8161P variant and an MT6735M variant. Although SP Flash Tool and the scatter file both indicate that my chipset is the MT6735M, I went as far as to disassemble my device to check the nomenclatures on my logic board -- which, to no surprise, is the MT6735M. Since the MT6735M and the MT8161P are in fact two entirely different chipsets, the only logical conclusion is that there are two variants to the TB3-850F. Curiously however, both chipsets are listed under MediaTek's specs as being arm64 architecture with a max clock of 1.0 GHz and 1GB RAM. My RCA Voyager tablet runs on the MT8161P and performs nearly exactly like my Tab 3 8.
Click to expand...
Click to collapse
Yes, you may be right, but perhaps not the only logical conclusion. My thinking is that there may be one variant with MT8161P CPU and MT6735M board chipset. (Eg. Kernel Auditor gives MT8161p as vendor, but MT6735 as hardware, and build.prop also gives ro.board.platform=mt6735m, but also ro.lenovo.cpuinfo=MT8735P). This would most likely mean MT8161P CPU functionality would be somewhat limited by MT6735M chipset, even though the two must be compatible. Of course, if you found MT6735M printed on your main chip (CPU), this theory would be wrong, and there could in fact be a number of variations.
I mentioned earlier: 'Phone Tester gives CPU Info: MT8161p. Kernel Auditor gives MT8161p as vendor, but MT6735 as hardware. CPU-Z gives MT6735 as SoC. Build.prop gives ro.board.platform=mt6735m, but also ro.lenovo.cpuinfo=MT8735P. Russian 4PDA forum gives 850f Processor Type: MT8161, with MT8735 for 850M variant. (http://4pda.ru/devdb/lenovo_tab3_8:850f)
So it's hard to know what or who's correct, but looks to me that newer CPUs have likely been installed on boards originally designed for MT6735. (My CPU could actually be MT8735 as given by build.prop if Lenovo had excess chips from 850M, or simply decided to use these in both models. - I guess they may even have started with MT6735 for 850f before progressively using MT8161 and MT8735.)'
Also, the MT8161p CPU specs I found say 1.3 GHz (although TB3-850f is limited to 1.0 GHz), hence my assumption that a kernel modified to allow overclocking should achieve 30% boost easily easily and perhaps 1.7 GHz or so would be achievable.
If you did find MT6735M printed on your main chip (CPU), I'm happy to try to disassemble mine to see if it's a different variant. (Guessing this would confirm my original TB3-850F Lenovo box sticker which says CPU:MT8161P QC 1.0GHZ 64BIT).
I'll do more digging into this if you think it may help with port or overclocking.
Hope it leads to some improvements anyway. Thanks for your efforts with our device. PW.

pndwal said:
Yes, you may be right, but perhaps not the only logical conclusion. My thinking is that there may be one variant with MT8161P CPU and MT6735M board chipset. (Eg. Kernel Auditor gives MT8161p as vendor, but MT6735 as hardware, and build.prop also gives ro.board.platform=mt6735m, but also ro.lenovo.cpuinfo=MT8735P). This would most likely mean MT8161P CPU functionality would be somewhat limited by MT6735M chipset, even though the two must be compatible. Of course, if you found MT6735M printed on your main chip (CPU), this theory would be wrong, and there could in fact be a number of variations.
I mentioned earlier: 'Phone Tester gives CPU Info: MT8161p. Kernel Auditor gives MT8161p as vendor, but MT6735 as hardware. CPU-Z gives MT6735 as SoC. Build.prop gives ro.board.platform=mt6735m, but also ro.lenovo.cpuinfo=MT8735P. Russian 4PDA forum gives 850f Processor Type: MT8161, with MT8735 for 850M variant. (http://4pda.ru/devdb/lenovo_tab3_8:850f)
So it's hard to know what or who's correct, but looks to me that newer CPUs have likely been installed on boards originally designed for MT6735. (My CPU could actually be MT8735 as given by build.prop if Lenovo had excess chips from 850M, or simply decided to use these in both models. - I guess they may even have started with MT6735 for 850f before progressively using MT8161 and MT8735.)'
Also, the MT8161p CPU specs I found say 1.3 GHz (although TB3-850f is limited to 1.0 GHz), hence my assumption that a kernel modified to allow overclocking should achieve 30% boost easily easily and perhaps 1.7 GHz or so would be achievable.
If you did find MT6735M printed on your main chip (CPU), I'm happy to try to disassemble mine to see if it's a different variant. (Guessing this would confirm my original TB3-850F Lenovo box sticker which says CPU:MT8161P QC 1.0GHZ 64BIT).
I'll do more digging into this if you think it may help with port or overclocking.
Hope it leads to some improvements anyway. Thanks for your efforts with our device. PW.
Click to expand...
Click to collapse
I see what you're saying, but let me emphasize that the board and the chipset are the same entity. If a device has an MT6735M CPU, it's hardware (or board platform) is also MT6735M. And vice versa for the MT8161P. The MT6735M and the MT8161P are both very different CPU/board platforms, but with very similar specs.
Same with Qualcomm, a MSM8909 CPU has an MSM8909 board platform.
The ro.board.platform (build.prop) of my Tab 3 8 has the MT6735M correct, as is my hardware confirmed by disassembly.
For an example, my RCA Voyager 7" tablet has the MT8161P CPU, supported by the MT8161P board platform (chipset).
With MediaTek, a failsafe way of checking hardware specs (aside from disassembly) is using the SP Flash Tool w/scatter file.
There is some room for overclock with the mt6735m. The mt6735 for example (without the "m" suffix) has a max clock of 1.394 GHz. The mt6735m is simply a ramped down version of the mt6735. Hardware wise, the mt6735 and mt6735m are the same. The difference arises in the coding of the kernel/ramdisk configs.
So, you and I agree on overclocking potential, albeit for different reasons.

MotoJunkie01 said:
I see what you're saying, but let me emphasize that the board and the chipset are the same entity. If a device has an MT6735M CPU, it's hardware (or board platform) is also MT6735M. And vice versa for the MT8161P. The MT6735M and the MT8161P are both very different CPU/board platforms, but with very similar specs.
Same with Qualcomm, a MSM8909 CPU has an MSM8909 board platform.
The ro.board.platform (build.prop) of my Tab 3 8 has the MT6735M correct, as is my hardware confirmed by disassembly.
For an example, my RCA Voyager 7" tablet has the MT8161P CPU, supported by the MT8161P board platform (chipset).
With MediaTek, a failsafe way of checking hardware specs (aside from disassembly) is using the SP Flash Tool w/scatter file.
There is some room for overclock with the mt6735m. The mt6735 for example (without the "m" suffix) has a max clock of 1.394 GHz. The mt6735m is simply a ramped down version of the mt6735. Hardware wise, the mt6735 and mt6735m are the same. The difference arises in the coding of the kernel/ramdisk configs.
So, you and I agree on overclocking potential, albeit for different reasons.
Click to expand...
Click to collapse
Thanks for that. Just though lenovo may have decided to use old board stock if pin outs still compatible with newer CPU, but I have no knowledge if this is possible in practice.
From what you're saying seems TB3-850F would have had two or more different sets of box specs, which I had thought would be illogical for one model, but I guess I'm wrong.
I'll open mine up sometime just to physically check chipset is in fact MT8161P as claimed on box. (How can I use scatter file to check specs?)
Guess knowledge of variants produced may prove useful in any case. Thanks for your attention to detail here. Hope port(s) are progressing well. PW.

pndwal said:
Thanks for that. Just though lenovo may have decided to use old board stock if pin outs still compatible with newer CPU, but I have no knowledge if this is possible in practice.
From what you're saying seems TB3-850F would have had two or more different sets of box specs, which I had thought would be illogical for one model, but I guess I'm wrong.
I'll open mine up sometime just to physically check chipset is in fact MT8161P as claimed on box. (How can I use scatter file to check specs?)
Guess knowledge of variants produced may prove useful in any case. Thanks for your attention to detail here. Hope port(s) are progressing well. PW.
Click to expand...
Click to collapse
Thank you also @pndwal for your devotion and support on this device. You have truly delved off deep into both the hardware and software attributes of the Tab 3 8. I, like yourself, truly hope that future development for this tablet yields fruitful.
I have noticed that the official Lenovo user manual for the Tab 3 8 covers both the 850F and the 850M. Likewise, the open source code for our stock OS is for both tablet variants. Interestingly, the 850M LTE variant of the device appears to use the MT8735 board platform which, of course, encompasses an LTE cellular modem. I just recently realized that both the MT8161P and the MT6735M also have LTE cellular modems. I have an acquaintance over at Droid Hub who has a TB3-850F and uses LTE data on his device by way of a simple GSM SIM card micro USB dongle. He changed a few lines in build.prop to enable the Mobile Networks menu in Settings and he uses his device exactly as if it were the 850M variant. I'm going to try the same thing with my 850F.
As far as custom Nougat goes, the only difficulty lies in the kernels for both LOS & RR. Both custom builds have kernels (boot.img) compiled specifically for the 850M's MT8735 chipset. I'm corresponding with a friend who specializes in Linux kernel coding to get some needed assistance on converting the kernels over to 850F specs.

MotoJunkie01 said:
Thank you also @pndwal for your devotion and support on this device. You have truly delved off deep into both the hardware and software attributes of the Tab 3 8. I, like yourself, truly hope that future development for this tablet yields fruitful.
I have noticed that the official Lenovo user manual for the Tab 3 8 covers both the 850F and the 850M. Likewise, the open source code for our stock OS is for both tablet variants. Interestingly, the 850M LTE variant of the device appears to use the MT8735 board platform which, of course, encompasses an LTE cellular modem. I just recently realized that both the MT8161P and the MT6735M also have LTE cellular modems. I have an acquaintance over at Droid Hub who has a TB3-850F and uses LTE data on his device by way of a simple GSM SIM card micro USB dongle. He changed a few lines in build.prop to enable the Mobile Networks menu in Settings and he uses his device exactly as if it were the 850M variant. I'm going to try the same thing with my 850F.
As far as custom Nougat goes, the only difficulty lies in the kernels for both LOS & RR. Both custom builds have kernels (boot.img) compiled specifically for the 850M's MT8735 chipset. I'm corresponding with a friend who specializes in Linux kernel coding to get some needed assistance on converting the kernels over to 850F specs.
Click to expand...
Click to collapse
Nice work by your acquaintance re. LTE from dongle. (Does this somehow use LTE modem in tablet CPU, as I would have thought modem must still be LTE capable to receive LTE data. - or can non LTE modem transfer LTE with CPU support?)
Regarding TB3-850F variants, it seems here are probably a few. TB3-850F is not the full model number. There are also Machine Types (ZA17 for TB3-850F [https://pcsupport.lenovo.com/za/en/products/tablets/a-series/tab3-8/za17/parts/PD104294] and ZA18 for TB3-850M [https://pcsupport.lenovo.com/za/en/products/tablets/a-series/tab3-8/za18/parts/PD104294]), and Machine Type Model No.s. For example, my box label says Machine Type Model No. :ZA170082AU. There is also ZA170001US, etc.
I guess the extension numbers (0082AU etc) identify different variants within the series (TB3-850F, or ZA17), eg different chipsets as we have deduced, as well as other differences (eg. Lenovo's specs mentions 1GB/16GB RAM as well as 2GB/16GB variants of TB3-850F, and Lenovo's Hardware maintenance manual (good photos of internals here too, bit no chipset identification shown) [https://download.lenovo.com/consumer/mobiles_pub/lenovo_tab3_8_hmm_en_v1.0_201604.pdf] lists different parts for black or white models, for 2 MPixel or 5 MPixel rear camera models, and for models with WiFi antenna only or WiFi, BT and GPS in combination it seems.) Seems these variants are largely determined by market location, but 1GB/16GB RAM versions are probably the most common. Hope this helps.
Glad to know you have Linux kernel specialist friend. This will no doubt prove invaluable. I trust you revel in a steep learning curve!
Did a little digging on scatter files. Would I be right in thinking that scatter files generated from different variants might provide enough information to make a kernel work across the 850F range? Regards, PW

pndwal said:
Nice work by your acquaintance re. LTE from dongle. (Does this somehow use LTE modem in tablet CPU, as I would have thought modem must still be LTE capable to receive LTE data. - or can non LTE modem transfer LTE with CPU support?)
Regarding TB3-850F variants, it seems here are probably a few. TB3-850F is not the full model number. There are also Machine Types (ZA17 for TB3-850F [https://pcsupport.lenovo.com/za/en/products/tablets/a-series/tab3-8/za17/parts/PD104294] and ZA18 for TB3-850M [https://pcsupport.lenovo.com/za/en/products/tablets/a-series/tab3-8/za18/parts/PD104294]), and Machine Type Model No.s. For example, my box label says Machine Type Model No. :ZA170082AU. There is also ZA170001US, etc.
I guess the extension numbers (0082AU etc) identify different variants within the series (TB3-850F, or ZA17), eg different chipsets as we have deduced, as well as other differences (eg. Lenovo's specs mentions 1GB/16GB RAM as well as 2GB/16GB variants of TB3-850F, and Lenovo's Hardware maintenance manual (good photos of internals here too, bit no chipset identification shown) [https://download.lenovo.com/consumer/mobiles_pub/lenovo_tab3_8_hmm_en_v1.0_201604.pdf] lists different parts for black or white models, for 2 MPixel or 5 MPixel rear camera models, and for models with WiFi antenna only or WiFi, BT and GPS in combination it seems.) Seems these variants are largely determined by market location, but 1GB/16GB RAM versions are probably the most common. Hope this helps.
Glad to know you have Linux kernel specialist friend. This will no doubt prove invaluable. I trust you revel in a steep learning curve!
Did a little digging on scatter files. Would I be right in thinking that scatter files generated from different variants might provide enough information to make a kernel work across the 850F range? Regards, PW
Click to expand...
Click to collapse
You are very correct in your analysis of extension numbers and variant specs. (By the way on disassembly, I should have mentioned that it is necessary to remove the battery and some of the reinforcement adhesive in order to view the MediaTek nomenclature identifying the SoC.) You are likewise correct on your scatter file analysis. In terms of kernels, since our TB3-850F stock OS is based on Android 6.0_r2, our supporting kernel is version 3.18.19. With the Nougat (7.1.2) LOS and RR custom ROMs to be ported from 850M, we need at least a version 3.18.31 kernel version to boot the ROMs and for hardware blob support. In fact, both ROMs would boot right now and would, in theory, function completely normally if we had a supported kernel. Of course you already know all this so I'm merely thinking out loud so to speak. My colleague (who assisted on the old BlueSpark kernel project for older Motorola smartphones) is helping me compile a Nougat supporting kernel from source. And, since Lenovo did release the source code for the camera drivers for the 850F, custom shims won't be needed and the available blobs can be put in place for fully normal camera function. (Although the cameras appear to be identical on both the 850F and 850M, the difference in SoC platforms gives rise to different hardware blobs.)
Interestingly, and just like the stock OS for our device, the LOS and RR Nougat ROMs are compiled to function on the 850F and 850M. So technically, no porting is needed whatsoever on the ROMs themselves. The only real work is compiling a kernel to boot the ROMs. This is where I hope to gain some much needed knowledge and instruction on the Linux kernel and GCC. To keep you up to date, I can proudly say that a version 3.18.31 kernel is currently being built for the 850F. Soon as it is finished I will plug the custom /system files and new kernel into my Android kitchen and, much like Chef Boyardee, cook up something real proper-like. :silly:

MotoJunkie01 said:
You are very correct in your analysis of extension numbers and variant specs. (By the way on disassembly, I should have mentioned that it is necessary to remove the battery and some of the reinforcement adhesive in order to view the MediaTek nomenclature identifying the SoC.) You are likewise correct on your scatter file analysis. In terms of kernels, since our TB3-850F stock OS is based on Android 6.0_r2, our supporting kernel is version 3.18.19. With the Nougat (7.1.2) LOS and RR custom ROMs to be ported from 850M, we need at least a version 3.18.31 kernel version to boot the ROMs and for hardware blob support. In fact, both ROMs would boot right now and would, in theory, function completely normally if we had a supported kernel. Of course you already know all this so I'm merely thinking out loud so to speak. My colleague (who assisted on the old BlueSpark kernel project for older Motorola smartphones) is helping me compile a Nougat supporting kernel from source. And, since Lenovo did release the source code for the camera drivers for the 850F, custom shims won't be needed and the available blobs can be put in place for fully normal camera function. (Although the cameras appear to be identical on both the 850F and 850M, the difference in SoC platforms gives rise to different hardware blobs.)
Interestingly, and just like the stock OS for our device, the LOS and RR Nougat ROMs are compiled to function on the 850F and 850M. So technically, no porting is needed whatsoever on the ROMs themselves. The only real work is compiling a kernel to boot the ROMs. This is where I hope to gain some much needed knowledge and instruction on the Linux kernel and GCC. To keep you up to date, I can proudly say that a version 3.18.31 kernel is currently being built for the 850F. Soon as it is finished I will plug the custom /system files and new kernel into my Android kitchen and, much like Chef Boyardee, cook up something real proper-like. :silly:
Click to expand...
Click to collapse
Well, you certainly know how to wet one's appetite! - Thanks for the heads-up - Hope you get into the kitchen soon. I'll try to generate scatter file for ZA170082AU soon and post. Thanks, PW

@MotoJunkie01
Sounds like you have a lot if good help. Thought I'd just mention a contributor who whose expert help broke ground for TB3-850F (in @Lister Of Smeg's thread), @Tzul, who may be of assistance.
Interestingly, among other things he wrote:
"I have mentioned this in the other topic you found. It's normal that scatter files sometimes don't list the exact chip type in the platform field. My Tab 2 A10-70F for example has an MT8165, but the scatter file says "platform: MT6752". The name that is used there must exist in the config files of the SPFT (see platform.xml and storage_setting.xml, for example), and the settings that are defined there must be "compatible" with your actual chip type...
I don't think that waiting for SPFT updates will help. Like I wrote above, the Tab 2 A8-50F was based on the same MT8161 chip, and its scatter file lists "platform: MT6735". There's either something strange going on with your Tab3, or it's a driver issue."
All best, PW

pndwal said:
@MotoJunkie01
Sounds like you have a lot if good help. Thought I'd just mention a contributor who whose expert help broke ground for TB3-850F (in @Lister Of Smeg's thread), @Tzul, who may be of assistance.
Interestingly, among other things he wrote:
"I have mentioned this in the other topic you found. It's normal that scatter files sometimes don't list the exact chip type in the platform field. My Tab 2 A10-70F for example has an MT8165, but the scatter file says "platform: MT6752". The name that is used there must exist in the config files of the SPFT (see platform.xml and storage_setting.xml, for example), and the settings that are defined there must be "compatible" with your actual chip type...
I don't think that waiting for SPFT updates will help. Like I wrote above, the Tab 2 A8-50F was based on the same MT8161 chip, and its scatter file lists "platform: MT6735". There's either something strange going on with your Tab3, or it's a driver issue."
All best, PW
Click to expand...
Click to collapse
That's good info to know. And yeah I may just give that member a shout and see if he'd be willing to join forces on developing for the 850F. A small development team would be nice -- and you would be more than welcome to be a part. You definitely have a broad understanding of Android and you know the 850F inside and out.
I'm still leaning towards the possibility that Lenovo sold variants of the 850F.

MotoJunkie01 said:
That's good info to know. And yeah I may just give that member a shout and see if he'd be willing to join forces on developing for the 850F. A small development team would be nice -- and you would be more than welcome to be a part. You definitely have a broad understanding of Android and you know the 850F inside and out.
Click to expand...
Click to collapse
Thanks for vote of confidence. Happy to help where I can, and I'd love to set up a machine for foray into 'developing', but I have serious time constraints presently, so just an 'ideas man' (and willing tester) for now.
Looking forward to being kept up to speed with progress though. Regards, PW.
MotoJunkie01 said:
...I'm still leaning towards the possibility that Lenovo sold variants of the 850F.
Click to expand...
Click to collapse
Yes, I think that's a given also. Didn't intend to infer otherwise - just thought Tzul's info might be of interest / use because of variations (and because scatter file info may be misleading but also may work fine for 'compatible' platforms (chipsets) - I'm guessing this may make things simpler when it comes to 850F/M differing chipsets as well as any different chipsets within 850F range)... PW.

pndwal said:
Thanks for vote of confidence. Happy to help where I can, and I'd love to set up a machine for foray into 'developing', but I have serious time constraints presently, so just an 'ideas man' (and willing tester) for now.
Looking forward to being kept up to speed with progress though. Regards, PW.
Yes, I think that's a given also. Didn't intend to infer otherwise - just thought Tzul's info might be of interest / use because of variations (and because scatter file info may be misleading but also may work fine for 'compatible' platforms (chipsets) - I'm guessing this may make things simpler when it comes to 850F/M differing chipsets as well as any different chipsets within 850F range)... PW.
Click to expand...
Click to collapse
Yes I totally agree with you there.

Ok @pndwal, I have successful boot of the LineageOS 14.1 ROM for our 850F. Everything force closes and crashes on initial setup but I know the issue there. (Involves the .dex files in /system/priv-app and /system/framework. I'm debugging now to get things stable enough to launch. Fingers crossed.

MotoJunkie01 said:
Ok @pndwal, I have successful boot of the LineageOS 14.1 ROM for our 850F. Everything force closes and crashes on initial setup but I know the issue there. (Involves the .dex files in /system/priv-app and /system/framework. I'm debugging now to get things stable enough to launch. Fingers crossed.
Click to expand...
Click to collapse
Great news! Looking forward with eager expectation. Really appreciate your efforts PW

pndwal said:
Great news! Looking forward with eager expectation. Really appreciate your efforts PW
Click to expand...
Click to collapse
Most apps are now stable on the LOS build. Ironing out Bluetooth and WiFi issues and hope to have a beta build posted this week.

Related

[Q] GB build from Nook Color or Droid X on P1010 (wifi only) Galaxy 7 inch tablet?

Everyone,
I know that we don't currently have a gingerbread (GB) update for the the famed Samsung 7 inch tablet (wifi only).
However, I was doing some research and discovered that the nook color runs either OMAP3621 or OMAP3622 system on a chip.
The P1010 runs the OMAP3630 system on a chip but the 3630, 3621 and 3622 have that same PowerVR SGX530 graphics chip. And of course, all of the listed OMAP SOC models have the same ARMv7 Cortex-A8.
I have also learned that the droid X has that same that same PowerVR SGX530 graphics chip.
Both the nook color and the droid X have GB builds.
So this begs the question, why can't we modify a nook color or droid X GB build for the P1010? I ask because the p1010 should have the same hardware minus a cell modem, sim slot, or HID device. So shouldn't it be a matter of removing software from the build?
Thanks for any time & effort reading or replying.
c0le
*** EDITED ****
**** BUMP ****
*****BUMP*****
Now, I'm a P1000 owner so I don't have much experience with the TI sets, but I don't think it will be anything like that easy. Generally speaking, porting a ROM from such very different sets of hardware is very tricky. Although the processor's and graphics units might be the same, they won't be built into the system the same way and all the other components like the display, touch screen, USB, power, audio, and everything else will be quite difficult.
I'm not saying it's impossible (it's probably not, not sure) but I will say that I don't think you'll see one anytime soon. It's very tricky and very unreliable, and the 1010 really doesn't have the developer base that would usually accompany a project like that.
Again, I'm not certain (never got that far into any devices other than the P1000, really), but I don't think it would be that easy.
I think that some things, like display and power might be the same as the p1000. As for the usb, isn't that part of the system on a chip? I find it hard believe that samsung didn't use some rather common components. Should just be a matter of finding the drivers from other builds and putting them in a new build.
Sent from my GT-P1010 using Tapatalk

BUYER'S GUIDE{Android Device's}[TUTORIAL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
INTRO -
Hi all.I made this guide to help people to buy good device.As you all have experience of a worst device,a device which doesn't even run Decent app's or games and from now onwards lets atleast make sure that we buy a Good device
We usually GOOGLE about some good device's out there where we follow what actually the Website's say blindly,but i really don't prefer it.I dont prefer it 'cause the Reviewer usually thinks with a Normal User mentality.We should not only look out for better specs but also for Developer support.Here let's get independent and take the decision of buying phone's by ourself .​
ABOUT ANDROID-
Android is a software bunch comprising not only operating system but also middleware and key applications.Android is still very much the ARM instruction set and all Android open source build's are geared towards ARM processors.Android is an ARM-centric OS.Android is a powerful Operating System supporting a large number of applications in Smart Phones. These applications make life more comfortable and advanced for the users. Hardwares that support Android are mainly based on ARM architecture platformApplications
These are the basics of Android applications:
• Android applications are composed of one or more application components (activities, services, content providers, and broadcast receivers)
• Each component performs a different role in the overall application behavior, and each one can be activated individually (even by other applications)
• The manifest file must declare all components in the application and should also declare all application requirements, such as the minimum version of Android required and any hardware configurations required
• Non-code application resources (images, strings, layout files, etc.) should include alternatives for different device configurations (such as different strings for different languages)​​
THE ARM Processor Family(ABOUT PROCESSOR'S)​
ABOUT ARM :
ARM (Advance RISC machines) is a UK company that built's RISC processor's.ARM doesn't sell microphone's intead it linces it's technology to other companies along with the option to drop the Vanilla (non-modified) ARM core in their SoC (System On Chip).Many company's like Qualcom,nVidia create their own processor by using ARM design as Blue-print and yeah ARM has it's share in the profit .​
ABOUT SoC (System On Chip) :
The system on Chip is single peice of chip which comprises of CPU,GPU,memory controller ..etc . SoC may either have ARM or x86 core technology.It is a unique chip which is a package that has Baseband,host of controller's that are need to process data.SoC is one single chip which is fabricated with the above stated functions.SOC's are efficient and reduce memory overhead.Top notch Company's's like Qualcom,nVidia,Apple built their SOC's using the blue-print processor design provided by ARM​
INSTRUCTION SET :
These are special functions that has a processor can perform several stuff such as Arithmetic instruction,floating point,bit manipulation..etc . ARM support's a variety of instruction's like x86..etc..They also support 64-bit which are high and powerful performance computing chips,whereas 32-bit chips are low-powered,Little performance deliverer .. ARM also support complex instuctions like SIMD instructions​
THE ARM ARCHITECTURE :
The ARM Architecture is the base for all ARM related Core's. Usually a companies like Qualcomm,broadcom ,etc which would be creating custom cores will license the Architecture for tweaking it from ARM itself.Using the Architecture and fine-tuning it for special work such as Real Time processing or High complex level purpose they create a particular Family names like Cortex-A, Cortex-R...etc . ​
THE ARM CORE :
By varying the core clock speed,instruction set,,ARM Produces many cores for SOC builder's . Such is Cortex A7,A8,A9 core family.Cortex family in used in almost every Top Notch device out there.Its completely depends on the OEM/Vendor to opt for the core's that are needed for their Devic​e​​
So,let's now move to the Basic point's one must keep in mind to buy an Android device ..​
1 . SCREEN SIZE :
This is the first thing that must Flash into our mind before buying an Android Device .Screen size is subjective and should be based on your taste.Still,smartphone,it's better to opt for a screen,that's bigger than 4" inches for a Device and more than 7" inches would do good for a Tablet.​
2 . RESOLUTION :
Look out for the device which has higher PPI (pixels per inch) value .. PPI more than 250 is considered good but higher the PPI the better the device would be .The best part is that these devices offer the ability to pinch to zoom or tap to zoom which aids in reading even with a lower-size display​
3 . HARDWARE :
In terms of Android OS one needs better hardware to get a lacklustre view of browsing and the fact 'THE HIGHER THE BETTER" apply's here too ..Architecture and process nodes boost performance more than stuffing in more cores with enhancement's .. Phone's with Quad-core SOC'S will surely lead to batter draining .. Go for the device which is powered by cortex A9 , A7 technology paired with Quad core's or even dual core's ​.​
3.1 . GPU : ]
Some of the best GPU'S out there are made by Qualcomm (adreno) ,ARM (mali) ..But make sure that you device doesn't have a BROADCOM powered GPU.. Broadcomm has a closed-source policy and they make the Best Buggy GPU'S out there .. Better opt fo Qualcomm powered GPU .Anyway Adreno and Mali based GPU occupy a large chunk over the system and leaving less for you .so make sure your device has 1GB Ram​..​
4 . UPDATE'S OF ROM :
This is plagued by OEM'S or vendors.This is the main reson behind the stagnating with fragmentation's over verions .This is completely controlled by the device Vendor's .Though Samsung tops in place of providing update but that actually wont be that satisfactory...
Just make sure to check the developement status of the device which you decided to buy, here at XDA .Anyhow if you want a Future-proof device regarding the upgrades then better stick to Nexus Line Family device which are provided by the tech Gaint and Android owner "GOOGLE"​..​​​​
Hope this thread helped you ..
credits:
OSY team for providing Such Knowledge
@mathm2013 @Hitesh2626 @DamnTarget FOR FEEDBACK
GFX Bandits and my whatsapp friends ..
Giupy 99 said:
BroadComm for the knowledge they gave to never buy a BCM-powered device again
Click to expand...
Click to collapse
Google Nexus 5
$349 (16 GB) or $399 (32 GB) unlocked, but don’t call it “cheap.” Also available starting at $410 on Swappa. With class leading specs and excellent software and developer support, the Nexus 5 is a force to be reckoned with.
You can’t even begin to think about creating a list of the best phones currently available—at any price—without at least mentioning the Google Nexus 5. The LG-sourced device packs some serious computing firepower, including the current best-in-class quad-core Qualcomm Snapdragon 800 processor running at 2.26 GHz. It also packs 2 GB of RAM, a 2300 mAh battery, and a gorgeous 5″ 1080p screen with pixels dense enough so that it doesn’t even matter anymore. The camera isn’t the best in the world, and neither is its speaker volume, but both of these issues have since been mitigated somewhat.
What makes this device special isn’t its admittedly great hardware. No, it’s the software. With a stock version of the latest and greatest Android and Google have to offer, as well as virtually limitless development potential, the Nexus 5 is a software tour-de-force.
XDA Breakdown:
Root? Yes
Recovery? Yes.
Unlockable? fastboot oem unlock. Need I say more?
Widespread Aftermarket Developer Support? Yes.
Multiboot? YES!
LG G2
$650 unlocked (or under $200 with carrier subsidy). Also available starting at $470 on Swappa.
Close cousin to the Nexus 5, the LG G2 shares many of its internals with the N5. Though the device features a larger screen and a markedly better camera, it also is weighed down by an OEM skin that only a mother could love. Despite that, the device still packs solid performance, and with a little aftermarket development love, it can truly shine.
XDA Breakdown:
Root? Yes.
Recovery? Yes (guide).
Unlockable? Loki Patch.
Widespread Aftermarket Developer Support? Official AOKP, OmniROM, CyanogenMod, and Paranoid Android available.
Multiboot? No.
Sony Xperia Z1
$609 unlocked. Also available starting at $450 on Swappa.
Sony’s flagship for late 2013 packs quite a punch in the specs department. The device features a super speedy processor, excellent camera, competent screen, and amazing developer friendliness from the OEM.
XDA Breakdown:
Root? Yes.
Recovery? Yes.
Unlockable? Yes.
Widespread Aftermarket Developer Support? Official OmniROM and CyanogenMod available.
Multiboot? No.
Moto X
$529 unlocked (or $99 with carrier subsidy). Also available starting at $390 on Swappa. Motorola’s flagship isn’t so much a flagship as it is an everyman’s phone.
Rather than cramming as many MHz and GB as possible into as think a device as possible, Motorola chose a different path. They instead came up with a few incredibly innovative software additions and tailored the hardware to match. As such, the Moto X doesn’t directly compete with the Samsung Galaxies and the HTC Ones of the world, at least not in raw specs, but it doesn’t have to. It’s a great device that offers solid performance and a reasonably good screen. And the touchless controls aren’t just the icing on the cake; they are the cake.
XDA Breakdown:
Root? RockMyMoto.
Recovery? Yes.
Unlockable? RockMyMoto
Widespread Aftermarket Developer Support? Not at the moment. A few source-built ROMs including official PAC nightlies, but no official PA, Omni, or CM for the device.
Multiboot? No.
PHABLETS
Samsung Galaxy Note 3http://www.xda-developers.com/wp-content/uploads/2013/12/samsung-galaxy-note-3-300x236.jpg
$645 unlocked (or under $300 with carrier subsidy). Also available starting at $550 on Swappa. When you need to do more, you can with various Samsung S Pen apps.
The Galaxy Note 3 continues to be the only very large phone that truly offers a “phablet” experience. Rather that simply making a very large phone, Samsung has made a device that is capable of doing fundamentally more than most phones. Now, you need to deal with TouchWiz in order to gain this functionality. But for many, the trade-off is well worth it.
XDA Breakdown:
Root? Yes.
Recovery? Yes.
Widespread Aftermarket Developer Support? Yes, but depends on variant.
Multiboot? No.
Sony Xperia Z Ultra
$520 unlocked. Also available starting at $430 on Swappa.
Although it lacks the S Pen functionality of Samsung’s Galaxy Note 3, the Xperia Z Ultra has one added trick up its sleeve: the recently launched Z Ultra Google Play edition. Due to their hardware similarities, it’s not unreasonable to assume that the GPe ROM will be ported over to the standard device, and that’s good news for Z Ultra owners everywhere!
OLDER FLAGSHIP DEVICES
HTC One
$540 unlocked. Also starting at $329 on Swappa.
HTC Started the year off strong with the HTC One. When we covered the launch back in March, we were quite impressed with the device’s stunning screen, speedy processor, tasteful skin, and beautiful build quality. While the phone is no longer one of the fastest devices available, it is still a powerful device for those looking for a sculpted work of art, rather than the bleeding edge in mobile tech.
XDA Breakdown:
Root? Yes.
Recovery? Yes.
Unlockable? Yes.
Widespread Aftermarket Developer Support? Official OmniROM and CyanogenMod, depending on variant.
Multiboot? Yes!
Google Edition Conversion? Yes!
Samsung Galaxy S 4
$560 unlocked. Also starting at $380 on Swappa.
While it’s starting to fall behind in the specs war compared to newer devices, Samsung’s Galaxy S 4 still packs quite a bit of power, a fantastic screen, great battery life, a nice camera, and expandable storage. Furthermore, the device has a healthy development community with more mods, tweaks, ROMs, and kernels than you can shake a stick at.
XDA Breakdown:
Root? Yes.
Recovery? Yes.
Widespread Aftermarket Developer Support? Varies depending on variant, but generally yes.
Oppo Find 5
$500 unlocked. Also starting at $310 on Swappa.
The Oppo Find 5 is a great device with a fantastic camera and impeccable screen. Its Snapdragon S4 Pro is no longer the fastest SoC available, but it can still breeze through most tasks without any slowdown. Finally, Oppo’s developer-friendly attitude earns it a place among all the heavyweights.
XDA Breakdown:
Root? Yes.
Recovery? Yes.
Widespread Aftermarket Developer Support? Official AOKP, Paranoid Android, and CyanogenMod.
On a Budget
Moto G
$179 (8 GB) or $199 (16 GB) direct.
This one’s simple. If you’ve only got $200 or less, and you want an unlocked phone, get a Moto G. It’s a solid phone at an utterly fantastic price. Developer support isn’t quite there yet, but with such good price/performance, we can’t imagine it being too far.
XDA Breakdown:
Root? Yes.
Recovery? Yes.
Unlockable? Through Motorola.
Widespread Aftermarket Developer Support? better than galaxy ace-i's
CREDITS: xda holiday guide 2013
rese
Are you sure you don't want to credit also BroadCom for the knowledge they gave you and us? They teached us to never buy a BCM-powered device again (except for a Raspberry Pi maybe :fingercrossed: )
Reserved, just in case
Sent from my Nokia 3310 using Tapatalk
Giupy 99 said:
Are you sure you don't want to credit also BroadCom for the knowledge they gave you and us? They teached us to never buy a BCM-powered device again (except for a Raspberry Pi maybe :fingercrossed: )
Reserved, just in case
Sent from my Nokia 3310 using Tapatalk
Click to expand...
Click to collapse
Sure buddy .. lol
But i believe Dev support is because Moto G just arrived, we haven't seen much of what it can do until now. I believe it and Moto X are the best by relation price/benefit.
Note 3 the Best!
mathm2013 said:
But i believe Dev support is because Moto G just arrived, we haven't seen much of what it can do until now. I believe it and Moto X are the best by relation price/benefit.
Click to expand...
Click to collapse
Believe me ,after Moto-G releases worldwide it might have Good developer support .. It might even have official support from CM,PAC,OmNI dev's ..
Motorola released the source code of Moto-x ,day before yesterday ..so in near future ,they might be releasing Moto-G source code along with device drivers ..
I like this phone!
Hey!
I like cooperve. Fact that there are complications made me to think more about all android. Right now I'm not so stupid as many people in supper-device-support-forum who are asking for any stupid thing. Compiling your own kernel because You want more freqs and ext2 (not ext4), and trying to trick device (Samsung reported 384MB RAM, CONFIG_CMDLINE uses 362MB, we have 289MB. I've increased CMDLINE to 364MB and nearly bricked device, but OS reported me 291MB Ha! ["?CONFIG_?"CMDLINE_FORCE=y]). Creating your own ROM (ROM created by someone else but You must customize it before flash). But I understand. I've bought this device for fun (I'm doing only this with all electronical equipment [even fridge]) and You don't must like this device.
My next step wil be GTAB2 + XPERIAZ.
misha1996 said:
Note 3 the Best!
Click to expand...
Click to collapse
One can buy it only if you enough money in your Hands ..
640 dollars buddy
Mr.Gentleman said:
One can buy it only if you enough money in your Hands ..
640 dollars buddy
Click to expand...
Click to collapse
Not only money. Gotta see if it fits on your hand
Prestigio's phones are good with dual sim cards and big displays. Prestigio Website
Flamestorm said:
Prestigio's phones are good with dual sim cards and big displays. Prestigio Website
Click to expand...
Click to collapse
Oh ! Great ! ..
Their are many many vendors which produce Good device at a reliable price but still the developer support will take us back ..
Their is a Local company in India called "MicroMax" this company actually became the whistle blower after releasing it's Canvas Device Family .. Even top companies like samsung,hTc faced tuff competition from this Canvas family device's ..But still this Great Company is called as "Re-Branded chinese device" (atleast refered as, by iamareebjamal) .. In similiar way every local company is called as "Chinese device" ,though it ain't ..
And great news guys ..tech Gaint Nokia is going to release its first Android device .. If they do,then samsung will be living in shadows of Nokia as it was some 4-6 years ago ..
Mr.Gentleman said:
And great news guys ..tech Gaint Nokia is going to release its first Android device .. If they do,then samsung will be living in shadows of Nokia as it was some 4-6 years ago ..
Click to expand...
Click to collapse
dont excite bro. i was heard that a while ago but now ive heard a new info about that nokia isnt gonna release an android device they will go with wp.
Galaxy Pop Plus'ımdan Tapatalk 2 ile gönderildi.
Nokia Normandy was supposed to be the first Nokia Android device. It was code name for a device on which they were testing Android. But I don't know what is going to happen that changes the mind of a company which refused Android on the first hand, specially, after it's under Microsoft's control
iamareebjamal said:
Nokia Normandy was supposed to be the first Nokia Android device. It was code name for a device on which they were testing Android. But I don't know what is going to happen that changes the mind of a company which refused Android on the first hand, specially, after it's under Microsoft's control
Click to expand...
Click to collapse
Anyway Nokia took Wrong choice .They wanted to bring something out-of-box by taking Windows as their primary OS ... Unfortunately they hit the wrong store .
Though Microsoft's Metro UI and lumia family is good , they lost in options of Customization and in the Availability of Apps . ..
Anyway Jolla is Quite Awesome.. (must check it out ! )
Mr.Gentleman said:
Anyway Jolla is Quite Awesome.. (must check it out ! )
Click to expand...
Click to collapse
yeah sailfish os is quite awesome i loved it but i think its expensive for that hardware. i would buy it if its 300€
Galaxy Pop Plus'ımdan Tapatalk 2 ile gönderildi.
Loved The second Post mahn. GG ^_^
Sent from my GT-S5830i using Tapatalk 2
Lalit Patil said:
Loved The second Post mahn. GG ^_^
Sent from my GT-S5830i using Tapatalk 2
Click to expand...
Click to collapse
Glad you like it .
Sooner or later i'm gonna add about best Tablet's in #3 post
For those who absolutely want an Android Lumia, there's a phone called "Nokia N9" which has an OS (MeeGO, the base of Jolla Sailfish) that is based on Linux. Some devs ported ICS and JB on it, take a look on YouTube
Sent from my Nokia 3310 using Tapatalk

is the project dead?

no updates
diehard2013 said:
no updates
Click to expand...
Click to collapse
Becauase JIDE was dead.
come again
Totally dead. They already give official statement in their Facebook Page
Requiem aeternam dona eis, Domine,
et lux perpetua luceat eis.
JIDE is NOT dead - just targeting enterprises (not ordinary users)
diehard2013 said:
Requiem aeternam dona eis, Domine,
et lux perpetua luceat eis.
Click to expand...
Click to collapse
JIDE is moving FROM ordinary users to enterprises; and I don't exactly blame them.
Let's be honest with ourselves - the two biggest problems RemixOS products face (all of them) is that they aim (literally) too high in the Android-on-PC subspace (two ways they aim too high - they are based on MM - not KK or L, which is where all the action is, and the reality is that - for precisely that reason - RemixOS is STILL too "hefty" for the Android-emulator space (which is still where the action remains, as opposed to the replacement-for-Windows space). If you have 16 GB of RAM, you CAN run RemixOS alongside Windows - however, why would you, unless there is a specific app/game that you want to run that requires MM or N - and even then, it's STILL easier to run that game or app on a device. The only folks that are going to be looking at that niche use (and the reality is that it IS a niche use) are enterprises and corporate users - not the everyday user. And, if anything, the availability of cheaper N devices (such as the launch of Lnovo's Tab 3 Essential line - which is now based on a commodity-designed Qualcomm SoC - as opposed to the original Mediatek SoC that Lenovo started with) has created a reliable easier-to-target SoC without the problems of Mediatek (at least for now, Qualcomm is NOT repeating the errors that got them in hot water in the networking space - the same errors that got Mediatek in hot water in the SoC space); basically, Qualcomm learned from the mistake they made in networking - the same mistake that the competition did NOT learn (and instead repeated). Result - the complaint that folks are making about Qualcomm is that they are a quasi-monopoly; however, how is it Qualcomm's fault that it learned from the mistakes that IT made elsewhere - and their competition largely didn't? Unless Qualcomm makes a similar egregious error to the one that Mediatek made (or that Qualcomm itself made in networking) I don't see them going anywhere - especially with other ARM licensees and competitors shooting themselves in one or both feet.
If you are in the emulation space (running alongside Windows), there is next to zero reason you would want an MM-based emulator - and especially if you have less than 16GB of system RAM. (I found myself replacing RemixOS Player with MEMu Player (which is still based on KitKat) after I added a second N-based Android device (ex-VZW Galaxy S7 running in SIMless/tablet mode) to my daily-driver Samsung GNex. Let's be honest - even as a TABLET, the two-year-old Snapdragon-driven S7 is far from a slouch; it's plenty speedy - and without the heavy lifting that phones typically have to do, if anything, it's even faster. Then there is the reality that there aren't many tablets (or phablets, for that matter) that can run N reliably without causing wallet rape (all of seven prior to the return of the Note7 - now the Note7 FE) - and three of those are not only Nexus devices, but are no longer manufactured - Nexus 6 (Motorola), Nexus 7 (ASUS) and Nexus 9 (HTC). The other four? Shield K1 (nVidia), Shield Original tablet (also nVidia), Galaxy Tab S2 (Samsung) and Pixel C. The vote in terms of emulators of the Android sort remains low-end/cheap - not the higher end stuff that JIDE built.
PGHammer said:
JIDE is moving FROM ordinary users to enterprises; and I don't exactly blame them.
Let's be honest with ourselves - the two biggest problems RemixOS products face (all of them) is that they aim (literally) too high in the Android-on-PC subspace (two ways they aim too high - they are based on MM - not KK or L, which is where all the action is, and the reality is that - for precisely that reason - RemixOS is STILL too "hefty" for the Android-emulator space (which is still where the action remains, as opposed to the replacement-for-Windows space). If you have 16 GB of RAM, you CAN run RemixOS alongside Windows - however, why would you, unless there is a specific app/game that you want to run that requires MM or N - and even then, it's STILL easier to run that game or app on a device. The only folks that are going to be looking at that niche use (and the reality is that it IS a niche use) are enterprises and corporate users - not the everyday user. And, if anything, the availability of cheaper N devices (such as the launch of Lnovo's Tab 3 Essential line - which is now based on a commodity-designed Qualcomm SoC - as opposed to the original Mediatek SoC that Lenovo started with) has created a reliable easier-to-target SoC without the problems of Mediatek (at least for now, Qualcomm is NOT repeating the errors that got them in hot water in the networking space - the same errors that got Mediatek in hot water in the SoC space); basically, Qualcomm learned from the mistake they made in networking - the same mistake that the competition did NOT learn (and instead repeated). Result - the complaint that folks are making about Qualcomm is that they are a quasi-monopoly; however, how is it Qualcomm's fault that it learned from the mistakes that IT made elsewhere - and their competition largely didn't? Unless Qualcomm makes a similar egregious error to the one that Mediatek made (or that Qualcomm itself made in networking) I don't see them going anywhere - especially with other ARM licensees and competitors shooting themselves in one or both feet.
If you are in the emulation space (running alongside Windows), there is next to zero reason you would want an MM-based emulator - and especially if you have less than 16GB of system RAM. (I found myself replacing RemixOS Player with MEMu Player (which is still based on KitKat) after I added a second N-based Android device (ex-VZW Galaxy S7 running in SIMless/tablet mode) to my daily-driver Samsung GNex. Let's be honest - even as a TABLET, the two-year-old Snapdragon-driven S7 is far from a slouch; it's plenty speedy - and without the heavy lifting that phones typically have to do, if anything, it's even faster. Then there is the reality that there aren't many tablets (or phablets, for that matter) that can run N reliably without causing wallet rape (all of seven prior to the return of the Note7 - now the Note7 FE) - and three of those are not only Nexus devices, but are no longer manufactured - Nexus 6 (Motorola), Nexus 7 (ASUS) and Nexus 9 (HTC). The other four? Shield K1 (nVidia), Shield Original tablet (also nVidia), Galaxy Tab S2 (Samsung) and Pixel C. The vote in terms of emulators of the Android sort remains low-end/cheap - not the higher end stuff that JIDE built.
Click to expand...
Click to collapse
in vino veritas, acta non verba..
diehard2013 said:
in vino veritas, acta non verba..
Click to expand...
Click to collapse
Just a thought here: If Jide had any thoughts about not being committed to this project, why did they even bother collaborating with the Android-x86 project in the first place? And why did they wait so long, between the latest releases of Remix OS (mid-November) and the official announcement?
With Remix OS for PC/Windows out of the picture (and with it, gone is perhaps one of the best--if not THE best--graphic environments for an Android-based OS), which of the remaining Android-based operating systems would you recommend? Right now, I'm giving consideration to either Phoenix or BlueStacks. If I had to choose, I'd be tempted to go with BlueStacks, because it has its own front end (or whatever it is called, which Remix OS had in Remix OS Player) which runs inside Win7/10; while for Phoenix (which has the better-looking graphic environment), I'd probably have to use VirtualBox or VMware, since as of now I don't know if they (or anyone else) developed a front end for this OS to run in a window inside Win7/10.
CookyMonzta said:
Just a thought here: If Jide had any thoughts about not being committed to this project, why did they even bother collaborating with the Android-x86 project in the first place? And why did they wait so long, between the latest releases of Remix OS (mid-November) and the official announcement?
With Remix OS for PC/Windows out of the picture (and with it, gone is perhaps one of the best--if not THE best--graphic environments for an Android-based OS), which of the remaining Android-based operating systems would you recommend? Right now, I'm giving consideration to either Phoenix or BlueStacks. If I had to choose, I'd be tempted to go with BlueStacks, because it has its own front end (or whatever it is called, which Remix OS had in Remix OS Player) which runs inside Win7/10; while for Phoenix (which has the better-looking graphic environment), I'd probably have to use VirtualBox or VMware, since as of now I don't know if they (or anyone else) developed a front end for this OS to run in a window inside Win7/10.
Click to expand...
Click to collapse
It's not that anything necessarily is WRONG with RemixOS - nobody has said that (not me - or anyone else, for that matter) - it's simply overkill for what most users want. It's like the market for high-end GPUs (without the price factor); it's still a niche market. As good a graphical environment as RemixOS - and Marshmallow itself, for that matter - is, why have things moved north (on actual Android devices) and stayed south (on Windows-based Android emulators)?
As the default OS (as is the case with devices), unless you are talking the low and cheap end, N is the new JellyBean - not MM. (Note that instead of doing OTAs for the existing J3 - which is running MM - Samsung chose a hardware refresh instead; this is despite the J3 pre-refresh being barely two years old - and not even that in North America,) As an emulator core (alongside or within Windows), the tendency is STILL to prefer lightweight emulators - which still means KitKat or JellyBean - primarily so Windows (the core OS) can keep most of the resources itself. RemixOS Player didn't require vmWare OR Oracle VirtualBox - just like most of the KK or JB-based emulators; hence none of them are shackled to HAXM. I RAN RemixOS Player because I could take higher-end Android games to it - which wasn't - and still isn't - the case for most emulators - with OR without HAXM. However, gaining that S7 did away with my own need for a high-end emulator. (Remember, the S7 - while not shipping with N - instead, it shipped with MM - now can be blanked and factory-type N-ified using nothing more complicated than either Odin or Heimdall.)
What is further trouble for JIDE is that N is expanding at the low-end. I mentioned earlier Samsung's J3 refresh (which is now N-based - not the MM of the previous version); the same is true of Lenovo's Tab 3 Essential - a refresh of the earlier Tab 2 series of tablets and phablets. Unlike the Tab 2 (which started at KK and went only to L - with only the phablets going beyond L with community ROMs, and typically in languages OTHER than English), the Tab 3 Essential has changed SoCs from MediaTek (MTK) to Qualcomm - they also ship with N out of the box. Amazingly, the price tags went nowhere compared to the MTK predecessors - even the largest of the new line is BARELY $100 from Amazon - including shipping for non-Prime customers. With N for cheap, whither RemixOS? (Basically, RemixOS is being made moot by N on devices - not nice, but there it is.)
What are you guys transitioning to? Any suggestion for someone who was looking into purchasing another Jide solution?
KingdomMan3 said:
What are you guys transitioning to? Any suggestion for someone who was looking into purchasing another Jide solution?
Click to expand...
Click to collapse
You mean SW or HE'S?
anyone still usinng it?
hi guys. anyone still using it? is it stable enough? im thinking to install it on my pixel c tablet
These are project for which
---------- Post added at 02:56 AM ---------- Previous post was at 02:54 AM ----------
Give me a link pixel experience Android p for resume 4x
Hey guys,
I'm planning going back to Remix OS 3.0 (MM) on my Pixel C since AOSP really sucks for a lapotp like tablet like the Pixel C.
But I am worried about Security... Is it possible to use Antivir software like Avast to compensate the missing security updates?
If yes, can you recommend me an antivir app?

I think we should have opened a discussion on some important points,

I think we should have opened a discussion on some important points,
1 adaptive storage, which I will draw on some specific model as our most has active others such as moto one, G6, and G7, motorcycle c, motorcycle and, we have to see if there is any limitation of hardware or software only thing, because this speech that Google does not support or that the cards do not have enough quality, not real, because every month we have models released with updated with this support.
2, dp vs dpi = 480 standard and high for this screen size, the base of android and 160, then it means that we have a base x3 of scale, this is legal for a worse point on the other, as this increases a lot more quality, the more the information displayed. You gain large, borderless icons plus loses in detail. Solution likely to set screen resolution lower than 540p, to have equibrio between size and quantity, or @ 1080p to have full amount of pixel there is screen, but if it is in stock has to activate a third party lacucher, because Motorola laucher does not support this pattern .
3, gpu is clock different from the specified, because it was to have maxima clock of 850mhz, more in the last version that I did read in the android with rom stock it was in setada the clock max 700mhz, more main problem was that even taking Max to 700mhz, in a good part of game and app it gets 450 MHz with low FPS content, even if it is not in the FPS limit of the game or application, it did not raise clock to its maximum .. probable solution for who has root, exchange governor gpu using kernel auditor, by order or by performance
4, this is less important and only one more doubt, mixed with indignation,. Because Samsung and some other privileged manufacturers can use 32bit android on their handset, which infinitely lighter and less consumer ram. What the 64bit, which Google has been forcing developer to use since the Android ..
It seems to prank some more Samsung with snapdragon 425 and 2gb of ram and HD + screen with 32bit android has usability, and multitasking better than our device that has 630 and 3gb of ram more with Android 64bit.
Mano has 5 years I see Google saying that there is no more Android 32bit, even so every year there is cell phone with input clip using Android 32bit fighting from equal to equal with Android intermediate with Android 64bit.
And I'm sorry if I said some nonsense, I do not understand much about development, but I had several devices and always made modifications, and always following the tropics and the developers
Ermes.mt/brasil said:
I think we should have opened a discussion on some important points,
And I'm sorry if I said some nonsense, I do not understand much about development, but I had several devices and always made modifications, and always following the tropics and the developers
Click to expand...
Click to collapse
So.... What are you trying to accomplish with this "discussion" that is probably already addressed in another thread??
jbaumert said:
So.... What are you trying to accomplish with this "discussion" that is probably already addressed in another thread??
Click to expand...
Click to collapse
yes and no, yes, because all the tropics in general seek 3 things (support, features or performance), and I'm approaching this three point, and yes! and discussion then everyone is welcome to try on a chair to have a coffee and speak their point of view .. #not much sound on this device and if we do not talk and we work together on it, we will not get a survival of it

[ROM][13][UNOFFICIAL] LineageOS 20.0 for Redmi 9A (Garden)

/*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, We will laugh at you.
* It is your fault because you chose to do all the modifications on your device.
* Remember projects like these and the work done on them is a hobby to the
* contributors and the team members, no one is working for you nor is getting paid for it
* have some respect for the work done by them since it is done purely on interest or a hobby
*/
Click to expand...
Click to collapse
WHAT WORKS?:
-Wi-Fi - vendor q needed
-BlueTooth - vendor q needed
-RIL
-GPS
-- WHAT DOESN'T WORK? --
Smoothness, thats it
if there are more bugs please report them​Official LineageOS Site: lineageos.org​H O W T O C L E A N I N S T A L L​
1. Use Reccomended recovery (OrangeFox)
2. Wipe Cache & Dalvik data
3. and Format Data
4. Flash vendor Q
5. Flash ROM
6. Reboot
(optional) 7. After Configuring (or turning on the OS) install GAPPS in recovery.
Hope it works
DOWNLOAD LINKS:
ROM
VENDOR Q
SOURCE CODE: S O U R C E
hej maksieku!
txpiq said:
hej maksieku!
Click to expand...
Click to collapse
Hello! If you like my work, please rate it. Thanks!
All i know is that this phone is not very stable , in android 12 onwards.
So i wouldn't use it, even MIUI is stuck in Android 11 for this device. They have it in A11 for a good reason.
jdd1996 said:
All i know is that this phone is not very stable , in android 12 onwards.
So i wouldn't use it, even MIUI is stuck in Android 11 for this device. They have it in A11 for a good reason.
Click to expand...
Click to collapse
I just found out yesterday that Xiaomi isn't updating it to Android 12, which brought me here, to look up for new ROMs. You said "they have it in A11 for a good reason", referring to it not being very stable. I'm curious. Why do you say so?
glofern97 said:
I just found out yesterday that Xiaomi isn't updating it to Android 12, which brought me here, to look up for new ROMs. You said "they have it in A11 for a good reason", referring to it not being very stable. I'm curious. Why do you say so?
Click to expand...
Click to collapse
Bare with me for 5-12 mins. You or may not agree with me, but it works like this in many ocassions.
Let's say i have a AMD A-5200 CPU , which is a cpu from 2013.
OR - Let's say i have a Intel Pentium 4 P4 - 2.0Ghz from the year 2008
OK? ok the example starts with 2 weak cpu's from ANCIENT TIMES now...
What OS can/would you install in those CPU's?
A Pentium 4 2.0 has 400 MHz. EACH 100mhz translates more or less to 5-15 khz of electrical power the cpu needs to process the information, the data.
Since its so weak, in windows10 or 11 when you open microsoft word 2020 or open office, it will LAG! because the overlay/background OS' is already consuming around 200ghz, all those 400 mhz of cpu power
(Animations, and Cortana, and simply the theme of the wallpaper, and the Registry, and Services, AND even USB peripherical drivers ARE ALL CONSUMING CPU POWER AT ONCE, and at high demands because the OS' Requests it with its kernel )
Since the core memory is so weak! you will most likely be installing windows xp or windows 7 if you're lucky !
BUT if you install windows 11 or 10, you will face unconsistent algorythmical graphic/memory processes
(This is what we call lag) core processing and clock problems, " MEMORY LEAKING problems " or over saturations of the system.
A CPU CONTAINS something called MMU's Memory management unit's, well they start to become obsolete unless you reball and resolder the cpu,
SAME applies if i tried to install LATEST FEDORA OR ARCH LINUX OS's , right? WHY would there be problems?
Because kernels are being update to be version 6.2 today, and that demands a constant clock and processing.
For the AMD A6-5200, Linux and windows 7 would be good options, but for the Pentium 4 2.0ghz of 2008 only windows 7 and Linux with low kernel version of 5 or 5.2 are acceptable.
So these techs at xiomi think similarly, on top of that the Storage of the OS increases, the RAM demand, CPU demand increases with each version, so when you boot your game (mostly the demanding apps) when you boot your designer pen drawing app, IT WILL LAG , perhaps not noticeably for the user in android 12 or 13, BUT AS VERSIONS WILL CONTINUE TO PASS, in Android 13-14 , we will see how this Xiomi Redmi 9A , ITS PROCESSOR and its weak 2gb will not be enough to process/render the datas and assets of the newest OS's
hahaha all that to say, sorry i got inspired " They need to optimize the OS's in the future maybe then we may be able to install newer OS's on older phones " Its like putting android 12 on an Android 8.1 Oreo phone, you understand? First of all an error will prompt saying " Allocating space of data : Error insufficient Space " AND EVEN IF YOU HAD THE SPACE? Lets say we hack the phone and give it 64gb of memory, and give it perfect partitions. ONCE IT BOOTS It will actually have problems, lag, while using the demanding apps.
The newer OS's Versions request mooore Ram , moore CPU powa, more storage space that redmi 9a doesn't have! uhum !
why? cuz the functions actually got smarter uhum !
Dont you see how newer phones have 64 gb of space all by default, tecnology thinks to advance and milk people over and over. They could add 200 gb of space, but no... (Lets wait until its necessary so we can reap the people)
One day an OS SYSTEM will be 25-35 and even 45GB SIZE ! AND THAT DAY YOUR 64 Gb will look like its too small, so you will need to buy the 120-200gb version phone.
Our PC motherboards, cpu's, phones all get old and so obsolete with time, all we can do is recycle them, melt them and make a new modern one, resolder, reball them. That's just how the modern industry works today. You cant just hope to upgrade your old junk/Hardware with the latest Software. One day we will get Android 15, A17 too its already planned ! and this phone will not run it, forget it , hoperfully we will be using opensource Linux OS's even more optimized tweaked than what google and these companies can do in the future. NOT BASED on Android 15 or 17.
You cant just hope to put the new hotdog on the old bread. At least not with the current technology/society
Please, can anyone who's installed this ROM report on whether or not manual camera controls (technically referred to as camera2 API) are available on this ROM either while using a 3rd party camera app (like Manual Camera, Open Camera, etc) or the LOS camera.
I'm considering going from MIUI 12.5 on Redmi 9A to this ROM.
Thanks.
jdd1996 said:
Bare with me for 5-12 mins. You or may not agree with me, but it works like this in many ocassions.
Let's say i have a AMD A-5200 CPU , which is a cpu from 2013.
OR - Let's say i have a Intel Pentium 4 P4 - 2.0Ghz from the year 2008
OK? ok the example starts with 2 weak cpu's from ANCIENT TIMES now...
What OS can/would you install in those CPU's?
A Pentium 4 2.0 has 400 MHz. EACH 100mhz translates more or less to 5-15 khz of electrical power the cpu needs to process the information, the data.
Since its so weak, in windows10 or 11 when you open microsoft word 2020 or open office, it will LAG! because the overlay/background OS' is already consuming around 200ghz, all those 400 mhz of cpu power
(Animations, and Cortana, and simply the theme of the wallpaper, and the Registry, and Services, AND even USB peripherical drivers ARE ALL CONSUMING CPU POWER AT ONCE, and at high demands because the OS' Requests it with its kernel )
Since the core memory is so weak! you will most likely be installing windows xp or windows 7 if you're lucky !
BUT if you install windows 11 or 10, you will face unconsistent algorythmical graphic/memory processes
(This is what we call lag) core processing and clock problems, " MEMORY LEAKING problems " or over saturations of the system.
A CPU CONTAINS something called MMU's Memory management unit's, well they start to become obsolete unless you reball and resolder the cpu,
SAME applies if i tried to install LATEST FEDORA OR ARCH LINUX OS's , right? WHY would there be problems?
Because kernels are being update to be version 6.2 today, and that demands a constant clock and processing.
For the AMD A6-5200, Linux and windows 7 would be good options, but for the Pentium 4 2.0ghz of 2008 only windows 7 and Linux with low kernel version of 5 or 5.2 are acceptable.
So these techs at xiomi think similarly, on top of that the Storage of the OS increases, the RAM demand, CPU demand increases with each version, so when you boot your game (mostly the demanding apps) when you boot your designer pen drawing app, IT WILL LAG , perhaps not noticeably for the user in android 12 or 13, BUT AS VERSIONS WILL CONTINUE TO PASS, in Android 13-14 , we will see how this Xiomi Redmi 9A , ITS PROCESSOR and its weak 2gb will not be enough to process/render the datas and assets of the newest OS's
hahaha all that to say, sorry i got inspired " They need to optimize the OS's in the future maybe then we may be able to install newer OS's on older phones " Its like putting android 12 on an Android 8.1 Oreo phone, you understand? First of all an error will prompt saying " Allocating space of data : Error insufficient Space " AND EVEN IF YOU HAD THE SPACE? Lets say we hack the phone and give it 64gb of memory, and give it perfect partitions. ONCE IT BOOTS It will actually have problems, lag, while using the demanding apps.
The newer OS's Versions request mooore Ram , moore CPU powa, more storage space that redmi 9a doesn't have! uhum !
why? cuz the functions actually got smarter uhum !
Dont you see how newer phones have 64 gb of space all by default, tecnology thinks to advance and milk people over and over. They could add 200 gb of space, but no... (Lets wait until its necessary so we can reap the people)
One day an OS SYSTEM will be 25-35 and even 45GB SIZE ! AND THAT DAY YOUR 64 Gb will look like its too small, so you will need to buy the 120-200gb version phone.
Our PC motherboards, cpu's, phones all get old and so obsolete with time, all we can do is recycle them, melt them and make a new modern one, resolder, reball them. That's just how the modern industry works today. You cant just hope to upgrade your old junk/Hardware with the latest Software. One day we will get Android 15, A17 too its already planned ! and this phone will not run it, forget it , hoperfully we will be using opensource Linux OS's even more optimized tweaked than what google and these companies can do in the future. NOT BASED on Android 15 or 17.
You cant just hope to put the new hotdog on the old bread. At least not with the current technology/society
Click to expand...
Click to collapse
I appreciate your detailed response. So the bottom line is that it's not advisable to put a Ferrari's engine in a Beetle. Also, about what you said, a future smartphone taking 45 GB of HD for system space is wild lol
I bought a Xiaomi Redmi 9A last month and I didn't know it could be so laggy. It works fine for the most part, but there are times I see some noticeable lag, probably because of the reason you mentioned, i.e. A11 (MIUI 12.5) is consuming a lot of its spare 2 GB RAM, though I think this is probably more caused by MIUI and its bloatware than purely Android 11 alone. I have Lineage OS 19 (which is A12) installed on a Galaxy S6, whose hardware specs are somewhat similar to Redmi 9A, and it doesn't cause any noticeable lag. I suspect that installing A11/A12 (but not MIUI!) on Redmi 9A may increase its performance, since it doesn't come with bloatware. What do you think?
glofern97 said:
I appreciate your detailed response. So the bottom line is that it's not advisable to put a Ferrari's engine in a Beetle. Also, about what you said, a future smartphone taking 45 GB of HD for system space is wild lol
I bought a Xiaomi Redmi 9A last month and I didn't know it could be so laggy. It works fine for the most part, but there are times I see some noticeable lag, probably because of the reason you mentioned, i.e. A11 (MIUI 12.5) is consuming a lot of its spare 2 GB RAM, though I think this is probably more caused by MIUI and its bloatware than purely Android 11 alone. I have Lineage OS 19 (which is A12) installed on a Galaxy S6, whose hardware specs are somewhat similar to Redmi 9A, and it doesn't cause any noticeable lag. I suspect that installing A11/A12 (but not MIUI!) on Redmi 9A may increase its performance, since it doesn't come with bloatware. What do you think?
Click to expand...
Click to collapse
I correct myself Android 13-14 can run on this phone, we have swap memory, and ways to increase the size of it, today i added 6GB of Swap memory. It makes the phone faster by 15%-20% (That can help to compensate)
But yes, at some point there will be too much size and beef inside a ROM, each linux distro today is 16 gb, they plan to drive Android to have even more functionalities, more compatibility with the pc, a more polished level, the system will get a bit bigger and become sluggish at some point, unless someone does something about it right, thats where the open source developers come in? But by personal experience, i use android since 2012, HTC ONE S, Blu Studio G2 HD, Samsung Galaxy S5 -- the higher you go in Version, the more lag you will encounter for gaming, or daily usage (SPECIALLY IF YOU USE MTK- Mediatek Cpu like this phone has, mtk is very bad compared to snapdragon, and the years of experience have proven it )
For this phone im using Android 11 CRDroid - This is my daily driver
CRDroid v316 GSI (Variant of AOSP-Phh-treble + CRDroid)
You're stuck on MIUI 12.5.4.0 and you cant flash a working custom recovery? You're too lazy or too newbish to build your own? Cant flash any Custom Rom? Well you can just learn how to flash these TREBLE PHH Images, GSI-AOSP based images. Here i...
forum.xda-developers.com
jdd1996 said:
I correct myself Android 13-14 can run on this phone, we have swap memory, and ways to increase the size of it, today i added 6GB of Swap memory. It makes the phone faster by 15%-20% (That can help to compensate)
But yes, at some point there will be too much size and beef inside a ROM, each linux distro today is 16 gb, they plan to drive Android to have even more functionalities, more compatibility with the pc, a more polished level, the system will get a bit bigger and become sluggish at some point, unless someone does something about it right, thats where the open source developers come in? But by personal experience, i use android since 2012, HTC ONE S, Blu Studio G2 HD, Samsung Galaxy S5 -- the higher you go in Version, the more lag you will encounter for gaming, or daily usage (SPECIALLY IF YOU USE MTK- Mediatek Cpu like this phone has, mtk is very bad compared to snapdragon, and the years of experience have proven it )
For this phone im using Android 11 CRDroid - This is my daily driver
CRDroid v316 GSI (Variant of AOSP-Phh-treble + CRDroid)
You're stuck on MIUI 12.5.4.0 and you cant flash a working custom recovery? You're too lazy or too newbish to build your own? Cant flash any Custom Rom? Well you can just learn how to flash these TREBLE PHH Images, GSI-AOSP based images. Here i...
forum.xda-developers.com
Click to expand...
Click to collapse
It seems MediaTek CPU is not only slower in terms of performance, but also hard to work with when intending to use a custom ROM. I haven't found any official release of a custom ROM for this phone model, "dandelion". LineageOS, Pixel Experience and alike websites; none of them list it. Looking up, it seems this is because there's no open-source version of a firmware for MediaTek chipsets. Lesson learnt to stay away from it on my future purchases.
I may try out the custom ROM you shared if I get stressed enough with the lags. Thanks!
glofern97 said:
It seems MediaTek CPU is not only slower in terms of performance, but also hard to work with when intending to use a custom ROM. I haven't found any official release of a custom ROM for this phone model, "dandelion". LineageOS, Pixel Experience and alike websites; none of them list it. Looking up, it seems this is because there's no open-source version of a firmware for MediaTek chipsets. Lesson learnt to stay away from it on my future purchases.
I may try out the custom ROM you shared if I get stressed enough with the lags. Thanks!
Click to expand...
Click to collapse
I love how you said it hahaha , Placing a 2020 Ferrari engine inside a little Bettle or 1998 Ford Fiesta, correct !
It wont fit, or it will have problems, well i come from Android 2.0 , 4.1 , 6.0 marshmellow. I know very well in my old phones i cant flash android 10-11 onwards. Specially because the Internal Memory is of 8 or 16gb , very small.
And because of performance.
Oh yes Xiaomi would never release anything official for Custom Roms hahaha thats like asking the developer to give up on their own creation MIUI ... Which is something i doubt those chinese people can do, they cant even speak proper english. They are all about limiting the user, control their environment, milk them slowly by forcing them to buy many devices, take advantage of their ignorance and bloat their device, polute and make the user feel bad because that makes the client more compulsive, block root with accounts, sell their data, prevent rolling back versions, yet sell at cheap price so that poor people buy us always. Even a Samsung Galaxy S5 from 2015 is faster than this phone and more capable of doing more Linux functions.
It all has a "Chinese" psychology.
There are certainly Roms for mediatek , thats why AOSP Phhusson was released was created too. Mediatek is not only a bit confusing to work with but also Mediatek is simply limited in terms of kernel functions and performance in many devices, yes. Today i can straight forwardly say " Its crap or not so good compared to snapdragon-qualcom " its like comparing AMD GPU with Nvidia right? AMD - Snapdragon are the straight winners for me inside the Linux Kernel. Linux Environment. Nvidia is only good for Windows lately. Right now im trying to create a Regulatory.db , Regulatory.bin , trying to build a new CRDA - Central Regulatory Domain Agent inside this mediatek phone, to increase our wifi range, and its confusing for rookies, indeed. Its like they're telling us in our faces " You cannot change that, thats ilegal " BUT IM A HUMAN BEING I WANNA CHANGE THAT ! i wanna have incredible wifi range, or fry my chip by putting txpower 60 or 30 , who are you to prevent me from doing whatever i want Mediatek or Xiaomi?
ALSO this phone COULD have monitor mode, negated ,they cancelled that with the cpu and the programmed instructions. The kernel, who are you to take away my wifi modes? WHICH HAVE ALWAYS BEEN PRESENT inside ANY Linux Desktop!! So no moral for them to take away functions from the device thats is NEWER.
They basically insulted us, i bought it just to see the insult and now i kinda just play with this phone seeking to fry it or hack it/improve it, i really dont care anymore about what happens to it. But looking forward for the best.
If we do lsmod on the terminal with root. This phone has wmt_chrdev_wifi - wmt_drv which are actually Linux generic conventional names for wifi chips/drivers -- This obfuscated wifi chip/driver name could actually be a
" MT6631 wifi chip " OR " WCN685x " or " mt7615 " either way this chipset could be from 2012-2013, so they placed a 2012 piece on a 2020 phone. The fact that simple commands dont work
mt6357_accdet is actually the name of the IC controller for LED screen and battery.
If we do getprop | grep baseband
The RADIO for SIM CARD, is called LCSH_QOMP1_MT6762_SP (LWCTG_6177M_G)
But everything is so obfuscated and hidden, closed source.
Either way other Older Wifi Chipsets are 2-8 times better than this one. 2014 wifi chip with monitor mode - mt7612 - 5 times stronger. You know why they placed an older chip without mon mode on a new phone? Cuz they know it can get dangerous, but thats not the right approach with us. They messed up big time. They're winning enemies. Witchcraft. They have no idea what HACKING - PROGRAMMING truly means, or how far it can go, once we hack existence and the Soul, we program reality further than the physical and the visual, we're gonna be on the real domain.
jdd1996 said:
I love how you said it hahaha , Placing a 2020 Ferrari engine inside a little Bettle or 1998 Ford Fiesta, correct !
It wont fit, or it will have problems, well i come from Android 2.0 , 4.1 , 6.0 marshmellow. I know very well in my old phones i cant flash android 10-11 onwards. Specially because the Internal Memory is of 8 or 16gb , very small.
And because of performance.
Oh yes Xiaomi would never release anything official for Custom Roms hahaha thats like asking the developer to give up on their own creation MIUI ... Which is something i doubt those chinese people can do, they cant even speak proper english. They are all about limiting the user, control their environment, milk them slowly by forcing them to buy many devices, take advantage of their ignorance and bloat their device, polute and make the user feel bad because that makes the client more compulsive, block root with accounts, sell their data, prevent rolling back versions, yet sell at cheap price so that poor people buy us always. Even a Samsung Galaxy S5 from 2015 is faster than this phone and more capable of doing more Linux functions.
It all has a "Chinese" psychology.
There are certainly Roms for mediatek , thats why AOSP Phhusson was released was created too. Mediatek is not only a bit confusing to work with but also Mediatek is simply limited in terms of kernel functions and performance in many devices, yes. Today i can straight forwardly say " Its crap or not so good compared to snapdragon-qualcom " its like comparing AMD GPU with Nvidia right? AMD - Snapdragon are the straight winners for me inside the Linux Kernel. Linux Environment. Nvidia is only good for Windows lately. Right now im trying to create a Regulatory.db , Regulatory.bin , trying to build a new CRDA - Central Regulatory Domain Agent inside this mediatek phone, to increase our wifi range, and its confusing for rookies, indeed. Its like they're telling us in our faces " You cannot change that, thats ilegal " BUT IM A HUMAN BEING I WANNA CHANGE THAT ! i wanna have incredible wifi range, or fry my chip by putting txpower 60 or 30 , who are you to prevent me from doing whatever i want Mediatek or Xiaomi?
ALSO this phone COULD have monitor mode, negative ,they cancelled that with the cpu and the programmed instructions. The kernel, who are you to take away my wifi modes? WHICH HAVE ALWAYS BEEN PRESENT inside ANY Linux Desktop!! So no moral for them to take away functions from the device thats is NEWER.
They basically insulted us, i bought it just to see the insult and now i kinda just play with this phone seeking to fry it or hack it/improve it, i really dont care anymore about what happens to it. But looking forward for the best.
Click to expand...
Click to collapse
Interesting way to look at it. Seeing phones as a political strategy of customer control and profiting out of their data. I hadn't thought this way, but makes sense lol After all, Chinese government is all about limiting and controlling people...
It seems your use case is different than mine. I bought this phone only because I was needing a dual-chip phone for my daily usage (Galaxy S6 is single chip), and it was on a promotion. I had heard good things of Xiaomi from friends who bought their phones, although they hadn't bought this one model specifically. I would really like to use a custom ROM, but the unofficial ones aren't "bulletproof" for this device, as users have reported some bugs. It's safer to stay in the stock ROM side for the time being
I looked up on this Project Treble. Interesting stuff. They are trying to abstract away the firmware code if I understand it correctly. Does that mean that there's hope for MediaTek devices to get support in the future and work smoothly with A13 custom ROMs?
jdd1996 said:
Samsung Galaxy S5 from 2015 is faster than this phone ....
Click to expand...
Click to collapse
I can confirm that my LG V20 (released in 2016 but purchased in 2021) can run circles around this Redmi 9A (which I also own), granted one is a flagship with 4GB/64GB while the other is entry-level with 2GB/32GB. But I didn't expect the performance gap to be this wide given the years in between. On the Redmi 9A (2GB), multitasking is 99% impossible; lag is terrible (even double tap to wake is 60% a failure due to lag). I'm not a developer, but I think Xiaomi cut too many corners with the storage speed and/or RAM rather than the processor itself. That's why I'm hoping a lighter ROM like this one can help.
MaverickNextDoor said:
I can confirm that my LG V20 (released in 2016 but purchased in 2021) can run circles around this Redmi 9A (which I also own), granted one is a flagship with 4GB/64GB while the other is entry-level with 2GB/32GB. But I didn't expect the performance gap to be this wide given the years in between. On the Redmi 9A (2GB), multitasking is 99% impossible; lag is terrible (even double tap to wake is 60% a failure due to lag). I'm not a developer, but I think Xiaomi cut too many corners with the storage speed and/or RAM rather than the processor itself. That's why I'm hoping a lighter ROM like this one can help.
Click to expand...
Click to collapse
I did some testing yesterday on another phone I have here, a Samsung Galaxy S4, which has 2GB RAM and runs on Lineage OS 18 (A11). It shouldn't be a surprise that this Galaxy S4 does way better multitasking than Redmi 9A.
I compared the usage of RAM for Android System in the Memory Usage settings app, and it turns out that they are roughly using the same amount of RAM. MIUI's use is around 600 MB, whereas Lineage OS is around 500 MB. That is, only 100 MB of difference. From that, one can assume that it's rather the processor usage that sucks: MIUI is probably using more CPU resources to run its "good-looking", yet heavy interface, whereas LineageOS doesn't, since its interface is simpler.
The downside of those older phones is that their battery drains out way faster. Redmi 9A's battery lasts for a whole day with Wi-Fi turned on. That's one upside of this phone
Lets hope for easier kernel installs, low sized and performance optimized roms in the future. I suggest waiting, for Android 14-15. When the projects and batches are out patched, improved, tested, we can then cater. Yes the phone boots at least haha. 2Gb ram, Helio 25 ! arm32_binder64 - A64 bits !
Maksieku.Tech said:
WHAT WORKS?:
-Wi-Fi - vendor q needed
-BlueTooth - vendor q needed
-RIL
-GPS
-- WHAT DOESN'T WORK? --
Smoothness, thats it
if there are more bugs please report them​Official LineageOS Site: lineageos.org​H O W T O C L E A N I N S T A L L​
1. Use Reccomended recovery (OrangeFox)
2. Wipe Cache & Dalvik data
3. and Format Data
4. Flash vendor Q
5. Flash ROM
6. Reboot
(optional) 7. After Configuring (or turning on the OS) install GAPPS in recovery.
Hope it works
DOWNLOAD LINKS:
ROM
VENDOR Q
SOURCE CODE: S O U R C E
Click to expand...
Click to collapse
wich gapps i need to install
AlphaJF972 said:
wich gapps i need to install
Click to expand...
Click to collapse
I used BiTGapps, works perfectly
Maksieku.Tech said:
​ROM
VENDOR Q
SOURCE CODE: S O U R C E
Click to expand...
Click to collapse
Where I can get device tree sources to build it from source?
Want to fix some bugs and rebuild for vendor R

Categories

Resources