Can someone point me in the right direction for compiling bacon bits on win xp 64 bit?
Basically, what I want to do is the following:
Modify the:
https://github.com/CyanogenMod/htc-kernel-vision/blob/master/arch/arm/mach-msm/acpuclock-7x30.c
change lines 103 to 120 such that:
Code:
static struct clkctl_acpu_speed acpu_freq_tbl[] = {
{ 24576, SRC_LPXO, 0, 0, 30720, 1000, VDD_RAW(1000) },
{ 61440, PLL_3, 5, 11, 61440, 1000, VDD_RAW(1000) },
{ 122880, PLL_3, 5, 5, 61440, 1000, VDD_RAW(1000) },
{ 184320, PLL_3, 5, 4, 61440, 1000, VDD_RAW(1000) },
{ MAX_AXI_KHZ, SRC_AXI, 1, 0, 61440, 1000, VDD_RAW(1000) },
{ 245760, PLL_3, 5, 2, 61440, 1000, VDD_RAW(1000) },
{ 368640, PLL_3, 5, 1, 122800, 1000, VDD_RAW(1050) },
{ 768000, PLL_1, 2, 0, 153600, 1050, VDD_RAW(1100) },
/* Make sure any freq based from PLL_2 is a multiple of 19200!
Voltage tables are being very conservative and are not designed to
be an undervolt of any sort. */
{ 806400, PLL_2, 3, 0, 192000, 1100, VDD_RAW(1100) },
{ 1017600, PLL_2, 3, 0, 192000, 1100, VDD_RAW(1200) },
{ 1113600, PLL_2, 3, 0, 192000, 1150, VDD_RAW(1200) },
{ 1209600, PLL_2, 3, 0, 192000, 1150, VDD_RAW(1200) },
{ 1305600, PLL_2, 3, 0, 192000, 1200, VDD_RAW(1200) },
{ 1401600, PLL_2, 3, 0, 192000, 1200, VDD_RAW(1300) },
{ 1497600, PLL_2, 3, 0, 192000, 1250, VDD_RAW(1300) },
{ 1612800, PLL_2, 3, 0, 192000, 1300, VDD_RAW(1400) },
{ 1708800, PLL_2, 3, 0, 192000, 1300, VDD_RAW(1400) },
{ 0 }
};
Related
Has anybody found out what triggers desk mode in the pogo pin dock? I am looking into replicating the functionality without spending 50+ dollars on the original. Also, does anybody have any good photos of the guts of the pogo dock?
Thanks,
Chris
so, after some digging about, it looks like the docking mode is set by the middle pin.
from digging about in the sources, I have found board-tuna-pogo.c which is the file that configures a GPIO pin to be used for the pogo functionality.
It looks like when first connected to a dock, the phone sends a wake up pulse of 100mS, then waits for the dock to respond with a similar pulse back to the phone.
The duration of the pulse is what sets the dock mode.
Here are the times from the sources(times are in mS):
Code:
#define POGO_ID_CARDOCK 100
#define POGO_ID_DESKDOCK 200
Going to try a couple of things to test this on my real phone
how would you get the dock to send a pulse back?
Probably with a microcontroller, in my case
silverchris said:
Probably with a microcontroller, in my case
Click to expand...
Click to collapse
Please let us know if you find a way to make it work, I'm not too good with electronics, but i'm no stranger to a soldering iron. I would LOVE to be able to modify my existing car dock to power it with AC charge capabilities.
Those of us that have built our own car pogo docks are already AC charging. Any of the ROM+kernels with fast charge override will do it. You also need to ensure your 12V source puts out over 500 milliamps. Placing an NFC tag in the dock can perform all the dock shifting functions. See here or here.
You could probably program an ATTiny flashed with Arduino code to transmit the appropriate response. An 8Pin DIP can be hidden pretty easily and runs on 5vdc. You could even include a car/desk mode toggle, for whatever reason.
subvertz said:
Those of us that have built our own car pogo docks are already AC charging. Any of the ROM+kernels with fast charge override will do it. You also need to ensure your 12V source puts out over 500 milliamps. Placing an NFC tag in the dock can perform all the dock shifting functions. See here or here.
Click to expand...
Click to collapse
the problem with this is that I would no longer be running stock and the ota updates would fail to apply until I flashed back the stock kernel
Sent from my Galaxy Nexus
So it looks like the code I was looking at was out of date. The new code is similar but is slightly more complex, allowing for charge current and audio device connection to be transferred from the dock to the phone.
I so far have accidentally put the phone in car dock mode. But I have yet to repeat that.
silverchris said:
So it looks like the code I was looking at was out of date. The new code is similar but is slightly more complex, allowing for charge current and audio device connection to be transferred from the dock to the phone.
I so far have accidentally put the phone in car dock mode. But I have yet to repeat that.
Click to expand...
Click to collapse
I believe this is the current board-tuna-pogo.c file. From what I can tell the phone sends out a 100ms wake up pulse then waits for three responses.
Code:
/* The below constants are in milliseconds */
#define POGO_WAKE_PERIOD 100
#define POGO_ID_PERIOD_TIMEOUT 750
#define POGO_ID_DESKDOCK 50
#define POGO_ID_CARDOCK 100
#define POGO_ID_CHARGER 50
#define POGO_ID_USB 100
#define POGO_ID_AUDIO 50
#define POGO_ID_NO_AUDIO 100
#define POGO_ENTER_SPDIF_WAIT_PERIOD 100
#define POGO_ID_PERIOD_TOLERANCE 20
#define POGO_DET_DEBOUNCE 80
The first response pulse determines if its a DESKDOCK or CARDOCK , the second response pulse is for AC Fast charging or USB charging , and the third response pulse is for whether there is audio out or not.
ya, thats the one I am working off of now. Still haven't gotten the phone to respond though. My phone keeps retrying the wake up pulse over and over again. Not sure if my timings are just off, or if I may have damaged the input on the phone(I hope not...)
ok, so here is how it works
The phone expects two pulses back from the dock. The space between the two pulses is also counted.
{
"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"
}
(The unreadable yellow words are: "Yellow is the wake pulse from phone")
That image has the break down.
So for dock type, there are two durations:
50mS for a Deskdock
100mS for a Cardock
For charge types:
50mS for AC Charging
100mS for USB Charging(Doesn't put the phone in a fastcharge state)
and lastly, Audio connection:
50mS that audio output is enabled from dock
100mS that audio output is disabled on the dock.
The signalling level is 1.8V, you should not exceed the 1.8V signalling level on the middle pin, because you may damage your phone.
I ended up using a transistor to shift the level up for my microcontroller, and a resistor divider network to bring it back down.
Now I just need to build the part that holds the phone....
Can you share what what you used for a mirocontroller and/or a schematic and perhaps a code example?
Ya, give me a little bit to bang it out in eagle, and I will also upload the code for the microcontroller. I am using a way overkill dspic30f3014, because I have it on hand.
silverchris said:
Ya, give me a little bit to bang it out in eagle, and I will also upload the code for the microcontroller. I am using a way overkill dspic30f3014, because I have it on hand.
Click to expand...
Click to collapse
Also maybe provide some info for the more layman people to follow?
Sent from my Galaxy Nexus
silverchris said:
Ya, give me a little bit to bang it out in eagle, and I will also upload the code for the microcontroller. I am using a way overkill dspic30f3014, because I have it on hand.
Click to expand...
Click to collapse
Yeah just a bit overkill. I was thinking an ATtiny or the like would do.
Schematic(Didn't bother with the power sections...)
The transistor provides the level shifting from 1.8V to 5V, but also inverts the signal, so keep that in mind when reading the code.
My proto typed board:
Code:
#include <p30f3014.h>
#include <InCap.h>
//config
_FOSC(CSW_FSCM_OFF & FRC);
_FWDT(WDT_OFF); //Turn off the Watch-Dog Timer.
_FBORPOR(MCLR_DIS & PWRT_OFF); //Enable MCLR reset pin and turn off the
//power-up timers.
_FGS(CODE_PROT_OFF); //Disable Code Protection
#define FOSC 7370000LL // clock-frequecy in Hz with suffix LL (64-bit-long), eg. 32000000LL for 32MHz
#define FCY (FOSC/4) // MCU is running at FCY MIPS
#define delay_us(x) __delay32(((x*FCY)/1000000L)) // delays x us
#define delay_ms(x) __delay32(((x*FCY)/1000L)) // delays x ms
#define __DELAY_H 1
#include <libpic30.h>
void __attribute__((__interrupt__)) _IC1Interrupt(void)
{
IFS0bits.IC1IF = 0;
CloseCapture1();
delay_ms(2);
PORTDbits.RD2 = 1;
delay_ms(50); //Dock Type Delay, 50mS for desk, 100mS for car
PORTDbits.RD2 = 0;
delay_ms(50); //Charge type delay, 50mS for High current, 100mS for low
PORTDbits.RD2 = 1;
delay_ms(100); //Audio Connection delay, 50mS for connected, 100mS for disconnected
PORTDbits.RD2 = 0;
delay_ms(600);
ConfigIntCapture1(IC_INT_PRIOR_1 & IC_INT_ON);
T3CON = 0x8000;
OpenCapture1(IC_IDLE_STOP & IC_TIMER3_SRC & IC_INT_1CAPTURE & IC_EVERY_RISE_EDGE);
Nop();
}
//main loop
int main(void)
{
/* Enable Timer1 Interrupt and Priority to '1' */
ConfigIntCapture1(IC_INT_PRIOR_1 & IC_INT_ON);
T3CON = 0x8000; /* Timer 3 On */
/* Configure the InputCapture in stop in idle mode, Timer
3 as source, interrupt on capture 1, I/C on every fall
edge */
OpenCapture1(IC_IDLE_STOP & IC_TIMER3_SRC & IC_INT_1CAPTURE & IC_EVERY_RISE_EDGE);
long count = 0;
//Set up Clock
//Loop forever
TRISBbits.TRISB0 = 0;
TRISDbits.TRISD2 = 0;
while(1)
{
count++;
if(count < 200000){
PORTBbits.RB0 = 1;
}
if(count > 200000){
PORTBbits.RB0 = 0;
}
if(count == 400000){
count = 0;
}
}
}
I am making use of the dsPICs input capture to interrupt on the falling edge of the wake pulse(We detect the rising edge on the pic pin because of it being inverted.) We then toggle RD2, first high for 50mS then low for 50mS then back high for 100mS. This signals the phone that the dock is desk dock, with high current charging, and that the audio output is not connected.
If you want the Microchip MPLAB project I can also put it up somewere.
My recommendations for this project would be to use a 1.8V microcontroller to avoid all the level shifting.
silverchris said:
I am making use of the dsPICs input capture to interrupt on the falling edge of the wake pulse(We detect the rising edge on the pic pin because of it being inverted.) We then toggle RD2, first high for 50mS then low for 50mS then back high for 100mS. This signals the phone that the dock is desk dock, with high current charging, and that the audio output is not connected.
Click to expand...
Click to collapse
How could we get SPDIF out of there too? After signaling POGO_ID_AUDIO, does SPDIF just start to flow? Not sure of the signaling voltage levels for coax SPDIF either...
--Bill
pdxbill said:
How could we get SPDIF out of there too? After signaling POGO_ID_AUDIO, does SPDIF just start to flow? Not sure of the signaling voltage levels for coax SPDIF either...
--Bill
Click to expand...
Click to collapse
It does look like it is outputting data, I don't have fast enough equipment at my disposal to see if it is true SPDIF data, but all the code seems to call it that. If it is just SPDIF data then you should just need to shift it to the correct voltage level, and feed it to a dac
silverchris said:
It does look like it is outputting data, I don't have fast enough equipment at my disposal to see if it is true SPDIF data, but all the code seems to call it that. If it is just SPDIF data then you should just need to shift it to the correct voltage level, and feed it to a dac
Click to expand...
Click to collapse
Do you have an A/V receiver or similar with a coax digital in? If so, give it a try!
--Bill
Certain people that use your work, trust you guys.
faux's 2.1ghz kernel is really 1.8
KT's kernel @ 1.5 is really running @ 1.86
he is making it seem his kernel is faster than it really is by
making it display x speed when it is really clocked higher.
Why faux does the opposite. I have no idea. But this is grimy.
here is KT747's code - you can see this for yourself at his github
here is the link to this part of his github -> https://github.com/ktoonsez/KT747-J...be41bf639e/arch/arm/mach-msm/acpuclock-8960.c
Code:
{ 1, { 1512000, HFPLL, 1, 0, 0x3C }, L2(16), 1200000 },
{ 1, { 1512000, HFPLL, 1, 0, 0x3E }, L2(16), 1200000 },
{ 1, { 1512000, HFPLL, 1, 0, 0x40 }, L2(16), 1200000 },
#ifdef CONFIG_SUPER_CLOCKED
{ 1, { 1512000, HFPLL, 1, 0, 0x42 }, L2(16), 1200000 },
{ 1, { 1512000, HFPLL, 1, 0, 0x44 }, L2(16), 1200000 },
#endif
{ 0, { 0 } }
};
this is part of his "static struct acpu_level acpu_freq_tbl_8960_kraitv2_stock[] = {" table
now lets have a look here
Code:
{ 1, { 1512000, HFPLL, 1, 0, 0x42 }, L2(16), 1200000 },
{ 1, { 1512000, HFPLL, 1, 0, 0x44 }, L2(16), 1200000 },
what he have here is some additional 1.512 entries on top of the stock samsung one
lets take this apart
1512000 is the clock speed displayed in sysfs, or apps such as system tuner, or set cpu - it has NO impact on cpu speed - you can put ANY number here
HFPLL is the reference clock, for most MSM based devices, HFPLL = 27 MHz, or 27000 Hz
the "1" following HFPLL is the divider used - mainly for lower clock speeds, as any number divided by 1 is the number
now on to the good part
the 0x42
and 0x44
are the multipliers used to adjust the clock
so
convert 42 hex to decimal, we get 66
we multiply 66 by 27,000 and we get 1782000
we divide by 1, we get 1782000, or 1.782 GHz
now - since he also uses 0x44 - lets do some math
0x44 hex = 68 dec
68 x 27000 = 1836000
1836000 divided by 1 = 1836000
so, his kernel will display 1.5GHz, even though it is really running 1.836
here are some pics for further proof. because faux has either deleted or removed his git. or made it hidden. who knows. he's a fox (pun). these are of ktoonz' however, but they use the same tricky mathematics nonetheless.
{
"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"
}
dont have to be a genius to see it. its simple math.
All respect. Lost. Until explanation is provided.
Pretty sheisty when you take donations for your "superior" work.
So faux kernel was set to.. .... wait for it..... a "faux 1.5 GHz".... ??
Looollll
It's 2:57 am I'm sure this thread will closed.by 3:00 am
Sent from my SGH-T999 using xda app-developers app
OP updated with screen shots... since faux decided to hide or delete his entries about ten minutes ago. i figured he would do this, because he is a faux
cobraboy85 said:
Did you cure cancer or something?
Click to expand...
Click to collapse
iirc he's a douche... (lol.. Google it)
Holy crabs, what is going on? That wins pic of the year in any case. "There's a cobraboy in my boot." Let's just hope the boot doesn't come and find you!
Also, to quote, you really have no ****ing clue who I am? Really? Son of a ***** you're re...diculously uproarious, son.
cobraboy85 said:
i found this rather funny. kind of depicts everything this thread stands for.
Click to expand...
Click to collapse
I'm so sleepy but waiting to see when they close this lol
Sent from my SPH-L710 using Tapatalk 2
oh i promise, it will be closed. and deleted as well. any type of truth around here about what people are really doing gets stifled out quickly.
i know people that use their kernels, and i have before. and this is flat out dishonest when you take donations from people for your "superior" work.
cobraboy85 said:
oh i promise, it will be closed. and deleted as well. any type of truth around here about what people are really doing gets stifled out quickly.
i know people that use their kernels, and i have before. and this is flat out dishonest when you take donations from people for your "superior" work.
Click to expand...
Click to collapse
It is..I have only ran one of those kernels it was great for a couple days then it went all weird on me..plus didn't like the app that forcefully was added. But this is shinning light to a point, but at least from sprint section there are limited kernels, therefore his creates traffic to that section even other kernels I've seen with his "governor" so doubt any action would be taken mods will point towards the disclaimer, probably hand out warnings if not bans and **** will remain dude
Sent from my SPH-L710 using Tapatalk 2
well hopefully that is all that happens, but we'll see. history of this site says otherwise, however.
i just want an explanation. and not some slimy excuse, which unfortunately faux is known for from what i have observed before.
Man wish it would happen but I seriously doubt it...another thing that will get blamed on "anthrax" people starting ****. Which is not even the case but the disclaimer and past actions here I guess will be used to scapegoat into no explanation
Sent from my SPH-L710 using Tapatalk 2
That escalated quickly!
Sent from my SGH-T999
chrisram88 said:
That escalated quickly!
Sent from my SGH-T999
Click to expand...
Click to collapse
And died quickly, I was kinda hoping for a response from one of the devs :-\
we need/deserve some answers. do we need to start a petition or something. if we dont get some answers im going to all the android news sites to get the ball rolling with these saved pages. thanks for pointing this out cobraboy85
So faux still doesn't get his clock
tables right?
Or another innovation?
Sent from my SGH-T889 using Tapatalk 2
imneveral0ne said:
And died quickly, I was kinda hoping for a response from one of the devs :-\
Click to expand...
Click to collapse
I'm guessing that's not going to happen around here. But maybe we will get lucky..
Sent from my SGH-T999 with using Tapatalk 2
Closed due to flaming and disrespect to each other
It also became more about dev bashing than getting answers
Some posts had to be edited including the OP for name calling
The kernel source has ALWAYS been available as per GPL
And just NOW someone decides to examine it with a microscope?
We have too few developers making S3 kernels and you want to try and run them off?
XDA is about development and nothing here is aiding development
The developers in question have always responded to my PMs.
Perhaps you should have asked these questions there instead of this
Had this been an intelligent discussion politely requesting the developers to help understand what happened, it would have remained open.
Instead it became a circus and witch hunt. You might want to question the source of the information as well as the source of the code used as a base.
Have been having charging issues mentioned in another thread, but was wondering if any one has seen this or could explain why it might happen?
{
"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"
}
ADB connected
Connected as USB media device (not shown)
6% battery
Not charging
Any ideas? I am using a $30 disposable phone and am getting really frustrated with my GNex.
Thanks,
Annoyed and desperate
A little photo journey threw a failed charge cycle.
I also have the corresponding output of a SL4A script I wrote to monitor the battery and charging state and status
Code:
05-18-13 22:04:50
status : 4
temperature : 260
level : 17
battery_present : False
plugged : 2
health : 2
voltage : 3761
technology : Li-ion
05-18-13 22:08:57
status : 4
temperature : 290
level : 16
battery_present : False
plugged : 2
health : 2
voltage : 3726
technology : Li-ion
05-18-13 22:43:36
status : 4
temperature : 260
level : 18
battery_present : False
plugged : 2
health : 2
voltage : 3767
technology : Li-ion
05-18-13 23:12:49
status : 4
temperature : 250
level : 19
battery_present : False
plugged : 2
health : 2
voltage : 3773
technology : Li-ion
05-18-13 23:31:47
status : 4
temperature : 250
level : 20
battery_present : False
plugged : 2
health : 2
voltage : 3776
technology : Li-ion
05-18-13 23:50:00
status : 4
temperature : 250
level : 20
battery_present : False
plugged : 2
health : 2
voltage : 3776
technology : Li-ion
05-19-13 04:00:29
status : 4
temperature : 210
level : 41
battery_present : False
plugged : 2
health : 2
voltage : 3806
technology : Li-ion
05-19-13 05:03:43
status : 4
temperature : 200
level : 46
battery_present : False
plugged : 2
health : 2
voltage : 3817
technology : Li-ion
05-19-13 05:19:58
status : 4
temperature : 200
level : 46
battery_present : False
plugged : 2
health : 2
voltage : 3817
technology : Li-ion
05-19-13 13:29:58
status : 4
temperature : 310
level : 9
battery_present : False
plugged : 2
health : 2
voltage : 3671
technology : Li-ion
05-19-13 14:02:41
status : 4
temperature : 340
level : 6
battery_present : False
plugged : 2
health : 2
voltage : 3598
technology : Li-ion
The legend for the return values
Any ideas, particularly about the trickle charging while 'not charging', the discharge to 9% as seen on the right of pic12 and the 'battery_present : False' found in the script output.
Thanks,
Gabe
After multiple chargers, batteries, charging sub-boards and trip threw a re-flow oven it has been diagnosed as a bad power control chip. I hope that someone can benefit from this experience.
Gabe
I will share the latest review about ZUK Z2 Pro Smartphone Design, Hardware, Camera, Battery,OS Review, as you know, ZUK Z2 Pro adopts the brand new streamlined design and features the latest Snapdragon 820, 5.2 Inch Corning Gorilla 2.5D floating display with RAM 4GB and 64GB Storage. It is pre-installed U-touch 2.0, 3100 Mah battery,support heart rate and oxygen UV function.
{
"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"
}
Specs:
OS: ZUI 2
CPU: Qualcomm Snapdragon 820 14nm Kryo Quad-Core 64 bit Processer, 2.15GHz
GPU: Adreno™ 530 3D 624MHz
RAM 4GB,LPDDR4 Dual Channel 1866MHz
Storage 64GB,UFS 2.0(Gear3)5.8Gbps
Sim Card: Dual Nano SIM card
Service Provide: Unlocked
Band:
TDD-LTE Band 38, 39, 40, 41
FDD-LTE Band 1,2, 3,4,5,7,8,20
TD-SCDMA Band 34, 39
WCDMA 850, 900, 1900, 2100 MHz
CDMA2000 ( 800 MHz)
GSM/EDGE( 850, 900, 1800, 1900 MHz)
CDMA( 800MHz)
WiFi: 802.11 a/b/g/n/ac Support 2.4 GHz and 5 GHz
Screen: Corning Gorilla Glass Touch Screen,1920*1080 Super AMOLED, 424 PP
Size: 5.2 Inch
Visible Angle: 178°
Resolution: 1920*1080 Super AMOLED, 424 PP
Navigation GPS+GLONASS Navigator
Dual Camera: 8.0M front camera and 13.0M Back Camera, support Auto Focus and OIS/EIS
ZUK Z2 Pro Mobile Details:
Google Play: Support
Earphone Interface 3.5mm
USB: USB Type-C
Bluetooth: Build in 4.1 Support BLE
OTG: Support
Email and Browser: Yes, built in
Music MP3, M4A, AAC, MKA, AMR
FLAC, APE, WAV
AAC/AAC+/eAAC+, MP3, MP3 VBR, NB-AMR, WB-AMR
Weight: 145g
ZUK Z2 Pro Mobile contain:
1 x ZUK Z2 Pro 4G Android Smart Phone
1 x USB cable
1 x Charger
1 x Battery 3100mAh
Review source: igeekphone
ZTE Blade A2 Plus | 5.5" FHD | MT6750T | 3GB,4GB | 32GB | Fingerprint | PE-charge
ZTE Blade A2 Plus
{
"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"
}
OS: Android 6.0 Marshmallow
Display: 5.5 in, 2.5D, IPS, 1080 x 1920 pixels, 24 bit
SoC: MT6750T ; 8 Cores ; Cortex-A53 (4x 1.5 GHz) + (4x 1.0 GHz)
RAM: 3 GB, 4 GB, 667 MHz
Storage: 32 GB
Camera: front 8MP and 13MP back camera
Battery: 4900 mAh, Li-Polymer, PE-quick charge;9V/1.5A (50% in one hour)
Sensors : Proximity, Light, Accelerometer, Compass, Fingerprint, !..no Gyrometer
Dimensions: 76.2 x 155 x 9.8 mm
Weight: 189 g
Baseband :
GSM 850, 900, 1800, 1900 MHz
CDMA 800 MHz
TD-SCDMA 1880-1920 MHz
TD-SCDMA 2010-2025 MHz
UMTS 850, 900, 1900, 2100 MHz
LTE 1800, 2100, 2600 MHz
LTE-TDD 1900 MHz (B39)
LTE-TDD 2300 MHz (B40)
LTE-TDD 2500 MHz (B41)
LTE-TDD 2600 MHz (B38)
Start to sell on October 17
any way to root this phone?
sceptikart said:
any way to root this phone?
Click to expand...
Click to collapse
Did you find any?
sceptikart said:
any way to root this phone?
Click to expand...
Click to collapse
Here you go
https://forum.xda-developers.com/showthread.php?t=3713190
Sent from my FRD-L04 using Tapatalk
Yes i want to root zte blade a2 plus
root possible
i have original disk of zte a2 plus device, with root, any one interested