I want to buy a MediaPad X2 so I asked for help. It is very important that the GPS works fine. Maybe I'll buy a used unit so that I have a few questions:
- Is there X2 where it is not possible to fix the GPS with upgrade / downgrade?
- Is about the GPS appears only on Android 6 or is this a problem on Android 5?
- Does gem702 gem703 can downgrade to Android 5 if there 6 Android?
To conclude: it is not my bit OS, only that it's important that the entire device functional.
I have a GEM-702L running the stock ROM (B006, Android 5.0.1) and everything works fine, including the GPS.
I also have 702L upgrated to Marshmallow 6.0 and GPS works perfectly.
In my case, 702 upgraded to Android 6.0 firm B202:
Gps works perfectly on Android 5
On Android 6, and just booted works too, but after a period undefined of time, gps position is perfect but google maps navigation does not work. Doing a reboot works again
Enviado desde mi GEM-702L mediante Tapatalk
In my 703 upgraded to Marshmallow (B211) GPS works flawlessly
In my 703L using KanVip b211... GPS works for awhile then stops after a certain amount of time then you have to reboot again and again and again and again... Really sucks nobody has a fix yet... It does seem in other forums that some of the other huawei phones with marshmallow are having the same problems
Ok, thank you guys, do you phone with Android 6 can return to Android 5?
This would solve the problem with GSP?
Steamer2499 said:
In my 703L using KanVip b211... GPS works for awhile then stops after a certain amount of time then you have to reboot again and again and again and again... Really sucks nobody has a fix yet... It does seem in other forums that some of the other huawei phones with marshmallow are having the same problems
Click to expand...
Click to collapse
Same issue for me :/
Does the b202 have GPS problem too?
Steamer2499 said:
Does the b202 have GPS problem too?
Click to expand...
Click to collapse
See you my reply before
Enviado desde mi GEM-702L mediante Tapatalk
AnthonyXavier said:
I also have 702L upgrated to Marshmallow 6.0 and GPS works perfectly.
Click to expand...
Click to collapse
Which software version are you on and are you rooted?
trurl3 said:
In my 703 upgraded to Marshmallow (B211) GPS works flawlessly
Click to expand...
Click to collapse
Hi I'd like to know what is different about your device setup than the rest of ours on Marshmallow because as you may already know there are very many of us (all of us I think) who are on Marshmallow with major GPS problems where it works once or twice but then doesn't work anymore until reboot.
To confirm, your device is 703L Stock on B211?
Can you confirm you are able to use GPS successfully, then stop for a while, and then use it successfully again?
What Navigation app are you using?
Are you running any other gps utilities in the background?
E--Man said:
Which software version are you on and are you rooted?
Hi I'd like to know what is different about your device setup than the rest of ours on Marshmallow because as you may already know there are very many of us (all of us I think) who are on Marshmallow with major GPS problems where it works once or twice but then doesn't work anymore until reboot.
To confirm, your device is 703L Stock on B211?
Can you confirm you are able to use GPS successfully, then stop for a while, and then use it successfully again?
What Navigation app are you using?
Are you running any other gps utilities in the background?
Click to expand...
Click to collapse
- I am using KangVip Slim B211 from @ajsmsg78, of course after upgrading to stock B211. It means, I have root.
- Yes, I am able to use GPS whenever I want, with breaks in using too. Although I am not heavy user of apps needing GPS.
- I use only generic Google Maps for navigation.
- No, I am not using any third part apps concerning GPS in the background.
It's all what I can say about it. It's a piity so you have such problems, but I cannot say why, sorry.
trurl3 said:
- I am using KangVip Slim B211 from @ajsmsg78, of course after upgrading to stock B211. It means, I have root.
- Yes, I am able to use GPS whenever I want, with breaks in using too. Although I am not heavy user of apps needing GPS.
- I use only generic Google Maps for navigation.
- No, I am not using any third part apps concerning GPS in the background.
It's all what I can say about it. It's a piity so you have such problems, but I cannot say why, sorry.
Click to expand...
Click to collapse
Thanks for your quick reply. It really is a pitty.
Not sure why some on KangVIP have this GPS issue as well whereas others on KangVIP like you do not.
I am using 703L Stock B211 non-rooted and have the issue.
@ajsmsg78, I wonder if we could find out how to solve the issue for those using KangVIP would also solve it for those who are on Stock non-rooted like me. Not sure where to start though.
Too bad, I love the device but really need my GPS working and don't want to downgrade to Lollipop. When will Huawei already address this?
E--Man said:
Thanks for your quick reply. It really is a pitty.
Not sure why some on KangVIP have this GPS issue as well whereas others on KangVIP like you do not.
I am using 703L Stock B211 non-rooted and have the issue.
@ajsmsg78, I wonder if we could find out how to solve the issue for those using KangVIP would also solve it for those who are on Stock non-rooted like me. Not sure where to start though.
Too bad, I love the device but really need my GPS working and don't want to downgrade to Lollipop. When will Huawei already address this?
Click to expand...
Click to collapse
Has anyone on stock non-rooted tried taking the boot.img from KangVIP Slim and flashing it through fastboot? There's not much else I can really do if you plan on staying on stock non-rooted.
ajsmsg78 said:
Has anyone on stock non-rooted tried taking the boot.img from KangVIP Slim and flashing it through fastboot? There's not much else I can really do if you plan on staying on stock non-rooted.
Click to expand...
Click to collapse
@thor1553 @Steamer2499 @shaolin95
If you guys are already rooted, do you think you can try this?
Here's something I done... Out of frustration I decided to boot into recovery. And install "KangVIP-B112-Slim.zip". First thing I done was I did an advance wipe, checked everything except external memory and installed "KangVIP-B112-Slim.zip". Didn't think this would work because I was on Marshmallow. Well it sorta worked, system would auto reboot once you started going through menus every single time.... Well, I decided to boot back into recovery and Install "KangVIP Slim B211". I did an advance wipe, checked everything except external memory, then installed "KangVIP Slim B211" rom, then did a wipe dalvik cache, then booted system like always.... GPS has been working for 24 hours now.... I'm thinking, something could have been left over from "B112" that has my GPS working without it fallen to sleep.... I will keep doing updates on my GPS status for the next few days.... It's been 25 hours and GPS is still awake and alive... ON THE 26th HOUR..... GPS FELL ASLEEP!!! DARN!
PS: Everything I installed was on my external sd card.
FINALLY got B212 OTA. See informative screenshot lol. I see no difference at first glance... View attachment 3954296
Will test to see if it fixes this notorious GPS issue and report back
UPDATE 3 BELOW.
Dec 1 UPDATE: So far so good since yesterday. Used GPS off and on about 6 times at random times. More testing required to conclude anything... Looks like B212 OTA just might be the solution.
*** PLEASE NOTE: The Google Maps app does have a minor issue but it does not seem to be the Huawei GPS module's fault - the issue occurs when closing and reopening the app and the current position shows as a gray dot as opposed to blue with no GPS notifications in the notification bar such as "Searching for GPS" or "Location Set by GPS". This is because the Google Maps app is not calling the GPS module to turn at that time, but if you start navigating then it DOES turn on and successfully gets a fix on the location - proof that the GPS module is indeed working.
Waze does not have this problem. This shows the issue is with Google Maps not the GPS module.
Does this help?
Dec 2 UPDATE 2: So far so good at day 2, used GPS a few times to test and getting a fix is extremely fast under 2 seconds so that I'd an improvement as well. I did have a random reboot earlier today when turning off wifi but I consider this to be am anomaly of B212.
Dec 3 UPDATE 3: Everything was going 100% smooth and until I decided to update the
Google Maps app via Play Store and that triggered the issue right away, I don't know why - very annoying. Had to reboot and tried GPS twice since and so far working again. Any reason someone can think of why a reboot would be necessary after updating an app? I can't and hope it's just a fluke.
Related
Hi, I've got some random reboots after upgrading on stock Lollipop 5.1 on my Nexus 5.
I've used Android 5.0.1 without any reboots or problem, but after upgrading on 5.1 I'm facing many random reboots when I switch from an app (like a game or Hangouts) using Recents or Home button from NavBar (it also happens randomly when I'm using my phone, like writing a message on Hangouts).
The reboots I'm talking about are not "soft" but "hard", because bootloader's logo (Google) appears and restarts my phone, so it is caused by Kernel Panic (as you'll see in my last_kmsg) and they occured on both stock and custom rom.
Here is a "last_kmsg" when it occured on stock Lollipop 5.1: http://pastebin.com/80dDgzae (attached too).
The_Wolf91 said:
Hi, I've got some random reboots after upgrading on stock Lollipop 5.1 on my Nexus 5.
I've used Android 5.0.1 without any reboots or problem, but after upgrading on 5.1 I'm facing many random reboots when I switch from an app (like a game or Hangouts) using Recents or Home button from NavBar (it also happens randomly when I'm using my phone, like writing a message on Hangouts).
The reboots I'm talking about are not "soft" but "hard", because bootloader's logo (Google) appears and restarts my phone, so it is caused by Kernel Panic (as you'll see in my last_kmsg) and they occured on both stock and custom rom.
Here is a "last_kmsg" when it occured on stock Lollipop 5.1: http://pastebin.com/80dDgzae (attached too).
Click to expand...
Click to collapse
Flashed Android 5.0.1 and no random reboots (as I also said when i wrote my first post).
I don't know if the "question" is clear, but can you help me reading the "last_kmsg" which I attached in first post? Thanks
Same exact thing happening to me also.
Sent from my Nexus 5 using XDA Free mobile app
The same is happening to me. And it looks like a hardware problem cuz when the phone reboots it keeping reboot until I keep pressing the power button while boots.
I have a bad experience about it. In my Nexus S when updates to Jelly Bean the same occurs until phone suddenly die. (I live in Brazil so, guess what? I have now a wonderful paper weight)
No luck with 5.1.1
You guys found any fix?
I was waiting for 5.1.1 update from Google (5.1.1 code is already available on AOSP and I tested it on Chroma), but unfortunately it didn't solve this problem: it keeps rebooting after a long daytime doing the same things I already wrote in first post. I'll wait for factory Google factory images, but I'm pretty sure it won't fix this.
P.S.: I tested Chroma on 5.0.2 bootloader and modem.
Anyone can read "last_kmg" I posted in first post? Any other has the same trouble?
The_Wolf91 said:
You guys found any fix?
I was waiting for 5.1.1 update from Google (5.1.1 code is already available on AOSP and I tested it on Chroma), but unfortunately it didn't solve this problem: it keeps rebooting after a long daytime doing the same things I already wrote in first post. I'll wait for factory Google factory images, but I'm pretty sure it won't fix this.
P.S.: I tested Chroma on 5.0.2 bootloader and modem.
Anyone can read "last_kmg" I posted in first post? Any other has the same trouble?
Click to expand...
Click to collapse
Try another (custom) kernel.
beekay201 said:
Try another (custom) kernel.
Click to expand...
Click to collapse
I just flashed ElementalX kernel but no luck, random reboot happened on 5.1.1 too. By the way it was quite obvious because it happened already on 5.1 Google's factory image (stock kernel so)..
I have exactly the same issue with nexus 5 since upgrading to 5.1.0.
I went back to 5.0.1, which solved it for a few days, but now this happens with 5.0.1 as well.
also, before random reboots happen, the power button becomes extra sensitive, so one keypress causes the screen to turn on and off again, or to display the shutdown menu.
this does not happen when the phone is stable.
Hey guys i have the exactly same problem since i upgraded to 5.1.1 i am non-rooted please need help
Sent from my Nexus 5 using XDA Free mobile app
noob424 said:
Hey guys i have the exactly same problem since i upgraded to 5.1.1 i am non-rooted please need help
Click to expand...
Click to collapse
Same here.
LG Nexus 5 - Lollipop 5.1.1 LMY48B
Unlocked bootloader;
Rooted;
ClockWorkmod 6.0.4.5 (not flashed - just boot on image when used);
Wipe factory reset (in cwm). Flashed 5.1.1 image files (boot, radio, bootloader, system and cache).
Random reboots, and sometimes with apps optimizing.
I have the same problem with N5 since upgrading to 5.1.1 - never had any problems before. Doing it several times an hour now. Trying a cache clean next, after I wait for the optimising apps to finish yet again!
Hi all,
I had the same problem. Everything stock, up to datę, no root. Phone was rebooting itself several times in a row.
Right now it seems that problem dissapeared. Reboots in my case was caused probably by application Autoguard Dash Cam Blackbox. After removal no reboots for 2 months and no memory leak.
cleared cache and it happened again within a minute...
Does seem to be linked to the power button
There's a long thread about this issue over at Google Groups. It's affecting a lot of users and not just Nexus 5 users. Some in the thread are 4 and 7 users having the same issue. Some have replaced the battery and it has resolved the issue, at least temporarily. Others, like myself, saw success in rooting and replacing the kernel or using a new ROM. Users who have downgraded to Kit Kat report the issue goes away, so despite the power button triggers, it seems to be a software issue. Anyone have any insight? It's getting feisty in Groups thread.
Google Groups reboot thread
simbapenn said:
There's a long thread about this issue over at Google Groups. It's affecting a lot of users and not just Nexus 5 users. Some in the thread are 4 and 7 users having the same issue. Some have replaced the battery and it has resolved the issue, at least temporarily. Others, like myself, saw success in rooting and replacing the kernel or using a new ROM. Users who have downgraded to Kit Kat report the issue goes away, so despite the power button triggers, it seems to be a software issue. Anyone have any insight? It's getting feisty in Groups thread.
Google Groups reboot thread
Click to expand...
Click to collapse
I have N5 kit kat 4.4.2 in Chrome watching videos randoms reboot its happens
This is happening to my fiance's N5. It happens when she's using it and also when it's not being used. When it reboots, it optimizes the apps and says the battery is at 0 when it was a full charge. Only way to turn it back on is to connect it to a charger. Frustrating.
FYI the update to 6.0 did not solve the restart problem. It's either hardware related, app related or a bug that's still in the OS.
I'm selling my Nexus because of this, has been happening for a few months now.
It's not software related, it has to do with the actual power button. Some people had success changing it out, soldering it etc., but I don't have that time or knowledge.
Google wouldn't help, as I'm out of warranty. So I guess it's goodbye Nexus. Really unfortunate given that the phone works fine, it's just a quality issue.. will have to re-evaluate buying another Nexus in the future.
The_Wolf91 said:
You guys found any fix?
I was waiting for 5.1.1 update from Google (5.1.1 code is already available on AOSP and I tested it on Chroma), but unfortunately it didn't solve this problem: it keeps rebooting after a long daytime doing the same things I already wrote in first post. I'll wait for factory Google factory images, but I'm pretty sure it won't fix this.
P.S.: I tested Chroma on 5.0.2 bootloader and modem.
Anyone can read "last_kmg" I posted in first post? Any other has the same trouble?
Click to expand...
Click to collapse
Im getting them as well on 5.1.1. I hope its fixed in the 6.0 ota update.
---------- Post added at 04:41 PM ---------- Previous post was at 04:20 PM ----------
I have been using this awesome app on my nexus 5, just so I don't have to use the power button here is the play store link.
https://play.google.com/store/apps/details?id=com.plexnor.gravityscreenofffree
maccboy2010 said:
Im getting them as well on 5.1.1. I hope its fixed in the 6.0 ota update.
Click to expand...
Click to collapse
Confirmed the update will NOT fix this issue.
Hi guys,
for some reason after I did update to KangVIP I can't get rid off it. Besides I got no wifi and bt and I was going to start over with b023 as suggested but at this point I wont bother anymore.
I did wipe the system, I did advanced wipe using twrp but no matter what I do none of the stock firmwares are going through however the Kanga one always goes through.(KangaVIP goes through only in TWRP)
twrp 2.8.7.0
wipe
advanced wipe
I select all the partitions
mkdosfs process ended with error=1
unable to wipe /usb
unknown mtp message type: 1
unable to wipe /usb
I go back, restart to fastboot, (device is saying there is no OS installed), I restore the recovery, create dload folder on my sdcard, put there 028 (actually I tried all of them already), volume+ volume - power and I get error.
What am I missing ?
Anyone can help ?
Thanks in advance.
Eric
First you did a OTA from B029 to B209?
If so you are now on a Android 6 ROM you cant go back to Android 5 without a Rollback from Huawei.
Hirs_E_Fruit said:
First you did a OTA from B029 to B209?
If so you are now on a Android 6 ROM you cant go back to Android 5 without a Rollback from Huawei.
Click to expand...
Click to collapse
Yes I did then I wiped everything and started with b028 again.
Same thing, wifi didn't work same with BT.
Wipe again and this time I did local update and since the local update I can't go back not even b029.
77Eric77 said:
Yes I did then I wiped everything and started with b028 again.
Same thing, wifi didn't work same with BT.
Wipe again and this time I did local update and since the local update I can't go back not even b029.
Click to expand...
Click to collapse
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Hirs_E_Fruit said:
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Click to expand...
Click to collapse
I'm stuck on 6.0
I know I can do force update on 5.0 I said it above I just can't do it with 6.0 -> b029, only with your rom.
Anyone else is having this issue ?
The Kanga rom got a quite few problems no wifi and not BT, Google play services crashing (this can be fixed with gapps) my co worker just tried it with his own methods and same issue. After I went through the whole Kanga thread 60% of the posters got problems most of them are ignored.
I don't have any problems but I think the people with problems are people who have a DAV 701L.
Hirs_E_Fruit said:
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Click to expand...
Click to collapse
Hirs_E_Fruit said:
I don't have any problems but I think the people with problems are people who have a DAV 701L.
Click to expand...
Click to collapse
I got DAV-703L, just simple question, why is the wifi and bt not working ?
When I get into Kanga I can remove the root or deny access to it is there a way to ditch it ?
Yeah I know it's working for you and it's not working for 10 other people including 703L owners. There is something wrong with the rom no doubt about it.
77Eric77 said:
I got DAV-703L, just simple question, why is the wifi and bt not working ?
When I get into Kanga I can remove the root or deny access to it is there a way to ditch it ?
Yeah I know it's working for you and it's not working for 10 other people including 703L owners. There is something wrong with the rom no doubt about it.
Click to expand...
Click to collapse
I think there was an error while flashing and without a full clean Rom flash i can't see a solution.
Before I got it to work I flashed it more than 3 times and everytime everything worked so I think don't think the ROM is that bugged.
Hirs_E_Fruit said:
I think there was an error while flashing and without a full clean Rom flash i can't see a solution.
Before I got it to work I flashed it more than 3 times and everytime everything worked so I think don't think the ROM is that bugged.
Click to expand...
Click to collapse
The first rom you introduced is working "fine" I get the wifi and bt no problem but once I switch into the latest build it's gone.
Any idea where can I get full clean Rom ?
This one is a no go http://www.needrom.com/download/p8max-dav-703l/
I managed to rollback to 5.1.1 but when I try to force flash it, it says it's not compatible.
If you don't update properly to B209, when you flash any B209 rom you are going to run into issues such as the wireless Bluetooth and sim card switching for some. If you properly updated the dload method should have completed successfully. Look at the kernel and radio version of B209 in About phone and compare it to others and see if they match.
ajsmsg78 said:
If you don't update properly to B209, when you flash any B209 rom you are going to run into issues such as the wireless Bluetooth and sim card switching for some. If you properly updated the dload method should have completed successfully. Look at the kernel and radio version of B209 in About phone and compare it to others and see if they match.
Click to expand...
Click to collapse
I don't want to use your rom even if you removed the Chinese it's still inside the system. Boot load times take much longer. Unexpected crashes. I did try it on 4 phones with OTA and local updates 2 are working but the Kang does crash twice a day minimum.
All what I'm asking is how to restore it to it's original settings, this was my worst mistake ever.
What I'm trying to say if I do something I do it properly just look at your thread 85% failure ratio that doesn't look like it was done properly does it ?
77Eric77 said:
I don't want to use your rom even if you removed the Chinese it's still inside the system. Boot load times take much longer. Unexpected crashes. I did try it on 4 phones with OTA and local updates 2 are working but the Kang does crash twice a day minimum.
All what I'm asking is how to restore it to it's original settings, this was my worst mistake ever.
What I'm trying to say if I do something I do it properly just look at your thread 85% failure ratio that doesn't look like it was done properly does it ?
Click to expand...
Click to collapse
Really dude?? No worries, it will be the last time I do anything for the P8Max. Maybe you should just sell the phone since you're having all sorts of issues with it....or maybe you should have left it totally stock then. Or maybe read through the Mediapad X2 forums because the two phones are very similar.
This is not a guide as such but more of direction to other peoples hard work and effort. I am not a developer, just an experimenter!
Main Credits - @MishaalRahman and @phhusson.
For me one of the main selling points of the Mediapad M5 was being Project Treble enabled. Being a big Nexus/Pixel fan I am not particularly fond of EMUI.
So after reading this detailed and clear guide by Mishaal Rahman http://www.xda-developers.com/flash-generic-system-image-project-treble-device/, I was able to successfully install an AOSP Generic System Image by phhusion http://forum.xda-developers.com/project-treble/trebleenabled-device-development/experimental-phh-treble-t3709659
My device - CMR-W09 (10.8" non pro wifi).
I flashed v17 with Gapps and SU and apart from an Android System error upon boot it seems to work ok. I have not had much time to play with it but so far Wifi, Bluetooth, sound, camera, fingerprint sensor, MTP and SD card appear to be working. I had issues with google play not downloading apps but worked after clearing data/cache on google play and google play services. Also have issues with superuser force closing.
For the nervous and unsure, you can easily return to stock Huawei firmware by flashing your devices stock system.img in fastboot.
Obviously bootloader needs to be unlocked see guide - https://forum.xda-developers.com/mediapad-m5/how-to/bootloader-unlock-guide-t3781275 by @Apo11on. You can use Apo11on's root guide to download your firmware to get your stock system.img.
OEM needs to be disabled in developer options.
It is best to factory reset via recovery mode and then boot straight into bootloader to keep FRP unlocked.
Do this at your own risk but please read all the available information and guides on XDA.
pphusion has made other Project Treble roms but I have yet to try them. Hopefully it would be nice if someone could fully develop Lineage for this device.
which rom did you use ? the A/B one or A only ?
It's an A-only device.
I tried AOSP with GAPPS and SU but SuperSU shows the su binary as being occupied through several reboots. Getting the Lineage GSI now and will root with magisk.
Edit:
Blah... Lineage is not an option until we have twrp :/ (at least for me) No way to install GAPPS.
Edit:
SU works with phh's super user available from the play store.
Yes i have the AOSP one now on my AL-09 and it works fine till now. Bugs : home Button not working but fingerprint works, supersu with the phhs one works. Bluetooth sometimes gives an error message. Battery drain is a little bit high. I installed the Huawei camera apk from treble forum and This works also good.
Another Bug is Apps sometimes force closing but Not often.
How is Lineage performing?
A little bit off topic, but how did you unlock the bootloader on the Wifi only version since the website for the code is offline for a few weeks now?
Thanks in advance.
Fantastic to see that Treble works.
On my AL09(ASOP with gapps and su) bluetooth never connects to any of my devices and fc on pairing.
Lineage was a non-starter, since I was unable to get gapps running. I was also getting a vendor mismatch toast. I'm back on the stock .125(C00), no working tether is infinitely more useable than no BT.
It was nice to be able to flash something that didn't brick it and was partially useable.
fargonaz said:
On my AL09(ASOP with gapps and su) bluetooth never connects to any of my devices and fc on pairing.
Lineage was a non-starter, since I was unable to get gapps running. I was also getting a vendor mismatch toast. I'm back on the stock .125(C00), no working tether is infinitely more useable than no BT.
It was nice to be able to flash something that didn't brick it and was partially useable.
Click to expand...
Click to collapse
I understand, Do you think it gets more stable for our device in the future?
florian-m19 said:
I understand, Do you think it gets more stable for our device in the future?
Click to expand...
Click to collapse
I think so, if you look at the github comments there is a huawei phone having the same problem, so as long as a phone is having problems it should get fixed
We would like some screenshots to see if this is real @AndDiSa @rcstar6696 @phhusson @MishaalRahman
Just installed it, attached a few screenshots. Haven't tested it a lot, but it boots.
Wie are Not joking, its real ??
Delete, double post
I will be getting my Mediapad M5 8.4 tomorrow and will be flashing the AOSP treble build straight away. Just a heads up a updated build has just been posted with some Huawei related fixes.
i flash it now, and give feedback tomorrow
I flashed the new one with gapps and su, and for the sht-l09 there is no working bluetooth, so that's as far as I go. It will be nice when the BT is fixed for this device.
Works good with dirty flash, Home Button is working now and also Automatic Brightness, but battery draining is really high and it gets hot.
florian-m19 said:
Works good with dirty flash, Home Button is working now and also Automatic Brightness, but battery draining is really high and it gets hot.
Click to expand...
Click to collapse
Have you tried changing the cpu governor? Is it set to something like interactive? I got my Mediapad today but I am waiting for the bootloader unlock code from Huawei.
darren1 said:
Have you tried changing the cpu governor? Is it set to something like interactive? I got my Mediapad today but I am waiting for the bootloader unlock code from Huawei.
Click to expand...
Click to collapse
yes it is on interactive, should i change this ?
florian-m19 said:
yes it is on interactive, should i change this ?
Click to expand...
Click to collapse
Might be worth experimenting with. Try conservative or ondemand if they are available. You can always change back if it doesn't make any difference.
darren1 said:
Might be worth experimenting with. Try conservative or ondemand if they are available. You can always change back if it doesn't make any difference.
Click to expand...
Click to collapse
okay i change it in helix engine to ondemand and the suspend engine is now on powersafe.
Here is my stock rooted debloated B230 ROM.The rom is debloated to remove the Chinese apps along with a bunch of fixes and mods.
Features:
Magisk Pre Patched B230 boot image
Magisk Manager
Double tap to wake working
Added Video and Music from the International ROM
Updated Google Apps
Deodexed to shrink system size
Removed Touchplus
Added in a few themes
https://www.androidfilehost.com/?fid=1395089523397905233
For those of you with camera issues install this app and set it to permissive:
https://f-droid.org/repo/com.mrbimc.selinux_20171031.apk
ajsmsg78 said:
B227 for the GEM-703L was released on firmware finder. I actually flashed the update.zip in twrp and was able to flash it without an issue. Then I did a factory reset and can confirm I'm now on stock B227. I'm gonna play around with this.
Click to expand...
Click to collapse
Is B227 built on android 6 or 7? Thanks AJ.
mouse723 said:
Is B227 built on android 6 or 7? Thanks AJ.
Click to expand...
Click to collapse
It's still Android 6 unfortunately. Kernel security patch is July 2018 though. According to the changelogs it's just a security patch but may have other changes as well.
ajsmsg78 said:
It's still Android 6 unfortunately. Kernel security patch is July 2018 though. According to the changelogs it's just a security patch.
Click to expand...
Click to collapse
Hi, do (double tap to wake) function work on this B227 new rom ? thanks.
LH88 said:
Hi, do (double tap to wake) function work on this B227 new rom ? thanks.
Click to expand...
Click to collapse
Unfortunately, no, not even on the older boot.img. Since I updated to B227 even installing KangVIP Slim double tap to wake doesn't work anymore so I would not update until I can figure this out.
ajsmsg78 said:
It's still Android 6 unfortunately. Kernel security patch is July 2018 though. According to the changelogs it's just a security patch.
Click to expand...
Click to collapse
Is there any further changes beside security changes? Im on a b209 stock build, and im not sure if this gonna be as easy u told for me too or not, upgrading from b112 to 209 was a disaster for me, although now i like 209 much more than that 112.
My device is gem701>gem 703 b112> gem 703 b209
ajsmsg78 said:
Unfortunately, no, not even on the older boot.img. Since I updated to B227 even installing KangVIP Slim double tap to wake doesn't work anymore so I would not update until I can figure this out.
Click to expand...
Click to collapse
thanks.
safseyed said:
Is there any further changes beside security changes? Im on a b209 stock build, and im not sure if this gonna be as easy u told for me too or not, upgrading from b112 to 209 was a disaster for me, although now i like 209 much more than that 112.
My device is gem701>gem 703 b112> gem 703 b209
Click to expand...
Click to collapse
I dont think so. There was firmware, for example the radio that was updated when I flashed the update.zip. You can update to B212 if you want and stay on that.
Normally one can just flash systemless SuperSU or Magisk to patch the boot.img for root but when you do that to any boot.img on the X2 you get app freezes, freezes when charging etc. The only root that works properly is system root but the kernel and boot needs to be patched to allow system root or else it won't boot. I'm not that great with boot images so I've been using the B212 boot that was patched from the HRT Team (KangVIP). If they release a B227 KangVIP or a patched boot.img then I'll start using that boot.img in my next builds.
ajsmsg78 said:
I dont think so. There was firmware, for example the radio that was updated when I flashed the update.zip. You can update to B212 if you want and stay on that.
Normally one can just flash systemless SuperSU or Magisk to patch the boot.img for root but when you do that to any boot.img on the X2 you get app freezes, freezes when charging etc. The only root that works properly is system root but the kernel and boot needs to be patched to allow system root or else it won't boot. I'm not that great with boot images so I've been using the B212 boot that was patched from the HRT Team (KangVIP). If they release a B227 KangVIP or a patched boot.img then I'll start using that boot.img in my next builds.
Click to expand...
Click to collapse
Well thanks for info, but one thing remains here, im sure ive installed TWRP-ENG-6.0-BLACK-BLUE.img after flashing b209 stock, but just checked recovery and saw its twrp 3.2.1.0, are they same? And do u think i get into any trouble if i flash b227? Thanks in advance.
safseyed said:
Well thanks for info, but one thing remains here, im sure ive installed TWRP-ENG-6.0-BLACK-BLUE.img after flashing b209 stock, but just checked recovery and saw its twrp 3.2.1.0, are they same? And do u think i get into any trouble if i flash b227? Thanks in advance.
Click to expand...
Click to collapse
You want the latest twrp in my twrp thread, it's the black light blue version. I would update to B212 and stay there for now or just stay on B209 if you're happy with it.
ajsmsg78 said:
B227 for the GEM-703L was released on firmware finder. I somehow flashed the update.zip in twrp and was able to flash it without an issue. Then I did a factory reset and can confirm I'm now on stock B227. I'm gonna play around with this.
Click to expand...
Click to collapse
This is positive news, though I wish it was a full update.
Since I run TWRP I probably won't get Updater notification for it.
Please use the QUOTE feature when replying to me to get my attention. Thanks!
ajsmsg78 said:
You want the latest twrp in my twrp thread, it's the black light blue version. I would update to B212 and stay there for now or just stay on B209 if you're happy with it.
Click to expand...
Click to collapse
Btw, i installed b227 through twrp and it's working fine, haven't reseted or wiped data yet, if anything comes up I'll have to do a clean wipe
safseyed said:
Btw, i installed b227 through twrp and it's working fine, haven't reseted or wiped data yet, if anything comes up I'll have to do a clean wipe
Click to expand...
Click to collapse
well, a little later i found out it has problem with google services including google play services and play store, i tried many things to fix them but they didnt, and since i use google services very much i decided to go back to b209, and then problems started, i got stuck and phone has bricked, trying to instal b112 so that i can get back to b209 by that way, i hope it works
safseyed said:
well, a little later i found out it has problem with google services including google play services and play store, i tried many things to fix them but they didnt, and since i use google services very much i decided to go back to b209, and then problems started, i got stuck and phone has bricked, trying to instal b112 so that i can get back to b209 by that way, i hope it works
Click to expand...
Click to collapse
I'll make a stock B227 rom with google apps if you want so you can just flash it in TWRP.
ajsmsg78 said:
I'll make a stock B227 rom with google apps if you want so you can just flash it in TWRP.
Click to expand...
Click to collapse
+1
Here you go. Stock B227 Rooted, Lightly Debloated with Google Apps. I left in the stock Chinese Music Player. Kernel is from B212 so root will work. EMUI version is 4.0.3. Double tap to wake does not work in B227. I enabled it but it doesn't work. Why Huawei keeps removing features like that is a mystery to me.
https://www.androidfilehost.com/?fid=3700668719832236050
ajsmsg78 said:
Here you go. Stock B227 Rooted, Lightly Debloated with Google Apps. I left in the stock Chinese Music Player. Kernel is from B212 so root will work. EMUI version is 4.0.3. Double tap to wake does not work in B227. I enabled it but it doesn't work. Why Huawei keeps removing features like that is a mystery to me.
https://www.androidfilehost.com/?fid=3700668719832236050
Click to expand...
Click to collapse
installed this through twrp flash, works fine, multi screen not working, i think hivoice is good to be removed, it doesnt show network type on top of anthena bars, cant tell if it's 2g,3g or 4g! google related apps are not working properly, that is cant sign in using any google account using google apps, phone seems to be slower than normal and maybe a little battery drain(not sure)
safseyed said:
installed this through twrp flash, works fine, multi screen not working, i think hivoice is good to be removed, it doesnt show network type on top of anthena bars, cant tell if it's 2g,3g or 4g! google related apps are not working properly, that is cant sign in using any google account using google apps, phone seems to be slower than normal and maybe a little battery drain(not sure)
Click to expand...
Click to collapse
Do a wipe and flash again, the Google apps are working fine for me. I will release another build tonight with working multi screen and all of the hivoice stuff removed and removal of the Chinese text on the lockscreen photos. I was tied last night and needed some sleep.
ajsmsg78 said:
Do a wipe and flash again, the Google apps are working fine for me. I will release another build tonight with working multi screen and all of the hivoice stuff removed and removal of the Chinese text on the lockscreen photos. I was tied last night and needed some sleep.
Click to expand...
Click to collapse
All of a sudden Google related apps started working! Without wiping or anything, however there is a problem with Gboard, when want to open its preference it crashes and comes out, can't add more languages to keyboard, and when I try to install it from play store it downloads and installs but at the end it doesn't install at all
safseyed said:
All of a sudden Google related apps started working! Without wiping or anything, however there is a problem with Gboard, when want to open its preference it crashes and comes out, can't add more languages to keyboard, and when I try to install it from play store it downloads and installs but at the end it doesn't install at all
Click to expand...
Click to collapse
When you first sign in you have to wait a minute to let Google play services update. Then it works fine. I'll include the newest play services.
StatiXOS
Download StatiXOS for free. StatiXOS is a homebrew distribution of Android. StatiXOS is a custom ROM based on the Android Open Source Project aiming to be minimal and clean, while providing quality of life improvements and up to date security patches. This page is to provide downloads for...
sourceforge.net
4.2 has been release
"Introduce our OTA Updater!"
For those with the Chrome issue of freezing I have a fix that another user in another ROM thread accidentally found!
If you download
PH1-OTA-PQ1A.190105.090.zip
and then reboot into recovery (TWRP, be sure to disable pin on phone before hand and backup everything) then flash the above (I wiped everything first but DON'T wipe internal storage) then I did a second wipe of everything but internal storage and then I flashed 4.2 of StatiXOS and then I flashed TWRP, then I rebooted phone and set it up from new and restored everything from Cloud backup and I can confirm that I no longer have the Chrome freezing issue.
You can thank seungbaekm over in the Evolution-X 5.4 thread for this fix as he is the one that accidentally flashed the older PH-1 factory image and discovered Chrome then worked again! This should fix the issue for all the new Android 11 ROM 's out there for us folks that have the Chrome browser locking issues.
I did not even test the new 4.2 ROM on its own to see if it happens to fix the Chrome issue but I doubt that it does since it is not mentioned in the release notes. Also I have no idea if any of the other original factory images will also fix the issue, I only downloaded the one they he said he accidentally flashed and used it.
Hope this helps everyone with this issue as I know how frustrating it has been. Sure, there is the Bromite/Brave/Firefox work around, and I have been using and enjoying Bromite since 4.1 but I like having things working the way they are supposed to work.
Thanks you very much
I will test
Following this great insight about the fix of the Chromium issue, I only flashed mata PQ1A.190105.090 NOVENDOR firmware from this old thread, without wiping anything of my current StatiXOS 4.2 installation, and after booting Brave is working perfectly.
So, it seems the issue was caused not by the ROM system or vendor, but the mata QQ1A.200105.007 firmware.
As a consequence of flashing this old no system nor vendor firmware, my device baseband was downgraded, but mobile data seems to be working just fine. I guess it's possible to test newer firmware available at the referenced thread, like PQ1A.190105.112, QP1A.190711.107 or QP1A.190711.148, to identify the latest firmware free of the Chromium issue.
More good news: now Netflix is working fine, also.
UPDATE: I tried all the these firmwares and Netflix worked fine only with the Pie ones. So, PQ1A.190105.112 is the more recent mata firmware that I can use on my PH-1 with StatiXOS 4.2 in order to keep Chromium browsers and Netflix working.
aamadorj said:
Following this great insight about the fix of the Chromium issue, I only flashed mata PQ1A.190105.090 NOVENDOR firmware from this old thread, without wiping anything of my current StatiXOS 4.2 installation, and after booting Brave is working perfectly.
So, it seems the issue was caused not by the ROM system or vendor, but the mata QQ1A.200105.007 firmware.
As a consequence of flashing this old no system nor vendor firmware, my device baseband was downgraded, but mobile data seems to be working just fine. I guess it's possible to test newer firmware available at the referenced thread, like PQ1A.190105.112, QP1A.190711.107 or QP1A.190711.148, to identify the latest firmware free of the Chromium issue.
More good news: now Netflix is working fine, also.
UPDATE: I tried all the these firmwares and Netflix worked fine only with the Pie ones. So, PQ1A.190105.112 is the more recent mata firmware that I can use on my PH-1 with StatiXOS 4.2 in order to keep Chromium browsers and Netflix working.
Click to expand...
Click to collapse
This is some great news, thank you and SirDigitalKnight for the research! I haven't tried this fix yet, but I'm planning to when I flash this week if I do run into the chrome freeze problem. You mentioned this downgrades the device baseband version. I'm not too familiar with that, you did say it's working fine so far, but do you think that could cause issues in the future?
Just a question, does StatiXOS have slim recents included?
Mous3kteer said:
This is some great news, thank you and SirDigitalKnight for the research! I haven't tried this fix yet, but I'm planning to when I flash this week if I do run into the chrome freeze problem. You mentioned this downgrades the device baseband version. I'm not too familiar with that, you did say it's working fine so far, but do you think that could cause issues in the future?
Click to expand...
Click to collapse
I have no idea if using a.Pie firmware could have side effects in the future. So far, I haven't seen any.
Using the StatiXOS Telegram support group, I shared the information about the different firmwares to the devs, so I think they'll tell us if something can go wrong in the future.
Is anyone else having issues with sending a text message with this rom?
vineetbhatia said:
Is anyone else having issues with sending a text message with this rom?
Click to expand...
Click to collapse
If you have VoLTE on, turn it off
vineetbhatia said:
Is anyone else having issues with sending a text message with this rom?
Click to expand...
Click to collapse
If you have VoLTE on, turn it off
Double Post
Just reporting that I did a clean install - "Fastboot -w" on the latest working firmware (JAN20 FW, FEB20 Vendor iirc) and I'm very impressed.
Plus replaced the screen, battery, and buttons cable and now the phone is "essentially" new. Parts are actually quite cheap.
Chrome is working without issues.
360 Camera is working without issues
Haven't tried sending SMS with VoLTE On yet.
Amazing that we still a maintainer.
chanh2018 said:
If you have VoLTE on, turn it off
Click to expand...
Click to collapse
Yup, that worked. Thanks mate..
The March 10th update they pushed out through the OTA updater worked perfectly. It is nice to see we still have good support on this great phone.
SirDigitalKnight said:
For those with the Chrome issue of freezing I have a fix that another user in another ROM thread accidentally found!
Click to expand...
Click to collapse
Thank you for this! And also thanks to @aamadorj for the further investigation!
It's too much of a hassle for me to do this fix right now, and I admit I have adapted to using Bromite and Firefox, but I'll definitely keep this in mind for some other time when I feel more like it... BTW, I did check, and Chrome stil freezes on the latest 4.2 update, no surprise here.
This ROM has been working great for me, very stable, no issues, and the updates are a breeze, especially with the latest OTA updater.
kt-Froggy said:
Thank you for this! And also thanks to @aamadorj for the further investigation!
It's too much of a hassle for me to do this fix right now, and I admit I have adapted to using Bromite and Firefox, but I'll definitely keep this in mind for some other time when I feel more like it... BTW, I did check, and Chrome stil freezes on the latest 4.2 update, no surprise here.
This ROM has been working great for me, very stable, no issues, and the updates are a breeze, especially with the latest OTA updater.
Click to expand...
Click to collapse
You should be able to flash the older Pie firmware without wiping from what I have read but I have not tried that yet. I might try it with the very latest firmware of Pie, PQ1A.190105.112 and see if it screws anything up without wiping the phone. Anyway I always to a backup of the phone to the cloud and also of Whatsapp before I start messing around just in case I have to wipe and so far all my restores have worked perfectly, but yes it is a pain to have to setup wifi's and add back in BT devices and setup security and any double authentication apps you use. Getting used to it now though.
SirDigitalKnight said:
You should be able to flash the older Pie firmware without wiping from what I have read but I have not tried that yet. I might try it with the very latest firmware of Pie, PQ1A.190105.112 and see if it screws anything up without wiping the phone. Anyway I always to a backup of the phone to the cloud and also of Whatsapp before I start messing around just in case I have to wipe and so far all my restores have worked perfectly, but yes it is a pain to have to setup wifi's and add back in BT devices and setup security and any double authentication apps you use. Getting used to it now though.
Click to expand...
Click to collapse
Flashing the contents of the attached files using fastboot should make your device to use last firmware for Android Pie, without losing your current ROM installation.
aamadorj said:
Flashing the contents of the attached files using fastboot should make your device to use last firmware for Android Pie, without losing your current ROM installation.
Click to expand...
Click to collapse
OK, here is my update... Noting your comment in the other post about the downgraded baseband, I decided to exclude the modem from flashing. Flashed everything else from PQ1A.190105.112-NOVENDOR via fastboot, rebooted, and... Chrome froze again. Ugh... :\ OK. I went back to fastboot and flashed the modem - this time after the reboot the problem was fixed.
So, I'd say it's safe to conclude that the modem (baseband) is the actual component that was screwing up the Chromium-based browsers. Go figure...
This ROM is great on the PH-1. At the moment I can't get the LED to blink when notifications arrive. The setting is toggled on.
I've installed magisk, nanodroid and microg (not tried that sort of thing before!). Could that have anything to do with it?
chrisrg said:
This ROM is great on the PH-1. At the moment I can't get the LED to blink when notifications arrive. The setting is toggled on.
I've installed magisk, nanodroid and microg (not tried that sort of thing before!). Could that have anything to do with it?
Click to expand...
Click to collapse
Even with stock rom LED is not blink if you're using stock messages, try Textra and see if it works for you.