Related
*** PLEASE READ CAREFULLY BEFORE INSTALLING OR FLASHING ANY SOFTWARE POSTED IN THIS THREAD ***
The software posted here is for TESTING purposes only, The Polaris Android Linux development team or any of the posters of software or links to software on this thread, take absolutely no responsibility or liability for damage caused by the result of installing or flashing software or links to software found on this thread - correctly or otherwise, you do so on the sole understanding that you do so at your own risk.
Previous thread was closed because too big you can find lot of information into it with the search button : http://forum.xda-developers.com/showthread.php?t=555000
Hello to all of you, Android user.
This thread is the right place to talk about non-kernel related discussions, questions and requests.
Please, remember that the thread is public, so don't use bad word
So...have fun
-------------------------------------------------------------------------------------------------------------------------------
01-09-09 - new link to files for working wifi
http://www.4shared.com/dir/19593527/...a/sharing.html
From Google Code Vogue-Android:
01-09-09 - Initrd - works with unpartitioned cards, otherwise no changes.
01-09-09 - Rootfs - works with unpartitioned cards, otherwise no changes.
Reserved for future use
Reserved for future use.
Reserved for future use,
Reserved for future use-
what packages do i have to dload? everything?
nicandris said:
what packages do i have to dload? everything?
Click to expand...
Click to collapse
From the first link (4share), you took all but rootfs and initrd, these one you could download it from the other links
You should put name Android in the title to know about what is this thread
whitealien said:
You should put name Android in the title to know about what is this thread
Click to expand...
Click to collapse
Thanks for the suggestion
@Mormy
Could you give us your startup/default haret script? With script whitch you uploaded to 4shared, graphics don't work properly.
Good thing to open a clean thread to speak about testing
I'm currently testing the SquashFs version, latest on http://code.google.com/p/vogue-android/downloads/list
With this system.sqsh : http://vogue-android.googlecode.com/files/hero.zip
And this base files : http://vogue-android.googlecode.com/files/squashfsbasefiles.zip
It's very stable. With this build I haven't got anymore the 'reload UI' problem when I go back to home screen.
But it's very slow. It takes more time to launch application, wake up the phone, open settings... But the scrolling is normally fast.
Wifi doesn't work for me with it.
Maybe I'll try this one tonight : system-090109r1.img on http://code.google.com/p/vogue-hero/downloads/list
I didn't understood how works the last one with 'userinit.sh' system, so I think I will not try it
Averne said:
@Mormy
Could you give us your startup/default haret script? With script which you uploaded to 4shared, graphics don't work properly.
Click to expand...
Click to collapse
I've tried Neocore and won't start either with the 4share startup and with mine.
By the way, this the one I usually have:
Code:
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz
#
# The following kernel parameters are useful
# ppp.username - The username used to connect to the network when dialing
# ppp.password - The password used to connect to the network when dialing
# ppp.apn - Set apn of your provider
# ppp.nostart - Set ppp.nostart=1 to disable starting the ppp connection on boot
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 1, use 1 for best power savings
# board-htcpolaris.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
# lcd.density - Defaults to 160, 128 shows more on screen
#
set cmdline "board-htcpolaris.panel_type=3 ppp.apn=tre.it ppp.username=none ppp.password=none pm.sleep_mode=1 mddi.width=324 mddi.height=432 no_console_suspend board-htcpolaris-battery.battery_capacity=1350 clock-7x00.mddi=0xa51 mddi_client_vogue.vsync=0"
boot
Averne said:
@Mormy
Could you give us your startup/default haret script? With script whitch you uploaded to 4shared, graphics don't work properly.
Click to expand...
Click to collapse
Try with '1' instead of '3' for "board-htcpolaris.panel_type" property.
Averne said:
@Mormy
Could you give us your startup/default haret script? With script whitch you uploaded to 4shared, graphics don't work properly.
Click to expand...
Click to collapse
if you mean neocore then yes that is broken in this kernel.
if you are having display issues, then try changing the panel type or try to be more specific on what you mean by "graphics dont work properly".
Ok, this is my default.txt file:
Code:
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz
set cmdline "board-htcpolaris.panel_type=0 ppp.apn=orange ppp.username=orange ppp.password=orange pm.sleep_mode=1 mddi.width=336 mddi.height=448 lcd.density=160 no_console_suspend board-htcpolaris-battery.battery_capacity=1350 mddi_client_vogue.vsync=0"
boot
With this settings display works fine, but you must disconnect usb cable before press [Run] button in haret.
Hi ,
with the last files taken from bally site I have wifi working but data connection li ke previous release taken from vogue-android sometime starts sometimes no.
And with this files I can't start calling it creashes.
No Gps..
Why start up logo is changed? and button mapping?
Averne said:
Ok, this is my default.txt file:
Code:
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz
set cmdline "board-htcpolaris.panel_type=0 ppp.apn=orange ppp.username=orange ppp.password=orange pm.sleep_mode=1 mddi.width=336 mddi.height=448 lcd.density=160 no_console_suspend board-htcpolaris-battery.battery_capacity=1350 mddi_client_vogue.vsync=0"
boot
With this settings display works fine, but you must disconnect usb cable before press [Run] button in haret.
Click to expand...
Click to collapse
why have you got lcd density set at 160 and width and height at 336x448?
this is not my startup file. you should try that first.
Does somebody know what are the benefits of using 'squash FS' system instead of old standard system.img?
Kiiv said:
Does somebody know what are the benefits of using 'squash FS' system instead of old standard system.img?
Click to expand...
Click to collapse
if you are really interested: (from http://groups.google.com/group/andr...ad/e4ce4f06f982d51b/30fa2b5deb6533b2?lnk=raot)
I think it would be a good idea to compress /system/bin and /system/
lib at least with squashfs, I have done this on a couple ubuntu and
gentoo systems and it actually increased performance and space
significantly!
Reasons (short version): decompressing data is faster than reading it
from the hard drive, in most current computers, especially when you
have multiple programs reading from the disk, causing thrashing, and/
or when the data on the disk is fragmented. You can read more details
about what was done and the results on http://forums.gentoo.org/viewtopic-p-4732709.html#4732709
Squashfs is intended for general read-only file system use and in
constrained block device/memory system, it can also be combined with a
union mount system like unionfs and aufs for read/write access.
We will be able to improve android boot time, app launch time, and
increase space, what more could we ask for? Maybe a little bit more
ram? Whats up with compcache too?
So now we just need to compile squashfs-tools for android and
experiment, im pretty damn excited to try this!
Also ubifs has lzo compression, not sure how that would work either,
it seems ubifs is favored over jffs2 and yaffs2
Well right now it looks squashfs+lzma wont be in the kernel until
2.6.30 found this via:
http://www.squashfs-lzma.org/
So I think we are left with UbiFS with lza compression but I have no
idea on how to add it to the kernel, and test this out, im really
interested in seeing some results and doing some benchmarks, if
someone more knowledgeable than me can help out that would be awesome
defcon
found a nice pdf comparing the filesystems:
http://free-electrons.com/doc/flash-filesystems.pdf
Benchmarks Of Yaffs2, JFFS2, SquashFS, & UBIFS:
http://free-electrons.com/pub/conferences/2008/elce/flash-filesystems...
Seems like people are already using ubifs on android:
http://groups.google.com/group/android-porting/browse_thread/thread/a...
Reference:
http://forums.gentoo.org/viewtopic-p-4732709.html#4732709
http://jt0.org/news/squashing_usr_and_the_2629_kernel
Hum, thank you for the link
So I don't understand why it's slower with squash FS on my phone... I will try to find other discussions on the subject.
I bought this mobile last week and the first thing I wanted to do was rooting that phone. Sorry, I have no time to explain in more detail these instructions, but I will answer your questions if any. To do so, I downloaded:
* SP_Flash_Tool_v3.1304.0.119
* MTK Droid Tools 2.4.3
* MTK Usb Drivers
* MTK Tools ( h t t p s : / / g i t h u b . c o m / b g c n g m / m t k - t o o l s ) ( h t t p : / / forum .xda-developers . com / showthread.php?t=1587411 )
* Busybox
* su
(Where can I upload this files so I can make them available for you?)
So, once we have installed the drivers:
- Connect the mobile to your USB port
- Run MTK Droid Tools (Patience, for me it was so unstable so I had to try several times)
- Wait while all the information is on screen (if you can't see all the information, or loss connection with your mobile, maybe you have installed the wrong USB Driver).
- Extract Blocks map information into a scatter file
- Close MTK Droid tools
- Open SP Flash Tool and load the scatter file we have created.
- Look into the BOOTIMG Partition (begin and end address), and calculate the size (begin address of the next partition and begin address of this partition, they are in hex; sometimes we can look into the end address). I did the calc with bc (enter obase=16; ibase=10; before anything) (linux) but I suppose there are online tools to do it. For me, my begin address was 0x2780000 and the next partition (RECOVERY for me) starts in 0x2D80000 so the size will be 0x600000
- Go to the read back tab, add a read back file with start addrees the start address of BOOTIMG (0x2780000 for me) and the size we have calculated. Creating a boot.img for your mobile.
- Press read back button
- Turn off the phone, extract the battery and wait for 4-5 seconds, connect the battery again, SP Flash Tool will notice you have connected the phone and will start extracting the image (if this doesn't occur, you may have to disconnect USB and reconnect with the phone turned off. We will see two or three progress bars and finally we will see a green disc on screen.
( It would be a good idea doing the same with RECOVERY partition, for backup )
- We have the boot image of our phone in our hard disk, so lets extract it.
- I did this in linux, but reading the docs of mtk tools you can do it in Windows:
- Run:
$ mtk-tools-master/unpack-MT65xx.pl boot.img
- Now I have boot.img-kernel.img and boot.img-ramdisk folder so enter this folder and edit init.rc with your favourite text editor:
* after "on early-init" write:
- chmod 755 /rtkt/run.sh
- chmod 755 /rtkt/busybox
* find services start (the first line starting with "service ***** /****/**** and, before that write:
service root_now /rtkt/busybox ash /rtkt/run.sh
oneshot
- Save and close the file
- Then create the folder rtkt (you can name it whatever you want, but make sure to replace all rtkt with the name you want)
- Copy there:
* busybox
* su
* Superuser.apk.gz (optional)
- Create a new file in that folder (run.sh) and write this contents inside:
/rtkt/busybox cp /rtkt/su /system/bin/
/rtkt/busybox cp /rtkt/su /system/xbin/
/rtkt/busybox chmod 06755 /system/xbin/su
/rtkt/busybox chmod 06755 /system/bin/su
# Install Busybox.
/rtkt/busybox cp /sbin/busybox /system/xbin/
/rtkt/busybox chmod 06755 /system/xbin/busybox
# Done.
/rtkt/busybox mount -o ro,remount /system
- So, we have now to repack the file, to do so:
mtk-tools-master/repack-MT65xx.pl boot.img-kernel.img boot.img-ramdisk root-boot.img
- Then, we run again SP Flash Tool, with the scatter file we had before, and select only BOOTIMG and chose the file we have created, then hit download button, repeat the process, turn off phone, extract the battery, connect to the USB and reconnect the battery to flash the file. When we reboot the phone, we will be root. But we can exceed BOOTIMG size, so that's because saving RECOVERY was a good idea.
That's what I did. But i must say I'm no responsible of what you do with your phones, be aware that any false step can cause a disaster in your phone.
thanks for your job.
can you upload the BOOTIMG file for us.
thaks again
eukisei said:
thanks for your job.
can you upload the BOOTIMG file for us.
thaks again
Click to expand...
Click to collapse
BOOTIMG is designed for your phone, your phone may become unstable with my BOOTIMG, but anyway, I'll upload it.
Do you know a free service where I can upload it? Maybe Mega?
blakeyed said:
I bought this mobile last week and the first thing I wanted to do was rooting that phone. Sorry, I have no time to explain in more detail these instructions, but I will answer your questions if any. To do so, I downloaded:
* SP_Flash_Tool_v3.1304.0.119
* MTK Droid Tools 2.4.3
* MTK Usb Drivers
* MTK Tools ( h t t p s : / / g i t h u b . c o m / b g c n g m / m t k - t o o l s ) ( h t t p : / / forum .xda-developers . com / showthread.php?t=1587411 )
* Busybox
* su
(Where can I upload this files so I can make them available for you?)
So, once we have installed the drivers:
- Connect the mobile to your USB port
- Run MTK Droid Tools (Patience, for me it was so unstable so I had to try several times)
- Wait while all the information is on screen (if you can't see all the information, or loss connection with your mobile, maybe you have installed the wrong USB Driver).
- Extract Blocks map information into a scatter file
- Close MTK Droid tools
- Open SP Flash Tool and load the scatter file we have created.
- Look into the BOOTIMG Partition (begin and end address), and calculate the size (begin address of the next partition and begin address of this partition, they are in hex; sometimes we can look into the end address). I did the calc with bc (enter obase=16; ibase=10; before anything) (linux) but I suppose there are online tools to do it. For me, my begin address was 0x2780000 and the next partition (RECOVERY for me) starts in 0x2D80000 so the size will be 0x600000
- Go to the read back tab, add a read back file with start addrees the start address of BOOTIMG (0x2780000 for me) and the size we have calculated. Creating a boot.img for your mobile.
- Press read back button
- Turn off the phone, extract the battery and wait for 4-5 seconds, connect the battery again, SP Flash Tool will notice you have connected the phone and will start extracting the image (if this doesn't occur, you may have to disconnect USB and reconnect with the phone turned off. We will see two or three progress bars and finally we will see a green disc on screen.
( It would be a good idea doing the same with RECOVERY partition, for backup )
- We have the boot image of our phone in our hard disk, so lets extract it.
- I did this in linux, but reading the docs of mtk tools you can do it in Windows:
- Run:
$ mtk-tools-master/unpack-MT65xx.pl boot.img
- Now I have boot.img-kernel.img and boot.img-ramdisk folder so enter this folder and edit init.rc with your favourite text editor:
* after "on early-init" write:
- chmod 755 /rtkt/run.sh
- chmod 755 /rtkt/busybox
* find services start (the first line starting with "service ***** /****/**** and, before that write:
service root_now /rtkt/busybox ash /rtkt/run.sh
oneshot
- Save and close the file
- Then create the folder rtkt (you can name it whatever you want, but make sure to replace all rtkt with the name you want)
- Copy there:
* busybox
* su
* Superuser.apk.gz (optional)
- Create a new file in that folder (run.sh) and write this contents inside:
/rtkt/busybox cp /rtkt/su /system/bin/
/rtkt/busybox cp /rtkt/su /system/xbin/
/rtkt/busybox chmod 06755 /system/xbin/su
/rtkt/busybox chmod 06755 /system/bin/su
# Install Busybox.
/rtkt/busybox cp /sbin/busybox /system/xbin/
/rtkt/busybox chmod 06755 /system/xbin/busybox
# Done.
/rtkt/busybox mount -o ro,remount /system
- So, we have now to repack the file, to do so:
mtk-tools-master/repack-MT65xx.pl boot.img-kernel.img boot.img-ramdisk root-boot.img
- Then, we run again SP Flash Tool, with the scatter file we had before, and select only BOOTIMG and chose the file we have created, then hit download button, repeat the process, turn off phone, extract the battery, connect to the USB and reconnect the battery to flash the file. When we reboot the phone, we will be root. But we can exceed BOOTIMG size, so that's because saving RECOVERY was a good idea.
That's what I did. But i must say I'm no responsible of what you do with your phones, be aware that any false step can cause a disaster in your phone.
Click to expand...
Click to collapse
Thank you for you work. I have the same phone. Please send boot.img
MTK6589 Opinions/Sellers?
Thanks for sharing your Root Process. Im looking for a MTK6589 Phone, but am unsure where to buy. I see a lot of people that claim the phone takes too long or have left bad reviews about the sellers responses to broken/defective items out the box. Im looking for an honest opinion but google and Youtube only brings the sellers opinions. How is this ISA phone and does anyone have any knowledge on the sellers and any other MTK6589 phones?
Edit* What can you do with a boot.img? Is the bootloader unlocked? I dont understand this process.
cyrusalmighty said:
Thanks for sharing your Root Process. Im looking for a MTK6589 Phone, but am unsure where to buy. I see a lot of people that claim the phone takes too long or have left bad reviews about the sellers responses to broken/defective items out the box. Im looking for an honest opinion but google and Youtube only brings the sellers opinions. How is this ISA phone and does anyone have any knowledge on the sellers and any other MTK6589 phones?
Click to expand...
Click to collapse
Well I bought both of mine through Geek buying and the first phone arrived in 12 days of my order being put into their website.
Second phone also arrived in a decent time of about 9 days. Both are the "ISA" A19Q, but miine phones have A19S on the info screen and have Android 4.2.1 installed.
Both phones work, Although only thing I found irregular was that the IMEI numbers are all showing the following info:
IMEI Code : 35839204229xxxx
IMEI legitimate Phone Model: iGlo W102
Manufactured by : Oteda Industrial Co Ltd
Frequency bands : GSM 1800, GSM 1900, GSM 900, GSM850 (GSM800), WCDMA FDD Band I, WCDMA FDD Band II, WCDMA FDD Band III, WCDMA FDD Band IV, WCDMA FDD Band IX, WCDMA FDD Band V, WCDMA FDD Band VI, WCDMA FDD Band VII, WCDMA FDD Band VIII
This is true for others who have gotten the phones through some Vendors.
I used my T-Mobile SIM and worked right away. I am in Mass USA so I get service where I am unless I go to the Quabin Res area.
nivo88t said:
Well I bought both of mine through Geek buying and the first phone arrived in 12 days of my order being put into their website.
Second phone also arrived in a decent time of about 9 days. Both are the "ISA" A19Q, but miine phones have A19S on the info screen and have Android 4.2.1 installed.
Both phones work, Although only thing I found irregular was that the IMEI numbers are all showing the following info:
IMEI Code : 35839204229xxxx
IMEI legitimate Phone Model: iGlo W102
Manufactured by : Oteda Industrial Co Ltd
Frequency bands : GSM 1800, GSM 1900, GSM 900, GSM850 (GSM800), WCDMA FDD Band I, WCDMA FDD Band II, WCDMA FDD Band III, WCDMA FDD Band IV, WCDMA FDD Band IX, WCDMA FDD Band V, WCDMA FDD Band VI, WCDMA FDD Band VII, WCDMA FDD Band VIII
This is true for others who have gotten the phones through some Vendors.
I used my T-Mobile SIM and worked right away. I am in Mass USA so I get service where I am unless I go to the Quabin Res area.
Click to expand...
Click to collapse
Do you get 3G data with T-Mobile? Or any other carrier? I dont really understand this part where they say : 2G GSM 850/900/1800/1900MHZ 3G: WCDMA 2100 MHZ. Does this mean 3G only runs on WCDMA?? Tmobiles 3G frequency is 1700/2100 MHZ, 1900 MHZ according to Wikipedia.(lol). It says 4G also uses 1700/2100 MHZ, but I would think 3G would not work here.
~Darklords Development Team~
Is GPS working for you? I want to use phone for navigation.
ISA A19Q no operating system
Hello friends
First I want to thank you for the excellent work you are doing for all users.
I have a cell phone and try A19Q ISA ROOT do believe I have become a brick.
Right now you have installed the Recovery TWR 2.4 and I do not have a SO. I've had to do a system wipe.
The phone stays on the boot logo ISA. Recovery so I can enter the TWR but I know I can get it back.
I think we need an official or cooked ROM to install from the SD.
I hope someone can help me, I'm pretty desperate.
Thanks again for all your work.
Star 7589 Dragon Cart Ali Express
Cusiek27 said:
Thank you for you work. I have the same phone. Please send boot.img
Click to expand...
Click to collapse
Free flip cover Star S7589 Quad Core MTK6589 1.2GHz 1GB RAM 5.8 HD Screen Smart Phone Android 4.2.1 3G GPS
You came to the right place.
Dragoncarts Guo at Ali Express sell this. I got my phone in 7 days. Florida USA.
After a month of research.
These guys answer my quires in a day. The ad says white. I asked if they have grey and they said yes. The phone is awesome for $213 including shipping! VERY FAST! 12500 on benchmark. That is faster than Samsung Note II.
Comes with case, a backplate,pen,2 3200 ion batteries,screen protector installed,charger but it is European so you have to buy an adapter. I use my Samsung adopter DC 5 volts 500 milliamps micro plug.
Or u just buy universal adapter.
It is very well made.
Dont have to root it as it comes with no bloatware and plenty of space. Interesting and a very happy surprise it installs all my apps on the SD cards 32gbs. U can go to settings/apps and have an app moved to internal but not necessary. it is Jellybean. it can use live wallpaper. It uses Google maps, My tracks all the GPS stuff I love. Turn by turn navigation is much much improved! All it lacks is a compass but works fine with GPS.
View Ranger by the way along with google lets you download free maps you can use offline! So you do not even need a data plan.
The seller is the best! Dragon wrote back to me in perfect English.
The other sellers were not clear.
I was afraid to order from China.
The way ALI Express works is this. You pay ALI. They hold the money. Once you get the phone and play with it then you confirm order and seller is paid. Only then.
If you are not satisfied they do not get the $$ until you are! Took alot of work but it paid off for me. I got a $700 phone for $213!
Will work on 3g network. has dual sim. I am T-mobile.
Good Luck Tell them Duncan sent you they may give you special treatment. Free shipping is China Express but they liked me so sent it USPS!
Got it in 7 days instead of 15.
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
cyrusalmighty said:
Do you get 3G data with T-Mobile? Or any other carrier? I dont really understand this part where they say : 2G GSM 850/900/1800/1900MHZ 3G: WCDMA 2100 MHZ. Does this mean 3G only runs on WCDMA?? Tmobiles 3G frequency is 1700/2100 MHZ, 1900 MHZ according to Wikipedia.(lol). It says 4G also uses 1700/2100 MHZ, but I would think 3G would not work here.
~Darklords Development Team~
Click to expand...
Click to collapse
T-mobile I have and Star 7589 Quad works great.
Also GPS for Nav also. I bought this for work over GPS tracker.
I found a simple solution on the web
---------- Post added at 07:52 AM ---------- Previous post was at 07:46 AM ----------
I can not give link. I have a little message. Located on the forum androidiani.com
Discussione:
[MT6589] Root generico per i cellulari basati sul MT6589
Root.img
Here is my boot.img
Caution! It may make unstable your phone.
https://mega.co.nz/#!iQ4wXTjZ!crPfRBBBFsrA_URnsGomyF0l_CcCaAyZjRpglbzcqsQ
I rooted my isa with the italian site just fine (adb and pdanet via windows). Peace of cake without problems....I could reboot to some kind of cwm recovery mode as well.
But...I messed around with rom toolbox app and wanted to change the system font. Now it won't boot and it freezes on the isa logo (pdanet on my windows reports that the phone is connected). What is the standard button combination to go to cwm and do a factory reset? Or can I change the font from within windows (via adb or so)?
Please help..
I tried to do a factory reset with http://stackoverflow.com/questions/10817721/wipe-data-factory-reset-through-adb .. it did not help.
Should I adb push the above boot.img or am I making things worse then?
Isa a19q easy root method
please check bottom for download links
1.Make sure USB debugging is enabled. Go to settings > developer options > enable USB debugging
2.Install the PDAnet Drivers in the installation they ask for a brand select other.
After installing the drivers unplug your phone
3.Extract the Motochopper MTK6589 Auto Root folder from the .rar download
4.Connect your phone to PC
5.Run run.bat from the Motochopper MTK6589 Auto Root folder
6.Press any key and wait while it roots your phone
7.After finished, now reboot
8.You''re phone is rooted please check root with root checker. This worked for me and if you brick your phone just reinstall the isa a19q rom
rom is available here: check .txt file on the bottom for the rom
please press thank button
tijsh111 said:
please check bottom for download links
1.Make sure USB debugging is enabled. Go to settings > developer options > enable USB debugging
2.Install the PDAnet Drivers in the installation they ask for a brand select other.
After installing the drivers unplug your phone
3.Extract the Motochopper MTK6589 Auto Root folder from the .rar download
4.Connect your phone to PC
5.Run run.bat from the Motochopper MTK6589 Auto Root folder
6.Press any key and wait while it roots your phone
7.After finished, now reboot
8.You''re phone is rooted please check root with root checker. This worked for me and if you brick your phone just reinstall the isa a19q rom
rom is available here: check .txt file on the bottom for the rom
please press thank button
Click to expand...
Click to collapse
yes that method worked like a charm...
but now I have the problem that I used the rom toolbox pro to install different things without a backup. With a reboot it just stops with the isa logo...
I think I will try the option for a custom rom for the star b94m (almost the same as the isa): http://www.needrom.com/mobile/star-b94mb943-2/
I installed the stock rom again described on http://blog.geekbuying.com/index.ph...are-for-isa-a19q-android-4-2-os/#.UYjH3sfCTVg
Rooted it there after. That worked...but superuser.apk is not pushed. Tried to install it from market..but no go. ..strange
Sent from my A19Q using xda app-developers app
ISA A19Q fix for superuser
Try to reinstall the stock rom.
root it again.
install root checker and push on check.
wait a few seconds (around 10 seconds) till su pop up comes up the first time you use SU it's handeling very slow.
After you tried this SU will work fast.
This is what I did after i rooted it you just have to wait a few seconds.
please tell us if this worked for you
tijsh111 said:
Try to reinstall the stock rom.
root it again.
install root checker and push on check.
wait a few seconds (around 10 seconds) till su pop up comes up the first time you use SU it's handeling very slow.
After you tried this SU will work fast.
This is what I did after i rooted it you just have to wait a few seconds.
please tell us if this worked for you
Click to expand...
Click to collapse
Finally it worked.. Thanks! Now looking for custom roms instead stock
Henkl said:
Finally it worked.. Thanks! Now looking for custom roms instead stock
Click to expand...
Click to collapse
Is there any custom Roms available for this phone or any other of these knockoffs? I bet they are harder to find. I have ported Roms from similiar devices (I.e. Xperia arc or neo to Xperia Play), but its a little harder for different brands. But if this phone has been out a while someone should have ported some AOSP based Roms like CM and PA/AOKP or MIUI by now right.
Edit* Installing Superuser.apk from market may not work for you. You probably have to install in system/app folder(maybe using root explorer) but you would need to have root already.lol.
Darklord Development Team
WiFi COUNRTY PROBLEM solving
Hello!
We, who did buy phones from other countries using internet shopping,
instead of joy face the problem of WiFi-service functioning.
WiFi scan not works or shows network; but there is written NOT IN RANGE..
Problem resides in new WifiCountryCode, which phone recieves from our SIM-card.
But this new WifiCountryCode is not known for internal WiFi-program,
so it does not know which WiFi rules use.
During 2 mounth of tries I found following 3 ways to solve:
1. ARHD7.3 ROM has not THIS WiFi problem! Bravo!
(sorry, didn't check previous versions).
2. program WiFi Fix by Fardjad.
This program updates WiFi Country Code on boot and afterwards.
For most ICS roms it works good, for AOSP roms less good.
Requires: before SHUTDOWN or REBOOT WiFi should be turned off.
Slightly annoying.
On AOSP roms first WiFi TURN ON stucks;
needs 1-2 minutes to TURN OFF stucked WiFi and then second TURN ON works.
Greatly annoying!
Current version is WiFix Manager V1.32;
Author promised to solve this problem.
3. in AOSP CM10.1, before starting WiFi, goto
System settings > WiFi > Advanced > WiFi region code >>
and if here is nothing selected (your country not in list), press United States (or Europe?),
then get back from this Advanced menu and only now TURN ON WiFi.
Wifi scan now should work.
...Until next restart....
also before SHUTDOWN or REBOOT you should turn off WiFi to prevent stuck on start..
(this setting is not available in SuperXE 4.2.2 build_6)
********************************************
Buttt.. seems I found solve before WiFix author, YESS!
How this happened:
greatly annoyed, I learned about USB-debugging and Logcats and ApkTool.
here is lines from Logcat (XX replaces new country code):
Code:
D/MccTable( 636): updateMccMncConfiguration: mcc=..., mnc=..
D/MccTable( 636): locale set to null_XX
D/MccTable( 636): WIFI_COUNTRY_CODE set to XX
I/WifiService( 445): WifiService trying to set country code to XX with persist set to true
Where is this MccTable? not found such file..
Web search gives me this:
https://android.googlesource.com/pl.../com/android/internal/telephony/MccTable.java
this IS source, where is written updateMccMncConfiguration code from line 169 to 208.
and actually we need to disable these lines:
Code:
189 if (mcc != 0) {
190 setTimezoneFromMccIfNeeded(context, mcc);
191 setLocaleFromMccIfNeeded(context, mcc);
192 setWifiCountryCodeFromMcc(context, mcc);
193 }
Because Timezone you can setup in settings > Date& Time
and LOCAL parameters are set in most roms in file "/system/build.prop":
Code:
ro.product.locale.language=en
ro.product.locale.region=US
(if not, make it..)
Alternate "mild" edition:
you can disable only line setWifiCountryCodeFromMcc(context, mcc);
and live rest 2 updater lines.
now let me guess, this program code should be inside of some JAR file..
exactly in "/system/framework/telephony-common.jar"
I did decompile this file with ApkTool:
Code:
apktool d telephony-common.jar
it made output as folder "telephony-common.jar.out" and there is file:
"telephony-common.jar.out/smali/com/android/internal/telephony/MccTable.smali"
and inside are above mentioned lines:
Code:
.line 189
if-eqz v2, :cond_0
.line 190
invoke-static {p0, v2}, Lcom/android/internal/telephony/MccTable;->setTimezoneFromMccIfNeeded(Landroid/content/Context;I)V
.line 191
invoke-static {p0, v2}, Lcom/android/internal/telephony/MccTable;->setLocaleFromMccIfNeeded(Landroid/content/Context;I)V
.line 192
invoke-static {p0, v2}, Lcom/android/internal/telephony/MccTable;->setWifiCountryCodeFromMcc(Landroid/content/Context;I)V
.line 195
:cond_0
lets gently change line 189:
Code:
.line 189
goto :cond_0
in newer android, there is also second call to setWifiCountryCodeFromMcc, so comment out it also.
so program will jump over unwanted updates!
now recompile back "telephony-common.jar" with command:
Code:
apktool b -f -d telephony-common.jar.out
and in folder "telephony-common.jar.out/dist" you will find it out.
from original file do copy of directory "META-INF" in new file with any archive manager.
now we should put "telephony-common.jar" in phone.
for this we need:
ROOT access,
with ES_file_manager >Tools >Root Explorer >Mount R/W > mount /system RW,
replace telephony-common.jar and set proper file attributes (-rw-r--r-),
mount /system R
and afterwards do REBOOT.
on new BOOT there will be "Android updates" files ...
AND WiFi problems HAVE GONE!!
Now you even can do SHUTDOWN or REBOOT with TURNED ON WiFi
AND WiFi will connect before SIM card joins GSM network!!!
Tools used:
ADB
JDK
ApkTool
ES file manager
Notepad+ or Edit+
Credits to:
[TOOL/GUIDE GB/ICS/JB] Decompile/Recompile apk | jar | sign + Basic editing xml/smali
in attachments I put:
google_src_code,
patched_MccTable.smali
*************
For SuperXE 4.2.2 build_6 (MD5=2DBDDB534A7CA6DE627EF75FCE3E7CF0)
more steps reqiured.
SuperXE has other "telephony-common.jar" MD5=C8917C386BA7FD24A0203058BFDC17F5,
so we again perform above steps for patch;
See attached file "SUXE_patched_telephony-common.jar"
now we should replace "telephony-common.jar" in phone.
with ES_file_manager >Tools >Root Explorer >Mount R/W > mount /system RW,
replace telephony-common.jar and set proper file attributes (-rw-r--r-),
Extra step 1
click on "/system/build.prop" and open in ES Note Editor;
seek line
ro.product.locale.region=GB
and change GB to US; confirm OK for save file.
mount /system R
Extra step 2
because of first boots, in Settings database is written our country code,
which should be US.
for this: install "Sqlite Editor", run, grant ROOT access. after program finds
& lists databases, look for & open "Settings Storage" > settings.db > global:
find "wifi_country_code", select it and press menu button > Edit Record;
change value to US and press "save"
if this step is too hard for you, from "wipe data, cache, dalvik"... but many
other stuff will be erased..
Now do REBOOT.
on new BOOT there will be "Android updates" files ...
*************
for VIPERS roms you should patch framework2.jar
then
Extra step 1
click on "/system/build.prop" and open in ES Note Editor;
add line
ro.product.locale.region=US
confirm OK for save file.
Extra step 2
because of first boots, in Settings database is written our country code,
which should be US.
for this: install "Sqlite Editor", run, grant ROOT access. after program finds
& lists databases, look for & open "Settings Storage" > settings.db > global:
find "wifi_country_code", select it and press menu button > Edit Record;
change value to US and press "save"
if this step is too hard for you, from "wipe data, cache, dalvik"... but many
other stuff will be erased..
Now do REBOOT.
*************
attached file CM1012_20130806_telephony-common.jar for AOSP CM10.1.2 albinoman887,
which has original telephony-common.jar file with MD5=90521F154A0E37302496D88DA879EA75
*************
attached file CM102_20131028_telephony-common.jar for AOSP CM10.2 albinoman887
*************
attached file CM11_20131119_Albinoman887_telephony-common.jar for AOSP CM11 albinoman887
"mild" patch!
*************
in MIUIandroid framework.jar should be patched; code line is 188;
also copy from old to new archive file preloaded-classes
attached file for MIUIandroid 3.10.25
attached file for MIUIandroid 3.11.15, use this also up to MIUIandroid 3.12.27
*************
attached file Inspiration_v1.0.1_framework2.jar for Inspiration v1.0.1
which has original framework2.jar file with MD5=8f67ad19fe72513489972cbfd76f244c
*************
attached file Elegancia_Sense_4.1_v7.5.0_framework2.jar for Elegancia Sense 4.1 v7.5.0
which has original framework2.jar file with MD5=a9b34b25201d592f41677c94039b520d
*************
attached file CM10_bruce_20130914_framework.jar for CM10 bruce 20130914,
*************
attached file VIPERS1.6.3_framework2.jar for VIPERS 1.6.3,
which has original framework2.jar file with MD5=3d16f3818e0ce6b7fe201f9188408491
*************
attached file ViperS2-0-0_framework2.jar for ViperS 2.0.0,
which has original framework2.jar file with MD5=c7bd6fa8a2f0fd210f21fd223089d094
*************
attached file ViperS5-0-0_framework2.jar for ViperS 5.0.0
*************
attached pack ViperS5-1-0
*************
attached pack ViperS5-2-0
*************
android1234567 accepts this patch already
http://forum.xda-developers.com/showthread.php?t=2320657
*************
CyanogenMod12 by ivanich 20150118
attached pack CyanogenMod12_by_ivanich_20150118_telephony-common.jar
after replacement go to settings > Backup & reset > Factory data reset and RESET PHONE
*************
seems, many people done patch in their sources:
https://github.com/search?utf8=✓&q=setWifiCountryCodeFromMcc&type=Code&ref=searchresults
HTCZ715E!
some tips:
yep, good tip:
on first installation of ROM, start it without SIM-card.
in attachments some patched files per users requests.
added for [ROM][N1] Evervolv Kitkat 4.4
added for [ROM]Cyanogenmod 11 | kernel 3.4 | dominos_liberty
added for [ROM] [4.4.2] [8.Feb 2014] CyanogenMod 11.0 | KitKANG | PRE-ALPHA | v0.5 for HTC Desire
thanks for share working for me !
Sent from my HTC Sensation using xda premium
question
The explained steps are too much; so as I realized we just need to replace the attached files with the original ones; right?
mohammad0089 said:
The explained steps are too much; so as I realized we just need to replace the attached files with the original ones; right?
Click to expand...
Click to collapse
So you want replace MY ATTACHMENTS with original ones??? : : : ) ) )
HTCZ715E said:
So you want replace MY ATTACHMENTS with original ones??? : : : ) ) )
Click to expand...
Click to collapse
yes if i can; i have the same problem which you mentioned; so can i replace them in all cyanogen mod roms?:
mohammad0089 said:
so can i replace them in all cyanogen mod roms?:
Click to expand...
Click to collapse
patched_AOSP_telephony-common.jar file is for AOSP CM10.1
original file MD5=30BBC2690C8A08A4C5D977BC27D42885
SUXE_patched_telephony-common.jar file is for SuperXE 4.2.2 build 6
original file MD5=C8917C386BA7FD24A0203058BFDC17F5,
CM10-1-20130720_telephony-common.jar for AOSP CM10.1.2, which has original
telephony-common.jar file with MD5=00c7d16ae721ef64dfc1bbf2aee4bf92
one of this file you should copy on sdcard, rename as telephony-common.jar,
then with RootExplorer, replace original file in /system/framework
if original file is same, you can replace.
if not, upload it here.
patch for CM10.1.2 update
patch for CM10.1.2 update.
look in first post
what about sense 4 ROMs? I have same issues on all Sense 4 roms
Fix works perfectly for albinoman887's CM10.1 ROM ! Thanks a ton!
I'm sorry sir but i didn't understand... I've just to replace attached files or i edit first them?
Wifi solve is a flashable file for any rom?
Inviato dal mio HTC Sensation
Please forgive the noob question, but there is a lot of information in the OP, which of the attachments did you run on Albinoman's ROM?
you two,
read post 1 & 7
http://forum.xda-developers.com/showpost.php?p=43773366&postcount=7
HTCZ715E said:
you two,
read post 1 & 7
http://forum.xda-developers.com/showpost.php?p=43773366&postcount=7
Click to expand...
Click to collapse
Thanks
works great on miui 3.7.19
shayan538 said:
Thanks
works great on miui 3.7.19
Click to expand...
Click to collapse
wait, at least in MIUI 3.7.12 I did not sow telephony-common.jar.
instead, did you modified bouncycastle.jar?
mamarda said:
what about sense 4 ROMs? I have same issues on all Sense 4 roms
Click to expand...
Click to collapse
write here ROMs and I will look.
ok, for MIUI MccTable is in framework.jar, thus I creates patch for it. see 1 post
Hi. Where is MccTable for Sense 4 ROMs? I didn't find this strings in framework.jar.
P.S. Found it in framework2.jar. Fixed by the same code. Thnks. It works like a charm.
Mikhei777 said:
Hi. Where is MccTable for Sense 4 ROMs?
Click to expand...
Click to collapse
yeo, search for string updateMccMncConfiguration
HTCZ715E said:
yeo, search for string updateMccMncConfiguration
Click to expand...
Click to collapse
I've patched it already. Thanks again.
I tested the GPS a little and it seems to be fixed. It keeps updating every second without resetting after few seconds. Then I checked the configuration files (/etc/gps.conf) and there is indeed a difference:
Code:
# 0x1: RRC CPlane
# 0x2: RRLP UPlane
# 0x4: LLP Uplane
-A_GLONASS_POS_PROTOCOL_SELECT = 0
+A_GLONASS_POS_PROTOCOL_SELECT = 0x2
where "-" is in .175 and "+" is in .182. "#" lines are just comments in the conf file describing the values. Just "0" felt wrong indeed, by convention it should have been at least 0x0. probably someone messed up while editing.
Also I tried disabling the tweak for the wifi showing the exclamation mark:
Code:
settings put global captive_portal_detection_enabled 1
as explained in my post and it seems fine. But that needs more time testing.
Can confirm the GPS is now working as I've took the updated file from the ftf
[email protected] said:
Can confirm the GPS is now working as I've took the updated file from the ftf
Click to expand...
Click to collapse
Can you make flashable zip or just zip them and share? I'm on vacation and don't have pc to mess with ftf's here
Thanks
Sent from my D2303 using Tapatalk
Here this is where I've grabbed all of the updated files from I'm still on 18.6.A.0.175 you can download the required files and push straight to system manually no unzipping or flashing required
http://forum.xda-developers.com/showthread.php?p=64648145
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.