{
"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"
}
Flashing tips by @ramjet73, this should be read by everyone
http://forum.xda-developers.com/showpost.php?p=55228784&postcount=12583
This is an enhanced version of the 81c developer preview that google released.
It has currently been ported for Mako and Deb and improved for Hammerhead and Flo
It offers a permissive selinux policy, aosp merged in and rock solid stabilty along with drastic improvements in speed and smoothness.
It offers updated proprietary files, updated google apps, fonts, res files and animations from the newer sdks.
Click to expand...
Click to collapse
Deb does not have a working mobile radio yet, radio turns on but without access to the settings, we can't configure it. A work around is being worked on
Big thanks to @defconoi , @zyr3x , @percy_g2 , @ben1066 [MENTION=1050103] for improving and originally helping with the old lpv79 port to Mako.
Right now I rebased the entire project to clean it out and smooth it out
Huge thanks to @ramjet73 @bitstra @manueltts @skiman10 @psycho693 @jayfallen for helping me get it over to the other devices I don't have and testing everything I threw at them and the huge brainstorming and trying things I couldn't. It would have not been possible without these guys so please thank them
Click to expand...
Click to collapse
Warning. This has heavy ramdisk mods that are essential for it to work. You can flash current up to date "kit Kat kernels or L updaters only" but not full boot.imgs as this will break the ROM. If you do happen to flash a a boot.img, you can pull it out if the rom and fastboot flash boot boot.img
Hammerhead can only use L preview Kernels.
Remember, this is a port of a developer preview, there is already bugs in the official version from google and without the L code, we can not fix google's bugs. There are fixes to known problems in N7 2013 and N5 forums so if you do find them, please provide them with the bug
Click to expand...
Click to collapse
INSTALLATION INSTRUCTIONS
FIRST TIME FLASHING
Put the file onto your Internal Storage
Reboot into Recovery (CWM/TWRP]
"wipe data/factory reset"
"mounts and storage" -> "format system"
"install zip" -> "install zip from sdcard" -> choose the mako-bla-bla-zip and confirm flashing procedure
"reboot into system"
first boot may take up to 10 minutes - be patient
UPDATING
Put the latest L-bla-bla.zip onto your Internal Storage
Reboot into Recovery (CWM/TWRP)
"wipe data/factory reset"
"install zip" -> "install zip from sdcard" -> choose the [filename.zip] and confirm flashing procedure
"reboot into system"
Updater-script wipes the cache files so no need to wipe cache
Sources
Mako
GPL KERNEL SOURCE - github.com/Android-L-Porting-Team/android_kernel_mako
Flo, Deb and Hammerhead use the modifed stock preview with the kexec-hardboot patch directly provided by @tassadar to provide multirom support. Flo and Deb use the same kernel.
Hammerhead - http://forum.xda-developers.com/showpost.php?p=48508468&postcount=2
Flo - http://forum.xda-developers.com/showpost.php?p=45886584&postcount=2
We are using the rebase repos right now since they are cleaned out
Github https://github.com/Android-L-Porting-Team
Downloads
Stable - 9001
Full
Afh - https://www.androidfilehost.com/?fid=95747613655040641
Google Drive - https://drive.google.com/file/d/0By0vn8iv_zrVYUlFbmVrMEtHcDA/edit?usp=sharing
Dev-Host-
Mega-
Click to expand...
Click to collapse
Downloads
Stable - 9001
Slim -
Afh - https://www.androidfilehost.com/?fid=95747613655040642
Google Drive - https://drive.google.com/file/d/0By0vn8iv_zrVS1hDakt6VWM3WGc/edit?usp=sharing
Dev-Host
Mega-
Click to expand...
Click to collapse
slim builds have excess google apps cut out for those on a bandwidth budget or like to pick and choose their google apps from the play store
OT talk is welcomed in my threads and development is done in the open. I encourage involvement in the project in any way.
Please do not complain about OT, it encourages a fun and relaxed environment
Like the work I did, consider donating. I'm currently not working so it helps feed me
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=BPFLE54YPRV92
Yes, my PayPal account is thatguy32404, I like to keep my banking stuff separated from my social account
nexus devices threads
Mako
http://forum.xda-developers.com/nexus-4/development/lpv-79-mako-port-beta-t2807446
deb
http://forum.xda-developers.com/nex...e/l-android-lpv-dev-deb-t2856915#post55016443+
flo
http://forum.xda-developers.com/nex...id-lpv-dev-flo-enhanced-t2856920#post55016534
hammerhead
http://forum.xda-developers.com/google-nexus-5/development/l-android-lpv-dev-n5-enhanced-t2856934
Changlelog.
Changlelog.
Stable-9001
Now over 9000!!!!!!
Updated selinux security policy
tracked down some missing permissions
did some other work but can't remember
B7.0.1
Flo & Deb
removed some excess apps that were replaced and I missed in b7
B7
updated fonts, res files, animations from the latest sdk
updater-script wipes cache files
updated some more google apps.
now using smart-art
force dns to google's public dns
B6
6 finishes up the rebasing work from 5 (5.9 was just a stepping stone and getting it out to other devices so we could work out all the kinks)
(Mako only info)
The rebasing work meant a lot of clean up and trying to get it as efficient as possible so from 5 to 6 is a big step and will be quite noticeable
(mako, flo, deb)
updated egl drivers are from qcom developer are in here which are newer then the preview ones
(Hammerhead )
Proper working sound now
(All)
Built in Busybox should be working. I tested the functions and seemed good to me.
Got rid of all the looping code and debugging code to speed everything up.
Updated the preview proprietary binaries to the latest version (some can't go all the way up and are stuck on a previous set or even original preview versions)
(Hammerhead has the latest preview egl drivers)
Built in google apps have been updated.
Introduction of slim builds for those on a bandwidth budget.
Can't think of what else.
Most kinks have all been worked out
Click to expand...
Click to collapse
B5.9
Rebased completely from scratch on 81c
improved reliability and stability.
Ported to Deb, Flo and Hammerhead
Beta 5
fully permissive sepolicy based on aosp, cleaned out a lot of crud
removed reliance on n5 frameworks, merged in some current aosp
improved smoothness and increased reliability, daily driver status
Beta 4
New Kernel
more smashy smashy bugs
Dpat09 said:
For all camera issues please try this: go to the Dev settings and disable nuplayer! I'm posting it again because I think it will be lost in all the posts! If it works hopefully the contributing devs will catch it and put it in the main post
Click to expand...
Click to collapse
reserved for @defconoi kernel info
Installed it now, works great. Thank you for bringing this to deb.
Now all we gotta do is figure out how to access the radio setting outside of the setting app since they aren't there.
I had to track down the radio files and pulled them out of 4.4.3 to get the radio to start but I don't have a deb so I can't troubleshoot it as well.
I'm using the n7 as a base for mako along with all the framework files but had to use the n5's apps. The problem with deb is that if you try to use non tablet apps, it breaks the multi user feature so that might not be am option there so a script or an app that replicates the setting and configure it to the network might have to be done
sykopompos said:
Now all we gotta do is figure out how to access the radio setting outside of the setting app since they aren't there.
I had to track down the radio files and pulled them out of 4.4.3 to get the radio to start but I don't have a deb so I can't troubleshoot it as well.
I'm using the n7 as a base for mako along with all the framework files but had to use the n5's apps. The problem with deb is that if you try to use non tablet apps, it breaks the multi user feature so that might not be am option there so a script or an app that replicates the setting and configure it to the network might have to be done
Click to expand...
Click to collapse
What's the difference between your port and my
http://forum.xda-developers.com/nexus-7-2013/development-lte/android-lpv81c-deb-t2849013
Just so you all know it was me who actually did all this stuff, @sykopompos is taking all the credit ? no but really without sykopompos and his wizardly ways there would be no way this would have gotten done. He was nice enough to help with the project, then "take it over" and get it done the right way. Make sure to give him a big thanks for taking time out of his day and working on this through the nights. Without him this might have never happened. Thanks a lot man!
Sent from my Nexus 7 LTE using Tapatalk
Ansanen said:
What's the difference between your port and my
http://forum.xda-developers.com/nexus-7-2013/development-lte/android-lpv81c-deb-t2849013
Click to expand...
Click to collapse
Give it a flash and come back and give me an answer.
Oh BTW, this should have been out like a month ago but I didn't realize my really stupid derp of not modifying the bootclasspath so it wouldn't boot. I didn't realize this till after I started work on flo so if @skiman10 was helping you, you might have a part of my earlier work in yours.
Also do you have the radio files in yours?
Hoping that you guys could figure out the radio issue, soon~ thanks!
jayfallen said:
Hoping that you guys could figure out the radio issue, soon~ thanks!
Click to expand...
Click to collapse
@skiman10 is looking into our options here since he has a deb.
This is gonna be a bit of a pain to figure out how to work around this
Being that the file is almost 500mb, I assume the gapps are included in the file?
Yes @papikev thats right.
papikev said:
Being that the file is almost 500mb, I assume the gapps are included in the file?
Click to expand...
Click to collapse
Yes... Because the L apps are speeeeecccciiiiaaaaallll. Very special.
skiman10 said:
Yes... Because the L apps are speeeeecccciiiiaaaaallll. Very special.
Click to expand...
Click to collapse
oooooh, sounds phuuuuuun, Thanks guys.
Now I need L for Nexus 10 and I'll be happy
Fatal1ty_18_RUS said:
Now I need L for Nexus 10 and I'll be happy
Click to expand...
Click to collapse
Buy me a Nexus 10 and your wish will be granted lol
Once the radio gets straightened out, this will be (yet it already is) a killer rom. Very smooth. Nice new features on L. First time running it, good stuff guys. 5 star this thread. Look forward to the future with this one.:good:
skiman10 said:
Buy me a Nexus 10 and your wish will be granted lol
Click to expand...
Click to collapse
You mean buy me one...
sykopompos said:
You mean buy me one...
Click to expand...
Click to collapse
I got this one... Your apprentice is ready!
skiman10 said:
I got this one... Your apprentice is ready!
Click to expand...
Click to collapse
Good, because it wouldn't be one bit easy
Related
// Droid Bionic
// Android 4.2.2
// Current Version [ 4.2.14 ]
// All Languages
{
"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"
}
MIUI ROM 4.2.14 Full Changelog
[Home screen]
New - New Edit Home screen interface (2-12)
New - View the notificiation shade by swiping down anywhere on the Home screen (2-12)
Optimization - Previewing Home screens uses less system memory (2-12)
Fix - When user created a shortcut without a name, FC would occur (2-12)
[Phone]
Fix - Sometimes the switch for auto IP identification would display incorrectly (2-11)
[Gallery]
New - Album thumbnails of screen shots will be detected automatically (2-10)
Fix - User could not delete albums that they had shared with themselves (2-10)
Fix - When Wi-Fi was disabled, photo downloads would be canceled (2-10)
Fix - User could not copy photos to shared albums (2-10)
Fix - When user rotated phone photo would not maintain its scale or position (2-10)
Click to expand...
Click to collapse
MIUIv5 4.2.14 Download
2-19-2014: MIUI v5 4.2.14 XT912
Working:
- Everything, hopefully
MIUI General FAQ
Q: How do I root this?
A: Enable root in the perm manager, which can be found in the security folder.
Q: Why is G-Apps not listed for Download?
A: Too Bloaty, add a Google account and install the play store as an APK, I suggest using Aptoide to find it.
Q: 4G LTE isn't working
A: Load the Phone, dial *#*#4636#*#*, goto Phone information, Set preferred network type to LTE/CDMA auto (PRL).
Q: Help! Phone/SystemUI/Keyboard Isn't working/Is Force Closing!
A: Make sure to do a completely clean wipe, also I'm not sure how well this will work if flashed in CWM.
Q: The Browser looks terrible.
A: Settings -> Advanced -> User agent string -> MiOne (It Renders much better & more naturally!)
Q: My Filesystems won't mount/My PC can't see my device/My phone won't act as a MTP/USB Mounting isn't working!
A: Settings -> Developer Options -> Enable Development / USB Debugging (switch both to on)
Link as soon as rom uploads!
Sent from my XT910 using Tapatalk
kascro said:
Link as soon as rom uploads!
Sent from my XT910 using Tapatalk
Click to expand...
Click to collapse
I'm source building for the entire Moto device tree, each source build takes about 3-4 hours, so I have roughly 40ish hours of source building for 12 devices to do before this is completed.
Honestly though since this thread got a reply first I'll play favorites and finish this before everything else
Thank you very much !
Sent from my XT910 using Tapatalk
@Tquetski Thank you very much for your efforts. You mentioned in the header of your post "All languages", does this mean the Chinese & English like default or did you manage to include further translations? If so, which?
the thread says "Droid Razr", does this mean there will be only XT912 version? Do you plan releasing a version for umts_spyder (XT910)?
Thanks!
woonaval said:
the thread says "Droid Razr", does this mean there will be only XT912 version? Do you plan releasing a version for umts_spyder (XT910)?
Thanks!
Click to expand...
Click to collapse
You can directly download for UMTS_SPYDER version here :
http://en.miui.com/download-21.html
All Languages Miui v5 (XT910) ; http://forum.xda-developers.com/showthread.php?t=2597488
majamee said:
@Tquetski Thank you very much for your efforts. You mentioned in the header of your post "All languages", does this mean the Chinese & English like default or did you manage to include further translations? If so, which?
Click to expand...
Click to collapse
My MIUI releases are international and include every avail language, in 2-3 hours I should be done with MIUI for this device.
I just finished my 'code test' for XT926, and have begun building for this device.**edit: As soon as building for already supported phones are done this is next
To be clear I don't care who is releasing MIUI for this phone, I'm doing this for 'completion' purposes and not to be in competition, It's my goal to fork MIUI to every device I can in bulk atm; I'm fine with people using the CM base I'm building for their own MIUI projects on this device as well, It's not about money or territory just fun
Um, this may be a little off topic but since the other MIUI thread is closed, I dunno where else to ask. I am trying to install the official santajin port of 4.2.7. So I am on clean 4.1.2 en.eu OTA. I factory reset erasing my internal storage. On the 2nd boot, after the android guy, I go into SS. I made a 1G/4G/1G slot 1 in SS, the maximum size. I installed MIUI 4.2.7. I clean cache/davlik. I reboot into system without installing gapps yet. That seems to be as clean as an install as I can think of. After going through the setup phase, I have about 70M/1G free and it goes down fast without doing anything. It's so slow it's basically unusable. I reboot again, same thing. Is this normal? This seems like I shouldn't even think of opening the default MIUI apps, forget installing my own stuff... I tried miuiandroid's version of 4.2.7 and it was the same. Oh BTW my device was asiaretail. What am I doing wrong here? This can't be what everyone is using...
Is this ROM cm based smali ported? Or offical 4.1 based?
Sent from my XT875 using XDA Premium 4 mobile app
adtrisno said:
Um, this may be a little off topic but since the other MIUI thread is closed, I dunno where else to ask. I am trying to install the official santajin port of 4.2.7. So I am on clean 4.1.2 en.eu OTA. I factory reset erasing my internal storage. On the 2nd boot, after the android guy, I go into SS. I made a 1G/4G/1G slot 1 in SS, the maximum size. I installed MIUI 4.2.7. I clean cache/davlik. I reboot into system without installing gapps yet. That seems to be as clean as an install as I can think of. After going through the setup phase, I have about 70M/1G free and it goes down fast without doing anything. It's so slow it's basically unusable. I reboot again, same thing. Is this normal? This seems like I shouldn't even think of opening the default MIUI apps, forget installing my own stuff... I tried miuiandroid's version of 4.2.7 and it was the same. Oh BTW my device was asiaretail. What am I doing wrong here? This can't be what everyone is using...
Click to expand...
Click to collapse
Memory leak; I have no idea,
Give me some time to finish souce builds and I'llhave this up soonish
waiting with fingers crossed mate!!
Tquetski said:
Memory leak; I have no idea,
Give me some time to finish souce builds and I'llhave this up soonish
Click to expand...
Click to collapse
Ok, take your time... I was wondering, what steps are people doing clean installing miui v5 and what am I doing differently?
adtrisno said:
Ok, take your time... I was wondering, what steps are people doing clean installing miui v5 and what am I doing differently?
Click to expand...
Click to collapse
Full wipes and format system
Also any volunteers to test this before I wantonly throw it up
!
this thread should be deleted !!!! you make thread open with some rom theme but you don't have any rom.that what you do i for nobody interestingly. first make your rom finish and after that make new thread with link for download !!!!!:silly: before that do not make time waste here !
mirot said:
this thread should be deleted !!!! you make thread open with some rom theme but you don't have any rom.that what you do i for nobody interestingly. first make your rom finish and after that make new thread with link for download !!!!!:silly: before that do not make time waste here !
Click to expand...
Click to collapse
Take it easy..... He is source building MIUI for lots of motorola devices so this could be considered...
Sent from my XT875 using XDA Premium 4 mobile app
mirot said:
this thread should be deleted !!!! you make thread open with some rom theme but you don't have any rom.that what you do i for nobody interestingly. first make your rom finish and after that make new thread with link for download !!!!!:silly: before that do not make time waste here !
Click to expand...
Click to collapse
I've already build CM10.1 for this device with source edits to accommodate MIUI's gfx and using that source base patched MIUI to it.
I can update this as MiCode updates their builds internally; as of right now the only thing standing in my way is your phones kernel, which is a little different than what I have experience with.
Even if I don't finish MIUI for this phone which may happen depending on how things play out with the kernel, I'll have still finished a suitable CM10.1 base for it that anyone can consider using for MIUI, Lewa, Color OS which would normally have severe GFX issues otherwise.
The XT925, XT926, XT907, XT897, XT897c, MB886, AtrixHD didn't have functional MIUI for a while even though the thread existed on XDA, It's a development site and since I've started this project I'm starting a thread for it, now I can push weekly updates to those devices on a solid CM base.
Truth be told I didn't like some of the posters who frequented one of my device forums and so I ignored the phone completely for uh.. a really long time.
I'm really not above being a dickhead too. Especially when you consider I'm just some guy not someone making a living off of this.
There you go dummy, I included a 'best of' because I know your attention span is real short
Edit: Project update for everyone else, everything beside the kernel is done. If I have to use your stock kernel I'll have to employ other options.
My friend kernel has always been a problem for us. For example we have only kexec kernel option and that didn't allow us to use our full hd camera till 4.4.2. With that I mean it would be maybe easier for u to build the miui with 4.4.2 which has a good functioning kernel with full hd video. But I dunno if it's possible. Just saying
Sent from my XT910 using XDA Premium 4 mobile app
Where link?
[ROM][3/26/15] Pure AOSP ROM -★| 5.1.0_R3 | LMY47I | Build #6 | Proof of concept! |★-
Pure AOSP for the Nexus 6
Preface:
This is meant to be a Pure AOSP build with just minor edits to stop the stock recovery from replacing custom recovery, add some Google edits to the ROM for GPS, and modify the ramdisk so as not to preclude it from being rooted! Its not meant to be a fancy ROM, its just meant to be a baseline AOSP ROM. This ROM was produced by following the steps in the build guide I wrote. See post #2 for build guide links!
Install Instructions
Must have custom Recovery on unlocked device
Copy ROM to device (Gapps and root too!)
Reboot to recovery
Choose Factory reset (TWRP, not sure what CWM is)
Choose Install ROM
Now you can install the Gapps, and Root if you desire!
Specs and Download Link!
Android Build Version: 5.1.0_R3 / LRX22G
Current Build Date: 3/26/2015
Download: HERE!
Recommended Add-Ons
SuperSU by Chainfire here: SuperSU Stable Version
PA Gapps here: [GAPPS][5.0.x][BETA] OFFICIAL Up-to-Date PA-GOOGLE APPS (All ROM's)
Change Log
1/19/15 - Build 6 - Complete rebuild as proof of concept for 5.1.0_r3. This is PURE AOSP with no edits and no fixes.
1/19/15 - Build 5 - Fixed Youtube, Net flix DRM play back issue. Thanks to @sykopompos for pointing me to @ayysir git hub for the fix by @BeansTown106
1/17/15 - Build 4 - Fixed Browser force close in settings.
12/19/14 - Build 3 - Updated to Android 5.0.2_r1
12/15/14 - Build 2 - Switched back up to block based build for installation speed! Thanks to @hlxanthus for the 411!
12/14/14 - Build 1 - Initial build
{
"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"
}
Click to expand...
Click to collapse
Build Guide Link
Want to build this exact ROM yourself?
Here is a great build guide I wrote: [Guide][1/19/2015] Building AOSP for the Nexus 6!
Change Log
Add-Ons
Sprint Data connectivity linked by @orlzzt is HERE!
Reserved!
Hmm... I'll take this for a spin later. Thanks!
Is it safe to say with this being pure aosp shamu that it is still set to force encryption?
Also, the drawback of not doing the block style flashable is it takes several times longer to actually install via recovery.
hlxanthus said:
Is it safe to say with this being pure aosp shamu that it is still set to force encryption?
Also, the drawback of not doing the block style flashable is it takes several times longer to actually install via recovery.
Click to expand...
Click to collapse
Yes. Its pure AOSP.
Can you give me a calculation of time to install block based and file based ROM? Several times longer is a strong statement. If you could produce factual data I would appreciate.
However I am still not going block based installs because the user can take this ROM, add or remove things before it is even installed.
But I look forward to the numbers you show me! If you dont have the data that is fine. I can change the false to try in the script ota_from_tools and test it myself. Should only take a few minutes to recompile as block based.
But thanks for the input!
Took like 3-5 minutes to install your ROM and maybe 20 seconds to at most a minute to install either rastapop or cm12alpha. Honestly I thought it stalled or failed so I rebooted recovery and installed just your ROM (instead of gapps together via twrps) and it simply takes a LONG time to flash.
Great to finally see you here scrosler!!! Always great to welcome another knowledgeable developer to the forums
hlxanthus said:
Took like 3-5 minutes to install your ROM and maybe 20 seconds to at most a minute to install either rastapop or cm12alpha. Honestly I thought it stalled or failed so I rebooted recovery and installed just your ROM (instead of gapps together via twrps) and it simply takes a LONG time to flash.
Click to expand...
Click to collapse
The exact numbers your reported time can vary buy almost 66%! Thats a huge variance.
Also, you are testing differnt ROMS. For a control I need to build this exactly as it is but block based.
I will test it on my device with a high end chronograph and report my results.
Also, what recovery are you using?
Ok, I timed the file based intall, it was 2:16.08 (which was closer to your 3 minute estimate but a far cry from the 5 minute estimate)
I will build a block based ROM tonight and test to see the difference. However its still very unlikely I would change the current set up. Although I could just post both! :highfive: Win Win for everyone :good:
But once again! Thanks for your input!
scrosler said:
The exact numbers your reported time can vary buy almost 66%! Thats a huge variance.
Also, you are testing differnt ROMS. For a control I need to build this exactly as it is but block based.
I will test it on my device with a high end chronograph and report my results.
Also, what recovery are you using?
Click to expand...
Click to collapse
I can time it if that helps, or you can test yourself if you would rather. As for recovery, the only one I know of is twrp, downloaded directly via their website (only one version there) and manually fastbooted in place.
hlxanthus said:
I can time it if that helps, or you can test yourself if you would rather. As for recovery, the only one I know of is twrp, downloaded directly via their website (only one version there) and manually fastbooted in place.
Click to expand...
Click to collapse
We are cross posting. I timed it myself and it was just a hare over 2.25 Minutes. Which is not that far off from your assert of 3.0 minutes.
Im going to build the block based tonight and post it so people can have both options.
You brought a valid point. Once again, thanks for your input!
Edit: Also, wasnt trying to beat you up, I just like solid number comparisons.
Haha no worries, us old optimus s veterans need to stick together ?
Edit: if you wanted to remove the force encryption, it is a very simple fstab.shamu edit. Under the /userdata line, change "forceencrypt" to "encryptable". Looking at a few rom sources, that is how they all do it. That way if you are encrypted you will stay encrypted. If not, then it wont force encrypt you. Would save people from having to flash an alternate kernel . .
hlxanthus said:
Haha no worries, us old optimus s veterans need to stick together ��
Edit: if you wanted to remove the force encryption, it is a very simple fstab.shamu edit. Under the /userdata line, change "forceencrypt" to "encryptable". Looking at a few rom sources, that is how they all do it. That way if you are encrypted you will stay encrypted. If not, then it wont force encrypt you. Would save people from having to flash an alternate kernel . .
Click to expand...
Click to collapse
OMG!!! Optimus S? Are you serious? That was my first Android Phone / ROM!
Yeah, I know how to shut it off. But i wanted to leave this as close to pure AOSP as I could. I think I will shut it off on the next build though. I heard the encryption can slow things down a hair too.
Ok, I just got lost reading comments. Is this encrypted? If it is, does anyone mind letting me know what to do BEFORE I flash to decrypt.
Ty.
gcng said:
Ok, I just got lost reading comments. Is this encrypted? If it is, does anyone mind letting me know what to do BEFORE I flash to decrypt.
Ty.
Click to expand...
Click to collapse
You just flash a no force encrypted kernel which I basically any of them. And as @scrosler just said he may just build it into the next build.
---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------
And yes, same user name over at android central, I had DanteRom that I released. ?
EDIT:
DAMN! There is no comparison from Block Build and File based build
Block build was roughly 2 minutes and 30'ish seconds
Block based build was 10'ish seconds!
Hey Scott glad you are building for the nexus 6 are you planing on a Clean Rom also? Or just keeping it aosp
scrosler said:
OMG!!! Optimus S? Are you serious? That was my first Android Phone / ROM!
Yeah, I know how to shut it off. But i wanted to leave this as close to pure AOSP as I could. I think I will shut it off on the next build though. I heard the encryption can slow things down a hair too.
Click to expand...
Click to collapse
I'd say leave it encrypted for now until faux finally makes it to the threads...from his g+ posts it seems his found a way to keep the device encrypted yet have around the speed as though it was unencrypted. And he's a very open source guy so I'm sure he'll share the magic
Hello everybody,
I've just compiled PACMAN-ROM for my new Z3C. Current version is PAC-LP MR1 Beta2.
Device trees are CyanogenMod's so probably all device specific CM-bugs will be there too.
The boot.img inside the zip contains CM 12.1 kernel and "Cyanogen Recovery" (no backup right now!).
For alternative recoveries/kernels scroll down to "TESTED - WORKING"...
If the rom is stable for daily use (as I hope) I'm gonna build newer version periodically (depending on PAC & CM updates).
{
"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"
}
EDITS:
2015-07-09:
i've been trying to get rid of the latest problems, i.e. crashing android browser, opera browser, voice recorder and google apps (if installed). tried 4 or 5 builds in the meantime. i've got no idea why and not the skills to search in log files.
if anyone likes to test and find out, i uploaded version from july 4th.
2015-06-25:
New Version - updated CM & PAC sources. Some new PAC features there!
Version is PAC-LP MR1 Beta2 now. Unstable with crashes.
2015-05-24:
New Version - updated CM & PAC sources
2015-05-12/13:
New Version - updated CM & PAC sources
Volume bug on in-call got solved today!
2015-05-01:
I've uploaded an EXTRA boot.img including XZDualRecovery provided by NUT's!
http://nut.xperia-files.com/?ql=34070511dc3ee6809f305c66a5fa122fcbf9dcff
Flash it before or after installing the PACROM zip. It contains the zip's
kernel + DualRecovery. Installing the rom zip will overwrite recovery again
so for backups it might be necessary
to flash it always before installing a new zip, e.g.
2015-04-29:
- Screenshots
- Yes! I got it running. After some hours of use, it seems really smooth & snappy. No reboots.
- How I installed everything: Root on Kitkat stock rom, backup TA-partition, install
Dual-recovery, update to Lollipop rooted, make nandroid backup of hole system,
unlock bootloader, flash PACMAN boot.img, wipe data/caches,
flash PACMAN zip + GAPPS ... quite some hours of work.
TESTED - WORKING:
- 2G, 3G, 4G
- wifi, wifi hotspot
- bluetooth audio
- nfc
- usb otg
- GAPPS (mentioned below)
- titanium backup
- PAC customizations (not all tested)
- video playback on youtube, vlc, mxplayer
- camera & video recording
- GPS using Google Maps
- headphone sound
- XZDR recovery (version 2.8.15 not working): http://nut.xperia-files.com/
- FOTA TWRP recovery (persistent in fota kernel partition): http://forum.xda-developers.com/z3-...12-nightly-t3010550/post58854063#post58854063
- M5 kernel (CM12.1 based): http://forum.xda-developers.com/z3-compact/orig-development/kernel-m5-kernel-t3115498
BUGS:
- phone call volume loud / not reducable in dialer app. (skype & whatsapp calls are alright) solved on 150512
- If alarm clock is set active -> reboot leads to normal shutdown -> deactivate alarm for that case
- photo: Little fish-eye effect on short distance (it's not that little actually)
NOT TESTED YET:
- encryption
Installation notes: Unlocked bootloader required
- flash boot.img (rashr on phone/ fastboot on pc), then boot into custom recovery
- wipe cache, wipe art/dalvik cache
- when coming from a different rom wipe data (factory reset)
- when changing between different gapps packages format system may be useful
- flash rom zip
- if needed flash gapps zip
Download PACMAN: https://www.androidfilehost.com/?w=files&flid=30581
Download GAPPS: http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Device trees used: https://github.com/filou76/manifest/blob/master/z3c.xml
Credits!!!:
PACMAN project for their great and cool work!! www.pac-rom.com/#Home
All CM developers for giving a solid custom rom ground!!
All Z3C developers who are trying hard to make this great phone ready for daily use, especially those couple of root/bootloader/recovery hackers!! bilbao1 for the great howto root/backup etc! [NUT]'s for this very cool online kernel builder!
Google, of course
Screen shots please...
I guess its a cm based. So we need unlocked bl right?
shakkirk said:
Screen shots please...
Click to expand...
Click to collapse
It's the same as any Lollipop based PAC ROM, so just search the web for pics.
basti2909 said:
I guess its a cm based. So we need unlocked bl right?
Click to expand...
Click to collapse
Yes.
at least a custom rom for z3c. thanks man for your efforts...
basti2909 said:
I guess its a cm based. So we need unlocked bl right?
Click to expand...
Click to collapse
I think PAC is AOSP & CM based. Custom kernel. Unlocked bootloader, yes.
drorcun said:
at least a custom rom for z3c. thanks man for your efforts...
Click to expand...
Click to collapse
Happy to build actually it's not that difficult with CM device support. Probably I'll build some monthly versions or so...
drorcun said:
at least a custom rom for z3c. thanks man for your efforts...
Click to expand...
Click to collapse
just what i wanted to write. big thanks
hope we can see some more, maybe validus/resurrection remix? (maybe i should get me better informed to do it myself^^)
becks0r said:
just what i wanted to write. big thanks
hope we can see some more, maybe validus/resurrection remix? (maybe i should get me better informed to do it myself^^)
Click to expand...
Click to collapse
:good: In case of resurrection remix you only need to add/edit 1 file (local_manifest) to be able to compile a working rom. All the rest it just setting up ubuntu, init/sync repo an start building ...
Hmm it could be a reason to unlock bootloader.,)
XZDualRecovery
I've uploaded an EXTRA boot.img including XZDualRecovery provided by NUT's! http://nut.xperia-files.com/?ql=34070511dc3ee6809f305c66a5fa122fcbf9dcff
Just flash it before or after installing the PACROM zip. It contains the original kernel + DualRecovery. CyanogenRecovery really sucks, not even a way to make backups. Now we can
does this have a camera fix included, or does that need to be flashed separately? I don't have a backed up TA partition, so I rely on the fix for image processing (like many others on here, I'm sure).
thanks in advance and nice to see the ROM!
beflythis said:
does this have a camera fix included, or does that need to be flashed separately? I don't have a backed up TA partition, so I rely on the fix for image processing (like many others on here, I'm sure).
thanks in advance and nice to see the ROM!
Click to expand...
Click to collapse
there's nothing like this included. as far as i know custom roms/ custom kernels can't handle drm keys from TA partition. not sure about flashable drm replacement, i don't think it will work, but maybe it does
perhaps someone knows more about this sony image processing stuff.
isn't that all software based? if so, i could imagine that a good camera app (FV-5 or something like) can bring the same results.
Great work mate. Been running a few hours with the updated boot.img
Hopefully there is no "memory leak"
beflythis said:
does this have a camera fix included, or does that need to be flashed separately? I don't have a backed up TA partition, so I rely on the fix for image processing (like many others on here, I'm sure).
thanks in advance and nice to see the ROM!
Click to expand...
Click to collapse
That fix is only useful on stock Sony based rom's.
bugs update
(1) i found a small, almost funny bug. couldn't reboot to recovery today because phone always ended with shutdown. i desperately flashed the boot.img again but no change. only after deactivating everything i thought not being active at installation the problem disappeared.
well, it's the active alarm, that i use every morning ...
(2) in call volume issue seem's to be somewhere hidden in android_device_sony_z3c/audio/mixer_paths.xml of the repo. just in case someone likes to search :laugh:
I have noticed a small bug, could be just me though. When rebooting while plugged in to the USB charger it goes as far as the Sony logo then freezes until I unplug it. How would I go about submitting a bug report for it?
Sent from my Xperia Z3C using Tapatalk
mrrflagg said:
I have noticed a small bug, could be just me though. When rebooting while plugged in to the USB charger it goes as far as the Sony logo then freezes until I unplug it. How would I go about submitting a bug report for it?
Sent from my Xperia Z3C using Tapatalk
Click to expand...
Click to collapse
Hi, thank's for that! I've just reproduced what you wrote. On my phone this is also connected to active alarm clock. It's rebooting fine when alarm is off. So, quite the same as my last post.
I have no suggestion about real bug reports, because of 2 reasons: this is an unofficial build, primarily for myself ... but shared. I would stop building if Z3C would get official PAC support. And I've just started building roms 2 months ago. So, I'm not having the skills (yet) for advanced debugging. Right now it's more like being voluntary apprentice :laugh: ... I'm gonna add your input it into 1st post.
For now stability of this rom is mainly dependent on PACROM itself and official CM support.
Im glad you could reproduce the same bug. I think you have done a great job mate. I'm loving this ROM and appreciate your efforts. I'm trying to figure the dev side of things myself, not having much luck yet.
Sent from my Xperia Z3C using Tapatalk
Good job, m8!
Can someone post a picture, taken by camera on this phone with this rom ?
A picture of a door , or a wall, for example. Any picture featuring a rectangular shape with straight lines.
I had a broblem be4 on CM12 @z3c , the camera ( any camera app ) took pictures, distorting proportions, like there was a fisheye filter applied
Hi guys if you don't know what wakeblock is then it is basically amplify but for users with no xposed and users on nougat. For deodexed roms it requires a modification of the services.jar file which means you need to make a build from a computer and go through hell if you're like me. I'm taking requests though to get wakeblock on different roms.
If you would like wakeblock on a rom you are using then please tell me and tell me what device and rom you are using. Also if you can then I'd appreciate it if you link me the github repository for that rom so I can sync it easier. Thanks! So to recap, tell me your rom, device, link roms github repo (optional but recommended) and I'll send you a zip with the mod to flash. After flashing download wakeblock from the play store and service should be bound. From there you can block wakelocks.
Credit to this thread for creating wakeblock and the necessary patch file. https://forum.xda-developers.com/nexus-6p/development/wakeblock-blocking-drain-late-t3526313
Credit to the user SimoIanni for helping me understand how this works and for doing two roms already.
Just download flash and install the app. Below are the wakelocks I recommend blocking.
- NlpWakeLock -- 900 000ms
- GCoreFlp -- 900 000ms
- RILJ -- 900 000ms
- UlrDispSvcFastWL -- 900 000ms
- CMWakeLock -- 900 000ms
- *net_scheduler* -- 3 600 000ms
- Wakeful StateMachine: GeofencerStateMachine -- 900 000ms
- LocationManagerService -- 900 000ms
- SyncLoopWakeLock -- 900 000ms
- NetworkStats -- 900 000ms
- Icing -- 3 600 000 ms
- ULR_BarometerReading_WakeLock -- 900 000ms
- NfcService:mRoutingWakeLock -- 3 600 000ms
- NlpCollectorWakeLock -- 900 000ms
- wake:com.google.android.gms./ measurement.PackageMeasurementService -- Disable
- Anything with FireBaseInstantIDService -- Disable
- Anything with the word analytics in the name -- Disable
- GOOGLE_C2DM -- Disable
Thanks to @Face_Plant for suggesting 900000 instead of 600000 and for suggesting the bottom four in the list above to block.
SUPPORTED ROMS:
AquariOS (built into source code)
Pure nexus
Omni
SAOSP
Dirty unicorns
Uber
ABC (ezio84)
Euclidean N5X (built into source code)
UAOSPA
crDroid
Screwd
Dark rom (I think and might be built into source code
Carbon rom (built into source code)
S.I.X rom (built into source code)
sos rom (built into source code)
AICP (built into source code)
Keep in mind that the above roms supported may not work as I don't have time to build for every rom as that would take too much time away from my life and college/university. If you are in doubt then ask me or backup then flash it. Make sure to ask me to update it if the current posted version doesn't work.
Take in mind that this wakelocks are blocked without impacting ANY functionality of the phone. You may want to increase the time if don't use geolocation at your own risk
Here are where some more zips for more ROMs will appear as there is a limit per post of how many attachments you can attach. I'm just trying to get this and everything setup as I will soon be having a batch of new roms supported. Stay tuned, as many will appear with the coming days and weeks. Thanks for all your support guys and do remember to check out the official wakeblock thread and thanks to @KennyG123 for being such a kind soul and sorting out this thread as I stupidly forgot to make a reserved post.
Here's wakeblock for pure nexus and Uber. More will arrive here in the future as roms are requested.
Works great on Pure Nexus. Thank you very much! Amplify was one of the Xposed modules I was missing the most and I'm overjoyed to have a working alternative now
{
"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"
}
How about for Six ROM? For the nexus 6p or nexus 6?
https://github.com/SiXROM?language=java
Sent from my Nexus 6P using Tapatalk
I am on stock 7.1.2 with elementalx kernel. The wakeblock app shows unsupported rom/version. Any Guide for this?
grgsujan said:
I am on stock 7.1.2 with elementalx kernel. The wakeblock app shows unsupported rom/version. Any Guide for this?
Click to expand...
Click to collapse
Stock is harder to get working but the wakeblock team is working on it so head over to their thread
Face_Plant said:
Works great on Pure Nexus. Thank you very much! Amplify was one of the Xposed modules I was missing the most and I'm overjoyed to have a working alternative now
Click to expand...
Click to collapse
Thanks I really appreciate it. Make sure you thank and check out the actual wakeblock thread
tikizondo94 said:
How about for Six ROM? For the nexus 6p or nexus 6?
https://github.com/SiXROM?language=java
Click to expand...
Click to collapse
I will definitely try and get that done today or tomorrow if possible. I'm not sure which repo to use but I think I have a good idea.
DEVILOPS 007 said:
I will definitely try and get that done today or tomorrow if possible. I'm not sure which repo to use but I think I have a good idea.
Click to expand...
Click to collapse
That would be awesome! Much appreciated..
tikizondo94 said:
That would be awesome! Much appreciated..
Click to expand...
Click to collapse
I'm having a small issue with it right now but could you do me a favor and try the pure nexus version I posted as SiXROM is extremely similar and based off pure nexus so there is a good chance it will work.
Face_Plant said:
Works great on Pure Nexus. Thank you very much! Amplify was one of the Xposed modules I was missing the most and I'm overjoyed to have a working alternative now
Click to expand...
Click to collapse
How do you have nlp wakelock? I don't have that.
DEVILOPS 007 said:
Thanks I really appreciate it. Make sure you thank and check out the actual wakeblock thread
Click to expand...
Click to collapse
I already gave you some thanks and I follow the other thread pretty closely :good:
DEVILOPS 007 said:
How do you have nlp wakelock? I don't have that.
Click to expand...
Click to collapse
Do you have location turned on? NLP is related to location.
Face_Plant said:
I already gave you some thanks and I follow the other thread pretty closely :good:
Do you have location turned on? NLP is related to location.
Click to expand...
Click to collapse
No location services?
DEVILOPS 007 said:
I'm having a small issue with it right now but could you do me a favor and try the pure nexus version I posted as SiXROM is extremely similar and based off pure nexus so there is a good chance it will work.
Click to expand...
Click to collapse
I flashed the pure nexus version. just got a boot loop. No biggie. There must be something else in there. I appreciate you trying though!
tikizondo94 said:
I flashed the pure nexus version. just got a boot loop. No biggie. There must be something else in there. I appreciate you trying though!
Click to expand...
Click to collapse
Did you try extracting services.jar, booting into TWRP, moving the file to system/framework, and setting permissions to 0644 manually? This is the method that worked for me. Flashing the file also gave me a boot loop. Make a copy of your original services.jar just in case something goes wrong so you can move in back in recovery to avoid having to reflash your ROM.
DEVILOPS 007 said:
No location services?
Click to expand...
Click to collapse
If you have no location services then that's why you don't see the wakelock
tikizondo94 said:
I flashed the pure nexus version. just got a boot loop. No biggie. There must be something else in there. I appreciate you trying though!
Click to expand...
Click to collapse
Okay, I'll try to work this problem out. Try what Face_Plant said
Face_Plant said:
Did you try extracting services.jar, booting into TWRP, moving the file to system/framework, and setting permissions to 0644 manually? This is the method that worked for me. Flashing the file also gave me a boot loop. Make a copy of your original services.jar just in case something goes wrong so you can move in back in recovery to avoid having to reflash your ROM.
If you have no location services then that's why you don't see the wakelock
Click to expand...
Click to collapse
I mean I have it but it isn't enabled and flashing the mod worked fine for me so I'm not sure what's going on with you flashing it.
DEVILOPS 007 said:
I mean I have it but it isn't enabled and flashing the mod worked fine for me so I'm not sure what's going on with you flashing it.
Click to expand...
Click to collapse
If it isn't enabled then that's why you aren't seeing the wakelock. I use "battery saving" location services, which relies heavily on Google Play Services, so that's why I have so many of those wakelocks.
I suspect that I either got a bad download or it had something to do with the unofficial build of TWRP I was using that tends to be somewhat buggy, so that's probably why I boot looped.
Face_Plant said:
If it isn't enabled then that's why you aren't seeing the wakelock. I use "battery saving" location services, which relies heavily on Google Play Services, so that's why I have so many of those wakelocks.
I suspect that I either got a bad download or it had something to do with the unofficial build of TWRP I was using that tends to be somewhat buggy, so that's probably why I boot looped.
Click to expand...
Click to collapse
Oh okay. I tried enabling location services to get the wakelock but don't see it so I might just leave it.
MARS SOM
{
"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"
}
Years of porting, Stock ROMs and My Patches came to an end...
Since Magisk has grown to a full root and modding Solution for Android have i switched with My Development to creating Magisk Module Patches. Or in other Words, Systemless ROMs.
Mainly focusing on extending the Android Build Props are there also pure Parts of the latest Pixel Device Firmwares. Get the full Pixel UI Expierence, get extra Pixel Functions and Apps together with a better overall Experience. Better Audio In- and Output, better Display Calibrations, better Performance, more Functions packed into a simple Magisk Module.
Features:
Ported Pixel Apps
Ported Pixel Features
Ported Pixel UI & Colors
Ported Pixel Black Dark Mode
Xperia Sound Enhancements
Xperia Pro-I Content Ported
HTC UI & User Sounds
Xperia Live Wallpapers
Enabled various Android Features
Enabled various Hardware Features
Enhanced Security Support
Enhanced Display Quality
Enhanced Audio Output
Enhanced Audio Input
Enhanced FHD/4K HDR Output
Enhanced Camera Functionalities
Enhanced Graphical Handling & Rendering
Enhanced Network Functionalities
Faster booting and Reboots
Requirements:
Magisk Stable 24+
Android 13 Stock Xperia FW
Magisk Init.d Injector
Download:
Sign in - Google Accounts
Bugs:
Report them if You found one!
Donations:
paypal.me/miustone
Reserved <3
Nice work. I'm glad to already see some custom ROMs (well, in that case, SOM).
However, this is the first time I encounter a SOM, is it just a Magisk module that can be turned on and off at will, switching between stock and Mars? Or shouldn't I do that?
Miustone said:
Welcome to MARS SOM
The first so called SOM
Systemless-On-Memory
SOM - The right naming for a new age of Android ROMs
Years of porting, Stock ROMs and My Patches came to an end...
Since Magisk has grown to a full root and modding Solution for Android have i switched with My Development to creating Magisk Module Patches. Or in other Words, Systemless ROMs.
Mainly focusing on extending the Android Build Props are there also pure Parts of the latest Pixel Device Firmwares. Get the full Pixel UI Expierence, get extra Pixel Functions and Apps together with a better overall Experience. Better Audio In- and Output, better Display Calibrations, better Performance, more Functions packed into two Zip Files...
Features:
Full Camera API2 Support
Full Pixel User Interface
Full Darkmode Support
Ported Pixel Apps
Ported Pixel Features
Enabled various Android Features
Enhanced Security Support
Enhanced Display 4K HDR Support
Enhanced Audio Output
Enhanced Audio Input
Enhanced Display Output
Enhanced Camera Functionalities
Enhanced Graphical Handling & Rendering
Enhanced Network Functionalities
Faster booting and Reboots
Requirements:
Magisk Beta or Canary Channel
Android 11
A way to extract and create Zip Files
(For GitHub Zips)
Downloads:
Miustone - Overview
Founder of Dev Ice Software Technologies. Miustone has 10 repositories available. Follow their code on GitHub.
github.com
Note: Zips from GitHub can't be flashed ootb.
GitHub?!:
Extract the 2 Downloaded Zips and repack everything inside of the second "MARS_SOM_XXX" Folders to Zips
Flash these Zips with Magisk and enjoy <3
Bugs:
QuickSwitch is needed for the Pixel Launcher
Donations:
paypal.me/miustone
Click to expand...
Click to collapse
Could you please tell me where can I obtain more information about this "Mars Som" and more details instruction to install it. Thanks for your reply.
Thanks for Your Interest! I'm reconstructing the SOMs on GitHub and the ReadMe's there will be updated soon with more Infos! For now, just Check My (Discontinued) MARS-SOM Repo on GitHub...
BR
Hrm guessing this isnt rdy yet? Just tried installing the base and rom in Magisk 23 as modules but it causes a bootloop. Noticed on GitHub says android 12 is required?
tonysunshine said:
Hrm guessing this isnt rdy yet? Just tried installing the base and rom in Magisk 23 as modules but it causes a bootloop. Noticed on GitHub says android 12 is required?
Click to expand...
Click to collapse
Sorry for the Issues! Could You try again now? I have removed the Vendor stuff for now...
Can You also try to use them seperated? I do actually not own the 1 III so i can't test Myself. Feel also free to collab. with Me on GitHub
Miustone said:
Sorry for the Issues! Could You try again now? I have removed the Vendor stuff for now...
Can You also try to use them seperated? I do actually not own the 1 III so i can't test Myself. Feel also free to collab. with Me on GitHub
Click to expand...
Click to collapse
Hi what do you mean by use them separated? Like install/activate the base module, reboot, then do the system module?
Yep, it could be one of them or both which causes the Bootloops. I updated the Base so it might be that... The System should cause less Problems at the end... @tonysunshine
I also got a bootloop after installing the zips. I tried following the instructions on your github and was able to do the device simulation with the props config module, but can't follow the next step "Download and extract the NgaResources.apk to /MARS_SOM_SYSTEM/system/product/app/NgaResources" as there's no NgaResources.apk file anywhere on the github that I can find. Could it be this missing file that's causing issues?
Xperia 1 III here.
I followed the steps on github and everything went smoothly even after I flashed the MARS_SOM_BASE zip. However, after flashing the MARS_SOM_SYSTEM , I stuck in a bootloop. I have downloaded the MARS_Product_Overlay apk and place it.
I am willing to help if you need further info.
akkk44 said:
Xperia 1 III here.
I followed the steps on github and everything went smoothly even after I flashed the MARS_SOM_BASE zip. However, after flashing the MARS_SOM_SYSTEM , I stuck in a bootloop. I have downloaded the MARS_Product_Overlay apk and place it.
I am willing to help if you need further info.
Click to expand...
Click to collapse
Wow, I'm glad the BASE zip worked so far. You are getting a lot out of it. But I'm pretty sure there will be bugs around somewhere...
And thanks a ton for Your Post! I'm on the go but if You want to test around...
Move folders out of the _SYSTEM /system Folder like /product, /vendor and so on. Start with removing all except for one Folder and try if it boots up. If You can tell Me which folder causes issues or even which files will I handle it on GitHub for You.
About the Files @tardis_42 . You can find the Files on My Website / Google Drive. The link is in the Readme on GitHub
Miustone said:
Wow, I'm glad the BASE zip worked so far. You are getting a lot out of it. But I'm pretty sure there will be bugs around somewhere...
And thanks a ton for Your Post! I'm on the go but if You want to test around...
Move folders out of the _SYSTEM /system Folder like /product, /vendor and so on. Start with removing all except for one Folder and try if it boots up. If You can tell Me which folder causes issues or even which files will I handle it on GitHub for You.
About the Files @tardis_42 . You can find the Files on My Website / Google Drive. The link is in the Readme on GitHub
Click to expand...
Click to collapse
I wanna help but recovering from bootloop is a real pain in my a**. I somehow managed to disable all magisk moudules and get out of boot loop but I am not sure if I can do it again. The only two methods I knew about getting out od a bootloop is removing modules with TWRP but currently 1 iii doesn't have one, the other method is using the adb command but I am not sure how to send adb commands to the phone while it stucked in a bootloop.
Any ideas?
akkk44 said:
I wanna help but recovering from bootloop is a real pain in my a**. I somehow managed to disable all magisk moudules and get out of boot loop but I am not sure if I can do it again. The only two methods I knew about getting out od a bootloop is removing modules with TWRP but currently 1 iii doesn't have one, the other method is using the adb command but I am not sure how to send adb commands to the phone while it stucked in a bootloop.
Any ideas?
Click to expand...
Click to collapse
You can simply hold Volume down while booting to get into "Recovery Mode". It disables all Modules and most Apps. You can reboot from that into the normal state again... Should mention that somewhere I think... (It's a Magisk Feature too)
Edit: Does not work with USB Connected! Hold Volume down after You see the Bootloader Unlocked Message. Keep holding until You are in Android
Edit 2: Think Ill make Video guides too for some needs if there is enough Interest...
Miustone said:
You can simply hold Volume down while booting to get into "Recovery Mode". It disables all Modules and most Apps. You can reboot from that into the normal state again... Should mention that somewhere I think... (It's a Magisk Feature too)
Edit: Does not work with USB Connected! Hold Volume down after You see the Bootloader Unlocked Message. Keep holding until You are in Android
Edit 2: Think Ill make Video guides too for some needs if there is enough Interest...
Click to expand...
Click to collapse
Understood! I will test the module out sometime……
akkk44 said:
Understood! I will test the module out sometime……
Click to expand...
Click to collapse
Great! Thanks in advance!
Miustone said:
About the Files @tardis_42 . You can find the Files on My Website / Google Drive. The link is in the Readme on GitHub
Click to expand...
Click to collapse
I tried there, but the file mentioned on the github readme (NgaResources.apk) isn't there - just these two:
tardis_42 said:
I tried there, but the file mentioned on the github readme (NgaResources.apk) isn't there - just these two:
View attachment 5445471
Click to expand...
Click to collapse
Thanks for pointing out. I'm uploading the latest Version to this Google Drive Directory rn! Sorry for the Trouble...
Updated the Thread, MARS_SOMs and GitHub<3
HUGE UPDATES INCOMING!
MARS will be available over GitHub Releases so You can easily Download ready-to-use Zips of MARS for Magisk. Also included are now OTA Updates for MARS over Magisk and the focus Changed to GSIs again. Use PHH AOSP 12 or PIXEL EXPIERENCE 12 by Ponces to unleash Your Xperias