{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
KatKiss Marshmallow ROM
Asus TF300T Q&A Thread
Please note that this version is made for and tested on the TF300T model.
Thanks to keep this thread for the TF300T
Rom Thread: http://forum.xda-developers.com/transformer-tf300t/development/rom-t3237867
-
Long time starting whilst whilst "optimizing App 1 of 1"
Great job Tim,
Have successfully installed ROM 007 and recommended GAPPS. Works well, but on restart spends several minutes with “Android is starting optimizing App 1 of 1”.
I have checked the forum and others have mentioned this but have not spotted a fix.
Any advice?
Thanks
DPR59 said:
Great job Tim,
Have successfully installed ROM 007 and recommended GAPPS. Works well, but on restart spends several minutes with “Android is starting optimizing App 1 of 1”.
I have checked the forum and others have mentioned this but have not spotted a fix.
Any advice?
Thanks
Click to expand...
Click to collapse
not sure,
I don't have that issue.
Try to format /cache and dalvik-cache to force a full optimize process.
Maybe something went wrong whent art tried to optimize one app.
Did it do that from the 1st install or after you restored some of your apps ?
Would help to find out which app it is exactly.
If it is still doing it after the cache and dalvik format,
reboot and Grab a logcat right after it is done optimizing the 1 of 1 app.
timduru said:
not sure,
I don't have that issue.
Try to format /cache and dalvik-cache to force a full optimize process.
Maybe something went wrong whent art tried to optimize one app.
Did it do that from the 1st install or after you restored some of your apps ?
Would help to find out which app it is exactly.
If it is still doing it after the cache and dalvik format,
reboot and Grab a logcat right after it is done optimizing the 1 of 1 app.
Click to expand...
Click to collapse
Tim, thanks for a prompt response. I have now done a clean install, including a factory reset and data format.
Problem still present on second boot, with only apps in your recommended GAPPS package installed.
Then installed ES File Explorer and Chainfire's LiveBoot to create the logcat.log file. However, I don’t have the knowledge to understand the output, even with the help of google.
I then wiped cash and dalvik and on restart the optimization process moves along at a reasonable pace, but spends a long time optimizing app 69 of 72. Not sure if this helps, and remember this is with ES File Explorer and Liveboot installed.
Any advice would be appreciated.
Regards
DPR59 said:
Then installed ES File Explorer and Chainfire's LiveBoot to create the logcat.log file. However, I don’t have the knowledge to understand the output, even with the help of google.
Click to expand...
Click to collapse
post the logcat file here.
timduru said:
post the logcat file here./
Tim, sorry but can not work out how to post the file.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
DPR59 said:
Great job Tim,
Have successfully installed ROM 007 and recommended GAPPS. Works well, but on restart spends several minutes with “Android is starting optimizing App 1 of 1”.
I have checked the forum and others have mentioned this but have not spotted a fix.
Any advice?
Thanks
Click to expand...
Click to collapse
i have the same problem not a big issue just a bit annoying
[email protected] said:
i have the same problem not a big issue just a bit annoying
Click to expand...
Click to collapse
Seems to be google gms app taking too much time to optimize for users who left /data as ext4
I'll increase the timer in V008,
but if you change /data to f2fs that should be faster and work fine too.
It seems to be the difference between those who have the issue and those who don't: /data ext4 Vs f2fs
timduru said:
Seems to be google gms app taking too much time to optimize for users who left /data as ext4
I'll increase the timer in V008,
but if you change /data to f2fs that should be faster and work fine too.
It seems to be the difference between those who have the issue and those who don't: /data ext4 Vs f2fs
Click to expand...
Click to collapse
hey, sorry for the noob question but how do i change to f2fs and also the browser seems to block going on google sites that are advertised if i try go on bookings.com for example through a google search it says err connection refused
[email protected] said:
hey, sorry for the noob question but how do i change to f2fs
Click to expand...
Click to collapse
Wipe => Advanced wipe
check the box for data then click on Repair or change file system
then click F2FS
and also the browser seems to block going on google sites that are advertised if i try go on bookings.com for example through a google search it says err connection refused
Click to expand...
Click to collapse
That's the adblocker included.
What is the hostname in the url? I can remove that to let it go through.
timduru said:
Wipe => Advanced wipe
check the box for data then click on Repair or change file system
then click F2FS
Click to expand...
Click to collapse
it seems I'm very unlucky lol, I tried doing this but get an error that says file system could not be changed or something like that, I tried some other sollutions on google but none of them worked, I still get the same error
[email protected] said:
it seems I'm very unlucky lol, I tried doing this but get an error that says file system could not be changed or something like that, I tried some other sollutions on google but none of them worked, I still get the same error
Click to expand...
Click to collapse
You need to use a recovery that supports it and is not buggy.
ie use the KANG TWRP linked in the 1st post of the rom
(Some of the TWRP out there won't support formatting F2FS correctly.)
timduru said:
You need to use a recovery that supports it and is not buggy.
ie use the KANG TWRP linked in the 1st post of the rom
(Some of the TWRP out there won't support formatting F2FS correctly.)
Click to expand...
Click to collapse
thanks this solved everything, you really are a mastermind
DPR59 said:
timduru said:
post the logcat file here./
Tim, sorry but can not work out how to post the file.
Click to expand...
Click to collapse
Tim, update
have now changed /data to f2fs and installed version 008 of the ROM, not added any of my apps yet but so far no apps optimizing on a restart. Thanks for you help with this, donation on the way, and keep up the great work.
Paul
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Screen rotation cure?
I have found that with rotation control app installed, but NOT running, auto rotate appears to work for apps I am using, if rotate screen is enabled in display properties.
No need for manual rotation, indeed, the rotation app is not running, just installed then stopped in app properties.
So far works every time for me
Hey Tim just for curiosity sake would there be any benefit in having cache and system as f2fs aswell? If so can you make the next update compatible I tried doing it just to see if it would work but was just stuck on the meerkat screen so I put system and cache back to ext4
Fantastic work, Timduru. I installed the 08 without a problem and without changing partition to F2FS. Installation and App optimization took less than 10 min. I got frustrated though because of the autorotation issue and the lack of marshmallow support (card access) of some apps (i.e. Dropsync). With the 09 and the autorotation issue solved I will go back to MM. Thanks for your effort :good::good::good::good:
I actually hadn't touched my TF300t for the last year. But with your great roms - it is a pleasure to use it again.
MPSmart said:
Fantastic work, Timduru. I installed the 08 without a problem and without changing partition to F2FS. Installation and App optimization took less than 10 min. I got frustrated though because of the autorotation issue and the lack of marshmallow support (card access) of some apps (i.e. Dropsync). With the 09 and the autorotation issue solved I will go back to MM. Thanks for your effort :good::good::good::good:
I actually hadn't touched my TF300t for the last year. But with your great roms - it is a pleasure to use it again.
Click to expand...
Click to collapse
Is 7 --> 8 --> 9 dirty flashable?
Google Play Wont Download apps
I installed the ROM but for some reason none of the apps will install from Google Play. They start downloading and stay downloading forever - never actually downloading.
Any suggestions....
Thanks
Jay
timduru said:
You need to use a recovery that supports it and is not buggy.
ie use the KANG TWRP linked in the 1st post of the rom
(Some of the TWRP out there won't support formatting F2FS correctly.)
Click to expand...
Click to collapse
Thanks for all your work on this ROM.... A noob here, am using the KatKiss Lollipop v030 and it is the best. Have tried to install KatKiss Marshmallow v009, seems to be slow as i suspect am doing it wrong, here is the steps i did using TWRP 2871.
1. Full Wipe = success
2. Flash KatKiss Lollipop v009, flash super su, flash gapp (in that order) = success
3. Wipe cache/davlic = success
4. Tried to change data to f2fs with twrp 2871 = not allowed or error or failed
5. Reboot to system = tablet booted to marshmallow but very slow even though i let it optimize for an hour and a
half.
Questions:
1. When should i change the data from ext4 to f2fs? Is it before step 1 or after step 1, step 2?
2. I also see some post that i should unmount, how to do that and in which step should i do unmount?
3. Maybe TWRP 2871 is the culprit?
I update TWRP by flashing the latest TWRP(zip file). The problem now is the latest twrp(2872) is an img file.
Will that img file be flash to update my TWRP?
Have returned back to KatKiss Lollipop v030. Sorry for all this troubles, this tablet is my only computer and you made it very fast. Helps me with my studies. If someone can help me?
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FINALLY THE GREAT GUYS HERE ARE SUCCESSFULL IN BRINGING CYANOGENMOD 7.2 FOR OUR BELOVED EXPLORER
cyanogenmod 7.2 is a free, community built, aftermarket firmware distribution of android 2.3.7 (gingerbread), which is designed to increase performance and reliability over stock android for your device.
Click to expand...
Click to collapse
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Code:
desclaimer--
#you are flashing this rom (which i may add is awesome) on your own risk
#we are not responsible for any bricked devices or fried sd cards
FIRST OF ALL I HAVE NO HAND IN COMPILING THIS ROM I AM JUST BUILDING A NEW NOOB FRIENDLY THREAD (No offence to noobs as i am kinda one myself :silly: ) CREDITS BELOW
Working Features--
- WiFi
- Hardware acceleration
- RIL
- Gps
- Audio
- Usb Mass Storage
- Bluetooth
- USB Tethering
- Fm Radio
- Everything else except below
Not Working--
- Camera
- Phone sometimes reboots when playing videos
Click to expand...
Click to collapse
NOW INTRUCTIONS--[--Unlock bootloader and root your explorer (if you haven't already) follow this link http://forum.xda-developers.com/showthread.php?t=1415223 to root. Dont create a partition just yet.
--Download cm-7-20120807-UNOFFICIAL BUILD #4-pico.zip from mediafire link below and copy it anywhere on sdcard.
--Download gaaps from link below and copy it on sdcard
--Boot into recovery
-- (optional but recommended) go to backup and restore and select backup. This will backup your phone just as it is so that if u ever wanna revert back you can just restore from recovery. (Thanx Liverpool_fan for tip)
--Go into mounts and storage and format /system and /boot and come back and wipe data/factory reset (even if you have any custom rom installed)
--Select Install zip from sdcard-> choose zip from sdcard-> browse to where you have copied the zip file and select it
--Wait for the installation to complete and download latest kernel from link below and flash it in recovery. (format of kernal MDD so update to the latest one)
--flash gaaps to install basic google apps.
--Now select reboot and wait for your phone to boot up.
--If you want to move your dalvik cache to sdext first you will have to partition your sd card. 512mb partition is enough. Use minitoolwizard to partition your sdcard. Partition it in only ext2, ext3 or ext4 format because fat32 is not supported. You can also use recovery (advanced>partition sdcard) to partition but it will erase all data on your sdcard so back it up.
--Now dowload a2sd.zip (credit- Sakindia) and flash it through recovery. You can find a2sd.zip where the kernals are uploaded (check below)
--Reboot and go into Terminal emulator and type "a2sd cachesd" (without quotes)
--Wait for the working to finish and reboot. You have 148mb internal memory free now. :good:
--Alternatively people are saying that s2e is more stable. So download s2e from play store.
--check everything except application data. Reboot.
NOTE: Either flash a2sd or install s2e.
--Enjoy.!!
(OPTIONAL)--
--Download titanium backup and come to the app list now long press on any app and select move data to sd. It will ask you to create a directory, accept! Now select menu button while still in titanium backup and select batch. Come down to option "move app data to sd". Run it to get more internal memory but I recommend to use class 6 sdcard if you are moving app data.
LINK FOR KERNALS AND A2SD(CREDIT- sakindia)--
http://goo.im/devs/sakindia123
Click to expand...
Click to collapse
LINK FOR BUILD #1
http://www.mediafire.com/?2hash35eaw61ibn
Click to expand...
Click to collapse
LINK FOR BUILD #2
http://www.sendspace.com/file/h8s855
Click to expand...
Click to collapse
LINK FOR BUILD #3
http://www.sendspace.com/file/x14u9i
Click to expand...
Click to collapse
LINK FOR BUILD#4
http://www.sendspace.com/file/ci209s
http://www.mediafire.com/?oy3mrrf6ts9olim
Click to expand...
Click to collapse
Gapps
http://goo.im/gapps/gapps-gb-20110828-signed.zip
Click to expand...
Click to collapse
If you want to help in development or want the source code check out this link
http://forum.xda-developers.com/showthread.php?t=1793026
Click to expand...
Click to collapse
Now importantly THE CREDITS--
- lirokoa
- derefas
- LiVeRpOoL-FaN
- rom2maru
- sakindia
AGAIN I HAVE NO HAND IN DEVELOPMENT OF THIS PORT
I will be uploading screenshots and mediafire links soon! Please be patient!!
RESERVED for FAQs and troubleshooting!!
ReSeRvEd just like that :silly:
:cyclops:
Reserved for Changelogs ....too lazy to do it now
Fantastic work!
But I suggest you to change the thread name, and including the following "[TUTORIAL]", because poeple will think that is the main thread to this rom.
Regards!
a nice guide to help people:good:, one thing to though is you need to say "backup your old rom with cmw 1st before installing any other" (just incase) and also to stop conflicts from other roms that have been installed you really need to format system, boot, in mounts/storage menu aswell as factory wipe..............
You sir just made my day.
LiVeRpOoL-FaN said:
a nice guide to help people:good:, one thing to though is you need to say "backup your old rom with cmw 1st before installing any other" (just incase) and also to stop conflicts from other roms that have been installed you really need to format system, boot, in mounts/storage menu aswell as factory wipe..............
Click to expand...
Click to collapse
Not really. You'd only ever need to do a factory wipe/reset and then dalvic-cache wipe Cheers.
Txask said:
Fantastic work!
But I suggest you to change the thread name, and including the following "[TUTORIAL]", because poeple will think that is the main thread to this rom.
Regards!
Click to expand...
Click to collapse
Did it ..thanx for the heads up!!(sorry reached thanx limit of the day will surely do it tomorrow)
LiVeRpOoL-FaN said:
a nice guide to help people:good:, one thing to though is you need to say "backup your old rom with cmw 1st before installing any other" (just incase) and also to stop conflicts from other roms that have been installed you really need to format system, boot, in mounts/storage menu aswell as factory wipe..............
Click to expand...
Click to collapse
Did this too..thanxx for the tip!!
AIndoria said:
Not really. You'd only ever need to do a factory wipe/reset and then dalvic-cache wipe Cheers.
Click to expand...
Click to collapse
thats what i thought..and dalvik cache also gets cleared by factory wipe!! Anyway whats the harm in being extra cautious!!
ToinouAngel said:
You sir just made my day.
Click to expand...
Click to collapse
I aim to please :angel:
vshl2995 said:
I aim to please :angel:
Click to expand...
Click to collapse
Yeah well I can't unlock the bootloader, thanks to HTC Sync who doesn't recognize my phone. So I'm screwed.
ToinouAngel said:
Yeah well I can't unlock the bootloader, thanks to HTC Sync who doesn't recognize my phone. So I'm screwed.
Click to expand...
Click to collapse
Did you download the latest htc sync software? Here
http://www.htc.com/sea/software/htc-sync/
vshl2995 said:
Did you download the latest htc sync software? Here
http://www.htc.com/sea/software/htc-sync/
Click to expand...
Click to collapse
Yeah, but no luck. I'll try on another laptop when I have a chance.
EDIT: Windows 8 seems to be the problem, I can't update the drivers with the unrevoked f.ile. So yeah, I'll try with Windows 7.
ToinouAngel said:
Yeah, but no luck. I'll try on another laptop when I have a chance.
EDIT: Windows 8 seems to be the problem, I can't update the drivers with the unrevoked f.ile. So yeah, I'll try with Windows 7.
Click to expand...
Click to collapse
You shouldn't really use consumer preview as your primary OS..u should install it in a different partition!!
vshl2995 said:
You shouldn't really use consumer preview as your primary OS..u should install it in a different partition!!
Click to expand...
Click to collapse
I know, I installed the Consumer Preview in order to try it out, problem is I was doing multiple things at the same time and accidentally installed it over Vista.
I was too lazy to reinstall Vista back so I just decided to wait for the final version to be released as the preview works just fine for everything I do with my laptop... Well until now anyway, ha.
ToinouAngel said:
I know, I installed the Consumer Preview in order to try it out, problem is I was doing multiple things at the same time and accidentally installed it over Vista.
I was too lazy to reinstall Vista back so I just decided to wait for the final version to be released as the preview works just fine for everything I do with my laptop... Well until now anyway, ha.
Click to expand...
Click to collapse
Lol..
(I would use jaggy's tutorial to ask but since it hasn't been active for ten days I thought I'd be better to ask here instead of bumping the other thread, if I'm wrong I apologize)
So yeah, I'm still at the rooting process and it seems I'm definitely out of luck on this one.
So first off, I apparently managed to unlock the bootloader (and it IS unlocked, when I'm in bootloader mode I do have the "*** unlocked ***" on top of the screen) and at the same time keeping my apps, settings, etc...This was the first flag that something was wrong.
Adding the Recovery seems to have worked out fine, however when I tried to install the Superuser.zip I got the apparently not-so-uncommon "(Status 0) Installation aborted" message. I did some research and tried the method of removing the extra "updater-script~" from the archive but it did not work. Tried the method of doing a nandroid backup and then installing Superuser but no luck either.
I'm getting seriously hopeless, any idea on what I might have done wrong and how to get Superuser working?
Which recovery did you install, I was having some problems flashing anything with non-yannou's (I know i wrote it stupid but, you've got the idea )
Anyway, give a try to flash some rom, not sure if it will work without superuser installed, but nothing worse can happen (I think)
shortyoko said:
Which recovery did you install, I was having some problems flashing anything with non-yannou's (I know i wrote it stupid but, you've got the idea )
Anyway, give a try to flash some rom, not sure if it will work without superuser installed, but nothing worse can happen (I think)
Click to expand...
Click to collapse
I installed the Recovery given by jaggy's tutorial. But Recovery isn't the problem as far as I know, since I've the option to install .zip file when in Recovery mode. My only issue comes from the fact that the Superuser file won't install itself.
Q&A for [ROM][5.1.1] CyanogenMod 12.1 for Acer A700[UNOFFICIAL]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.1.1] CyanogenMod 12.1 for Acer A700[UNOFFICIAL]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
My A700 don't want anything but CM10 ... what happens ?
Hi
I try to install it on my A700 rooted and with CM11 and encounter a problem that i can't solve.
I use Clockworkmod 6.05
I have wipe data/factory reset and format dalvik cache as well
During installation i have seen a message telling something about "detected EXT4 [...] and a folder name beginning with /dev and including TEGRA-3 in it (sorry, i didn't made a screen copy)"
Then after a long time "Script succeded : Result was [/system]".
And a message telling the installation was completed.
But when i reboot the phone, i do have the Acer logo, then after a long wait, it reboot and do the same again and again
So after some despair, i try to reinstall CM11 and also try Pac-man but to no avail... seems impossible to reinstall any kitkat android .
As a consequence, i try to install CM 10.2 and it works
Another strange thing is that the "wipe data/factory reset" now hang on "format /cache"... i have to reboot the a700, then go to advanced and choose format /cache from there to be able to finish it.
As i can guess i missed something and want to try your version of CM12 , can you help me understand how to solve this problem ?
Hi,
You should try to make a cleaner install by
- make a factory reset
- format /system
- flash the CM 12.1 ROM
- flash the CM 12.1 Gapps
- reboot
Shreps said:
Hi,
You should try to make a cleaner install by
- make a factory reset
- format /system
- flash the CM 12.1 ROM
- flash the CM 12.1 Gapps
- reboot
Click to expand...
Click to collapse
Hello
thanks but i can't use the factory reset as it hang on the "format /cache" operation
So what i have done each time i try was :
format /system
format /cache
format /data
wipe dalvik cache
I don't get it ... could this be a problem with the CWM i install on it ?
this is insane
OK i install CTR yesterday to give a try but still have issues
Now i am 100% sure there is no link with CM 12.1, so i don't know how to remove my message from [Q&A] about it.
Here is the message i got when installing it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is it the normal behavior ?
When i want to install Full GAPPS, i have this message
Is it normal as i just format the /system ?
As said yesterday, i do each time :
-Format /system
-Format /cache
-Format /data
-wipe dalvik cache
I even remove all backups as they don't works
even with CTR, i am still unable to use wipe/factory reset ... when doing the format /cache, nothing happens, the menu never came back ...
If i do one after another Format /system, Format /cache ,Format /data, the menu disappear... and i have the same issue on CWM so perhaps this is an issue that everyone has ?
OK so CM11, CM12 and Pacman don't works (loop on the Acer logo).
This is strange as before trying to install CM12, i was using CM11.
The only one that works is CM10.2.
But now the insane part : at the beginning, to install CTR, as my CM10.2 was "fresh" i install firefox and flashify.
So i have the 2 icons on the desk
After formatting many times, wiping all i could, and installing many OS, i reinstall CM10.2
And the icons and wifi parameters were still there !
It is as not everything was wipe
is there any way to check what happens using Adb or fastboot at each step ?
VICTORY!
Thanks to Shreps, i have been able to resolve my issue
Here are what i have done using his advices in fastboot mode
> fastboot erase cache
> fastboot erase system
> fastboot erase userdata (takes 28s to finish it !!!)
> fastboot reboot-bootloader
> fastboot erase boot
> fastboot erase recovery
> fastboot flash recovery C:\.........\recovery-ctr.img
> fastboot boot C:\.........\recovery-ctr.img
I have change the boot and recovery erase to do it at the last moment - just in case something goes wrong
Then i have install CM12.1 and i have the following message
After rebooting, i was glad to see this expected screen :victory::victory:
Oh i forget to add i use CM12.1 Gapps
I have test many features (camera, wifi, checking each parameters screen to see each options) and you have done a wonderful work Shreps !
Ok one last tought for people who want to try
The "desktop" seem to be quite small for icone at first, as on this screen capture
I mean, i have put the google icon on the right and you still have a big place unavailable on the right
In fact, this is because of the google search bar - after removing it, the screen was resized to take space available.
Ok again THANKS Shreps for both your help on my problem , the CTR and CM12.1
Ok i have less than 10 posts, so my comments won't be on the discussion about CM12.1 - sorry for that.
RichieXX said:
My parents have a Acer A700 . I have changed ROM from CM11 to Pacman, because the performance was very poor. They are actually very happy with it. What is the performance of your CM12 against CM11 or Pacman KK? Is it worth changing to Lollipop.
Click to expand...
Click to collapse
Mankann said:
Thank you, Shreps, for this ROM! Have been testing it for a couple of days, and it's nice, the performance is the same as on CM 11 - actually it feels even smoother
Click to expand...
Click to collapse
Ok i never try Pac-man but i have use CM11 for some months, CM10 for some days and now CM12 for some hours
I have the same feeling as Mankann - for me, CM12.1 is somewhere between CM10 and CM11 regarding the smoothness
The navigation between menu is far quicker than CM11, the applications on another side are slower to launch than CM10 but still a little quicker than CM11. It was quite slow when reinstalling all apps from Playstore.
But the result is fine, i believe only a few is missing to have something very smooth. I don't know if this is more RAM or CPU.
I have to use it for a couple of hours to see if i encounter issues
Strikerfoxx said:
Ok i have less than 10 posts, so my comments won't be on the discussion about CM12.1 - sorry for that.
Click to expand...
Click to collapse
No problem. I found your answer yet.
Ok i never try Pac-man but i have use CM11 for some months, CM10 for some days and now CM12 for some hours
I have the same feeling as Mankann - for me, CM12.1 is somewhere between CM10 and CM11 regarding the smoothness
The navigation between menu is far quicker than CM11, the applications on another side are slower to launch than CM10 but still a little quicker than CM11. It was quite slow when reinstalling all apps from Playstore.
But the result is fine, i believe only a few is missing to have something very smooth. I don't know if this is more RAM or CPU.
I have to use it for a couple of hours to see if i encounter issues
Click to expand...
Click to collapse
Thank you for your first impressions of CM12. At the end I probably remains only the self-test.
I have found an issue
When i use the camera, if i switch from frontal to back on or vice-versa, the application hangs, then stopped with an error message
You have to restart the camera application and from time to time you have the message "impossible to connect to the camera" (probably bad Translation as i use CM12 in French "Impossible de se connecter à la camera") so you have to restart the tablet
---------- Post added at 09:47 AM ---------- Previous post was at 09:39 AM ----------
Second issue is noise in headphones (there was no noise on CM 11). Disabling stock AudioFX (and its complete removal) as well as installing ViperFX, which I used on CM 11, change some audio effects but not the constant ssssshhhhhhh.
Everything else is very nice
Click to expand...
Click to collapse
I also have the audio blank noise "shhhh" when using VLC and headphone. For me it is just a small noise
I didn't check audiofx but the sound is there even after the video have ended, and it stop if i close VLC.
Sorry for all theses post , the goal is to help improve this version of CM:fingers-crossed:
No Apps can be installed
I've installed the latest rom 16.06 250MB space of 32 Gib could be used , can you fix it? Its the first lollipop rom and it run verry well !
I had CM11 KK on my a700. I tried to flash cm-12.1-20150616-UNOFFICIAL-a700 in CWMR 6.0.4.4.(couldnt find newer version) like usual, but it didnt work. Now my a700 is stuck in a bootloop. I tried to flash CM11 KK again, but only a cyanogen logo appears and then it reboots. Can someone help?
Stammleser said:
I had CM11 KK on my a700. I tried to flash cm-12.1-20150616-UNOFFICIAL-a700 in CWMR 6.0.4.4.(couldnt find newer version) like usual, but it didnt work. Now my a700 is stuck in a bootloop. I tried to flash CM11 KK again, but only a cyanogen logo appears and then it reboots. Can someone help?
Click to expand...
Click to collapse
Do You have a JB bootloader? Did you try to factory reset?
Envoyé de mon One+
>>bootloader version jb-653b3d3 (unlock mode)<< appears always above in the left corner. when i do wipe data/factory reset, it reboots, but only to the acer logo.
Just dusted off my Acer 700 from the closet. I had totally forgotten I had it (received free gift sometime ago!). Went from stock 4.1.1 straight to this and I am still testing things out. One recommendation I have is to go with CTR (not TW or CW) and wipe+format partitions. You don't see any errors and just installs in a cleaner filesystem.
Stammleser said:
>>bootloader version jb-653b3d3 (unlock mode)<< appears always above in the left corner. when i do wipe data/factory reset, it reboots, but only to the acer logo.
Click to expand...
Click to collapse
Try to install CTR for A700 made by shreps and if it didn't work, follow what i have done in that post using fastboot to be sure that no data are still on your device.
---------- Post added at 09:20 AM ---------- Previous post was at 09:09 AM ----------
Hi Sterist
Did you try to remove the flex partition and expand the system one ?
Strikerfoxx said:
Try to install CTR for A700 made by shreps and if it didn't work, follow what i have done in that post using fastboot to be sure that no data are still on your device.
---------- Post added at 09:20 AM ---------- Previous post was at 09:09 AM ----------
Hi Sterist
Did you try to remove the flex partition and expand the system one ?
Click to expand...
Click to collapse
not on the a700
I tried it on my s4 and note 4 since they can recover (most) partition errors, and upon trying to resize any partition, it failed and have a error. that was several days ago and I can't remember what the error was
maybe I forgot to unmount it...
A new build is online based on the r6 tag
Click to expand...
Click to collapse
I download it this morning and plan to install it in a few days
Is there any way to install it using the update screen in Cyanogen instead of using CTR each time (and format everything) ?
Great !
5.1 on my A700, I'm gonna test it right now...
Strikerfoxx said:
Try to install CTR for A700 made by shreps and if it didn't work, follow what i have done in that post using fastboot to be sure that no data are still on your device.
Click to expand...
Click to collapse
i downloaded the CTR file, but i dont know how to install it.
My experience with the rom : installed it without any issue, with nano gapps, after full wipe (TWRP 2.6). Install and set up was not that long. Restored my apps with TB.
Great to have CM12 (thanks to the dev !) All seemed to work fine at first. But I got many huge lags, ~30 sec to load an app, then again ~30 sec to change page or scroll down... (not all the time - and Antutu scired a good 19500). Got the same kind of lags when I tested CM11 I think.
More importantly, I can't play most of my videos (with MX player or some streaming app). It freezees on the first images while the sound continues to play normally. Someone have any idea where that come from ? I tested some ambient display parameters, some 2d/3d acceleration parameters under development parameters but nothing changed...
I think I might have to go back to pac man rom, which didn't had these issues for me...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 20.0
lineage-20.0-20230507-UNOFFICIAL-flo.zip
lineage-20.0-20230507-UNOFFICIAL-deb.zip
Known issues:
- We are still Permissive (SELinux)
- Encryption is not working .. Pls do NOT encrypt your /data partition!
- Camera is not fully working .. Only certain Camera apps are working well.
- And maybe more issues .. ?
Installation:
1.) Do factory reset in TWRP - keep internal storage this way.
2.) Format /system partition in TWRP
3.) Install ROM
4.) Install Gapps (optional)
5.) Install Magisk 26.1 (optional)
6.) Reboot into system and start to setup your device.
Gapps:
Mind the Gapps
LiteGapps
TWRP:
twrp-3.7.0_9-1-flo_followmsi.img
twrp-3.7.0_9-1-deb_followmsi.img
Magisk:
Tested with Magisk 26.1
MicroG:
The builds have been patched to support microG !
Android 11/12/13 File-system size:
Flo and Deb device -> 1275 MB -> both devices needs reparition !
Pls check below for more details.
System repartitioning / Opengapps: Error 70
The current system partition is (getting) full !
You need to do repartition your system partition .. either via TWRP package or manually via shell.
It's an one time task.
But the filesystem of the system.img inside the ROM will keep always the same size .. approx. 880mb.
The filesystem does not know the "real" size of the actual partition.
In general .. If you install an image into a partition the filesystem will have the size of the image (in our case 880mb).
The free space we got thru repartitioning needs to be allocated again.
For this reason we need to enlarge/resize the filesystem after each ROM update and/or clean install.
Only the filesystem .. the partition itself will stay untouched.
The automatic enlarge/resize of the filesystem is part of the ROM installer.
There are repartition solutions from @ipdev @Clamor @k23m .. and maybe more.
Made new sysrepart.zip based on the original from @k23m
https://forum.xda-developers.com/showpost.php?p=76278047&postcount=19
The original code is changing to 1140MB (system) and 260MB (cache).
These days /cache is not used anymore .. a few MB only.
For this reason I have changed the values to 1280 (system) and 120MB (cache) now.
https://forum.xda-developers.com/showpost.php?p=78703434&postcount=1971
In latest version we have changed to 1380MB (system) and 20MB (cache)
https://forum.xda-developers.com/t/...neageos-18-1-2021-11-05.3569067/post-85999781
sysrepart_1380_20.zip
All the credits to @k23m !!!
Pls check REPIT script from @ipdev .. to get 1480MB system partition .. to be able to install opengapps !
https://forum.xda-developers.com/t/tool-unofficial-port-repit-for-nexus-7-2013-deb-flo.4237183/
Sources:
https://github.com/followmsi/manifests/tree/flo-deb-lineage-19.1
https://github.com/followmsi/manifests/tree/flo-deb-lineage-18.1
https://github.com/followmsi/manifests/tree/flo-deb-lineage-17.1
https://github.com/followmsi/manifests/tree/flo-deb-aex-pie
https://github.com/followmsi/manifests/tree/flo-deb-lineage-16.0
https://github.com/followmsi/manifests/tree/flo-deb-pixel-pie
https://github.com/followmsi/manifests/tree/flo-deb-rros-lineage-16.0
https://github.com/followmsi/manifests/tree/flo-deb-aosp-p
https://github.com/followmsi/manifests/tree/flo-deb-aosp-o
https://github.com/followmsi/manifests/tree/flo-deb-aosp-nougat
Download:
https://drive.google.com/drive/fold...HZThGTnM?resourcekey=0-0BunAmDBWluYPghT0Fs6CA
All other ROM have been moved to androidfilehost.com ..
https://androidfilehost.com/?w=files&flid=289295
All the testing has been done by @ipdev - big thanks to him !
Thanks to @nbehary and @DevSwift1 and @flex1911 and @yattodettaman and @emmett.tsai !
Big Thanks to LineageOS Team !
Enjoy
Thanks will download when I get home
lollyjay said:
Thanks will download when I get home
Click to expand...
Click to collapse
Cool .. go for it
It seems there are some download issues using mobile devices.
Google Mobile version wants to redirected to some ...mobile... link, which is not working.
At least for me.
Also the import into Google Drive App seems not to work.
If you choose "request desktop version" in Chrome mobile settings it should work.
On normal desktop browsers there are no problems.
This issue occurs since a few days .. for "all" my Google Drive projects
Hi I downloaded in Windows 10 and all working atm. More after I test.
---------- Post added at 08:31 PM ---------- Previous post was at 08:01 PM ----------
ROM seems fully functional. Working well with data and dalvik formatted f2fs.
Your recovery is also functioning well, with the the exception that it takes over a minute to load. Not a problem for me though.
This is related to F2FS .. if you would have ext4 data it will load much more quickly.
followmsi said:
This is related to F2FS .. if you would have ext4 data it will load much more quickly.
Click to expand...
Click to collapse
After installation, does not go into the recovery (3.0.2)
On version 3.0.3-3, such a problem will not exist?
Which sections have the format f2fs ?, and whether it is possible to add a night mode?
boom1982 said:
After installation, does not go into the recovery (3.0.2)
On version 3.0.3-3, such a problem will not exist?
Which sections have the format f2fs ?, and whether it is possible to add a night mode?
Click to expand...
Click to collapse
/system/bin/install-recovery.sh
You loose recovery .. this is normal ... if not rooted ..(SuperSU.zip)
The easiest solution is to install SuperSU.zip via TWRP.
Maybe I can remove it for next build .. not sure.
F2FS .. via TWRP
Wipe - Repair/Change file-system ...
Jus install the ROM and test and play yourself
Cheers
Does micro gapps work with this ROM, or only nano?
Reason I ask is that some things (Face Unlock) don't come with nano and there is no easy way to add that back in that I've found.
rajsris said:
Does micro gapps work with this ROM, or only nano?
Reason I ask is that some things (Face Unlock) don't come with nano and there is no easy way to add that back in that I've found.
Click to expand...
Click to collapse
Micro gapps works! [emoji6]
I cannot install Gapps 7.1.1 (tried micro and aroma), message saying I am on Android 6.0.1 and need to use proper version. Deb.
finkbg said:
I cannot install Gapps 7.1.1 (tried micro and aroma), message saying I am on Android 6.0.1 and need to use proper version. Deb.
Click to expand...
Click to collapse
I installed open gapps arm 7.1 pico with no problem. Not enough system available space for micro
You can try to resize file system of system partition inside TWRP to get full partition size.
Or use the Update.zip_resizefs_flo.zip inside the download folder.
Works for deb too.
Cheers
Hmmm not sure what I'm doing wrong. Tried the process twice, both times after reboot step, TRWP tells me no OS installed. Suggestions?
Enough space is available for micro. I managed to install it after a few reboots (no clue how). However, having converted data to f2fs, I now cannot write to data from within the ROM (play store crashes on install of any app, webview cannot start a download and camera cannot save photos). Latest rom from yesterday, haven't installed any fstab patches (thought this rom being the next release would not need any patches, am I correct?). Any suggestions?
rajsris said:
Does micro gapps work with this ROM, or only nano?
Reason I ask is that some things (Face Unlock) don't come with nano and there is no easy way to add that back in that I've found.
Click to expand...
Click to collapse
Keep in mind that all Open GApps installs can be customized so if you want FaceLock you would chose the lowest package with it and them use the config file to remove the rest of the differences.
Also Face Unlock DOES come with Nano BTW, only package without it is Pico.
(Disclaimer: I'm a former Open GApps team member.)
Yes, micro works. It worked with the original ROM by nbehary and it works with this one as well.
finkbg said:
Enough space is available for micro. I managed to install it after a few reboots (no clue how). However, having converted data to f2fs, I now cannot write to data from within the ROM (play store crashes on install of any app, webview cannot start a download and camera cannot save photos). Latest rom from yesterday, haven't installed any fstab patches (thought this rom being the next release would not need any patches, am I correct?). Any suggestions?
Click to expand...
Click to collapse
Did you fix your problems ?
The fstab has been changed ... you can verify yourself.
Open terminal app ..
Code:
su -
cat fstab.flo
To see the current partitons and there used/mounted filesystems ..
Code:
mount
Pls have a look here ..
https://forum.xda-developers.com/showpost.php?p=71296026&postcount=716
F2FS seems to work fine on data - I still use it on cache only.
If you face strange issues, pls start with a fresh TWRP factory reset first.
Cheers
bgiesing said:
Also Face Unlock DOES come with Nano BTW, only package without it is Pico.
Click to expand...
Click to collapse
Thanks for the info, I meant pico actually, as all other nougat roms for this device only have space for that package.
followmsi said:
F2FS seems to work fine on data - I still use it on cache only.
Click to expand...
Click to collapse
Working fine here.
I have the rom flashed and everything looks good with cache and data converted to F2FS. However I am experiencing an odd issue. When i first set up the tablet I sign in with my gmail account and everything looks good. I do a clean setup so nothing restores and download the official gmail from the play store. Once it installs and opens it does not seem to notice that my google account is configured. It asks me to add a mail account and if i put the same account in it says the account already exists. I've factory reset this 3 times trying something different each time thinking maybe I did something dumb. Flashed many roms before and never seen this, any ideas?
---------- Post added at 08:07 PM ---------- Previous post was at 08:03 PM ----------
followmsi said:
You can try to resize file system of system partition inside TWRP to get full partition size.
Or use the Update.zip_resizefs_flo.zip inside the download folder.
Works for deb too.
Cheers
Click to expand...
Click to collapse
dumb question but what does the partition resize change it to? I was looking to find a stock partitioning sizes vs this script chart or explanation.
[ROM][11.0][4.9][AOSP][KUGO] Explosive Lobster
KUGO F5321
Hi! Just wanna share with you Android 11 ROM builded for Sony Xperia X Compact
Many Thanks for development @Cubbins
I'm not responsible for any damage caused with your device after flashing this ROM. Flash only on your own risk.
This ROM bring us Treble support ( ARM64 A/B ) structure for all GSI images based on 11 Android. Just flash any GSI at System partition after it.
How to Install:
1) Copy ROM to SD card and flash with recovery
2) Download SW_BINARIES_FOR_XPERIA_ANDROID_9.0_2.3.2_V9_LOIRE.ZIP, unzip and copy image to sdcard too
3) Flash Binaries with recovery to OEM/ODM partition
4) reboot
5) After reboot we need to flash/format userdata partition. So, download it and flash with ADB: fastboot flash userdata userdata.img or fastboot erase userdata
6) reboot.
Warning:
We use /cache partition at thid ROM as a /vendor, so if you format /cache partition on recovery - you'll catch a bootloop.
Features:
Working:
- Wi-Fi
- Bluetooth
- Fingerprint
- Sensors
- Camera
- Calling
- Music Playing
- GPS
Not Working:
You tell me
Sources:
build ROM sources:
github.com/ExplosiveLobster
kernel sources:
github.com/ExplosiveLobster/kernel_sony_msm-4.9
bug reports:
github.com/ExplosiveLobster/bug_tracker/issues
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
Google Drive
Explosive Lobster - Google Drive
drive.google.com
Mega
3.11 GB folder on MEGA
12 files and 3 subfolders
mega.nz
So good to see some people still working on this device. I'm considering leaving the official rom to this one as soon as GPS is operational. Thank you very much.
mhemart said:
So good to see some people still working on this device. I'm considering leaving the official rom to this one as soon as GPS is operational. Thank you very much.
Click to expand...
Click to collapse
GPS Working fine with latest build, so you can try it right now
lubik1 said:
GPS Working fine with latest build, so you can try it right now
Click to expand...
Click to collapse
Really good, I have to backup my data and I'll give a try tonight. Thanks !
[QUOTE = "lubik1, post: 84244519, member: 5897890"]
Which vendor should I use?
mister-13x said:
Which vendor should I use?
Click to expand...
Click to collapse
F5321 is for X compact.
mister-13x said:
Which vendor should I use?
Click to expand...
Click to collapse
SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.img
The one vendor binaries for both devices - suzu and kugo
Are the Flame Gapps in your Google Drive the Gapps you recommend, or can we just use OpenGapps as usual? This is my first experience with Android 11.
Edit1: Installation worked like a charm with your description. For me, there was no change after flashing userdata.img. The phone behaved the same way, whether I flashed userdata.img or I did not. What did NOT work was just to delete userdata - then my phone would show an error message after boot and just shut down again.
After every boot, I receive the error message “There’s an internal problem with your device Contact your manufacturer for details”. According to Google, this has something to do with Treble. I will install my apps now and get the tests going. Thank you SO much for this. If you leave your PayPal here somewhere, I will send you some small bucks that I can afford for the good development.
Spaceoid said:
Are the Flame Gapps in your Google Drive the Gapps you recommend
Click to expand...
Click to collapse
You can flash any Gapps you want, but this gapps was tested with EL ROM and work fine.
Spaceoid said:
Thank you SO much for this. If you leave your PayPal here somewhere
Click to expand...
Click to collapse
It's allways on my profile, on section "about"
Hello. I had no time to perform an install yet but I have a question (maybe stupid ?). I noticed the binaries were for Android 9 but I saw that there was a newer version called SW_binaries_for_Xperia_Android_10.0.7.1_r1_v7a_loire (no more binaries for android 11). Do you think it could be used with your ROM ? Maybe it would prevent the message that Spaceoid see at every boot ?
Just in case, here is the link to the newest version : https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-loire/
I just send you two coffees via PayPal for the good work. I know it is not much, sadly I am a student with little income... But I hope it keeps you energized for further improvements to the ROM!
After half a day of testing the pure ROM, without any apps and just Gapps, here is what I found so far:
- Wifi is working, but, at least for me, after like 30 minutes after every boot, it seems to break. After that, I am not able to reconnect to my home wifi network, or to find any Wifi networks in general. Only a reboot fixes this.
- Regarding the error message mentioned in my last post, I found this:
How to Fix Android system There's an internal problem with your device
How to Fix Android system error "There's an internal problem with your device Contact your manufacturer for details" and How to remove NFC Service 'NFC keeps stopping'.
www.recovery-mode.com
I cannot say how reliable/safe this procedure is, though.
- Connected to this, the NFC tile in the pulldown menu (from the status bar) does not work. I can activate NFC via the settings, though; I did not try yet if it really works, but at least it can be activated.
- After every reboot, the phone forgets the time and date until it is connected to cellular network or wifi for the first time.
(- one minor thing - the alarm clock does work well, but it does only sound the alarm and not wake up the screen. So, before disabling the alarm, one has to unlock the screen first.)
Will start installing my apps now and keep on further testing.
mhemart said:
Hello. I had no time to perform an install yet but I have a question (maybe stupid ?). I noticed the binaries were for Android 9 but I saw that there was a newer version called SW_binaries_for_Xperia_Android_10.0.7.1_r1_v7a_loire (no more binaries for android 11). Do you think it could be used with your ROM ? Maybe it would prevent the message that Spaceoid see at every boot ?
Just in case, here is the link to the newest version : https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-loire/
Click to expand...
Click to collapse
I was about to ask the same. Are the 10 binaries not compatible?
@betacrypt
Binaries for 10 are available however the kernel development was abadoned. Kernel 4.14 did not mature into an operational state. Kernel 4.9 is the current stable version, using the 9 binaries are the most recent option at the moment.
@lubik1
This is being trebled? SELinux is permissive? If that's the case, I imagine the cache.img and boot.img can be used to GSI other OS'.
Warning:
We use /cache partition at thid ROM as a /vendor, so if you format /cache partition on recovery - you'll catch a bootloop. [QUOTE/]
Click to expand...
Click to collapse
&(*) said:
@betacrypt
Binaries for 10 are available however the kernel development was abadoned. Kernel 4.14 did not mature into an operational state. Kernel 4.9 is the current stable version, using the 9 binaries are the most recent option at the moment.
Click to expand...
Click to collapse
Ah that makes sense. Somehow I thought 4.14 was stable.
Also thanks @lubik1 for your efforts to create this! Glad to see continued support for the XC - was worried we'd lost support for it. I own two and had been hoping to see an update.
betacrypt said:
Ah that makes sense. Somehow I thought 4.14 was stable.
Also thanks for your efforts to create this! Glad to see continued support for the XC - was worried we'd lost support for it. I own two and had been hoping to see an update.
Click to expand...
Click to collapse
Don't forget to thank @Cubbins too for the build.
@lubik1 ,
Can you also provide a GSI variant (of boot.img and cache.img) for those of us who like to use other systems?
Anything different to do when rooting with Magisk? I flashed the latest Magisk in TWRP successfully but when I boot into system the Magisk App says no root.
betacrypt said:
Anything different to do when rooting with Magisk? I flashed the latest Magisk in TWRP successfully but when I boot into system the Magisk App says no root.
Click to expand...
Click to collapse
Strange. I did the same this morning, downloaded latest Magisk version from Github, and it worked for me. I already used root for Titanium Backup. I used v21.2.
On another note, after one day of usage, I'd already consider this ROM quite stable. The wifi problem really is the main problem, as I only can connect to my home wifi in 20% of the day. I already lost all my mobile data because of that, now I am surfing in less than 2G speed on my phone xD
Spaceoid said:
- Wifi is working, but, at least for me, after like 30 minutes after every boot, it seems to break. After that, I am not able to reconnect to my home wifi network, or to find any Wifi networks in general.
Click to expand...
Click to collapse
We'll switch to another wi-fi driver on next build.
Spaceoid said:
- Regarding the error message mentioned in my last post, I found this:
Click to expand...
Click to collapse
Will be Fixed on next build
Spaceoid said:
- Connected to this, the NFC tile in the pulldown menu (from the status bar) does not work. I can activate NFC via the settings, though; I did not try yet if it really works, but at least it can be activated.
Click to expand...
Click to collapse
Will be added on next build
Spaceoid said:
- After every reboot, the phone forgets the time and date until it is connected to cellular network or wifi for the first time.
Click to expand...
Click to collapse
Missing rtc-service, will be added on next build
Hi,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DarkJoker360 AOSP 11 for Huawei P8 Lite 2017
*** Stable Version ***
About
Android is an open source software stack for mobile devices and a corresponding open source project led by Google. This site and the Android Open Source Project (AOSP) repository offer the information and source code needed to create custom variants of the Android stack, port devices and accessories to the Android platform, and ensure devices meet the compatibility requirements that keep the Android ecosystem a healthy and stable environment for millions of users.
Click to expand...
Click to collapse
Working
* Touchscreen
* Audio
* Boot
* Bluethoot
* Internal/External storage
* Mtp / Adb
* Sensors
* Wifi
* RIL
* Camera
* NFC
* FP gestures
Click to expand...
Click to collapse
Not Working
* You tell me
Click to expand...
Click to collapse
NOTE: The signal icon is buggy due to Huawei weird ril implementation, I am still looking to fix it over the new Android 10-11 telephony changes.
Installation
* you must have TWRP installed, use this one (make sure to have the unofficial Android 11 one ! )
WARNING: You must be decrypted before installing it otherwise it won't boot. (Read second post.)
* go to TWRP
* format data
* reboot to TWRP again
* do a full wipe (system, data, cache, dalvik/art cache) !
* reboot to bootloader
* extract AOSP 11
* run: fastboot flash system <drag system.img here>
* reboot to TWRP
* resize system
* flash gapps (optional)
* flash NFC.zip
NOTE: this zip is needed for having working NFC. DO NOT IGNORE IT !
* reboot to System
* Enjoy !!!
Click to expand...
Click to collapse
Update
* reboot to TWRP and do a wipe cache, dalvik/art cache
* reboot to bootloader
* extract AOSP 11
* run: fastboot flash system <drag system.img here>
* reboot to TWRP
* resize system
* flash gapps (optional)
* flash NFC.zip
NOTE: this zip is needed for having working NFC. DO NOT IGNORE IT !
* reboot to System
* Enjoy !!!
Click to expand...
Click to collapse
If you are getting Error 70 while flashing gapps just resize system from TWRP !
If gapps are giving network errors or other kind of errors install them after first boot !
Download
AOSP 11 and NFC fix
NikGapps
OpenGapps
Click to expand...
Click to collapse
Please support my work, it's very important! Thanks
DONATIONS
Regards !
NOTES
* For root method read this post, for rooting with magisk read this instead.
* If you face corrupted storage issues you need to go back on emui and re-install the rom.
* I recommend NikGapps core with SetupWizard add-on.
* Use 8.0.0.360 or maximum .400 firmware for booting the rom.
* Gapps can may give "Uncertified device" error and abort the google account login, use this guide to fix it (thanks to @latviandude )
* If you want VoLTE/Wifi Calling working flash this zip
** You must be decrypted for booting this rom **
Before following the installation steps format data and flash this file via TWRP.
Hi, I flashed yesterday AOSP 11via fastboot, storage decrypted with recommanded TWRP using edited fstab.hi6250. Rom seems to work better for me than AOSP 10, screen recorder works, backlight works, already resolved problem with bluetooth(connected/disconnected) by disabling HD Audio in developer options.
Battery drainage while using worries, but it is too early to say, still testing it. There is no way I can get NFC fix working(never could on any custom rom) so obviously I’m doing something wrong. Hope I’ll figure it out.
Thanks @DarkJoker360, great work!
EDIT: Flashing NFC fix worked and it is present in settings(Connected devices), but it's absent in status bar(I can live with that)
Hi . how can i "resize system" ?
piterconlai said:
Hi . how can i "resize system" ?
Click to expand...
Click to collapse
Go to twrp recovery, press "Wipe" Then choose "Advanced Wipe". After that select/check "System" box and then press on "Repair or Change File System" and then you will see down "Resize File System" - press on it and done ur System has been resized.
hardcorehenry said:
Hi, I flashed yesterday AOSP 11via fastboot, storage decrypted with recommanded TWRP using edited fstab.hi6250. Rom seems to work better for me than AOSP 10, screen recorder works, backlight works, already resolved problem with bluetooth(connected/disconnected) by disabling HD Audio in developer options.
Battery drainage while using worries, but it is too early to say, still testing it. There is no way I can get NFC fix working(never could on any custom rom) so obviously I’m doing something wrong. Hope I’ll figure it out.
Thanks @DarkJoker360, great work!
View attachment 5194331 View attachment 5194333
EDIT: Flashing NFC fix worked and it is present in settings(Connected devices), but it's absent in status bar(I can live with that)
Click to expand...
Click to collapse
Hello I would like to ask you some information
- the bluetooth headphones work?
- How's the battery drain going? More or less how many hours of screen does it make?
Added to AOSP 11 accent, font and icon shape picker (like theme picker), now working on an aosp icon pack picker (aka styles) !
piterconlai said:
Hello I would like to ask you some information
- the bluetooth headphones work?
- How's the battery drain going? More or less how many hours of screen does it make?
Click to expand...
Click to collapse
I made more thorough research, hope it’ll be useful for further development.
Battery:
When idle(sleep) it looses 1% overnight, when only screen on battery drain is 1% per 10 min, when only stopwatch on it looses 1% per 5 min. Checked without SIM and brightness level 45%. Now I’m going to let it drain completely and charge again. Maybe this results are normal(right define normal) and needles to worry about.
Bluetooth:
After pair my earbuds automatically trying to switch to aptX audio codec(they have aptX, AAC and SBC support) without success(connected/disconnected again and again), not possible to chose other codec when HD Audio in developer options is enabled. When disabled it automatically chooses SBC(without possibility of change), but this codec works without problems.
hardcorehenry said:
I made more thorough research, hope it’ll be useful for further development.
Battery:
When idle(sleep) it looses 1% overnight, when only screen on battery drain is 1% per 10 min, when only stopwatch on it looses 1% per 5 min. Checked without SIM and brightness level 45%. Now I’m going to let it drain completely and charge again. Maybe this results are normal(right define normal) and needles to worry about.
Bluetooth:
After pair my earbuds automatically trying to switch to aptX audio codec(they have aptX, AAC and SBC support) without success(connected/disconnected), not possible to chose other codec when HD Audio in developer options is enabled. When disabled it automatically chooses SBC(without possibility of change), but this codec works without problems.
Click to expand...
Click to collapse
Thanks for the reply
so can you do 8 h of screen with this rom?
Have you tried if the blutooth smartwatch works by accident?
Last question :
Would it be possible to go back to a previous version if I didn't like it? I am currently using lineage 16 and I am very happy with it
piterconlai said:
so can you do 8 h of screen with this rom?
Click to expand...
Click to collapse
Well you have to calculate yourself from data I provided or flash rom and find out.
piterconlai said:
Have you tried if the blutooth smartwatch works by accident?
Click to expand...
Click to collapse
I don’t have such device.
piterconlai said:
Would it be possible to go back to a previous version if I didn't like it? I am currently using lineage 16 and I am very happy with it
Click to expand...
Click to collapse
If you are more interested in comfort than struggle, testing and help DEV to perfect this rom don’t change anything. Going back means flash and install everything from scratch.
I'm always getting an error when flashing system img via fastboot...
error code : Invalid sparse file format at header magic
The system partition can't be written after the first sparse.
I tried with linux and windows, changed the usb cable but nothing change.
Is there anything to do before this operation except the ones in the insttructions ?
Junkilito said:
I'm always getting an error when flashing system img via fastboot...
error code : Invalid sparse file format at header magic
The system partition can't be written after the first sparse.
I tried with linux and windows, changed the usb cable but nothing change.
Is there anything to do before this operation except the ones in the insttructions ?
Click to expand...
Click to collapse
I’m not sure I also had this warning( Invalid sparse file format at header magic) but after a while flash went from beginning till the end without problems. Two things come to my head: outdated platform-tools or/and you are on wrong firmware(take a look at screenshots DarkJoker 8.0.0.400 and mine 8.0.0.402), but as I said not sure and it’s pure guess from my side. Wait for second opinion.
hardcorehenry said:
I’m not sure I also had this warning( Invalid sparse file format at header magic) but after a while flash went from beginning till the end without problems. Two things come to my head: outdated platform-tools or/and you are on wrong firmware(take a look at screenshots DarkJoker 8.0.0.400 and mine 8.0.0.402), but as I said not sure and it’s pure guess from my side. Wait for second opinion.
Click to expand...
Click to collapse
I have exactly the same problem. Adb also gives me this error, even though it always continues flashing though and also finishes then.
The ROM is however never bootable for me and I can't figure out what I have done wrong. I was on 8.0.0.402 before and used AEX 9 ROM just fine.
What version of TWRP did you use for successful results? I can't find a newer one from pretoriano80 but 3.2.1.0. Maybe that is a problem?
Regards
Friedensfurz said:
I have exactly the same problem. Adb also gives me this error, even though it always continues flashing though and also finishes then.
The ROM is however never bootable for me and I can't figure out what I have done wrong. I was on 8.0.0.402 before and used AEX 9 ROM just fine.
What version of TWRP did you use for successful results? I can't find a newer one from pretoriano80 but 3.2.1.0. Maybe that is a problem?
Regards
Click to expand...
Click to collapse
Hi,
I’ll try exactly step by step how I did it(I’m on macOS so there might be small differences). When on stock after unlocking bootloader and flashing TWRP(took from this post), you need to copy on your external sdcard or USBOTG NFC_fix.zip, gapps(optional) and fstab.hi6250b.zip or edit your own from /vendor/etc like in this post. Boot into TWRP (backup just in case your vendor partition)and either flash fstab.hi6250b.zip(easy way) or replace fstab.hi6250 in /vendor/etc with edited one via TWRP file manager(harder way). After flashing/replacing enter in TWRP into Wipe and Format Data>yes then reboot into TWRP, wipe: cache, dalvik cache and data and reboot into system. You should reboot into ugly looking stock rom. In settings>security>more you should see Encrypt phone that means storage is decrypted. Enable debug and confirm via adb and boot into TWRP. Make backup(ramdisk, kernel, data, system) enter section Wipe>Advanced Wipe and wipe Dalvik/ART Cache, Cache, Data and System. Don’t Format Data again because most probably it'll f*up Internal Storage besides internal storage is already decryptet. Reboot into bootloader. Run in terminal(macOS) or whatever is used in Windows/Linux:
fastboot devices
fastboot flash system drag and drop aosp-11_prague_20210117.img
Reboot into TWRP, resize System if needed, flash NFC_fix.zip and gapps(optional).
Wipe Cache and Dalvik, reboot and that should be all.
Junkilito said:
I'm always getting an error when flashing system img via fastboot...
error code : Invalid sparse file format at header magic
The system partition can't be written after the first sparse.
I tried with linux and windows, changed the usb cable but nothing change.
Is there anything to do before this operation except the ones in the insttructions ?
Click to expand...
Click to collapse
It is a know "issue", just ignore it and boot it.
It is most likely a warning.
DarkJoker360 said:
It is a know "issue", just ignore it and boot it.
It is most likely a warning.
Click to expand...
Click to collapse
Nope it's caused by new version of official firmware for this phone, system partition on newer versions is 2GB on b388 is 3GB.
That would explain why in the past I had troubles reflashing even stock SYSTEM.img via fastboot on latest official firmware. @DarkJoker360 maybe it’s worth mentioning that flashing anything on latest firmware is not advised, and firmware should be downgraded(latest safe confirmed working firmware 8.0.0.402[service rom] or 8.0.0.400 [the same as developer's]).
hardcorehenry said:
That would explain why in the past I had troubles reflashing even stock SYSTEM.img via fastboot on latest official firmware. @DarkJoker360 maybe it’s worth mentioning that flashing anything on latest firmware is not advised, and firmware should be downgraded(latest safe confirmed firmware 8.0.0.402[service rom]).
Click to expand...
Click to collapse
I recommend .360 firmware or .400 (the one I am using)
Newer firmwares with newer security patches may refure to boot due to some Huawei changes for avoiding modding.
Thanks for all of your help. I managed to get AOSP 11 to boot, the reason why it initially just bootlooped for me was that I did not directly come from Stock ROM. Very weird. Following @hardcorehenry 's steps worked fine. Is it somehow possible to get Magisk going on this ROM? I read the AOSP 10 thread and installed the "magisk phh v21.0".zip file, but now I am stuck on the "Your device cannot be trusted, your device is booting" screen. Any ideas for this? Many thanks.
Friedensfurz said:
Thanks for all of your help. I managed to get AOSP 11 to boot, the reason why it initially just bootlooped for me was that I did not directly come from Stock ROM. Very weird. Following @hardcorehenry 's steps worked fine. Is it somehow possible to get Magisk going on this ROM? I read the AOSP 10 thread and installed the "magisk phh v21.0".zip file, but now I am stuck on the "Your device cannot be trusted, your device is booting" screen. Any ideas for this? Many thanks.
Click to expand...
Click to collapse
No magisk at the moment, I'm sticking with A10 untill Magisk 19.3 will work on this rom (need to pass safety net)