Hi
I'm planning to buy out Xperia ZR. Couple of questions are confusing me:
1. Will I be able to root/unlock the bootloader?
2. Will I be able to use custom roms like CyanogenMod, MIUI, XDA-Developer's superior roms etc?
3. As I'm learning android development, will this phone be good if I look at that purpose also?
4. I heard there are some issue with call volume as its lower than others? Is it true?
5. Heating up issue? Is there?
Why I choose this phone over nexus 4 or xperia z?
Same hardware as Nexus 4 but having good camra+water proof body+Better battery life+NFC etc. in the same price.
I know I'll miss the s/w updates..Will I be able to use stock android latest updates on this in case I want to?
Comparing to Xperia Z couple of things are more as in the price of 5K..
Why I came to ask here, Coz if I see under Xperia Z or Nexus 4 there are lots of threads regarding android development custom roms, tweaks...but under ZR, I see a few...
Things are pretty much confusing me...
Please guide me even if I miss anything help me to get a better phone ..
Thanks Alot
I think that if you want to learn about android development, any device will be a good device.
Every device works for learning the basics, and any device have your own issues, so you will have to deal with some issues every now and then...
S_Singh said:
Hi
I'm planning to buy out Xperia ZR. Couple of questions are confusing me:
1. Will I be able to root/unlock the bootloader?
2. Will I be able to use custom roms like CyanogenMod, MIUI, XDA-Developer's superior roms etc?
3. As I'm learning android development, will this phone be good if I look at that purpose also?
4. I heard there are some issue with call volume as its lower than others? Is it true?
5. Heating up issue? Is there?
Why I choose this phone over nexus 4 or xperia z?
Same hardware as Nexus 4 but having good camra+water proof body+Better battery life+NFC etc. in the same price.
I know I'll miss the s/w updates..Will I be able to use stock android latest updates on this in case I want to?
Comparing to Xperia Z couple of things are more as in the price of 5K..
Why I came to ask here, Coz if I see under Xperia Z or Nexus 4 there are lots of threads regarding android development custom roms, tweaks...but under ZR, I see a few...
Things are pretty much confusing me...
Please guide me even if I miss anything help me to get a better phone ..
Thanks Alot
Click to expand...
Click to collapse
1. Yes
2. Yes
3. Yes if you're willing to risk your device
4. Not really. The call volume is loud enough for average person, but not the best in the market of course.
5. It's a waterproof dustproof phone with IP58 rating. Expect some heating issue but it won't be serious from my experience. You can always cool it down with water.
CressKH said:
1. Yes
2. Yes
3. Yes if you're willing to risk your device
4. Not really. The call volume is loud enough for average person, but not the best in the market of course.
5. It's a waterproof dustproof phone with IP58 rating. Expect some heating issue but it won't be serious from my experience. You can always cool it down with water.
Click to expand...
Click to collapse
@CressKH
Thanks alot...
I have a doubt I dont see much developer theard for ZR. I can't see more of Official ROMs from cyan,akop,miui..
please clear me there
Thanks
S_Singh said:
Hi
I'm planning to buy out Xperia ZR. Couple of questions are confusing me:
1. Will I be able to root/unlock the bootloader?
2. Will I be able to use custom roms like CyanogenMod, MIUI, XDA-Developer's superior roms etc?
3. As I'm learning android development, will this phone be good if I look at that purpose also?
4. I heard there are some issue with call volume as its lower than others? Is it true?
5. Heating up issue? Is there?
Why I choose this phone over nexus 4 or xperia z?
Same hardware as Nexus 4 but having good camra+water proof body+Better battery life+NFC etc. in the same price.
I know I'll miss the s/w updates..Will I be able to use stock android latest updates on this in case I want to?
Comparing to Xperia Z couple of things are more as in the price of 5K..
Why I came to ask here, Coz if I see under Xperia Z or Nexus 4 there are lots of threads regarding android development custom roms, tweaks...but under ZR, I see a few...
Things are pretty much confusing me...
Please guide me even if I miss anything help me to get a better phone ..
Thanks Alot
Click to expand...
Click to collapse
Hi,
1. Yes, you will be able to root and unlock the bootloader.
2. This phone has very limited worldwide availability, so very limited dev support too. There are virtually no ROMs for this device save for CM by FXP. That's also why the Xperia ZR forum is under the 'Legacy & Low activity devices' forum.
3. For Android development (both apps & ROMs), the phone should be great. It's basically the same as Xperia Z except for some software changes. If you're learning development and you become good at it, you can contribute to the ZR development forum yourself.
4. I've just got my ZR and haven't put a SIM card in yet, so haven't checked the call volume, but Sony provides a lot of settings to tweak call volume in Settings -> Call settings.
5. Almost every new generation phone gets hot. Unlike PCs, there's no fan heatsink + thermal paste to quickly radiate the heat from the CPU. It has to dissipate from the back of the device, and quad-core CPUs get quite hot during gaming and other CPU intensive tasks. Adding to that, the battery also generates some heat. So it's natural for a high end CPU bearing phone/tablet to get hot. That said, ZR heats up less than Xperia Z from what I know, both having the same processor. I'm guessing this is because of the thicker back on ZR. HTC One, Nexus 4, Samsung Galaxy S4, Nexus 7 all heat up so it's not a deal breaker.
TL;DR -
Custom ROM support - Don't buy ZR, it doesn't have any save for one at the moment. Whether the situation will improve in future, I don't know, but it seems unlikely because of ZRs limited availability. I bought ZR for my dad because custom ROMs and stuff don't matter to him. Regarding upgrades, Sony has already promised to update ZR to 4.3, and they might also update it to the next version too. For that we'll have to wait and see.
Excluding ROM support, there's absolutely no reason not to buy ZR. Compared to Z, the smaller 4.55" 720p screen actually contributes to battery life as there's slightly less backlight area + the GPU has to power far less pixels than a 1080p screen (less that half the number), and the screen clarity is great because of the smaller size (greater pixel density than a 5" 720p screen for example). You really can't make out the difference between 720p and 1080p screens at the normal distance you hold your phone at while using it. Only if you look very, very closely. So the added battery life advantage is a bonus. The battery is also removable, so you can keep a spare with you to swap immediately if you ever need to do that, and even when the battery goes bad you can easily replace it with a new one yourself. This phone also has a higher water-proof rating, and feels very sturdy compared to the glass backed Xperia Z.
The only real disadvantages of the ZR compared to Z are the much lower resolution front facing camera (but then again most video calling apps don't do HD and therefore don't make use of a high-res camera), and 8GB internal storage instead of 16GB. That might be a problem if you install a lot of games and the phone doesn't allow to move them to a microSD card. I'm not sure if it allows that or not, so you'll have to check with others.
If you want ROM support, buy Nexus 4 or Xperia ZR. They have PLENTY of ROMs. If you don't care about that so much, you can't go wrong with this phone. You'll also get at least Android 4.3 officially by Sony, if not the next version too.
Hope that helped.
S_Singh said:
@CressKH
Thanks alot...
I have a doubt I dont see much developer theard for ZR. I can't see more of Official ROMs from cyan,akop,miui..
please clear me there
Thanks
Click to expand...
Click to collapse
As you can see, XZR is currently still in Low Activity Devices.
I think primarily it's because the fact that it's the 3rd sibling in Xperia Z series.
People are just happy with Z or ZL, or fed up with the releases.
Nevertheless, it offers much features that Z or ZL can't compare with, and that's why I chose it.
ZR is good for smart phone user,
Nexus family is good for rom tester.
yes fellas....
finally considering all the aspects I got it > Xperia ZR...
excited to test it....will do all type of test for what it stands for...
Thanks for your advices
S_Singh said:
yes fellas....
finally considering all the aspects I got it > Xperia ZR...
excited to test it....will do all type of test for what it stands for...
Thanks for your advices
Click to expand...
Click to collapse
Haha, congrats! First thing I did was dunk it in a bowl of water. :good:
Be careful. My last phone wasn't water resistant and I had to fight hard with Sony to get it replaced.
Sent from my C5502 using Tapatalk 4
Help!
I am also planning to buy Xperia ZR but my only concern is Call Recording feature. Will any developer work on any custom rom for xr?? Or the support will be less?? SHould I go for S4 then? (But, I dislike S4's design).. Pls. guide..
techie_vintage said:
I am also planning to buy Xperia ZR but my only concern is Call Recording feature. Will any developer work on any custom rom for xr?? Or the support will be less?? SHould I go for S4 then? (But, I dislike S4's design).. Pls. guide..
Click to expand...
Click to collapse
Cyanogenmod and FXP guys are already doing great job for our phones,so yes there is an active developement.Go for the ZR,its great phone. (S4 sux a..s for me too )
techie_vintage said:
I am also planning to buy Xperia ZR but my only concern is Call Recording feature. Will any developer work on any custom rom for xr?? Or the support will be less?? SHould I go for S4 then? (But, I dislike S4's design).. Pls. guide..
Click to expand...
Click to collapse
I use acr and it records my calls perfectly, even on Bluetooth.
Sent from my C5502 using Tapatalk 4
djpeesh said:
I use acr and it records my calls perfectly, even on Bluetooth.
Sent from my C5502 using Tapatalk 4
Click to expand...
Click to collapse
is this soft available on google play? What is it's full name? Can u pls. Send a sample clip of d rec?? Pls..
Here's a link to the software. Will update a clip soon. Btw, I bought the premium version that uploads the recordings to Google drive.
https://play.google.com/store/apps/details?id=com.nll.acr
Sent from my C5502 using Tapatalk 4
Hi guys.. right now I am about to buy a new phone... SP comes into my consideration and i find it pretty cool and powerful.. Though.. yesterday I found out that there is also P6 in the offer... What would you recommend ? I am probably going for the SP, but P6 has got 4 cores. Does it make that much of a difference ?
Personally i dont know anything about P6. So my recommendation is SP. Go For SP.. But while purchasing pls check one main thing in SP. Touch problem while Charging. U cant use ur phone while Charging.. But new phones doesnot have that problem i think. Any way make sure at the first day of the Purchase...
And also put ur phone in a flat surface and then use it.. That also a famous SP problem.. So pls check both of this two problems first..
jumptoin said:
Hi guys.. right now I am about to buy a new phone... SP comes into my consideration and i find it pretty cool and powerful.. Though.. yesterday I found out that there is also P6 in the offer... What would you recommend ? I am probably going for the SP, but P6 has got 4 cores. Does it make that much of a difference ?
Click to expand...
Click to collapse
galaxy s3 has 4 cores and in benchmark the SP is much better then S3 with 4 cores. Also Xperia sp has 4g (LTE) better battery and Andreno 320 GPU also is best gpu 4 playing games... i think xperia sp is the right choice..
Sorry for english (not my native language)
Its not the ammount of cores that tells you if the performance is high or not. It is the overall feeling of a device.
I've tested both the SP and P6 and I find the SP more suiteble for me.
Reason:
- UI: I dont like the UI of huawei
- GPU: Adreno 320 is very powerfull
- CPU: Cores and speed dont tell everything
Things the SP has:
-Notificatio ledbar
- Bluetooth 4.0
- 4G (LTE)
- NFC
Things the P6 has:
- Wireless charging
- 2GB RAM
Go to the website of sony and huawei and compare the features and specs. Dont use comparison websites because not all the websites have the correct specs.
Also go to a store and try both phones
Has P6 a HDR Camera?
heross said:
Has P6 a HDR Camera?
Click to expand...
Click to collapse
Yes but the SP too
The SP's 2 cores have a higher clock speed and the chipset in general has a superior manufacturer.
Don't think the P6 has 4G either.
The extra RAM on the P6 is useful though - 1 GB of RAM is OK, but Sony steal quite a lot of it for system resources - 2GB means you'd have to be doing insane amounts of multi tasking to ever worry about it.
I suspect there will be much more development on the SP, if you're into custom ROMS.
My reasons for chosing the SP were 4G and familiarity (I like using custom ROMS, know how Sony do things and am used to all the flashing tools etc.) - I also like the fact that not many people have the SP.
please see test of P6! the touchscreen response is very poor, however, the touch screen of the SP responds only in a few situations even bad. mostly is nice.
Thanks guys I am going for the SP... i am sure i wont regret ...thread can be closed
The screen of sp is horrible
Sent from my HUAWEI P6-U06 using xda app-developers app
--
Osku958 said:
mine doesn't have that problem
Click to expand...
Click to collapse
Some device have that problem... U r lucky if u don't have that problem..
Just search in YouTube like
"
Xperia SP Touch Screen bug while charging "
U can see that
Osku958 said:
mine doesn't have that problem
Click to expand...
Click to collapse
here also ok. :good:
P6在中国就是个垃圾。短续航，游戏性能低，发热量高和实际只有200Mhz的GPU。。
P6 in China is a waste. Short battery life, low gaming performance, high heat, and actually only 200Mhz for GPU. .
Sorry for my poor English
Osku958 said:
mine doesn't have that problem
Click to expand...
Click to collapse
Some Proofs
http://www.youtube.com/watch?v=RpZeiQ5oJ7E
http://www.youtube.com/watch?v=UcAt-iuZK-c
http://www.youtube.com/watch?v=yk1cgjuDGqM
http://www.youtube.com/watch?v=UTJ1vD2kv8g
http://www.youtube.com/watch?v=zhLy2fJ9AFk
So u are lucky....
I can confirm the charging problem on my X Sp as well... But i changed it from service centre for free via DOA process.. And new one has no issues.. I can perfectly use my phone during charging and flat surface.. Issues are no longer present..
Sent from my C5302 using xda app-developers app
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.