TL;DR: I am looking for some info from developers on which Xoom tablets running which tablets *fully* support Android USB Host API and whether I can reflash a EU-shipped device with the these img's.
Can a kernel be patched to fully support USB Host API?
--
I have a Motorola Xoom tablet that was originally shipped with MZ601 software (EU). I am trying to get it to work with a USB HID device. My code works well until I want to transfer data using controlTransfer - it then returns -1 as if there was no device connected (although the USB device was detected before by my code, using Host API).
I did some research and it turns out that US-shipped Xooms support Host API and that there was a guy who flashed the device to US MZ604. I did the same but the software img provided by Motorola was Android 3.0 which doesn't support Host API by default. I then tried to update this to 3.1 and 3.2 but it didn't work (tried with many copies, hazard triangle appears in the middle of installation process). Tried with rooted device.
I am now looking for any other software/ROM that proved to support USB Host API.
I would also like to know if in general Xoom tablets have hardware USB OTG support (meaning: whether flashing my device with a specific ROM should work).
Here you can find list of Android devices that was checked if they support USB Host API:
usbhost.chainfire.eu (based on USB Device Info app that lets you submit info after checking for Host API support). Most of Xoom devices are fully supporting Host API.
Thank you very much for taking on this project. Looking forward to the first release.
Sent from my Galaxy Nexus
ews said:
TL;DR: I am looking for some info from developers on which Xoom tablets running which tablets *fully* support Android USB Host API and whether I can reflash a EU-shipped device with the these img's.
Can a kernel be patched to fully support USB Host API?
--
I have a Motorola Xoom tablet that was originally shipped with MZ601 software (EU). I am trying to get it to work with a USB HID device. My code works well until I want to transfer data using controlTransfer - it then returns -1 as if there was no device connected (although the USB device was detected before by my code, using Host API).
I did some research and it turns out that US-shipped Xooms support Host API and that there was a guy who flashed the device to US MZ604. I did the same but the software img provided by Motorola was Android 3.0 which doesn't support Host API by default. I then tried to update this to 3.1 and 3.2 but it didn't work (tried with many copies, hazard triangle appears in the middle of installation process). Tried with rooted device.
I am now looking for any other software/ROM that proved to support USB Host API.
I would also like to know if in general Xoom tablets have hardware USB OTG support (meaning: whether flashing my device with a specific ROM should work).
Here you can find list of Android devices that was checked if they support USB Host API:
usbhost.chainfire.eu (based on USB Device Info app that lets you submit info after checking for Host API support). Most of Xoom devices are fully supporting Host API.
Click to expand...
Click to collapse
Look in the Development section and you should find a number of possibilities. If you look in my signature you will see the configuration that I'm running with success and I have full USB host capabilities (must use proven OTG cable, usually need a third party app like Drive Mount to successfully mount my HDD, but thumb drives mount just fine automatically on the EOS roms). Check out the long and rambling guide in my sig. as there is a bit of info on why you kept getting the error when in process of flashing recovery...
Thank you. In the meantime I've found an easy solution which works just fine. AFAIK the best choice if you want to have USB Host API support is to install the original MZ604 Android Honeycomb 3.0 software (downloaded from Motodev) and then update it to ICS. Then root the device (after applying few software updates).
Hi all,
yesterday I succeeded in rooting the new ASUS MeMo Pad HD 7.
Model-Number: ME173X
Android version: 4.2.1
Kernel version: 3.4.5
HD 7 Build: ME173X_WW_User_4.2.1.75146_20130523 release keys
PC operating system: Win.. XP
USB-Driver I used (but there's WdfCoInstaller.dll missing, which I already had on my PC):
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME172V/ASUS_Android_USB_drivers_for_Windows_20130415.zip
Maybe this more complete package would work, too (I didn't try that):
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/ASUS_Android_USB_drivers_for_Windows.zip
Method to root is by using motochopper.
You can follow the next steps in general as described in
http://forum.xda-developers.com/showpost.php?p=40129120&postcount=1
One important thing:
motochopper didn't recognize my HD7 at once, so I did the following
(while being connected with PC via USB and motochopper waiting for device):
While USB debugging activated, go to USB settings an connect it as
integrated CD drive. motochopper will automatically recognize it
and continue with rooting process.
And last but not least:
As always, all you do is your own risk and I'm not responsible for any damage.
Good luck
-----------------------------
EDIT 2013-07-06:
Above procedure for rooting works with the new HD7 update, too (but you have to re-root after the update).
Build version after the update: ME173X_WW_user_4.2.2.51129_20130619 release-keys
-----------------------------
Description for Linux users:
- use motochopper package from link above
- login as root
- extract package
- open console and change to directory where you extracted the package
- chmod +x adb.linux
- chmod +x run.sh
- Check your HD7 will be recognized:
-> ./adb.linux status-window
-> shows "State: unknown"
-> connect HD7 (with usb debugging enabled, connecting as MTP device)
-> above started adb command should show now "State: device"
-> HD7 recognized - greatful, you're ready
-> press Strg-C to abort
- (optional) for more information about your HD7 you can enter: ./adb.linux devices -l
-> this should show something like: D6OKCXXXXXXX device usb:1-3 product:WW_memo model:ME173X device:ME173X
- ./run.sh
-> follow instructions on screen
- you're done
-----------------------------
EDIT 2013-07-16:
Above procedure for rooting works with new HD7 update (but you have to re-root after the update).
Build version after the update: ME173X_WW_user_4.2.2.91525_20130711 release-keys
Thank you very much! I had it attached as a camera, worked fine as well. ^^
ASUS memopad HD 7
quaddler said:
Hi all,
yesterday I succeeded in rooting the new ASUS MeMo Pad HD 7.
Click to expand...
Click to collapse
Thats awesome, but how did you already purchase this when it hasnt hit the stores yet? I cant wait to replace my MSI Winpad with this bad boy
RELLC said:
Thats awesome, but how did you already purchase this when it hasnt hit the stores yet? I cant wait to replace my MSI Winpad with this bad boy
Click to expand...
Click to collapse
Amazon.de apparently received an early batch and sent them out immediately. I was surprised as well, target date was 10 July to 1 August and it arrived 25 June^^
SoWhy said:
Amazon.de apparently received an early batch and sent them out immediately. I was surprised as well, target date was 10 July to 1 August and it arrived 25 June^^
Click to expand...
Click to collapse
sooo jealous. :highfive:
SoWhy is right.
I bought mine last Thursday at amazon.de.
There were also some dealers on Amazon‘s marketplace who had some.
hi
it is possible to enable usb host with the root on the memo pad hd 7?
Memo Pad HD7
Thanks...
Have been looking for Root ever since I got one Device on Friday.
Root seems to be working fine.
By the way - Saturn Germany got stock now as well (blue and white back) - bought 3 more today.
The MircoSD is taking 32GB straight from my Galaxy Note 10.1 - the resolution is really cool and no errors or problems.
I personally can do no more than highly recommend the Tablet.
Change - just made a firmware update to 4.2.2 - root is gone...
Sky0ne said:
Change - just made a firmware update to 4.2.2 - root is gone...
Click to expand...
Click to collapse
Thanks for reporting that.
Do you mean that rooting is no more possible with 4.2.2 firmware?
Current version 4.2.1 is somewhat buggy. Launcher FC quite often. It would make sense to download 4.2.2 but it would be unusable for me without root
LaizyJumper said:
Thanks for reporting that.
Do you mean that rooting is no more possible with 4.2.2 firmware?
Current version 4.2.1 is somewhat buggy. Launcher FC quite often. It would make sense to download 4.2.2 but it would be unusable for me without root
Click to expand...
Click to collapse
Well, I wouldn't say not possible. It's just that I couldn't manage to get it done de same way so far.
The 4.2.2 update is pretty neat. The tablet works more stable now. The home screen rotates and the display is much brighter.
Just some update features I discovered.
As of root I was hoping that someone would discover some different, more stable way - like CF-Autoroot on the Nexus 7.
I‘m a little busy at the moment.
Hope to have a look on 4.2.2 on weekend.
Sky0ne said:
Well, I wouldn't say not possible. It's just that I couldn't manage to get it done de same way so far.
The 4.2.2 update is pretty neat. The tablet works more stable now. The home screen rotates and the display is much brighter.
Just some update features I discovered.
As of root I was hoping that someone would discover some different, more stable way - like CF-Autoroot on the Nexus 7.
Click to expand...
Click to collapse
Does it show the Android version 4.2.2 in System information? Or is it still 4.2.1 (and it says ME173X_WW_user_4.2.2.51129_20130619 in build number)?
I have Android version 4.2.1 and build number mentioned above. And I got it rooted without any problems on Linux (the way it is described in OP).
LaizyJumper said:
Does it show the Android version 4.2.2 in System information? Or is it still 4.2.1 (and it says ME173X_WW_user_4.2.2.51129_20130619 in build number)?
I have Android version 4.2.1 and build number mentioned above. And I got it rooted without any problems on Linux (the way it is described in OP).
Click to expand...
Click to collapse
Funny - you're right... :laugh: Didn't see that one.
Got exactly the same build no (ME173X_WW_user_4.2.2.51129_20130619 release-keys) and above Android Version 4.2.1...
I am running Linux too - couldn't make root so far - did you use some different settings?
Sky0ne said:
Funny - you're right... :laugh: Didn't see that one.
Got exactly the same build no (ME173X_WW_user_4.2.2.51129_20130619 release-keys) and above Android Version 4.2.1...
I am running Linux too - couldn't make root so far - did you use some different settings?
Click to expand...
Click to collapse
Nothing special... The only trouble I had in the beginning was to get ADB responding properly. I have different versions of adb utilities on my PC. Other ones did not work, the one in motochopper package worked fine. I was using the original motochopper files. I had to use root rights (running script with sudo) to get it working. Might be that this is the showstopper for you
Full sequence should be something like this:
* Switch on developer mode (multiple clicks in about box on build number).
* Find developer options in the setup menu. Switch on USB debuging.
* Plug in the USB cable, try different USB modes (I think I made it using cd-rom mode, modes can be changed in storage settings under advanced "USB computer connection" menu from the top-right corner menu icon).
* Run the motochopper script with sudo.
LaizyJumper said:
Nothing special... The only trouble I had in the beginning was to get ADB responding properly. I have different versions of adb utilities on my PC. Other ones did not work, the one in motochopper package worked fine. I was using the original motochopper files. I had to use root rights (running script with sudo) to get it working. Might be that this is the showstopper for you
Full sequence should be something like this:
* Switch on developer mode (multiple clicks in about box on build number).
* Find developer options in the setup menu. Switch on USB debuging.
* Plug in the USB cable, try different USB modes (I think I made it using cd-rom mode, modes can be changed in storage settings under advanced "USB computer connection" menu from the top-right corner menu icon).
* Run the motochopper script with sudo.
Click to expand...
Click to collapse
Thanks a lot - have been trying that already - not working with mine...
Sky0ne said:
Thanks a lot - have been trying that already - not working with mine...
Click to expand...
Click to collapse
Have you tried running adb.linux separately? Does it connect?
Run it first with "kill-server" argument and then "shell", for example.
If you get shell access then you should be able to root it. If not then there is something wrong in your pc setup or tab settings.
I assume it worked before you updated your HD7.
Hello everybody,
as promised I got some time to deal with the update.
In short, rooting with this update works, too (but you have to re-root after the update).
Build version after the update shows: ME173X_WW_user_4.2.2.51129_20130619 release-keys
I updated post #1 and put some additional information for linux users.
Regards
quaddler
My Memo HD7 arrived yesterday an it is great ! (amazon.de / germany)
Rooting procedure worked on Win 7 without installing new drivers very easy.
To turn on Developer Mode to switch USB debugging Mode on:
Build Number:
ME173X_WW_user_4.2.1.75146_20130532
Open “Settings”.
Scroll to the bottom and tap “About phone” or “About tablet”.
At the “About” screen, scroll to the bottom and tap on “Build number” seven times.
You will see a “You are now a developer!” message pop up, then you know you have done it correctly.
Done!
You can now enable/disable it under “Settings” -> “Developer Options” -> “Debugging” ->” USB debugging”.
Then just run "run.bat" from motochopper (http://forum.xda-developers.com/showpost.php?p=40129120&postcount=1) and
follow the instructions.
Sorry for offtopic but any info what's new in this update 4.2.2? I'm from Bulgaria and don't have update yet. l'm still with first version ME173X_WW_User_4.2.1.75146_20130523.
Sent from my ME173X using Tapatalk 2
update
Hello,
I have a question:
After the root any new Update can be install over the air?
[Edit] Additional testing has shown that this issue will occur when other modules are statically included using the same method below. The latest test I ran was to include the KMEMLEAK module by itself into a build. That build failed in almost exactly the same timeframe as described below - 76 hours. Has anyone had any success including modules in their builds and if so what method did you use to include them?
Hello all. I am working on a project using the TF300T and dock connector provided by Asus. We're having an issue where the tablet freezes after 3 days of operation. Some background:
We are building CM 10.2 stable version from source and installing it on the device.
We are including the FTDI_SIO module in the kernel build by modifying the kernel config file in the CM source code directory at ./kernel/asus/tf300t/arch/arm/configs/tf300t_cm10_defconfig. The CONFIG_USB_SERIAL_FTDI_SIO line is uncommented and its value is set to 'y'
After flashing the build to the device, we are using the Settings application to set the device to stay awake when it is connected to power, enable USB debugging and ADB over network, and connect it to a wireless network. We then put the tablet in a dock and connect the dock to power. The tablet is then left to run.
In the above scenario, the tablet will run for around 3 days and then fail. In most instances the tablet's screen will turn black and will not respond to touches. Attempting to ADB to the tablet also fails. In a few cases the tablet appears to try to reboot itself and gets as far as the CM boot animation, but then hangs there and eventually the screen freezes. In both scenarios a hard reboot is necessary. If we run a build of CM 10.2 stable that does not include the FTDI module, it runs properly for 7 days plus (we stopped the test ourselves at that point because the build appeared to be fine it did not crash).
Does anyone have experience including the FTDI driver in a build for the TF300T? Did you have a similar experience? We have looked at logcat output, tombstone files, and stacktrace files but have not been able to pinpoint a root cause. Any help or advice would be much appreciated. Thanks.
Hi
Im trying to connect easycap to my photon q 4G LTE xt897, and i have some problems. Nothing works and im feel totally stupid
Some details:
Sim mod
CM 12.1-20160319-NIGHTLY-xt897
Android version: 5.1.1
Kernel: 3.0.101-g1a2acd3
EasyCap with utv007 chipset.
EasyCap Viewer
And that does not work. EasyCap Viewer showing: No device attached.
Next i installed Usb Host Controller, and it shows:
Version number: 0.44
S3C USB Host driver NOT found!
Root hub is not present, USB Host mode not active or not available!
USB Host Diagnostics shows:
ANDROID API
Claims support: Yes
Classes found: Yes
Device detected: No
ROOTED API
Claims support: N/A
Device detected: N/A
KERNEL
Claims support: Yes
Device detected: No
I found this topic http://forum.xda-developers.com/photon-q-4g-lte/development/cyanogenmod-12-1-photon-q-t3073781 and theres link to kernel. There is easycap in drivers/staging.
Now im stuck. Totally stuck, and dont know what to do next, to make this working...
Anyone, any advice?
The intention behind this thread is to share some experience of a little project where I try to migrate the Sony Xperia Shinano devices (based on Qualcomm MSM8974 chipset with a Broadcom BCM4339 wifi/bluetooth chip) from the old bcmdhd wifi driver to a close-to-mainline brcmfmac driver. I want to share the progress and status here, and maybe get some hints. It is work in progress, and for sure it still contains some mistakes - I haven't done something like this before and am still learning.
Why?
The Shinano devices are still maintained by the LineageOS, and some devices are currently on the official LineageOS 17.1 stream.
The kernel however is terribly outdated, based on msm-3.4
There are some wifi issues with all LineageOS-based ROMs since years, like weak 5GHz connections and non-working wifi in some countries. There are some hacks around that, but they work (afaik) by practically disabling the kernel-level regulatory system by e.g. setting a static country code like "DE".
I am curious if we can improve that by updating the kernel drivers and network/wifi components, and maybe also the firmware (to the latest release available from Broadcom, 6.37.34.43 ?) . I got the ideas from Sonyxperiadev/Loire (+ related platform config), the Linux Backport Project and other MSM8974 based devices.
Working so far:
Did a few tests only so far, STA with WPA2 and p2p (hotspot) seem to work
Wifi connection is stable on 2,4GHz on 00 world regulatory domain (tested on a Z3 and a Z3c)
5GHz manually setting a country code (could only test DE)
Switching countries / setting new regulatory domains is now working, too
Download speed looks OK to me, in my case at least better than before Download >60MBit, Upload >30 Mbit on some initial tests.
Not working yet:
WifiHAL (qcom-caf) does not work correctly. This may create multiple issues, tbd.
Connection bandwidth seems to be not reported correctly
I don't know if wowlan works (interrupts working?)
Stability: After 1-2 days without reboot wifi sometimes crashes but immediately reconnects. Reason not yet understood.
Patches & Picks
Kernel:
backported and configured brcmfmac, cfg800211 wireless configuration API and wireless network stack from linux-stable v5.8 by adopting the compatibility patches from the linux backporting project.
updated Shinano device tree, updated Z3, Z3c and Z2 (Z2 test needed!) defconfigs (unset bcmdhd and enabled brcmfmac) and removed board-sony_shinano-wifi.o in the arch-msm makefile
Note: the backported drivers and compatibility-patches are located in a separate backports/ subdirectory
Sorry, this is work in progress and contains some hacks, to be cleaned up later
--> https://github.com/LineageOS/androi...1...Tom1000:lineage-17.1-driver-backport-v5.8
Vendor blobs / device z3(c): removed proprietary firmware and replaced that by publicly available firmware for bcm4339 on linux-firmware.git
z3c --> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
z3 --> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
Shinano-common: Use qcwcn instead of bcmdhd WLAN device, serve wpa_supplicant_overlay.conf
--> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
msm8974-common: raise wpa_supplicant version (unknown if we need that) and update sysfs node for MAC address
--> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
As a follow up, the driver seems to work quite stable already. I still have issues with nl80211 private commands, as a mainline brcmfmac does not seem to accept command strings passed via a libnl control socket like this:
qcwcn/wpa_supplicant_8_lib/driver_cmd_nl80211.c
@vknecht : I've seen your backporting work for the Xperia X. How does this work for Loire with SODP? Does e.g. a "set country code request" work for you, and if so, can you give me a hint?
I need some feedback from people with a Z3/Z3c/Z3Dual to see if the new builds work in affected countries, where 5GHz wifi is not working on current custom ROMs like e.g. LineageOS 17.1. I would appreciate if you test one of the builds below and send me a full log.
WARNING: The following builds are for debugging purpose only. Do not use them as a daily driver, as they have SELinux disabled and create excessive log entries. This ROM is not stable, some features are not yet implemented.
Xperia Z3 (D6603):
lineage-17.1-20201227-UNOFFICIAL-z3.zip
drive.google.com
Xperia Z3c (D5803):
lineage-17.1-20201227-UNOFFICIAL-z3c.zip
drive.google.com
Xperia Z3Dual (D6633) Update 10Jan2021:
lineage-17.1-20210110-UNOFFICIAL-z3dual.zip
drive.google.com
Z3Dual build has SELinux enabled already
If possible, please follow these steps:
Install ROM with TWRP for Android 10 or Lineage Recovery for 17.1
If possible, factory reset the device. Be sure to get rid of all former Magisk modules which try to set country codes etc. (if applicable).
Make sure a a local SIM card is inserted.
Boot the device. Enable mobile data and enable wifi. Connect to a 5GHz capable access point or router.
Optional: Increase log buffer size. This may be required as the kernel is set to verbose logging, creating large logfiles. You can do this via settings/developer options or via adb:
adb logcat -G 8M
Get close to the access point or router, so that the device would prefer 5GHz over 2.4GHz.
Reboot the device and let wifi connect. Check if device uses a 5Ghz connection. (Ignore bandwith / speed for now.)
Create a logfile, e.g. with this command via adb:
adb shell logcat -d -b all > mylog.log
The logfile may contain private information, so I recommend not to post them public. Together with the ligfile I would like to know
a) Wifi 5GHz working?
b) The country in which you have tested this.
nice work bro.
i live in iran and in this build my Z3 Dual detects wifi networks while the sim card is also connected.
but in 10 Jan 2021 update my phone can't detect my router's wifi unfortunately while the previous build could do it without problems.
hotspot turns on on both 2.4GHz and 5GHz.
in this new build cellular network and data are working.
Thanks @TheShadowOfAGhost20 !
Can you please run a root shell (E.g. by connecting via ADB, run adb root, then adb shell) and then
$> iw wlan0 scan → scan for networks
and then look if your access point is found?
Furthermore, can you please check which WiFi channel this particular router ist set to, and if possible the bandwidth?
Mr.Tom_Tom said:
Thanks @TheShadowOfAGhost20 !
Can you connect via ADB, run adb shell and then
$> iw wlan0 scan → scan for networks
and then look if your access point is found?
Furthermore, can you please check which WiFi channel this particular router ist set to, and if possible the bandwidth?
Click to expand...
Click to collapse
i did that but got this error: "/system/bin/sh: iw: inaccessible or not found"
but i found the cause: my wifi channel was set to 12. i changed it and then got detected!
TheShadowOfAGhost20 said:
i did that but got this error: "/system/bin/sh: iw: inaccessible or not found"
Click to expand...
Click to collapse
Sorry I forgot to write that you have to do this as root, I edited the post accordingly.
TheShadowOfAGhost20 said:
i found the cause: my wifi channel was set to 12. i changed it and then got detected!
Click to expand...
Click to collapse
Tha sounds reasonable. However, Channel 12 should be usable in IR.
Mr.Tom_Tom said:
Sorry I forgot to write that you have to do this as root, I edited the post accordingly.
Tha sounds reasonable. However, Channel 12 should be usable in IR.
Click to expand...
Click to collapse
channel 13 has detection problem too. the others are OK
.sorry erroneous post
New buildsFeedbacks have been positive so far, so here are some updated builds.
Lineage Sources* as of 20 March 2021
Kernel sources* based on Linux 3.4.113 with backported wifi from 5.8.18 plus cherry-pick of the following changes:
bluetooth: fixed #ifdef'ed PM callbacks ("BTLowPower" wakelock) 50f16d16b32871c5ce97b029e68692008c848bb2
SELinux enforcing
Build as userdebug, normal loglevels
* For links to sources see 1st post. Z3Dual does not have official Lineage17.1 sources yet, bringup is in progress.
Xperia Z3 (D6603):
HiDrive
hidrive.ionos.com
md5: d7aaf1fea120df3e2aad10b3a2d32226
Xperia Z3c (D5803):
HiDrive
hidrive.ionos.com
md5: 456ff87441c3a63e8dc8c7a8d03bdf39
Xperia Z3Dual (D6633):
HiDrive
hidrive.ionos.com
md5: 1848681c82d608f3212f1ace621327cb
As always, feedback is welcome.
Has anyone found a bug/installed this latest build yet? lineage-17.1-20210320-UNOFFICIAL-z3dual
Finding this super stable.. The only thing that does not work for me is the advanced boot recovery that goes back into system, But that's a known issue.
Mr.Tom_Tom said:
New buildsFeedbacks have been positive so far, so here are some updated builds.
Lineage Sources* as of 20 March 2021
Kernel sources* based on Linux 3.4.113 with backported wifi from 5.8.18 plus cherry-pick of the following changes:
bluetooth: fixed #ifdef'ed PM callbacks ("BTLowPower" wakelock) 50f16d16b32871c5ce97b029e68692008c848bb2
SELinux enforcing
Build as userdebug, normal loglevels
* For links to sources see 1st post. Z3Dual does not have official Lineage17.1 sources yet, bringup is in progress.
Xperia Z3 (D6603):
HiDrive
hidrive.ionos.com
md5: d7aaf1fea120df3e2aad10b3a2d32226
Xperia Z3c (D5803):
HiDrive
hidrive.ionos.com
md5: 456ff87441c3a63e8dc8c7a8d03bdf39
Xperia Z3Dual (D6633):
HiDrive
hidrive.ionos.com
md5: 1848681c82d608f3212f1ace621327cb
As always, feedback is welcome.
Click to expand...
Click to collapse
hi mr.tom. it's perfect as always, found no bug except wifi signal power, it's weak compared to stock roms but there was no difference in speeds. maybe it's because of wifi icon that shows little weaker signal.
and about overheating: i didn't test this build for long but while working with it i have noticed that my device is cooler than previous builds, maybe it's because of this new kernel.
i have recorded 4k for about 7 minutes then my phone rebooted i think that was because of too much heat, then i've reinstalled stock rom, however, stock rom's camera won't let me record much and the app shuts down because of heat, so i can't find out if stock rom can record 4k at least without rebooting.
i need to test this build for more time i hope the heating is now gone
and one question: can you port cyberian camera mod for these roms? or is that possible?
netwave said:
Has anyone found a bug/installed this latest build yet? lineage-17.1-20210320-UNOFFICIAL-z3dual
Finding this super stable.. The only thing that does not work for me is the advanced boot recovery that goes back into system, But that's a known issue.
Click to expand...
Click to collapse
lineage os recoveries have these problems yet, there's no fix for that, only the developer can fix it. currently the twrp works if you flash it to FOTAKernel partition but i think the twrp is useless because it doesn't install these builds.
Surely better to do: fastboot boot recovery-20201012-TESTING-z3dual.img rather than a "flash" recovery. What would be the point in flashing a recovery if its not working.
Hey
Thanks @Mr.Tom_Tom for new build and @TheShadowOfAGhost20 for testing dev builds!
today i installed the new release
but i have some problems with recovery and boot
after installing Lineage i cannot boot to recovery again
i tried adb, android advanced boot options and "fastboot boot image.img"
none of them taken me to recovery mode
so i needed to install Magisk , OpenGApps , and rom itself with adb sideload and reboot to system because i can't boot to recovery again
i'm now installing my apps for daily usage testing - i need about one or two week to test and use and see if anything is wrong or not
for now WiFi problem is gone , i have full wifi access and both sims antenna
again , thanks to everyone puts effort on this project (and sorry for bad English)
i will update this post if i found anything
navidmafi said:
today i installed the new release
but i have some problems with recovery and boot
after installing Lineage i cannot boot to recovery again
i tried adb, android advanced boot options and "fastboot boot image.img"
none of them taken me to recovery mode
Click to expand...
Click to collapse
If your going to settings\system\developer options\advanced restart\power\restart recovery , Forget it! this method doesn't work for now, & will only boot you back into Lineage. It's an issue that hopefully get's fixed in the future.
But here's a better way of entering recovery without having to flash it...
Check all your drivers are installed correctly & make sure you have the correct recovery to hand.
Here's what I Command:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot recovery-20201012-TESTING-z3dual.img
Good luck!
Hey again
Thanks to @netwave i can now boot to recovery without problems by going to fastboot from adb , and booting image directly by "fastboot boot"
while using devices after installing new release , i have a problem with WiFi connectivity
when i lock the screen by power button , the wifi disconnects
for example i use whatsapp a lot and when screen is locked wifi is not connected
i checked power settings - and even set the battery profile to "Quick" (and battery saver is off) but it did not help
is this a bug or a feature?
navidmafi said:
Hey again
Thanks to @netwave i can now boot to recovery without problems by going to fastboot from adb , and booting image directly by "fastboot boot"
while using devices after installing new release , i have a problem with WiFi connectivity
when i lock the screen by power button , the wifi disconnects
for example i use whatsapp a lot and when screen is locked wifi is not connected
i checked power settings - and even set the battery profile to "Quick" (and battery saver is off) but it did not help
is this a bug or a feature?
Click to expand...
Click to collapse
Have you tried without Magisk installed? Don't use v22.0 what ever you do as it disables WiFi
Ow
I'm using Magisk and it is version 22.0
and even root not works
should i reflash ?
Edit : Ok i'm flashing again now
navidmafi said:
Ow
I'm using Magisk and it is version 22.0
and even root not works
should i reflash ?
Click to expand...
Click to collapse
Install the Magisk uninstall.zip from recovery
when your back in Lineage your still have a disabled WiFi as Magisk does not uninstall correctly.
So Install the original boot extracted from the Lineage.zip to get things working again.
- adb devices
- adb reboot bootloader
- fastboot devices
- fastboot flash boot boot.img
- fastboot reboot
Then your be sorted.