These builds are unofficial, unsupported by the LiquidSmooth team. Do not file bug reports to the Liquidsmooth devs -- instead please post them in this thread.
What is LiquidSmooth? Find more information here: Official LiquidSmooth G+ Community
Installation instructions:
Backup what is precious to you
Wipe system, data and cache
Flash ROM (link below)
Flash gapps (link below)
Reboot and wait for welcome screen
Downloads:
Liquid-JB-v2.37-UNOFFICIAL-20131106-ovation.zip - 105.01 MB
Standard Gapps: Goo.im - gapps-jb-20130813-signed.zip
Slim Gapps (compatible with "Dark Liquid" switch): Slim Gapps download page
Banks's basic Gapps (absolute minimal gapps install): XDA thread
Known issues/bugs
Text strings in the UI are a bit wonky, especially those for Wi-Fi and Bluetooth (i.e. "deny" instead of "connect" when adding a new Wi-Fi network)
Bluetooth tethering does not work. Fixed in 2013-11-06
Potentially there can be some rotation bugs. LMK if you identify any
There is not Tablet UI available, and auto-patcher does not support LiquidSmooth at this point
Generic screenshot showing LS features
{
"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"
}
Interesting...
Sent from my Nook HD+ using xda app-developers app
It looks nice is trim disabled?
Sent from my PC36100 using xda app-developers app
jpisini said:
It looks nice is trim disabled?
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
+1.... would like to try if it's disabled (I have the chip that can be potentially bricked by trim).
320flyboy320 said:
+1.... would like to try if it's disabled (I have the chip that can be potentially bricked by trim).
Click to expand...
Click to collapse
Trim is disabled.
TY!! but wifi doesn't work for me
------------------------------------------------------------
oh, it woks after fixing permission @twrp. TY again!
Looks good. I will try to flash this this weekend.
Sent from my LG-LS855 using Tapatalk 2
Just noticed on the settings screen, and if you tap on BATTERY, settings crashes. Other than that, it's working good so far...:good:
320flyboy320 said:
Just noticed on the settings screen, and if you tap on BATTERY, settings crashes. Other than that, it's working good so far...:good:
Click to expand...
Click to collapse
flyboy,
As the other poster mentioned, I too can't get WiFi to work. How did you get past the initial start up settings procedure? Setup won't let me skip logging into a network so I'm stuck.
smithmal
Edit - figured it out. When setting up tablet on the "Wifi Select" screen, for some reason when adding a network, network settings cannot be saved (seeing this when manually adding a SSID as I have mine hidden). Click "Skip" and then click "Cancel" and then setup will finish.
Still cannot manually add my hidden SSID though so I can't connect to my WiFi network.
Ya WiFi is for sure screwed up. I did manage to add my hidden SSID after trying a few times. Although as with the APPS in SETTINGS the button names seem to be messed up. If I try to uninstall an app, I only get the option to either INSTALL or SDCARD...bit weird...:silly:
Could you please in the next release, switch the release flag here to false, this makes it so the build is Unofficial.
I really like the boot animation on the ROM!
Sent from my LG-LS855 using Tapatalk 2
320flyboy320 said:
Ya WiFi is for sure screwed up. I did manage to add my hidden SSID after trying a few times. Although as with the APPS in SETTINGS the button names seem to be messed up. If I try to uninstall an app, I only get the option to either INSTALL or SDCARD...bit weird...:silly:
Click to expand...
Click to collapse
I'll have a look at these issues (starting with Wi-Fi) and try to fix them next week.
deadman96385 said:
Could you please in the next release, switch the release flag here to false, this makes it so the build is Unofficial.
Click to expand...
Click to collapse
Will do.
jisoo said:
I'll have a look at these issues (starting with Wi-Fi) and try to fix them next week.
Will do.
Click to expand...
Click to collapse
I. Noticed something odd with the WiFi this weekend. I flashed the ROM on Friday,, and then yesterday I messed something up while restoring some stuff so I did another clean flash. This time I used the "minimal gapps" and when I tried setting up, it would not even show any of the 4or 5 access points nearby. And nothing I tried would produce any results.
So,, I went back and flashed the AIO gapps and then all the AP's showed up and I was able to log on to it.
Just thought I'd share. I think it's kinda odd that the gapps would make a difference in being able to see wifi.
Sent from my Nook HD+ with unofficial LiquidSmooth on emmc using Tapatalk 4
bpaulien said:
I. Noticed something odd with the WiFi this weekend. I flashed the ROM on Friday,, and then yesterday I messed something up while restoring some stuff so I did another clean flash. This time I used the "minimal gapps" and when I tried setting up, it would not even show any of the 4or 5 access points nearby. And nothing I tried would produce any results.
So,, I went back and flashed the AIO gapps and then all the AP's showed up and I was able to log on to it.
Just thought I'd share. I think it's kinda odd that the gapps would make a difference in being able to see wifi.
Sent from my Nook HD+ with unofficial LiquidSmooth on emmc using Tapatalk 4
Click to expand...
Click to collapse
Interesting. Are you refering to the AIO gapps listed for Slimbean (see here) or full CM listed 4.3 gapps (08/13/2013 gapps). I've tried this with the Slimbean AIO gapps and it didn't work (re-flashed it a couple time to make sure). I wonder if going from minimal gapps to AIO gapps is the trick?
Also, after getting all your APs to show up is LiquidSmooth supporting BT? As I recalled BT worked, I just couldn't connect to my AP.
Edit: Tried installing with minimal first and then re-flash AIO and I can't save password for my AP. Once password is entered I only have two options: "Failed to save network" and "Deny"
smithmal
Guys,
Sorry about the WiFi problems. I tested this build with no gapps and it worked ok for me, so I didn't know about the issues.
I'm a bit busy at work right now, but I will get back to this at the end of the week and try to put up a better working build.
I have no issues with WiFi
Sent from my BN NookHD+ using XDA Premium 4 mobile app
smithmal said:
Interesting. Are you refering to the AIO gapps listed for Slimbean (see here) or full CM listed 4.3 gapps (08/13/2013 gapps). I've tried this with the Slimbean AIO gapps and it didn't work (re-flashed it a couple time to make sure). I wonder if going from minimal gapps to AIO gapps is the trick?
Also, after getting all your APs to show up is LiquidSmooth supporting BT? As I recalled BT worked, I just couldn't connect to my AP.
Edit: Tried installing with minimal first and then re-flash AIO and I can't save password for my AP. Once password is entered I only have two options: "Failed to save network" and "Deny"
smithmal
Click to expand...
Click to collapse
I was referring to the SlimBean AIO.
The very first time I flashed it, I used the one (can't remember its name) that pulls up the interface where you can pick and choose the gapps you want to install. That worked for me.
Then when I re-flashed (clean) I just wanted to get going, and didn't really care what was on it, so did the minimal gapps. That's when I couldn't see any WiFi Access Points. But since I knew I had gotten access to WiFi the first time, I figured there had to be something different between my 2 flashes. But not wanting to go through and select things again, I just flashed the AIO gapps over everything. That time WiFi worked.
I can't answer about BT. I'm not using any BT connections with my Nook at this time.
And as to your edit, I think I got some kind of error message too, but when I got to the next part, where you log into your google account, it had access and everything worked. So despite the error message regarding WiFi, I was able to continue, and haven't really had any WiFi issues with it.
So I've uploaded a new build for v2.37.
I tested Wi-Fi, and although the text strings in the UI are wrong (for instance it says "deny" where it should say "connect"), Wi-Fi and BT tethering now work as far as I can test.
I also merged all of the bug fixes and cleanups the LiquidSmooth team has added since the last build, but these are quite minor. There does not seem to be any new features coming into the 4.3/JB3 branch. This is the case for more or less all ROMs, as everyone is busy rebasing and merging functionality into the 4.4 branches.
The new build is also properly marked as unofficial, as requested by the LiquidSmooth devs.
jisoo,
Thanks for this ROM, your work porting this to the HD+ is much appreciated. I loaded this up and took it for a spin earlier today. WiFi connection is still a bit dicey. It took me three or four times before it would connect (using WPA2 security on my network), but the tablet did finally connect. It seemed my signal strength was a bit lower than other ROMs, but I don't have any hard data to support that.
The ROM seemed snappy enough (coming from the Slimbean ROM which is very responsive). BT turned on when selecting it, but I haven't gotten a chance to test it yet so that's on my list.
I will do some more tests on DL speeds/UL speeds/WiFi strength later tonight and let you know.
smithmal
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"
}
Minidoudou is available online! There is still work to do, but it is already fully functional and you can try it on to configure your own mod of CyanogenMod 6.1.0 for HTC Dream / Sapphire.
Try it on here: http://minidoudou.joelcogen.com
and let me know what you think!
Todo (in the order it will be done, probably)
- Connect to an external storage provider (sendspace)
- Make it pretty
- Fix IE UI issues
- Add system/data option, with a nice drag&drop
- Add advanced mode, with moving of any APK in the ROM
- Display "hand" cursor on draggable elements
- Check /system size
- Fix changes application order
- Add deprecation to APKs
- Users management for contributors
- Select field for mutually exclusive packages (kernel)
- Fix double upload issue
- Whatever you suggest below
There has already been some discussion about how much control to include, so here is a first poll: How much control would you like when using Minidoudou?
I'm not sure if it's the rom or my phone,
But I've used your rom, and ir worked great.
When I walked trough the city that evening
I was looking for wifi (without passwords) when I found one,
I tried to connect, but it only said, getting IP adress, connecting and again getting IP,...
Even on my home wifi I had this problem. So i did a full wipe and reinstalled the minimou Final version.
Can you please tell me if this is rom based or just bad luck with the wifi on my phone?
And you are doing a great job, I also tried smoki rom, but it had some lag on the UI.
It would be nice aswell if we could put custom icons (of the topbar) and custom battery Icon
milowke said:
I was looking for wifi (without passwords) when I found one,
I tried to connect, but it only said, getting IP adress, connecting and again getting IP,...
Even on my home wifi I had this problem. So i did a full wipe and reinstalled the minimou Final version.
Click to expand...
Click to collapse
Hi,
You're the first to report wifi problems, so I'll look into it.
As for the icons, it might be hard because that means customizing the theme, something I don't have a lot of luck with. I'm keeping it in mind, and once it is stable and has most of its functionnalities regarding packages, I'll look into it or for a contributor with theming experience.
Thanks for your feedback!
jojotm said:
Hi,
You're the first to report wifi problems, so I'll look into it.
As for the icons, it might be hard because that means customizing the theme, something I don't have a lot of luck with. I'm keeping it in mind, and once it is stable and has most of its functionnalities regarding packages, I'll look into it or for a contributor with theming experience.
Thanks for your feedback!
Click to expand...
Click to collapse
Your welcome,
And Thank you for your work on this lovely rom.
I have made a new package on your website, and i'm going to use it again.
I'll report any issues I have
Not sure if I'm allowed to do this double post thing.
But when I tried to download the rom I found an issue.
Wen you click on download you get the link like this
http://minidoudou.joelcogen.com/download/MDD_HTC_Sapphire_CyanogenMod_610_RC1_Milow_Testingzip
So when you save it, it's just a file, no zip file
So you have to put a dot in front of the zip yourself
NOt sure if you noticed it
milowke said:
Wen you click on download you get the link like this
http://minidoudou.joelcogen.com/download/MDD_HTC_Sapphire_CyanogenMod_610_RC1_Milow_Testingzip
Click to expand...
Click to collapse
Didn't notice that. It's fixed.
Sent from my HTC Magic using XDA App
Hi
I have done a clean install of minimou final, and after it I did the install of
the minidoudou. But it seems to have an endless boot up
It's stuck on the Proximus logo for 15 minutes now.
I have the following things in my minidoudou:
Advanced Task Killer 1.9.3
Browser CM6.1.0-RC1
StopWatch & Timer 1.15
aNetShare (wireless tethering) 2.30
Twitter 1.0.5
XDA developers 1.3.2
Gapps MDPI MDD 2010.10.20
Facebook 1.4.0
Sapphire 32A kernel - Brian Crook Nightly 231
Barcode Scanner 3.5
LauncherPro 0.8.1.1
Email CM6.1.0-RC1
I have the same SPL, RADIO, HBOOT as you I only use another recovery
RA magic v1.7.0.1
Whats wrong on this ?
*EDIT*
I will try to do just a clean install of minidoudou, without extra apps
But i'm wondering, Do I need to install minimou final and than install the minidoudou?
OK I did a full wipe
and I installed the minidoudou,
this package:
Gapps MDPI MDD 2010.10.20
Sapphire 32A kernel - Brian Crook Nightly 231
LauncherPro 0.8.1.1
On the wizard, I had to connect to WIFI for the google account.
Well It found my wifi, typed in the password, but it was the same
Retrieving IP adress
remember
Connecting
and it keeps repeating.
I installed minimou Final again, cause I realy need WIFI.
I'll try again if it's fixed.
milowke said:
I have done a clean install of minimou final, and after it I did the install of
the minidoudou. But it seems to have an endless boot up
It's stuck on the Proximus logo for 15 minutes now.
I will try to do just a clean install of minidoudou, without extra apps
But i'm wondering, Do I need to install minimou final and than install the minidoudou?
Click to expand...
Click to collapse
Hi again,
I just tried your config over a Minimou-final install (already with several of packages) and it seems to work.
It might be a LauncherPro problem, I remember it gave me trouble when building Minimou-final, so maybe flashing a non-upgraded Minimou with MDD causes the problem. Try fully upgrading your Minimou, then flashing MDD.
If it still doesn't work, the best solution is usually to do an 'adb logcat' (from the android sdk tools) to see the phone's log and look up the error message, or post the result here.
MDD is a separate project from Minimou, they're only link is me, so you don't need Minimou to flash, you can wipe from the recovery and then flash and it should work fine.
On the sidenote, in the future it would be easier if you just post your config name rather than the set of packages. It makes for shorter posts and it's easier to find (I compare the list to download your config).
Ok I did installed minimou final, and did the wizard thing,
Since launcher pro was expired I had to download the newest version.
When it was installed everything was working fine.
So I disabled wifi and let my phone forget my wifi settings.
After it I flashed MDD (Clean_without_Launcher(UPGRADE))
It took about 5-7 Minutes to boot,
I tried wifi, and it worked
I hope this info was helpfull for you.
Great! This LauncherPro problem is a real *****, I don't know why upgrading is such a problem.
The WiFi is stranger. I still have to look into it, I'll see if I can reproduce it.
jojotm said:
Great! This LauncherPro problem is a real *****, I don't know why upgrading is such a problem.
The WiFi is stranger. I still have to look into it, I'll see if I can reproduce it.
Click to expand...
Click to collapse
OKi, thnx.
Maybe it's just your launcherpro apk?
cause when I installed minimou final, installed launcherpro from the maker his website, and upgraded to MDD (without extra apps (no launcher as well), it worked fine, when I did the same but with launcher in the MDD package it failed at the wifi connection.
Even a clean install of MDD with launcher (cause you need one) failed so.
NOt sure if it's the same with the AWD launcher.
Anyone happen to have problems with gps? 2 of my apps (Sygic and iGO) are crashing after moving to RC1. I don't blame minidoudou but just wanted to see if i'm the only one. I'm running bcrooks kernel.
saibot64 said:
Anyone happen to have problems with gps? 2 of my apps (Sygic and iGO) are crashing after moving to RC1. I don't blame minidoudou but just wanted to see if i'm the only one. I'm running bcrooks kernel.
Click to expand...
Click to collapse
Uhm, I didn't tried the GPS yet.
Do they crash when you open the app or when you are using it for a couple minutes?
Sygic freezes when i want to create a rather long (1k KM) route.. so i think it's Sygic's fault. It might not be compatible with 2.2.1. I'll try some other software as 'gps essentials' appears to be working fine.
On another note i cannot install brut's google maps... tried removing the original google maps, they're SapphireMaps package?
Thanks in advance for any help.
saibot64 said:
Sygic freezes when i want to create a rather long (1k KM) route.. so i think it's Sygic's fault. It might not be compatible with 2.2.1. I'll try some other software as 'gps essentials' appears to be working fine.
On another note i cannot install brut's google maps... tried removing the original google maps, they're SapphireMaps package?
Thanks in advance for any help.
Click to expand...
Click to collapse
Well I tried Navigon and it worked fine, couldn't try Sygic's GPS cause it needed 3D acceleration.
You can't remove the original google maps indeed. they are in the package.
As for the brut's google maps, you should look over here
http://forum.xda-developers.com/showthread.php?t=630887
try this one: maps4.6.0.4686-brut-renamed.apk
Same here, I only tried Google Navigation and it worked fine.
Regarding Maps, you can't remove them because they are in /system, but I'll add the option to install in /data to MDD soon. I remember having trouble updating it in the past, but I don't see why, because other /system packages can usually be updated just fine....
Hello, i tried to cook a rom yesterday using minidoudou but it still says "Pending" along with some others!
Also when i press on "x packages" to see what packages other roms include, i get an error with firefox 3.6.12. With chrome there is no such problem.
Thanks again for the great work.
I like this idea a lot. Kudos to the developer(s).
Can we add different devices? Per say the G1?
I've made a few edits to jt1134's 06/20 build of fascinate CM7MTD (which has working GPS!!) to get it working on our radio (EE19 or EC10, your choice) and have uploaded this for others to use. I'm not going to create a release thread of any kind yet as jt is working on getting all 3 of our phones supported officially by CM after he finishes a painstaking process of rewriting sensor drivers (that will mean all hardware will be working, then mms will be looked at). And lmartin92/jt will be able to get us native builds after that happens.
Please visit this thread to make sure you click his thanks and/or throw jt a little money, if it weren't for him alone we would probably never see the merging into mainline CM7!
This release is as is and we're not needing any bug reports at this time.
Note: It will also say Verizon wireless as your service provider, but that's just because I didn't edit the eri.xml file within framework-res.apk
jt1134 said:
Here is a test build/preview of the 2.6.35 MTD CM7 port for Fascinate. It is built off the work of TeamHacksung, and is very different from earlier CM7 builds. At this point it is very functional, but still in very much of an ALPHA state.
Working:
Calls!!
Bluetooth!!
3G data
WiFi
SMS
Camera/Camcorder
USB mass storage / sdcard
Sensors (accelerometer / compass)
GPS!!
Not Working:
MMS
light and proximity sensors
Included in the package is the base ROM and kernel. GAPPS must be flashed separately. Link below. You may also use nemesis2all's kernel here : http://forum.xda-developers.com/showthread.php?t=1119169
When flashed the first time, your filesystems will be converted to MTD (yaffs2/ext4). Do not try to flash any other ROMs via cwm at that point, and do not try to get into recovery via the 3 button method. Use adb reboot recovery or the reboot recovery option from the power menu. To revert, and switch to another ROM, flash a full Odin/Heimdall package (like DL09).
Since your filesystems are being fully converted, there is no need for Voodoo or any other lagfix. DO NOT TRY TO INSTALL ANY KIND OF LAGFIX ON THIS ROM!!! Voodoo sound capability is however included in the kernel.
To install, boot into cwm recovery, wipe data, and flash the ROM. It will reboot and the do the actual install. If you are on a previous version, you can simply flash it over your curren install. If you have problems, try wiping data first. The ROM will work whether you are on rfs or ext4.
*** Update 06/09 ***
fixed in-call audio
fixed bluetooth in-call audio
*** Update 06/20 ***
fixed GPS
re-enabled backlight notifications (you DO NOT need BLN control app)
disabled (broken) auto-brightness
other misc changes, see my github
This is a WiP, and meant as more of a preview than anything else. If you enjoy it, click the Thanks button. Enjoy
http://goo-inside.me/gapps/gapps-gb-20110613-signed.zip - GAPPS
Click to expand...
Click to collapse
Download link: Click Here
bd, shouldn't this thread be in the development forum for the Mes???
Snyperx said:
bd, shouldn't this thread be in the development forum for the Mes???
Click to expand...
Click to collapse
Could be, but I don't consider it development since this build is temporary until we get a native one built. (I didn't want to post another thread in there since lmartin already has one started and would simply update it once it's done.)
When you say native. Does that mean a build done specificly for mesmerize. In which most everything will be working. Sorry just trying to make sure I understand the lingo
Tap-a-Talked from my Mesmerize
Is this only for the Mes or is it safe for Showcase?
scarmon25 said:
When you say native. Does that mean a build done specificly for mesmerize. In which most everything will be working. Sorry just trying to make sure I understand the lingo
Tap-a-Talked from my Mesmerize
Click to expand...
Click to collapse
When I say native build, I mean that it's built from source with the appropriate uscc/cellular south edits made pre-build - instead of making a few edits post-build like I've done here with this release. Jt has repos on github for both the mesmerize and showcase but they weren't updated yet so we couldn't build it. When he does (after he get's sensor drivers rewritten) then he will either build it or lmartin92 willl and we'll update the thread in the dev forum. This is just to hold people over until then Regardless of whether it's built native or kang'd like I did here, it's still as functional as listed in the OP - but building natively is the better practice and guarantee of no bugs.
StuckinMemphis said:
Is this only for the Mes or is it safe for Showcase?
Click to expand...
Click to collapse
No sorry, I still have yet to learn exactly what changes are required to make it work for CS, so this is only for the mesmerize.
Cool deal. Thanks for clearing that up for me. Man I wish I had your guys inteligence when it comes to this stuff. It amazes me how you do what you do. I will be lookin for it as honestly that has been my reason for holding off on cyanogen. Waiting for it to get more functional which looks like it is now thanks to JT and the others. You all rock and thanks for all you guys do.
Tap-a-Talked from my Mesmerize
scarmon25 said:
Cool deal. Thanks for clearing that up for me. Man I wish I had your guys inteligence when it comes to this stuff. It amazes me how you do what you do. I will be lookin for it as honestly that has been my reason for holding off on cyanogen. Waiting for it to get more functional which looks like it is now thanks to JT and the others. You all rock and thanks for all you guys do.
Tap-a-Talked from my Mesmerize
Click to expand...
Click to collapse
No problem, glad to share knowledge when I can . At first I felt the same way, it was very overwhelming and I never thought I'd be able to actually get involved with bringing things to the community, but the more you hang out in IRC the more brave you get and once you start cracking open .apk's and get the basics down, it becomes fairly easy to learn and progress . Especially when you have brains to pick like jt1134/phidelt82/jamezelle (to name only a few)!
Alright, so I tried to flash this on CWM 3 (I was on Heinz 57 EE19 build before this), and I got an error almost immediately, saying "asset failed", along with a bunch of stuff regarding the Fascinate. I did wipe data and all that, so I'm wondering what I'm doing wrong. I would really like to try this out!
btoast777 said:
Alright, so I tried to flash this on CWM 3 (I was on Heinz 57 EE19 build before this), and I got an error almost immediately, saying "asset failed", along with a bunch of stuff regarding the Fascinate. I did wipe data and all that, so I'm wondering what I'm doing wrong. I would really like to try this out!
Click to expand...
Click to collapse
Can you be more specific on the "stuff regarding the Fascinate" ? I haven't come a crossed this issue, basically it should reboot as soon as you hit "install .zip" to a CM7 splash screen and then it'll go right back into CWM, finish the install then reboot a few more times before it actually boots up.
EDIT:
Okay someone else just had this happen, he was in EE19 H57 as you were, so I'm thinking that's the cause - I went from EE19 PNP to Cm7MTD with no issue. I'm looking into it further but for now it seems you need to be coming from a rom other than H57.
Here is a screenshot;
{
"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"
}
Okay, here's what it says (and sorry, I meant assert ).
assert failed: getprop("ro.product.device") =="aries"|| getprop("ro.build.product") =="aries"||getprop("ro.product.board") =="aries"||
These lines are repeated 3 more times, but instead of "aries", it is "fascinate", "fascinatemtd", and then "SCH-I500".
By the way, this is all on the recovery screen, it doesn't reboot at all.
EDIT: Just read your edit, haha. Alright, so I just flash some other ROM like PnP first and I'm all good? Cool, I'll try it and let you know
btoast777 said:
Okay, here's what it says (and sorry, I meant assert ).
assert failed: getprop("ro.product.device") =="aries"|| getprop("ro.build.product") =="aries"||getprop("ro.product.board") =="aries"||
These lines are repeated 3 more times, but instead of "aries", it is "fascinate", "fascinatemtd", and then "SCH-I500".
By the way, this is all on the recovery screen, it doesn't reboot at all.
EDIT: Just read your edit, haha. Alright, so I just flash some other ROM like PnP first and I'm all good? Cool, I'll try it and let you know
Click to expand...
Click to collapse
I would think you could flash pnp then go from there but to be safe you might just want to flash full EE19 stock then CM7
EDIT: Okay, scratch that last. I'm re uploading with a working version (same link). It should finish in 10 minutes or so.
Yeah, just flashed PnP and then tried CM7, but I got the same error...well, looks like I'll have to wait until I get back home to my computer this weekend and ODIN back to stock and try again.
EDIT: Wow, I have to stop posting before your edits, haha. Sounds good, I'll try the updated one in a few, then!
btoast777 said:
Yeah, just flashed PnP and then tried CM7, but I got the same error...well, looks like I'll have to wait until I get back home to my computer this weekend and ODIN back to stock and try again.
EDIT: Wow, I have to stop posting before your edits, haha. Sounds good, I'll try the updated one in a few, then!
Click to expand...
Click to collapse
No worries , please let me know how it goes! (it's all uploaded and available now)
bdemartino said:
No worries , please let me know how it goes! (it's all uploaded and available now)
Click to expand...
Click to collapse
So I clicked the download link and I get a notice saying the "content is not supported for the phone", the file is called Unknown and it won't download. Do I need to download from a PC now?
btoast777 said:
So I clicked the download link and I get a notice saying the "content is not supported for the phone", the file is called Unknown and it won't download. Do I need to download from a PC now?
Click to expand...
Click to collapse
I just deleted the old one and reuploaded with the same name, so it should be fine.
try going to http://olvisfoundation.com/xdadump/bdemartino/
Then click on the CM7.zip there
So, turns out I had to re-download the Dolphin browser in order to download it. Good news, CM7 installed successfully on my phone! However, later when I rebooted in order to add the GAPPS, I lost service; my phone couldn't even identify what network it was on and all that. So, I had to borrow a friend's computer and I ODIN-ed back to stock EE19. I'll try it again and see if I can get data working, but if you know anything about that, let me know! I'm getting closer...
EDIT: Alright, so I tried to flash again after getting back to stock, and this time when I rebooted to install the GAPPS, I got stuck in a boot loop with the CyanogenMod animation. So, I've restored my backup and am back on Heinz 57 for now. So I don't know if I'm just not supposed to flash the google apps or if this version only wants to run one time before something happens :/. Do you have any idea?
I had lost data too, so I pulled the battery and rebooted it's been good since.
Ya I had an issue with signal at one point, I toggled airplane mode on and off and it fixed it right up haven't had issues since, but haven't had any issues with data.
You do need gapps, so I'm not sure what the issue is - make sure you download the ones from jt's post.
Yeah, I don't know what was going on...I'm going to try flashing it again, and I'll see what happens.
{
"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"
}
Alien Stock provides a base TouchWiz ROM for your Galaxy S II Skyrocket. Samsung's original ROM stays fully intact with a few extras thrown in. I painstakingly mirrored all of the settings and files in a stock install. I know some users prefer stock ROMs and this gives them that flexibility. ROM developers, feel free to use this as a base.
Code:
- Based on AT&T UCLE2 4.0.4
- Zipaligned
- Deodexed
- Rooted
- Busybox and friends
- No CIQ
Alien Stock (full wipe - follow instructions below)
MD5 660610861b37d91f7206fc308b64bd1e
0) Take a Nandroid backup of your current ROM first!
1) Update to ICS radio if you haven't yet (Use my CWM zip here)
2) Wipe data/factory reset
3) Wipe cache
4) Install from SD card
5) Format /cache under "mounts and storage"
6) Reboot. First boot will take a while, be patient (5+ minutes).
7) AT&T Ready2Go seems broken in this build.
DesignGears
Original ICS Leak
KennethPenn
UCLE2 ICS Leak
It's not working when I install! I'm receiving force closes, sitting at bootloops, etc.
Make sure you're installing the ROM correctly. Remember that kernels, MODs, radios, and carriers can mess with your phone's performance and workability.
I'm not on AT&T and this ROM is completely broken!
This ROM is not necessarily designed for international compatibility. Please wait for future updates or attempt an install with a proper international kernel.
Why is my device running/booting slowly?
Your first boot will take an unimaginably long time. After that, your device will continue to run slowly until the application cache is built up. Don't worry, the speed will increase as you use the ROM!
Why is my battery life bad?
Your battery life is often killed when flashing ROMs in CWM. For the best battery life, you must drain your device’s battery until it turns off. Plug the device into the AC adapter and let it charge until the image says 100% charged. Then turn it on and use the volume buttons to boot into CWM. Click Wipe Battery Stats under the advanced menu. Then you should charge to 100% and install the ROM. Battery life should be comparable to (if not better than) every other ROM.
What is this?
With the various trouble people seemed to be having with CWM-flashable ICS zips, I took a few minutes to put this together. This is ICS in CWM form, with a few extras. It has none of the problems with other CWM zips (lag, etc). I've kept it stock for those that prefer stock ROMs. This will be the base ROM for Alien ICS. I'll also do my best to keep this updated for future ICS leaks/releases.
Coming soon (its stock, what do you expect?)
Changelog:
Alien Stock UCLE2
Updated to UCLE2 leak.
Alien Stock UCLD2 re-release
Fixed busybox. No one told me it was broken.
Properly format /system, /data and /cache using Samsung provided tools.
Alien Stock UCLD2
Updated to the UCLD2 leak.
Few minor bugs fixed. I don't think they affected ROM usage, but never hurts to be thorough.
Alien Stock UCALC4
Initial ICS leak.
Known issues:
The home button has a slight delay. This is common in ICS (check SGS2 for example).
[*]Messages crashes if you delete a thread from the list view. This is a problem with the leak. Maybe I'll fix it if I get time.
Anything else that has been common with ICS from Odin (I really haven't noticed hardly anything to be honest).
If installed properly, this will not have the lag, data connection issues, etc of other CWM stock releases.
Some people have noticed weirdness when coming from GB related to the Home/Search keys. This appears to be related to updating from GB only (perhaps files on the SD card). Flashing the ROM a few times and booting into it between each flash seems to clear this up. Alternately, try backing up your internal SD card to your PC and then formatting it.
Miscellaneous:
If you want to enable "Preferred install location" in Settings -> Applications, run the following through an ADB shell and reboot:
Code:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update system set value="1" where name="set_install_location";'
I love you.
nice!!!!!!
Nice, been waiting for this one. Screen shots are coming I assume? Can this be used on 727R's (Rogers)?
veebomb said:
Nice, been waiting for this one. Screen shots are coming I assume? Can this be used on 727R's (Rogers)?
Click to expand...
Click to collapse
Granted, I was still fleshing out the post, so maybe it wasn't there yet. But please check Help in the first post.
Short answer, I don't know. I'm an AT&T subscriber But if the ICS leak worked on Rogers, then this should too. The beauty of this release is really in the updater-script
I got an aborted install...Im gonna try to download again and flash.
mossination said:
I got an aborted install...Im gonna try to download again and flash.
Click to expand...
Click to collapse
MD5 should be 3764ce5059fd5174e4840960b0fa43cd
Downloading now
Munching on Ice Cream with XDA Premium
Installed fine. Need me to take screens, just ask. Thanks so much for this.
The Vol Down + Power has yet to work for me (for screenshots)... Nvm, you have to hold the buttons down.
ROM is good though. May I suggest adding the dictionary fix for the next go-'round?
MokujinX5 said:
The Vol Down + Power has yet to work for me (for screenshots)... Nvm, you have to hold the buttons down.
ROM is good though. May I suggest adding the dictionary fix for the next go-'round?
Click to expand...
Click to collapse
I'd say save that for Alien ICS, we need a good base around here. i Remember the first Alien back in November..first ROM i used.
EDIT: Donated...thanks romracer.
In case you need them.
So far so good. Smoother than the others so far. Had the home button bug. Reflashed and all is good. Thanks for all the work
mossination said:
In case you need them.
Click to expand...
Click to collapse
Thanks, I'll put them up in the morning. One of my dogs ripped the skin off her lower jaw ("degloved the lower mandible") shortly after I posted this. Been a long night; surgery in the morning. Thanks for taking those SS.
First, I hope your dog is OK, I am a dog lover as well.
Ok, this might be a bit lengthy, but I've just spent 10 + hours trying different things and I want to let you know what all happened in hopes that the info can be used to help make Alien ICS one of the greatest ICS ROMS ever. Alot of this is already known, but I'll cover it anyway. And, of course, this is the experience I had with my phone...others may differ.
Background. I ODIN'd the ICS leak already, but found it buggy, bad connectivity, and a battery hog, so I went back to ALien 6 (GB).
I saw this posted and decided to give it another go. I followed the directions and didn't have any trouble with the actual install precedures themselves. However:
The first time I flashed the ROM, I found that I had the problem with the "Home an search" keys not working as well as the "shutdown and reboot" hanging. I tried to do a factory reset in the settings, but it wouldn't work. So I did another clean install of the ROM using the superwipe script this time as well.
The 2nd install fixed the "Home and Search" buttons, but I still had the "shutdown and reboot" hang. I fixed permissions, re-downloaded busybox and installed your insecure kernel and the 14 toggle mod. Nothing fixed it. SO, I did a 3rd clean install.
The 3rd time seemed to do the trick. Home and search buttons work,shutdown and reboot works, the 14 toggle mod works, etc. and, this time around everything seems alot more responsive and snappy.
Here is what I noticed:
All three install attempts (and the ODIN leak install) acted different in some ways that were suttle and others obvious. It appears to be hit or miss on any install and any method that is based on the ICS leak. I'm not sure why this is. But I am certain that reguardless of install method, it might take the way it is supposed to the first time, it might take 3 flashes or it might take 10 or more tries. It's just the luck of the draw. The fixes that people have reported as working are only temporary. That's why they work for some and not for others. It might make a certain aspect work (ie. installing a program makes shutdown work) but your ROM will still not be installed correctly. The only way to get it to work right is to keep trying until it installs with everything working, otherwise there will still be problems.
It will take of couple of days for me to test the connectivity and battery life.
So, people, as for now, if it isn't working for you the only real fix on this ROM or any based on the ICS leak is to keep reflashing until it finally works all the way.
I can't wait for you (romracer) to start baking the mods into this and if I can help let me know. I'll post back here when I get more results from this last flash. Thanks.
Is it safe to apply this over Alien #6 (GB)? Just follow the instructions in the OP?
gravyplaya said:
Is it safe to apply this over Alien #6 (GB)? Just follow the instructions in the OP?
Click to expand...
Click to collapse
That's exactly what I did. Make sure you make a nandroid of 6 before you do it...just in case you want to go back. And follow the directions completely. Make sure you flash the modem first. And understand that even if you follow the directions exactly you might still need to flash this more than one time to get everything working. Just make sure you check for any of the known glitches right after you flash and before you start personalizing it. That way if something isn't working correctly and you need to reflash a time or two or more, you will not have wasted any extra time in the process. When you finally get it the way you want it and feel it is installed correctly (glitch free) do another nandroid so you'll have a point to jump to if you want to try something else and then go back again. Good luck.
Hi Romracer
can you please enable internet call settings under Settings>Call.....
AOSP 5.0.2 Barebones for D2303
Hi all.
This is my first run of compiling a barebones AOSP 5.0.2 for our D2303's. I got sick of all the failed ports and wanted to make my own from scratch. Here you have my first launch. You can not get as barebones as this. This ROM was made using the guides on Sony Developer website and should be the same result if anybody else follows the same steps.
I have made ZERO modifications to this ROM. I have changed no code, made no patches or even themed it with a custom name. This ROM is as-is if you built it following the same guides on Sony's site. I just saved you the time.
**This ROM works!**
Data / Calls / SMS / NFC / Bluetooth / GPS/GloNAS / Wifi all work!
Camera does not. It might, but I broke mine and doesn't even work after stock restore!
No lag!
Clean, basic, no-frills, xPosed ready!
Unlock your bootloader!
Be running either a modem from a 4.4.2 ROM or a 4.3 ROM!
This ROM is provided as-is. The sources are freely availble following Sony's guides. You use it purely at you own risk!
Let's clear some confusion with this device, which I am shocked top developers have missed!
* You **have* to be running either 4.3 or 4.4.2 MODEM! If you are running a 4.4.4 ROM, use Flashtool to drop back to 4.4.2 or 4.3 first
* You will not be able to boot ANY 5.x ROM with a 4.4.4 modem, it **HAS** to be 4.4.2 or 4.3 MODEM!
There are guides on how to revert back on this forum and I will not detail that here. But in essence, it is only the modem you need to revert back.
This ROM I would say is usable.
* Camera doesn't work on mine, but I broke it to the point it wont work in stock ROM
* Calls / SMS / Data / Wifi / GPS / NFC / Bluetooth all appear to work as they should
* Sensors appear to all be working as they should (at least compass and light)
* No lag or FCs
This is a totally unmodified ROM using the AOSP & Sony sources provided in Sony guides. I did not develop or make any of the code or scripts. I simply compiled it, flashed it and now using it. All credit to the software that made this ROM goes to all those involved in making, patching and taking the time to make this work.
I do not want any donations. If you wish to donate, donate to FXP/CM12/Omni/PAC/TWRP and the persons that created what I have simply bundled here.
Download via magnet/bittorrent only for now. For trackers, please use OBT trackers. Issue with previous download! I somehow crossed an .img from another project as the boot.img for this. I have recitified this issue and the correct boot.img has been added. Apologies for this & thankyou to all whom spotted it.
Magnet Link
magnet:?xt=urn:btih:44d710f71b92adb9e64475994b5ab905d665af7d&dn=AOSP-5.0.2-D2303.tgz&tr=udp%3A%2F%2Fopen.demonii.com%3A1337
Mega Link
https://mega.co.nz/#!HZUUCCJS!AgjmKr4Nx4NMWPKxVXIGfp72m9JyMMlsF0pvzuGBrg8
Sorry for the bad link effort, since I am new to contributions I'm stuck until I make the relevant posts.
I have no idea if this will work on any of the variants of this device. You are welcome to try, but don't blame me if you break it. This ROM comes as is, is provided under the same licenses as AOSP and Sony Development.
Tricks & Tips:
* Download the .zip for Omni ROM 4.4.4 for our D2303's. Extract the boot.img and keep it safe. This boot.img holds a reliable TWRP which we can use to ''fastboot boot'' instead of flash and even make a reliable backup of a stock ROM. When you put device into fastboot/bootloader (hold power up when plug in data ready cable), execute ''fastboot boot boot.img'' which will boot that kernel w/o modifiying anything. Now keep hitting volume down when you see Sony logo. TWRP should load!
* Use this for all your backing up, flashing zips, ROMs etc. Do NOT flash it. Just fastboot boot it instead. This can even be used AFTER we install Lollipop for the same reasons.
* Flashing this ROM requires you to use the above TWRP to wipe all partitions, System, Data, Cache etc. It's best to start afresh (I actually wiped everything except since I wanted a totally clean slate, wiping external storage isn't necessary but wiping internal is recommended.)
* Extract the tarball with the .img files
* Put the device into fastboot mode again!
* execute the following commands:
* fastboot flash boot boot.img
* fastboot flash system system.img
* fastboot flash userdata userdata.img
Make sure all processes complete successfully!
Unplug cable, wait a second or two and power up your device! (I prefer this to fastboot reboot as the data cable can hang the device in a weird, red led stays on mode that has bootlooped me a few times).
Give it a while to boot. Whalla, Lollipop!
If you want gapps, using the fastboot boot method above with our Omni 4.4.4 boot.img and TWRP.. Download CM's gapps for Lollipop and flash/install it. This does not lag the device. However, you will get a black screen for a while after first boot of installing any system/ZIP flashable (it wont show updating apps, just blank screen). BE PATIENT! The same applies if you do anything that triggers that "Updating App X of X.." Android is updating effort.
xPosed requires you to follow the instructions for flashing the ZIP then installing APK. Use the same method above for installing the ZIP.
To get root, just download the latest SuperSU-2.x.zip and flash the same way as above.
**Issues**
* With a 4.3 Modem, the Bluetooth is slow coming to life. Take about 5 mins when turned on from off. 4.4.2 modem doesn't seem to have this issue
* Location services will forget a change to Accurate on a 4.3 Modem. On 4.4.2 Modem doesn't seem to do this.
* My loudspeaker during calls is tempremental, sometimes it works sometimes it doesn't.
* Some OTG devices work, some dont. I had one or two pendrives that did, some that didn't & a 3G modem (with PPP widget's help) that did & another that didn't!
* Screencasting initially didn't work. Enabling Developer Mode and disable HDCP checks seemed to allow some functionality for me.
* Data icon always said 3G for me, even when on HSPA(+) - I use OSM which showed varying network types. GPRS/EDGE shows as 2G. I do not know for 4G as my carrier isn't 4G enabled yet.
* No hardware accelleration (using VLC & MX Player as guides) for video playback, however it can playback a 1080 MKV over wifi no problem.
* Same applies to screen-recording software. I can't seem to get native Lollipop one to work at all, but SCR Free works.
* 3D Performance is a little smoother than in stock ROM (IMPO playing Ingress).
* GravityBox for Lollipop works. However!! On some instances it can cause a softboot on a boot up (when it goes for PIN entry). For me it comes back after they next cycle. Not pinned it down to what in GB doing it though.
* Compass, proximity & light sensors all work. There is some screen flicker once so often when using dynamic brightness.
* No way to force use of 5Ghz or 2.4Ghz wifi (or leave it to select auto) as there is in stock ROM.
* Battery life when using the device as I do is as the same as stock, the device is however faster in general. I can sit it for 29 hours idling, providing not too many calls. The powersaving modes built-in can extend on this but I haven't properly tested.
I only mention these as some people may care to know. If the camera worked, I would actually be totally happy with this ROM minus it's few pitfalls.
MD5's for the paranoid:
2c053445ab096e813afc2a02079aba85 boot.img
af636c1558e8d6651f211dbd2042443f system.img
adbb0b8d0b5eee98186a71a00d8352a4 userdata.img
Good job, please, compile an AOSP 4.4.4
Sent from my D2303 using XDA Free mobile app
What if I told you I did the same as you and it is EXACTLY the same build you can find on FXP's blog (but files are not straight uploaded, so build can be a little bit outdated). Developers around here are working on sources, and changes are on Xperia Developers Github.
As you can see there are things jerpelea (FXP) has pushed.
https://github.com/sonyxperiadev/device-sony-eagle
Only untouched sources are for Nexus, all other devices need to be patched, and sometimes rewritten from scratch (for example camera wrapper).
If I install this rom, and when I back to stock rom, i won't be able to use camera?
Is that right?
Um ok but why there is no seeding?;/ and why dont u give an alternative link?? haw we supposed to try this rom mate?
who can confirm if camera works or not ?
Update
I will work on a 4.4.4 AOSP eventually. Thanks for the tip, I'd also be curious on this.
I do not doubt that developers that are working on Omni/PAC/CM/FXP have submitted code, that's probably why the barebones is working sweet. I did try FXP but ran into different issues on different versions (all already documented). I built this on a whim as I just got fed up.
With the camera, that is exactly how I killed mine, and I also lost the original backup I made with Flashtool/Companion as well as from TWRP. So I have no hope. If you keep/make a backup upon successful bootloader unlock (companion/flashtool), you should be OK if you do a stock revert that is documented on this forum.
For the download link, sorry about this. I used transmission and it went into meltdown last night from another seed. I believe mega is a method people use here, is there any other suggestions. I will do this when I get back home and check back here.
** I am uploading this to Mega now, I will add the download link to the OP. **
Thank you for uploading this rom Dutch.
I ll test this rom, correct it where i can and send you pm as soon as possible with some fixes plus solution about your camera
cross your fingers to not break mine lol
Best regards
Vampirian
Thanks
If you do make some patches, can you please put them as flashable ZIPs? I really don't want to go and start tampering with a somewhat stable base. I bless whoever made that boot.img for the Omni 4.4.4 - I would like to try and get that working here, but again tampering.. Just means needing a PC or tablet to make mods to your phone each time.
I may have a bash at a custom kernel with a recovery for this, but I'm not rushing into that idea just yet.
** Update **
I got curious about the FOTA partition I saw using Flashtool and see there are already ports of custom recoveries (with custom boot kernels with elf extract support). I am overly curious about this now as I would love to have this TWRP from Omni's boot.img for my internal recovery. I have already made a custom kernel for my device and it seems to not effect anything (not changed a thing mind). I may now start to tinker!!
Has anybody tested this rom?
---------- Post added at 03:37 PM ---------- Previous post was at 02:53 PM ----------
I have the problem with boot.img
It says, failed: this is not a boot image
Bug list same as the omni one
Can You explain that boot.img is over 400MB Large!!!
{
"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"
}
Which download did you use? That is so not right!! boot. img should only be about 6/7 mb. are the md5s matching on system and userdata? i will look into this asap
Sent from my Xperia M2 (AOSP) using XDA Free mobile app
The mega download is shot. It has become corrupted and I will remove the link from the OP. DO NOT USE IT!
The magnet link is still fine and extracts properly.. Just be patient as there are only 3 peers at present.
I am still using this ROM and there are some issues.
I failed to get Wifi tethering to actually route. It would run, give dhcp and even resolve DNS, but it is as-if the the nat forwarding rule has been missed and everything blackholes.
Camera is a total no go for me, I fooked mine in other ways though.
For how I use my phone (calls/sms/Ingress/HO/G+/Whatsapp/Maps/Wifi location mapping (OSM/Mozilla stumbler/Wigle) / Skymaps) it does just fine. Battery life isnt impressive vs. stock overall (doing same as above). xPosed allows tweaking, but this is where instability occurs.
GB works quite well, but avoid things that dont have direct L support (xPrivacy/Lightningwall etc.).
What I want to do is submit my phone into submission and try to get my camera working in a stock again, then give this another bash. It is a usable ROM if you just want a clean fast phone with no thrills (or camera).
Sent from my Xperia M2 (AOSP) using XDA Free mobile app
Magnet link not working
The magnet link you posted doesn't seem to work for me. I get "unable to parse magnet URI!" error
There is a space in the magnet part of the URI when you C&P. The forum did this. I should be able to post proper links soon.
Sent from my Xperia M2 (AOSP) using XDA Free mobile app
Nice for giving so much info on AOSP experiences and "prerequisites" (like 4.4.2).
I'm using a AOSP 5.1 build I made myself, and have to say the only issue with the latest build/kernel is battery drain (and camera, but "they" are working on it).
I Hope nobody will call you a troll because you share your builds and experiences with everybody
I got a massive lag when using browser or while using a few apps at once, also installing apps and turning on bluetooth take alot more time.
The things I do like is that it is pretty stable....
Thanks to all that have and are testing.
The tether issue was my tablets fault and does actually work. As does BT tethering.
All of the sensors work (i went out of my way to try each one (magnet sensors are always fun)).
The slow Bluetooth I found only happens when using a 4.3 modem. I dont get it now using a 4.4.2 modem.
There is no call record ability in this ROM. CM11/12 have enabled this feature, I believe its a small. xml patch, can anyone confirm please?
I do experience slowness with lots of open apps, i also notice if you have a lot in frequents its a pain to clear all (fixed with gravitybox mind). They also seem to come back even after a reboot. I do find myself regularly clearing the frequents which does sort it.
And thanks for the tips. I find trolls arent entirely too common here. Ive been reading from XDA for years and my sole idea was to demonstrate that its is doable and quite easy. I am still using this ROM everyday and Im quite happy with it. I do still prefer Kitkat though
I do want to play with 5.1.x (and nicer the camera works) - but i went 5.0.2 simply because of xposed support. Nothing else
There is a battery drain which I noticed "out-of-the-box" so to speak. This happens when there are issues with "qdoverlay" which i noticed sometimes occurs on bootup, then will savage your cpu. I spotted this in logcat and didnt find a direct fix (other than sleep the screen when the phone starts lagging, wait a second or two then wake it back up. Location type also counts, oddly high precision seems to give me more life. However, there is an "Over-Counted" cropping up in battery stats, which I cant pin is for what, as its usually a high figure at the bottom.
Can anyone confirm a working camera on this ROM? Opencamera or Googles should work if one doesnt show up.
Thanks again everyone
Sent from my Xperia M2 (AOSP) using XDA Free mobile app
Dutch Burdock said:
Thanks to all that have and are testing.
The tether issue was my tablets fault and does actually work. As does BT tethering.
All of the sensors work (i went out of my way to try each one (magnet sensors are always fun)).
The slow Bluetooth I found only happens when using a 4.3 modem. I dont get it now using a 4.4.2 modem.
There is no call record ability in this ROM. CM11/12 have enabled this feature, I believe its a small. xml patch, can anyone confirm please?
I do experience slowness with lots of open apps, i also notice if you have a lot in frequents its a pain to clear all (fixed with gravitybox mind). They also seem to come back even after a reboot. I do find myself regularly clearing the frequents which does sort it.
And thanks for the tips. I find trolls arent entirely too common here. Ive been reading from XDA for years and my sole idea was to demonstrate that its is doable and quite easy. I am still using this ROM everyday and Im quite happy with it. I do still prefer Kitkat though
I do want to play with 5.1.x (and nicer the camera works) - but i went 5.0.2 simply because of xposed support. Nothing else
There is a battery drain which I noticed "out-of-the-box" so to speak. This happens when there are issues with "qdoverlay" which i noticed sometimes occurs on bootup, then will savage your cpu. I spotted this in logcat and didnt find a direct fix (other than sleep the screen when the phone starts lagging, wait a second or two then wake it back up. Location type also counts, oddly high precision seems to give me more life. However, there is an "Over-Counted" cropping up in battery stats, which I cant pin is for what, as its usually a high figure at the bottom.
Can anyone confirm a working camera on this ROM? Opencamera or Googles should work if one doesnt show up.
Thanks again everyone
Sent from my Xperia M2 (AOSP) using XDA Free mobile app
Click to expand...
Click to collapse
Camera is not working
Dang. Thank you.
Sent from my Xperia M2 (AOSP) using XDA Free mobile app
Unfortunately the hoster where my build server is located raised the fees and i had no way to download a backup of my data... As i can't afford it now i had to delete everything. With a heavy heart I have to discontinue this great ROM for a great phone..
- first of all, thanks to @tdm for his tremendous effort to have us all enjoy LineageOS in the first place, without his contribution this thread would never exist. Also thanks for tdm's Lineage 14.1 where I took this post's layout from -
{
"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"
}
Gentlemen,
The time has come to share what's due to be shared.
Supported devices
* US model running 7.1.1 b14 firmware
* EU model running 7.1.1 b12 firmware
Pre-requisites
Make sure to have at least this TWRP version installed
Patience as first start takes a while
First time install Instructions
Use these instructions when coming from any other ROM (stock, AOKP, LineageOS 15.1, etc.)
Download ROM.
Download GAPPS if desired.
Boot into recovery.
Backup your current data.
Format/Wipe 'Dalvik/ART Cache', 'System', 'Data' and 'Cache'
Flash ROM.
Flash GAPPS if desired.
Reboot.
Upgrade instructions
Use these instructions when upgrading from a previous Lineage 16.0 build.
Download ROM.
Boot into recovery.
Backup your current data.
Flash ROM.
Reboot.
Flashing instructions
There are two main ways to flash files onto your phone: local and sideload. Most people are only familiar with local, but sideload is much quicker and easier if you are at a PC.
Sideload
Download the ZIP file(s) to your PC. In TWRP, select advanced and then sideload. Swipe the slider to begin, then on your PC run "adb sideload <filename>".
Local
Download and/or copy the ZIP file(s) to your phone. Note whether they are on internal storage (the default) or the sdcard. In TWRP, select install, find your file, and select it.
Status
This is currently stable quality
Known issues
Very minor graphical glitches
sometimes videos don't play, you have to remove the relevant all from your recent app list and restart (e.g. WhatsApp)
AKM DAC is not supported
Selinux permissive
To Do list
Implement Camera2 API Thanks for customizing libraries and not sharing any code or insight ZTE
Get DSP to kick in for high quality audio again
Download
Google Drive
* works well with open gapps
Sources
Device tree
Kernel
Vendor
Note: please refrain from requesting other Android distributions from me, like AOKP, AOSP, etc - this is most likely not going to happen from my end. As I provided all my sources you can fork the stuff yourself and try to build
Special thanks
@R3bornD4rth for having provided me an axon 7 mini for my testing/debugging, which is heavily in use and doing great so far
@tdm for his original work on this
@armandop_ for his ZMAX Pro Repo and help getting LiveDisplay to work (flawlessly, thanks mate)
intervigilium aka Ethan Chen for his work on HTC One A9 (hiae) (which shares the same chipset as our phones)
Thanks for this rom, there's a way to make work the camera API 2 (in the future)?
jose_777.mx said:
Thanks for this rom, there's a way to make work the camera API 2 (in the future)?
Click to expand...
Click to collapse
Good question, no clue if I will be making it to work somehow I can try to get some pointers if there are just some drivers to be altered or whatever is needed to have this done
I installed magisc 19.1, and dolby for better sound.Now it is my dayly driver,
Thanks Man!
bius88 said:
I installed magisc 19.1, and dolby for better sound.Now it is my dayly driver,
Thanks Man!
Click to expand...
Click to collapse
Cool!
Would be better if GPS and Cam would work though I am working on GPS right now, will soon test my latest build, so fingers crossed
Working well with open gapps 9 micro.
Play store works
Pixel launcher fc.
Camera works. The app doesn't. Download any other camera and you're good.
Looking great so far
Thanks
Holyoblation said:
Working well with open gapps 9 micro.
Play store works
Pixel launcher fc.
Camera works. The app doesn't. Download any other camera and you're good.
Looking great so far
Thanks
Click to expand...
Click to collapse
What? The camera really works? Then I shall replace the camera app with another one maybe ?
Works great with opengapps pico too i am using this for a day and there is not a big issue i will share if any unexpected issue happens. Thx for your effort
EDIT: I think there is still a problem with camera. i tried it with 2 applications and one game.
I have problem with instagram videos i cant play them.
Cant open flashlight from quick settings.
koktey14 said:
Works great with opengapps pico too i am using this for a day and there is not a big issue i will share if any unexpected issue happens. Thx for your effort
EDIT: I think there is still a problem with camera. i tried it with 2 applications and one game.
I have problem with instagram videos i cant play them.
Cant open flashlight from quick settings.
Click to expand...
Click to collapse
I see 2 issues here to be fixed. first with the video playing will be added to my known bugs post, the flashlight thing is related to the camera not working (pretty sure at least)
Small update: unfortunately I can't find a reason why GPS is not working on LOS16, but worked in LOS15.1, even just taking the files from 15.1 and placing them in 16 didn't help. The error messages in the log are not disclosing enough information what exactly the issue could be, just getting loads of invalid handle errors. Comparing with other msm8952 chipsets I don't really see any differences, so I am clueless now
TheSSJ said:
Small update: unfortunately I can't find a reason why GPS is not working on LOS16, but worked in LOS15.1, even just taking the files from 15.1 and placing them in 16 didn't help. The error messages in the log are not disclosing enough information what exactly the issue could be, just getting loads of invalid handle errors. Comparing with other msm8952 chipsets I don't really see any differences, so I am clueless now
Click to expand...
Click to collapse
Can there be a chain problem with sim card, graphics or camera maybe
koktey14 said:
Can there be a chain problem with sim card, graphics or camera maybe
Click to expand...
Click to collapse
Well, this really looks like it - I reverted back to the state where I took over from tdm and applied just the modifications to make nfc, wifi, bt, radio to work. Now GPS works, but wifi went back to sometimes fail to start where you have to reboot to make it actually work again.. it seems something I added along the lines fixed the issue with wifi and another one broke GPS
I am trying to fix wifi now somehow to make it behave stable again, then we can enjoy even a fixed GPS phone
Next stop is camera (after I repaired wifi)
TheSSJ said:
Well, this really looks like it - I reverted back to the state where I took over from tdm and applied just the modifications to make nfc, wifi, bt, radio to work. Now GPS works, but wifi went back to sometimes fail to start where you have to reboot to make it actually work again.. it seems something I added along the lines fixed the issue with wifi and another one broke GPS
I am trying to fix wifi now somehow to make it behave stable again, then we can enjoy even a fixed GPS phone
Next stop is camera (after I repaired wifi)
Click to expand...
Click to collapse
Apparently I fixed wifi I rebooted 15 times to be sure and it always turned on, GPS still functioning as well!
I will update the OP and proceed with cam (which is so broken that not even 3rd party apps work at the moment)
EDIT: Notification lights fixed as well
@TheSSJ -Great Work man!
Will try it out as soon as I get a chance
edit - is the TWRP version the same as Oreo or a newer one ?
edit 2 - Are you building an Aokp version ?
Hi, thanks for the hard work. Does the firmware support fast charging?
BAPK said:
Hi, thanks for the hard work. Does the firmware support fast charging?
Click to expand...
Click to collapse
Yes, as this is setup on kernel side the stock settings have been just kept
k500zm;79544339 [user=2388665 said:
@TheSSJ[/user] -Great Work man!
Will try it out as soon as I get a chance
edit - is the TWRP version the same as Oreo or a newer one ?
edit 2 - Are you building an Aokp version ?
Click to expand...
Click to collapse
Twrp is the same with oreo i installed it.
I was thinking about aokp too but didnt want to put pressure on you. you are already busy. @TheSSJ what do you think about this?
Once I fixed all issues with LOS16, compiling aokp should not be too hard, but I can't promise it
Now i installed the new build but i have a problem. First i made an update but i wasnt able to open get through lock screen after that i made a clean install but now it is too laggy always freezing. Its too difficult to use this build.
koktey14 said:
Now i installed the new build but i have a problem. First i made an update but i wasnt able to open get through lock screen after that i made a clean install but now it is too laggy always freezing. Its too difficult to use this build.
Click to expand...
Click to collapse
Strange,i just clean installed and it is working really fast
Can you provide dmesg and logcat please, then I can check