ROM:
http://www.mediafire.com/download/wkzcatpp7az4r5f/LS-KK-v3.2-2014-10-17-ovation.zip
MD5:
http://www.mediafire.com/download/piwirf8ee421dqv/LS-KK-v3.2-2014-10-17-ovation.zip.md5sum
A shoutout and thanks goes out to Rhyang for his help with the Slimkat rom, (to which this is somewhat similar).
Compiled with Sabermod toolchains. 4.8 for the rom and 4.7.4 for the kernel.
O3 optimized.
I made an attempt to fix 'OK Google'. Dunno if it's working or not (haven't tested). If it's still broken then it will be in the board files and will be a bear to try and find....
Dunno, it seems to work fairly well (ALMOST as good as Cyanogenmod 10.1 ) I kinda like it in a way (except it's KitKat).
I'll try and upload some source later. My internet connection has been giving me problems lately (took four hours or so to upload this). Even with source this is somewhat difficult to compile anyways (I fought with it some).
Cheers!
Great. I'll download now and try it out today :good::good:
Oh man I love LiquidSmooth! I am using it on my phone and have never looked back.
I guess I will have to give this a try. Thanks a lot for this. Is it also running on your yellow kernel or something different?
Which Gapps file is used with the rom please?
Yes it's using the same kernel as Slimkat except that /sound and /drivers/mfd folders have been swapped out with their CM11 kernel counterparts.
If you go into settings and 'about tablet', you will find download links to two types of gapps, full and minimal.
Things are running well. OK Google doors not appear to work too well
Jon Lee said:
Yes it's using the same kernel as Slimkat except that /sound and /drivers/mfd folders have been swapped out with their CM11 kernel counterparts.
If you go into settings and 'about tablet', you will find download links to two types of gapps, full and minimal.
Click to expand...
Click to collapse
Hey Jon, thanks for yet another new rom. :good: Looking pretty cool so far but as already mentioned, "Ok Google" is not working properly. I swapped out your yellow kernel with the stock CM11 kernel and Google Now is working as it should.
Since I lack the capability to compile a kernel, I simply replaced the yellow kernel boot image and the entire modules folder in /system/lib with the CM11 boot image and modules folder. I hated to lose the yellow kernel as I feel that it has better performance than stock CM11 but I love using OK Google. Btw, I did the same with your Slim rom with similar positive results.
Also, I see in the build prop that the density is set to 320DPI instead of the standard 240. I happen to prefer 320 but I would think that the masses might want the standard density and would be wondering why their desktop looks so big.
Anyway, thanks again for your contributions. It's appreciated.
Mike T
Ooh, nice!
Wow, is this fast!
So many ROMs, so little time.
I've been using CM 11 nightlies for a couple months now and didn't have many complaints. The usual CM 11 screen flicker problem when charging, some screen black outs (and crashes) on a certain screen in one of my aviation apps. That was about it. CM 11 was fairly fast and incrementally getting better all the time.
CM 11 doesn't have zRAM built in (yet), so I got a lot of app restarts when switching between my high memory aviation moving maps and other apps. But we're trying an experimental zRAM build that's helping with the HD+'s limited RAM.
But then I got a wild hair and decided to look around in the HD forum to see if perhaps Jon had an OC kernel for CM 11. Then I found his build of Liquidsmooth for the HD+. I didn't want to spend a half day wiping and installing a completely different ROM. But I'm glad I did. Wow.
I don't know if it's the overclocking or the other tweaks or all the above, but my AnTuTu score jumped from 17300 to 19100! Thanks, Jon!
(Hotplug governor seems to work best for me in both LS and CM 11. Too early to tell, but battery life doesn't seem any worse in LS.)
I assume that LS does not force the CPU to 100% when running AnTuTu, as CM 11 does. So the 19100 is probably a realistic reflection of performance.
(I haven't experimented with the I/O scheduler yet. I left it set at fiops for now. (Supposedly best for flash memory. Heretofore I've always used Deadline.) I lowered the SD cache to 512, which I found worked best in CM 11. (Using SD Booster to make that change.) FWIW, I enabled the GPU Acceleration and Super Tweaks in LS. )
[FWIW, the word "compiler" is misspelled (twice) in the "Just in Time Complier [sic]" setting.]
I'm happy to report that the screen flickering/crashes are gone when on that special page in my aviation moving map that always flickered - and sometimes crashed - in CM 11. (Requiring that I disabled HW overlays in Developer Options in CM11.) And since I set the "Low Memory Killer" to "Light" in LS, it doesn't kill my apps as aggressively as CM 11 did. (Not apples and oranges, because I was running ART in CM 11, whereas LS implies you shouldn't even try ART.) LS should be even better with zRAM. (And the boot animation is better than the frowning, scary CM alien face. )
(Speaking of zRAM, I noticed that someone in the Slimkat forum is running zRAM on Slimkat. I read here that Slim and LS are kinda the same. Is there a way to turn zRAM on it LS?)
I'd be curious to know what the major differences are between LiquidSmooth and Slimkat. Since Jon says LS is "similar" to Slimkat, why does LS exist?
Not much I could find on the web about it. I looked at the Slim home page. It's main advantage seems to be fancy interface stuff. (Although LS has PIE too.) Kinda like a toned down version of PAC? But the LS home page is silent about what makes it better/different.
Like I need to spend another half day wiping and flashing can customizing another ROM. (Titanium Backup is supposed to save data/settings. If it does, it doesn't seem to work for me. I have to reset the Settings on my apps when I restore from Titanium.)
---------- Post added at 10:34 AM ---------- Previous post was at 10:21 AM ----------
Every trying for that last bit of performance, some questions:
Q: On zip align apps on boot. Should I expect a toast or a notification if an app needed to be zip aligned?
Q: In CM 11, there's a Developer's Option to kill an app with a long press of the Back button. (Seems to be different from swiping "closed" in Recents, in that it completely shuts down the app.) Is there a similar trick in LS?
Q: I updated the host file for disable ads. I got a message that it worked, 0/4. Zero out of Four? That doesn't sound right. Is it?
Q: In CM's Launcher settings, you can disable transitions, stop scrolling wallpaper, etc. But I can't find a way to disable transitions - especially in the App drawer - in LS. (I see ways to change the transitions, but none of the options have "None.") Where are they or what's the trick to kill them?
Q: Last, and this is more of a Slimkat design element, but shouldn't there be a "Close All" button in the Slim Recent panel?
PMikeP said:
Q: Last, and this is more of a Slimkat design element, but shouldn't there be a "Close All" button in the Slim Recent panel?
Click to expand...
Click to collapse
For a while SlimROMs said they wouldn't support this, but now you can close all apps in the recents panel with a two-finger pinch. I think they might even have a youtube video of this ...
I like Slim because it's minimalist -- no bloated theme engine and its associated bugs. That said, their drivers tend to be a little more out of date than CM. The framework source is also slightly different. This makes sharing code between the two a PIA sometimes. I have no familiarity with LS, so I'm not sure how applicable these comments are to it.
Looks like you've been busy Jon
rhyang said:
For a while SlimROMs said they wouldn't support this, but now you can close all apps in the recents panel with a two-finger pinch. I think they might even have a youtube video of this ...
Click to expand...
Click to collapse
Thanks. I found the pinch gesture serendipitously while trying to swipe away a running app in Recents. Still, it's problematic trying to get it to 'close all' all the time. I went back to stock Recents for now. (Favorites implementation in LS Recents might be nice, as they've implemented in Slim, but I haven't figured out how to invoke it in LS if it's there.)
Here's the device and vendor source as promised:
http://www.mediafire.com/download/z3llb4mauxo8m16/liquidsmooth.tar.gz
Let me know if you need help or any other source to build.
I kept this one very much "original"/plain, meaning I didn't add the zram script (or anything else extra).
To add zram to it, just extract the attached 60ZRM script to /system/etc/init.d
(make sure it is executable & root:shell owned), and reboot.
I believe as far as 'ok google' is concerned, the next step would be to compile with the normal vanilla Cyanogenmod defconfig (sorry, but I refuse to install Gapps just to test). Microphone works, mixer values are the same, so... There's a reason I disabled some of that IPv6 stuff...
Behind the scenes I've been (rather unsuccessfully) attempting a port of ION CMA Heap.
http://pastebin.com/J1Ptxz3W
(Which is why I shared the first build without adding any extras, because I knew I was going to break it immediately following).
BTW, I'm still very new at compiling android and it will take me some time to become better acquainted with the build process.
A hack to fix auditd error "protocol not supported"
Jon Lee said:
To add zram to it, just extract the attached 60ZRM script to /system/etc/init.d (make sure it is executable & root:shell owned), and reboot.
Click to expand...
Click to collapse
Thanks again Jon! The Permissions for your script file were correct from the start. I don't know how to make sure it was root:shell owned, but it worked nevertheless.
Now, a hack to stop auditd errors:
After I got my apps reinstalled and set late last night, I decided to run catlog, just to see what I could see.
LiquidSmooth is definitely quieter than CM 11. (In the sense of less processes starting and stopping.) To be fair, not quite apples to apples because I'm back to running Dalvik on LS and was running ART on CM 11. (ART comes alive frequently to trim memory.)
But there was one process in LS, that I didn't notice in CM 11, auditd, that just kept starting and stopping with an Error, "Protocol not supported."
Despite that fact that auditd is constantly trying to run, it doesn't stop one of the CPU cores from shutting down (with Hotplug governor), nor does it prevent the CPU from dropping to its lowest freq. So, in practice, it doesn't seem to be a problem. Still, it can't be good to have this one thread constantly starting and stopping and it bugged me.
Now, maybe I caused the problem, because I typically uninstall a lot of Google junk and I disable a lot of Google services in the junk I can't remove. (Boy, Google just keeps pinging and pinging you!) And I hadn't run catlog with a virgin build of LS to see if the auditd Error was there at first.
Having said that, I did find a few other people on Google asking about the same auditd Error. (Apparently, auditd is a process from Sun.)
On the assumption you all get the same Error too, the best way to stop this would be to find out why it's trying to start. And to stop it. (Duh.) But that's WAY beyond me. So instead, I simply renamed the auditd file in /system/bin (it's a binary) to auditd.old.
I cringe when I think about it, but it worked anyway. (Worked in the sense that I don't get the auditd Error anymore.)
(As I write this, I wonder if the "d" at the end of audit is Unix convention to signal a daemon? If so, the I suppose there's probably a start up folder or file somewhere in Linux that's trying to start it? Or do daemons start themselves?)
When streaming video on any room using yellow kernel I get occasional freezes that require powering off my nook
Can I use Yellow Kernel in CM 11?
webdroidmt said:
I swapped out your yellow kernel with the stock CM11 kernel and Google Now is working as it should.
Since I lack the capability to compile a kernel, I simply replaced the yellow kernel boot image and the entire modules folder in /system/lib with the CM11 boot image and modules folder.
Click to expand...
Click to collapse
Clever! So, then, can I do this in reverse and swap Jon' s OC kernel into a CM 11 build?
PMikeP said:
Clever! So, then, can I do this in reverse and swap Jon' s OC kernel into a CM 11 build?
Click to expand...
Click to collapse
Never tried but in theory, it should work. Best way to find out is to make a nandroid and try it.
Mike T
webdroidmt said:
Never tried but in theory, it should work. Best way to find out is to make a nandroid and try it.
Click to expand...
Click to collapse
I tried it. Unfortunately on first boot, after immediately getting the CM set up screen, I got the message "Unfortunately, the process com.android.phone has stopped." (It didn't even go thru the process of updating apps like it normally does after a clean wipe, so something seems wrong. I re-did a second Factory Resent and /system wipe. Still no joy.)
So let's make sure I'm doing what you did. I downloaded the latest CM Nightly zip. I have Jon's LS zip. I opened both archives in 7zip.
I took Jon's boot.img from the LS zip and copied over (and replaced) CM's boot.img. I did the same with the modules folder in /system/lib. Then I closed up 7zip and tried installing the new hybrid CM 11 zip file.
But, since you said that you found that "Ok Google" didn't work for you on LS with Jon's kernel, it occurs to me that maybe you made these changes in a running install? That is, I would first install a "stock" CM 11 Nightly and then, after it's running, go in and change boot.img and modules? (I think changing the boot img in the partition would be a challenge for me.)
PMikeP said:
I tried it. Unfortunately on first boot, after immediately getting the CM set up screen, I got the message "Unfortunately, the process com.android.phone has stopped." (It didn't even go thru the process of updating apps like it normally does after a clean wipe, so something seems wrong. I re-did a Factory Resent and /system wipe. Still no joy.)
So let's make sure I'm doing what you did. I downloaded the latest CM Nightly zip. I have Jon's LS zip. I opened both archives in 7zip.
I took Jon's boot.img from the LS zip and copied over (and replaced) CM's boot.img. I did the same with the modules folder in /system/lib. Then I closed up 7zip and tried installing the new hybrid CM 11 zip file.
But, since you said that you found that "Ok Google" didn't work for you on LS with Jon's kernel, it occurs to me that maybe you made these changes in a running install? That is, I would first install a "stock" CM 11 Nightly and then, after it's running, go in and change boot.img and modules? (I think changing the boot img in the partition would be a challenge for me.)
Click to expand...
Click to collapse
You did it right. I did a total clean install of the Liquid rom with the newly "implanted" CM11 kernel. I wouldn't mess around with the partitions, dangerous territory. :laugh:
There's possibly some "hook" that Yellow is looking for that is not contained in CM11.
After reading your post, I just decided to see if it would work in reverse. I also got the same process phone has stopped error. With the ease of making nandroid backups, stuff like this is always worth a try when it's something you want or need. I'm thrilled that it works the other way, as I do use "Ok Google" a lot on all my devices and this Liquid rom runs nicely on the Nook.
In addition, with the introduction of Lollipop, Google has revamped GN and it's even better to use than before.
Mike T
webdroidmt said:
You did it right. . . .
After reading your post, I just decided to see if it would work in reverse. I also got the same process phone has stopped error.
Click to expand...
Click to collapse
Good to know I'm not alone then. Oh well, it was a promising experiment.
(Last night I tried experimenting (hacking) to get zRAM to point to a swap file on /cache. Not really a LS thing, but I might write about it later.)
I tried installing this today and it ran really nice and smoothly, but it doesnt seem to have the full HD+ screen resolution. Seemed more like 720p than 1080, large fonts and icons, just a lower resolution. Am I missing a setting or is it not working at full resolution?
Related
[ROM][32A RADIO 6.35]Eclair w/ Nexus1's 3D gallery CAM & most things are working well
this ROM is for Sapphire 32A SPL 1.76.2007 and latest Radio 6.35.07.29.
pure AOSP build, google bits and gallery are added. (make sure you think you have the rights for using the apps from google, i just make some copy for you)
thx: Cursordroid, Enomother, Cyanogen, RA, jnwhiteh, ChainsDD, sober (who have full of courage for testing my first kernel ) , and more...
what's new: less crash, more stable. new gallery app which use hardware accel. a new step to full working with our new radio.
the update.zip, just push it into ur sdcard then apply it from recovery: http://www.4shared.com/file/202007372/5352e8b4/my2x.html
mirrors:
http://hotfile.com/dl/24995574/2b6c9d7/sanpei_eclair32a.zip.html , by asero, thanks
http://www.megaupload.com/?d=5TH7FNC0 , by akai21, thanks
http://hoegsberg.net/fileshare/Sanpei Eclair 2.1/ , by Eukanaba, thanks
if you are a 32A user with old radio, and you want a upgrade or try this ROM, follow Cursordroid's instruction to Update your 32A Magic to 6.35.07.29 Radio and 1.76.2007 SPL
working (update: all confirmed by me or other users):
camera
gps
wifi
mobile data
sensor
lights
gps
bluetooth
openGL
Gallery3D
googlebits
working but leaving some questions open:
playback (will print error message in log, not tested with many format)
not working properly:
camcorder (only preview working)
I would not say "it is very fast", but I feel it fast enough. and if you do not care about the multi-media things, i think this build seems not bad.
(for the multi-media things, they are mostly caused by media libs in AOSP, which google have not done yet. (but i cannot understand why nexus-one can have a stable version !!!) it is not all the HTC/Qualcomm's fault, Google didn't do their job very well too)
if there are something I missed, or I made some mistake, don't be sulkiness plz. i will fix them with you. let us make it better and make more 32A user switching to new Radio, with more users, we can do better and more quickly.
file/things includes:
AOSP master, I keep it at the API version 5, because things with API 7 for other devices (except nexus1) are not stable, i don't want to pretend that we have a nexus1, and make things unstable.
su and superusers from ChainsDD.
kernel which i modified from msm-kernel-2.6.29.
libhtc_ril.so, omx libs are from a leaked official 2.x ROM. camera libs, libgps.so from another one. (thanks the man who provided them)
libhtc_acoustic.so and some miscs files from official 1.5 ROM. akmd too, but akmd from 1.6 ROM have newer version and i think it will works too.
google bits are come from different sources too:
Gallery3D/google framework parts from nexusone dump, i think Enomther deodexed them, thank you and I LOVE YOU.
Other google's things are versions used everywhere, and here are my thanks to the one dumped them --> m(_ _)m.
cyanogen's patch which is directed towards infinite sync. it may be a temporary workaround, when google do things right, i will remove it.
.......
more: lock screen and wallpaper is the eclair's initial one as AOSP source released with them. if you want other lock screen, customize it yourself, and tell me how ^^, I'm really not a good cooker .
known issues and workaround:
1. camcorder can not record, but it didn't crash anything as previous one (with my kernel, from jnwhiteh) would crash some.
2. video playback has many errors the video can be played though. just reported by logcat, and no more thing will happen in my tests.
3. if you stay in the Gallery3D UI, and the phone sleeps later, when it wake up, the Gallery3D lost hardware acceleration. you can quit and enter this app again, it will be fine.
4. first boot with google bits may not go without a hitch. you can remove all google apps in the zip (you must resign it) and push them later.if you boot with googlebits:
you will see a dialog let you choose the default behavior, select SetupWizard here. if you select another, you can not use internet during the first boot, it will say "no connection", though we are connected.
the SetupWizard will start twice, the second one is for asking you to sign in a google account, you can just press menu to quit.
and there are many lags in first boot, maybe black screen (can not light, you can "adb reboot" it) or some crash (i have met once for each and I flash it serveral times) if you operate too fast.
after second boot, it will works fine. it seems if we give the phone more time to do many initialize jobs, it will work happily even in first run.
5. with superuser, if you select deny, the app which needed the permissions may be force closed. it is a bug in su sources i used which is not belong to me and i have no time to look and fix it yet.
update:
6. when wake up the phone, screen turned on, but backlight of screen not. if you can see image, just go to setting and set brightness, then the light will open. need more reports (like situation/logcat/dmesg, etc.) to locate the problem. i encountered this problem once.
7. "died in sleep", this problem has been encountered by others, personally, i met it once during first run, after a reboot I never met it again. but I don't think this problem just appears during first run. instead, i think the situation of first run is more closed to the condition triggering it.
I think there must be more problems, let us find them together, and fix them by our hands.
update: after some search I found that some softwares (like nettraffic) will cause more "died in sleep" in some ROM/kernel/Radio combination. and many kinds of "died in sleep" can be avoid with some tweaks, but i don't know if they are same problems as ours, and i can not get what this tweaks are (or why, how..) from anywhere yet.
i am waiting for more details to fix 6 & 7. I will be grateful if someone can provide some info about similar problems, since I had seen these problems in some other ROM/kernel/Radio combination.
and guys who encountered these problems, could you provide more details plz? something like: occurred during first run/other, with situation XX (mobile/wifi/software X running, etc) which you think it caused the problem occurred more often. if you can reproduce it, we will get very closed to fixing them.
great job!
Another ROM using the latest SPL/Radio... great!
Downloading now.. will try flashing later...
Nice work sanpei!
Great job. I will try it immediatly.
Excellent, nice to see some other developers working on this radio/SPL version as well!
I will definitely be trying this out today!
Awesome will try when I get home from work.
Would it be possible to implement the Nexus apps-menu in a later build?
bug report:
The screen remains black (can't see anything) after sleeping even if I press any of the buttons. I just removed the battery then reboot.
Aside from that, it's quite fast and responsive. The transitions are nice too. Keep it up dude!
asero said:
bug report:
The screen remains black (can't see anything) after sleeping even if I press any of the buttons. I just removed the battery then reboot.
Aside from that, it's quite fast and responsive. The transitions are nice too. Keep it up dude!
Click to expand...
Click to collapse
I will look into this, but I cannot locate this problem quickly, since I just met it once during a first boot, and it never appears again.
is it like the situation "die in sleep" in some build which are based on CyanogenMod? (when i was using old radio)
can you reproduce the problem and description the operations? thx.
Eskibo said:
Awesome will try when I get home from work.
Would it be possible to implement the Nexus apps-menu in a later build?
Click to expand...
Click to collapse
maybe or maybe not is there anybody who have the right skills could try it for us? (i have some other things to do) i will join later.
Newb questions
Hi Guys,
Sorry for the lame newb questions. I just want to verify this prior to trying this ROM.
I'm currently using CursorSense 1.0.1 - which is my every day ROM (great functionality, fast, does everything I need)
I'm really interested in trying out Android 2.1 - and seeing as this uses the same SPL / Radio - it means I should be able to just wipe and flash this one. HOwever seeing as I just want to take a peek and play around with it, I don't want to screw up everything on my phone toooo badly lol.
If I do a nand backup - wipe and flash this new ROM, when I'm done, can I do a wipe, then reflash the nandroid backup and everything will go back to the way I have it setup now?
Also will anything get screwed up on my SD card leaving it as it is flopping from one ROM to the other and then back (it's non partitioned, and loaded with misc folders created from my apps)
Thanks!
Gritten
asero said:
bug report:
The screen remains black (can't see anything) after sleeping even if I press any of the buttons. I just removed the battery then reboot.
Aside from that, it's quite fast and responsive. The transitions are nice too. Keep it up dude!
Click to expand...
Click to collapse
I encountered this issue too. I also encountered this issue once with aosp-2.0.1-jnwhiteh-r6.
Gritten said:
Hi Guys,
If I do a nand backup - wipe and flash this new ROM, when I'm done, can I do a wipe, then reflash the nandroid backup and everything will go back to the way I have it setup now?
Also will anything get screwed up on my SD card leaving it as it is flopping from one ROM to the other and then back (it's non partitioned, and loaded with misc folders created from my apps)
Thanks!
Gritten
Click to expand...
Click to collapse
Yes.. backup, wipe, flash, try, wipe, restore.. I even think that last wipe isn't even necessary, but it doesn't harm either. A Nandroid restore restores your phone exactly as you left it (incl. your call log, SMS, apps, etc.)
It could be that some new folders/files are created on your SD card (if required by Eclair apps), but since they are not used by your previous rom it won't be a problem (unless you don't want to keep those unused folders and files on your SD card).
If you are not sure, or don't want to keep the extra folders/files, you can always make a backup of your SD card on a USB or PC prior to trying the rom.
Have fun! ;-)
Gritten said:
Hi Guys,
Sorry for the lame newb questions. I just want to verify this prior to trying this ROM.
I'm currently using CursorSense 1.0.1 - which is my every day ROM (great functionality, fast, does everything I need)
I'm really interested in trying out Android 2.1 - and seeing as this uses the same SPL / Radio - it means I should be able to just wipe and flash this one. HOwever seeing as I just want to take a peek and play around with it, I don't want to screw up everything on my phone toooo badly lol.
If I do a nand backup - wipe and flash this new ROM, when I'm done, can I do a wipe, then reflash the nandroid backup and everything will go back to the way I have it setup now?
Also will anything get screwed up on my SD card leaving it as it is flopping from one ROM to the other and then back (it's non partitioned, and loaded with misc folders created from my apps)
Thanks!
Gritten
Click to expand...
Click to collapse
Yes. You can restore from nandroid backup and everything will go back. I often switch between CursorSense 0.4 and sanpei's rom several times a day.
so can anyone answer if this is a good everyday rom? or equivelant to cursor sense?
shael said:
so can anyone answer if this is a good everyday rom? or equivelant to cursor sense?
Click to expand...
Click to collapse
The ROM is well done. It's responsive (no lag from my playing) even the 3d gallery ran very well.
I didn't use it too long for everyday items as I'm a Sense fan, however I find that standard plain Android is pretty empty when I don't have my sense stuff on top lol.
Definately play around with it if you're interested.
sober said:
I encountered this issue too. I also encountered this issue once with aosp-2.0.1-jnwhiteh-r6.
Click to expand...
Click to collapse
Me too!
Awesome ROM.
Keep UP dude!
Been testing it for a few hours. So far not a single FC and i can confirm that BT works just fine, also OBEX with Bluetooth File Transfer by medieval software.
SMS and emails send and get received just fine.
Tested the GPS in both google maps and the GPS status app to check efficiency, and so far everything works just fine.
The gallery is really sexy, now we just need to get the Nexus1 apps-menu implemented .
Actually there are three other things i'd like implemented also:
Animated desktop
Wireless tether
Google Nav
What do people think about that?
Eskibo said:
Been testing it for a few hours. So far not a single FC and i can confirm that BT works just fine, also OBEX with Bluetooth File Transfer by medieval software.
SMS and emails send and get received just fine.
The gallery is really sexy, now we just need to get the Nexus1 apps-menu implemented .
Actually there are three other things i'd like implemented also:
Animated desktop
Wireless tether
Google Nav
What do people think about that?
Click to expand...
Click to collapse
Will be even better with u suggestion and Sense!
fabioccoelho said:
Will be even better with u suggestion and Sense!
Click to expand...
Click to collapse
I wish I had some idea of how to do those things, then I would surely try help doing it.
Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Checkout http://andromadus.flinny.org for links/files/changelog's
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.
Reserved
Build 5 was pretty stable, interested to see what has changed.
Tapatalked from Desire S running Andromadus
Build 5 was first build i used of AOSP 4.2 and it was fantatic experience, i never expected 4.2 to work so flawlessly on desire s so fast after release. And to be honest i did not see many bugs.
So i flashed build 6 and i was not disapointed, as you said you will release only stable and advanced releases and it was the point with 4.2 build6.
It would be nice to see official changelog, but i have noticed some nice little resize job done and few small glitches fixed.
I just found one thing i dont know how to fix. On android keyboard swype Lithuanian dictionary doesnt work. It is not in official list until i refresh it and then it pops up and i install it ( it worked well with build 5) and with build 6 it just doesnt work, and when i return to dictionary list there is no Lithuanian dictionary again .
Sensors are not working properly. When i make a call, screen turns off even when i don't block the sensors and it stays that way till the time call is going
Sorry man posted it in wrong thread. Its for andromadus cm 10.1 but do look into the matter as its really is irritating
Sent from my Desire S using Tapatalk 2
Thanks for the info..
Why there is no Google Now on lock screen? Only unlock option...
I have latest gapps, updated Google Search etc.
Taranis said:
Why there is no Google Now on lock screen? Only unlock option...
I have latest gapps, updated Google Search etc.
Click to expand...
Click to collapse
That's just the way it is for 4.2, Google made it that way.
I thought I saw videos on YT with Google option on 4.2...
Taranis said:
I thought I saw videos on YT with Google option on 4.2...
Click to expand...
Click to collapse
Yeah, that is for devices with On Screen buttons (Galaxy Nexus or Nexus 4/7/10). For those, the buttons are replaced with a dotted circle on the lockscreen, swiping up from which opens Google Now. Since AOSP doesn't officially support any device without hardware buttons, Google probably thought that it would be best to remove the option from the lockscreen, since swiping from the buttons opens that anyways
Trouble with bluetooth
Hi,
Thanks for your work on this rom!
I would like to report an issue with the Bluetooth functionality in this (and earlier) versions of this rom. In my circumstance it doesn't produce an error of crash.
For example. My phone is connected with a handsfree carkit (parrot) and when entering the car it recognizes the phone, asks for pin code and 'gets connected'. The problem is that the phone is not visible (as usual) on the handsfree device and the overall functionality does not work.
If I can be of any assistance in this I'll gladly be of help.
Thanks for your work!
Well Google switched the bluetooth plugin in 4.2 from bluez to bluedroid. It has been causing issues across devices, even Nexus 7 has issues. As Flinny said we can't do much unless someone upstream fixes it.
Read more here...
http://forum.xda-developers.com/showthread.php?p=35093862
Tapatalked from Desire S running Andromadus
Anyone know why the sound disappear?. notifications, alarms, ringtones, ect.
Thanks for the enlightenment!
suku_patel_22 said:
Well Google switched the bluetooth plugin in 4.2 from bluez to bluedroid. It has been causing issues across devices, even Nexus 7 has issues. As Flinny said we can't do much unless someone upstream fixes it.
Read more here...
http://forum.xda-developers.com/showthread.php?p=35093862
Tapatalked from Desire S running Andromadus
Click to expand...
Click to collapse
Flinny, almost everything works great.
Issues I found (AOSP build 6):
- laggy Camera animations (not very important, maybe it cannot be better),
- high Android OS battery usage (battery really lasts less),
- dictionaries other than English doesn't work with swype keyboard feature,
- some people wrote about bluetooth audio issues.
ROM is very smooth, hope it will be smooth in next builds. Great work!
Taranis said:
Flinny, almost everything works great.
Issues I found (AOSP build 6):
- laggy Camera animations (not very important, maybe it cannot be better),
- high Android OS battery usage (battery really lasts less),
- dictionaries other than English doesn't work with swype keyboard feature,
- some people wrote about bluetooth audio issues.
ROM is very smooth, hope it will be smooth in next builds. Great work!
Click to expand...
Click to collapse
camera animations do lag sometimes and some pictures you take tend to not show up in gallery after you have taken them.
As for battery all i can say is :highfive: battery is almost same in all 4.0/4.1/ 4.2 roms AND it is not at all bad here. I managed to get from full charge(100%) to 81% in 30 hours. I doubt many roms can do something like this in low-med usage.
Other then that this rom is my personal favorite until someone release 4.2 rom with better theme or perfomance.
The only thing i lack in here is conservative cpu governor and maybe little undervoltage.
Taranis said:
Flinny, almost everything works great.
Issues I found (AOSP build 6):
- laggy Camera animations (not very important, maybe it cannot be better),
- high Android OS battery usage (battery really lasts less),
Click to expand...
Click to collapse
+1
Who can tell me how can I put GPS shortcut on quick setting ??I have everything I need except GPS shortcut...
Anyone else have an issue where Calendar just wont sync at all to any Google account? I don't have the options to sync calendars under any of the google accounts I've set up on the device. Tried reflashing, clearing app data etc.
Apart from that, great rom. Super nice battery life.
noponies said:
Anyone else have an issue where Calendar just wont sync at all to any Google account? I don't have the options to sync calendars under any of the google accounts I've set up on the device. Tried reflashing, clearing app data etc.
Apart from that, great rom. Super nice battery life.
Click to expand...
Click to collapse
Clean or dirty install?
By dirty install remove Google accound(s) and then add your accound(s) again.
Worked for me!
For JB4.2 based roms (CM10.1 and AOSP4.2)
if you use a BT headset and are having problems with the mic give this a try.
download the following file.
http://andromadus.flinny.org/libbt-vendor.zip
extract it
Push it to your phone with adb - from the command line
adb remount
adb push libbt-vendor.so /system/vendor/lib
adb reboot
try it now.
Give it a try again and tell me if it all works... If all goes to plan new builds soon
Nick.
Hi all,
This question has probably been asked; the problem is not a lack of solutions but there simply being too many - I've no idea where to begin with troubleshooting. Everything I've seen is just to general to be of any use.
Basically...
I installed CM11 (nightly build for my Motorola Moto G, AKA falcon). I've stripped down some of the GAPPS using the 'Barebones' guide on the CM wiki, e.g. removing the Google+ program I don't use, and the stock broswer (replacing with Lightning from the F-Droid repo). I've also installed various other programs to enable me to have absolute control over the device - AdAway, AFWall+ probably being the only two of interest.
I have no internet access either through data or via the house wifi; I have confirmation the problem is confined to my device since no one else in the house has problems, and my laptop and desktop work without trouble (incidently, the router has recently been changed also, so I now have the problem confirmed on two access points). It's not a reception issue either - the device connects fine to the router (albeit with fairly weak reception because of my distance away), in the 'Settings' dialogue I can see it 'Obtains IP address' etc without any obvious error message/hangs/stalling (and in settings displays itself as 'Connected').
Aside from being directed to a fix, I'd really appreciate it if someone could give me some kind of 'here's how you troubleshoot Android internet access' tutorial; I've got a bit of experience with desktop Linux, and more still with Windoze (albeit unwillingly) - I'm quite comfortable fiddling with the network manager or trying different kernel modules out. On Android, I've just no idea.
So far I have tried:
- Reinstalling the ROM (on both installs, the problem occurs after a few days to ~ a week of normal functioning).
- Uninstalling the AFWall+ (I think it's a DroidWall fork - acts as a frontend for iptables) on the last install, and on this one fiddling with the settings (unticking and re-ticking all boxes to allow on roaming/mobile data/wifi connections
- Uninstalling AdAway (on the last install only)
- Issuing 'ping' in the terminal. It's now just returning an "Error: Unknown host" message, yesterday when I was having trouble with the router, it was returning to do with insufficient privileges (even after I'd ran su to login as root).
-Turning the device on and off (in desperation only).
- I can also confirm the internet access affects not just Lightning (i.e. my browser) but is system wide - Skype, BBC iPlayer, weather updates in cLock etc.
As is probably obvious, I feel I've done little more than bash the screen with a rock and hoped for the best (metaphorically speaking).
I'm wondering if maybe there's something wrong with my hosts file - or else the way packets are sent/received, since Adaway will have altered that, and AFWall+ also. Maybe some bug whereby rules applied by AFWall+ are misinterpreted by iptables to block all access? Any help investigating this avenue in particular would be really helpful.
Also, just in case it wasn't clear, I've got full functionality of everything else, no crashes, able to make/receive calls and SMSes fine etc.
Cheers,
AA.
ArminasAnarchy said:
Hi all,
This question has probably been asked; the problem is not a lack of solutions but there simply being too many - I've no idea where to begin with troubleshooting. Everything I've seen is just to general to be of any use.
Basically...
I installed CM11 (nightly build for my Motorola Moto G, AKA falcon). I've stripped down some of the GAPPS using the 'Barebones' guide on the CM wiki, e.g. removing the Google+ program I don't use, and the stock broswer (replacing with Lightning from the F-Droid repo). I've also installed various other programs to enable me to have absolute control over the device - AdAway, AFWall+ probably being the only two of interest.
I have no internet access either through data or via the house wifi; I have confirmation the problem is confined to my device since no one else in the house has problems, and my laptop and desktop work without trouble (incidently, the router has recently been changed also, so I now have the problem confirmed on two access points).
Aside from being directed to a fix, I'd really appreciate it if someone could give me some kind of 'here's how you troubleshoot Android internet access' tutorial; I've got a bit of experience with desktop Linux, and more still with Windoze (albeit unwillingly) - I'm quite comfortable fiddling with the network manager or trying different kernel modules out. On Android, I've just no idea.
So far I have tried:
- Reinstalling the ROM (on both installs, the problem occurs after a few days to ~ a week of normal functioning).
- Uninstalling the AFWall+ (I think it's a DroidWall fork - acts as a frontend for iptables) on the last install, and on this one fiddling with the settings (unticking and re-ticking all boxes to allow on roaming/mobile data/wifi connections
- Uninstalling AdAway (on the last install only)
- Issuing 'ping' in the terminal. It's now just returning an "Error: Unknown host" message, yesterday when I was having trouble with the router, it was returning to do with insufficient privileges (even after I'd ran su to login as root).
-Turning the device on and off (in desperation only).
As is probably obvious, I feel I've done little more than bash the screen with a rock and hoped for the best (metaphorically speaking).
I'm wondering if maybe there's something wrong with my hosts file - or else the way packets are sent/received, since Adaway will have altered that, and AFWall+ also. Maybe some bug whereby rules applied by AFWall+ are misinterpreted by iptables to block all access? Any help investigating this avenue in particular would be really helpful.
Cheers,
AA.
Click to expand...
Click to collapse
maybe is a problem with ROM, flash different rom.
Paget96 said:
maybe is a problem with ROM, flash different rom.
Click to expand...
Click to collapse
AFAIK the dev has had no problems, and the two different installs I've had have been different builds.
Also I've no idea where to start to find a new ROM; Linux has the fantastic DistroWatch, but no such resource exists for ROMs (AFAIK).
Finally...I'm quite fussy . CM is just the right balance of features - if you want 'em - and stock, vanilla (or even barebones) if you don't. I had a HOX+ in the past, and so many of the ROMs for that were all about eyecandy and glitter - fat I'd rather trim.
ArminasAnarchy said:
AFAIK the dev has had no problems, and the two different installs I've had have been different builds.
Also I've no idea where to start to find a new ROM; Linux has the fantastic DistroWatch, but no such resource exists for ROMs (AFAIK).
Finally...I'm quite fussy . CM is just the right balance of features - if you want 'em - and stock, vanilla (or even barebones) if you don't. I had a HOX+ in the past, and so many of the ROMs for that were all about eyecandy and glitter - fat I'd rather trim.
Click to expand...
Click to collapse
you try to wipe cache?
Paget96 said:
you try to wipe cache?
Click to expand...
Click to collapse
When I installed the ROM, yep. My method is to wipe everything then sideload (IMO it seems cleaner ).
Otherwise, no, and don't see why it would make a difference, and would have no idea how to do it anyway...through the recovery, or is there a way to do it when booted?
No offence, but I get the feeling this is the blind leading the blind xD.
ArminasAnarchy said:
When I installed the ROM, yep. My method is to wipe everything then sideload (IMO it seems cleaner ).
Otherwise, no, and don't see why it would make a difference, and would have no idea how to do it anyway...through the recovery, or is there a way to do it when booted?
No offence, but I get the feeling this is the blind leading the blind xD.
Click to expand...
Click to collapse
I dont know, try to flash different rom and see if it will happen again or not. If not, problem is in that rom you already have.
Paget96 said:
I dont know, try to flash different rom and see if it will happen again or not. If not, problem is in that rom you already have.
Click to expand...
Click to collapse
Any suggestions on where to find one? Or of a particular ROM?
ArminasAnarchy said:
Any suggestions on where to find one? Or of a particular ROM?
Click to expand...
Click to collapse
[ROM] [4.4.4] [OFFICIAL] ParanoidAndroid 4.4 [FINAL/STABLE]
you can try this
[ROM][4.4.2] SlimKat 2.6 RC2 | Unofficial
bugs:
Problems with GPS.
- Sometimes recovery takes a LONG time to install the ROM.
[ROM] Infusion Beta III [Google Play Edition Based] [27th Jan 2014]
---------- Post added at 02:21 PM ---------- Previous post was at 02:19 PM ----------
all ROMs
http://alchemistar.blogspot.com/2014/02/moto-g.html
Hi,
I am back with one of my builds. Again this is just result of my hobby, feel free to use it, but do it on your own risk. Also any updates will be probably sporadic.
I wanted to publish my build as quickly as possible, becasuse I promised in another thread. So I simply took, what I have (and I am using right now). As a result there some detail I`d like to change for public release like this for the future (e.g. all the special feature enabled by default, the big dmesg buffer). Be careful. I`ll try to do better version as soon as possible. I don`t recomend this for begginers. Be sure you have backup.
This build is based on the official LineageOS code and contains several of my changes. In some cases it could be considered as fix, improvement, but sometimes a hack or even even security risk, so please read carefully following list. All the changes I did because I wanted the system on my device behave that way (at least time to time). Take it or leave it. Please note, that all the features are enabled by default. Be careful.
- built-in root support
- RIL is based on stock KitKat version (works better for me than the official version)
- the sensors libraries are also from stock KitKat (same reason as above )
- barometer sensor is correctly recognized by the system
- the menu button does, what it always did
- notification led brightness can be configured by user
- entering safe mode by holding specific keys during boot can be disabled by setprop persist.safe_mode_disabled true (this has always only annoyed me, but be sure you know you are doing)
- device wakeup by power button can be disabled when proximity and light sensors are blocked (e.g. in a pocket). Execute setprop persist.pwrbtn_proximity_block true
- external sdcard can be made world writeable by setprop persist.world_writable_sdcard true (be careful with this one, this opens a security risk)
- the notification led can blink when the battery is fully charged - enable by setprop persist.blink_when_charged true
- F2FS support
- the notification icons are also on the lock-screen as they ware in
previous Android versions. The carrier name is moved above the clock
(this cannot be turned off)
- the dmesg buffer size is increased to 16M. I set this for debugging
and remove it in next published build.
- ramdisk LZMA compression support
- sdcardfs support - This is faster replacemnt for the FUSE filesystem. I backported this for higher kernel version. Although I`ve been using this for several months without any problem, please consider this experimental. Enable with setprop persist.sys.sdcardfs
force_on
- mount directories for sdcard are protected against writing while the sdcard is not mounted (this solves a race condition problem which allows some apps to create files in there)
- there some other small changes related to my multiboot envrionment, czech translation, carrier name, etc.
Source code
In the installation zip there is a directory code_info with following content:
roomservice.xml - roomservice.xml for the build
commits - list of git repositories and commits used for the build
patches - directory tree with structure reflecting the source and containing
patches for individual projects. The idea (not always followed) is that one patch is one feature,if possible.
code1.diff - all the patches from patches directory together
code2.diff - changes which are not in patches directory
diff-commits.txt - obsolete, I`ll remove this one in the future or maybe use
it again
The only bug I know about is occasional crash of MTP, but I didn`t notice any negative consequences. There may some problem with battery charging (the display turns on time to time without no obvious reason during charging), but it may be some hardware error (bad cable or charger).
Since this is based on official LineageOS, thanks to everyone who contributed to it.
I am using this build for over a week without any problem, except those mentioned above.
Continue here, for the latest build.
UPDATE:
I totally forget about this yesterday - here are the proprietary files I used for this build proprietary-files-ocm13-skk-ril.tgz It is a mixture from the CM 13 official build and KitKat stock files, with modified ks file (then connect symbol is replaced with xonnect, so it doesn`t crash), maybe some other files and changes. I really don`t remember, I put this together during a long period of time. If you find any of your work inside, please accept my apologies and let me know. From my point of view it just works. If you want to apply the patches, then you will most probably want to change the hardcoded full path to these files in device/samsung/i9305/extract-files.sh.
UPDATE:
If you want to use anything from my patches, feel free to do so, just follow the license of the original project.
I tested it for about 4 hours for modem stability, taking the logs. All SAHARA transfers were ok, with no errors and retries. I should have mentioned your name in some post earlier
gongrats and many thanks @p.a.n. Your rom runs very well, its awesome. :good:
Do you mind, if I take your sources or parts of it or some files from your rom.zip for my builds? If I do so, I will mention you and what I took and give you credits.
rodman01 said:
gongrats and many thanks @p.a.n. Your rom runs very well, its awesome. :good:
Do you mind, if I take your sources or parts of it or some files from your rom.zip for my builds? If I do so, I will mention you and what I took and give you credits.
Click to expand...
Click to collapse
Thanks Use whatever you want from it just follow the license of the original project (I updated OP with similar note).
Help??? How to fix gps on this Rom plzz
Great work p.a.n.
Using for 24 hours no problems yet and seems very smooth.
Used it for a few hours with the built-in kernel then switched to Boeffla to get Boeffla Sound etc.
Very nice to have the customisable LED again as it was missing from the official LineageOS.
More importantly for me, the magnetic compass seems to work properly. I couldn't get it to work on official, nor on Rodman's RR.
No issues with GPS for me.
I had to install 'The SELinux Toggler' to set permissive so I could get Viper4Android to work (as with official) but I expected that.
One other thing, the MTP crash is the 'MTP host' app. I just disable this as it's only needed if you need your phone to be an MTP host for something like a digital camera, which I don't. It doesn't affect connections to your PC.
Is there an issue with the automatic execution of init.d scripts? I'm on Boeffla so it may just be that. Luckily you can tell Boeffla app to execute them anyway.
@Glenn2, thanks for testing I am not completely sure about it, but if I remember well, the compass problem is caused by the opensource sensor library (I think that just replacing the/system/lib/hw/sensors.smdk4x12.so with the one from my build should fix that). But the problem is not actually with the compass sensor, that one is ok, but in the opensource version there are missing some "fake" sensors, which provide calculated data based other "real" sensors. One of them provides orientation information, often used in apps as compass. Try some app (e.g. Androsens2) which lists all the sensors and you`ll see the difference - the "fake" ones have iNemo in their name.
I actually don`t care about the MTP crashes. It mostly happens after uninstalling some app, which doesn`t happen too often and otherwise I haven`t noticed any negative related to that. It is just annoying popup for me.
What do you mean by the question about init.d scripts?
p.a.n said:
What do you mean by the question about init.d scripts?
Click to expand...
Click to collapse
I have a couple of scripts and they were not running on boot. I don't know if Boeffla kernel affects busybox. I remedied this by telling the Boeffla Config app to run init.d scripts when it launches.
Also, I had a power manager service wakelock that kept my phone awake for hours, only a reboot cleared it. I had this happen a couple of times on official LineageOS too. Not the famous mdm_hsic_pm0 which now seems to be cured at long last! I had a period of no signal when I was on the London Underground, maybe that was the cause.
Glenn2 said:
I have a couple of scripts and they were not running on boot. I don't know if Boeffla kernel affects busybox. I remedied this by telling the Boeffla Config app to run init.d scripts when it launches.
Click to expand...
Click to collapse
There is /system/etc/init.d/* scripts, which run OK, or at least /system/etc/init.d/00banner does. There is also /system/etc/init.d/90userinit, which executes /data/local/userinit.sh. I remember that seme previous CM version there was also a user defined init.d somewhere in /data. This may what has changed, but I am not if this is your case.
Glenn2 said:
Also, I had a power manager service wakelock that kept my phone awake for hours, only a reboot cleared it.
Click to expand...
Click to collapse
This on is also often on the top of my kernel wakelock list, but never that bad, always with reasonable times.
Glenn2 said:
Not the famous mdm_hsic_pm0 which now seems to be cured at long last!
Click to expand...
Click to collapse
Yes, the solution has been sitting in the Samsung kernel source for a long time ...
Glenn2 said:
Great work p.a.n.
Using for 24 hours no problems yet and seems very smooth.
Used it for a few hours with the built-in kernel then switched to Boeffla to get Boeffla Sound etc.
Very nice to have the customisable LED again as it was missing from the official LineageOS.
More importantly for me, the magnetic compass seems to work properly. I couldn't get it to work on official, nor on Rodman's RR.
No issues with GPS for me.
I had to install 'The SELinux Toggler' to set permissive so I could get Viper4Android to work (as with official) but I expected that.
Click to expand...
Click to collapse
Do you install the last rom ??? Or not
It is worth pointing out that after backing and restoring between roms, the SELinux attributes for efs files can become not correct. That can lead to something like this :
Code:
06-28 04:17:43.705 3799 3799 W ks : type=1400 audit(0.0:30): avc: denied { read } for name="efs1.bin" dev=mmcblk0p11 ino=8200 scontext=u:r:qcks:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
Code:
06-28 04:17:43.712 3799 3799 E kickstart: Requested ID 16, file "/tombstones/qcks/efs1.bin"
06-28 04:17:43.712 3799 3799 E kickstart: ERROR: function: open_file:80 Unable to open input file /tombstones/qcks/efs1.bin. Error 13: Permission denied
It results in not working RIL because of enforced SELinux. Running restorecon fixes the problem.
moad gastro said:
Do you install the last rom ??? Or not
Click to expand...
Click to collapse
I don't know what your question means, as there is only one ROM. I installed from the link in the OP (dated the same date as the OP).
Still using this ROM, and still very few problems.
The day before yesterday it crashed with the screen off. Had to hold power button in to restart.
And yesterday the damn wakelock. It got stuck at a time when I had no signal, and also I used the camera, so either may be relevant. It didn't seem to cause any drastic battery drain though (see images attached). I suppose when the CPU is awake but only at 200MHz and not doing much it uses little more than when it is sleeping?
Regarding init.d scripts. I added one to /system/etc/init.d that simply writes a file to /data when it runs, to test that it DID run. Script starts #!/system/bin/sh
Results:
1) rom with its own kernel - didn't run
2) rom with Boeffla kernel - didn't run
3) rom with Boeffla kernel and Boeffla Config app set to execute init.d scripts itself - did run
One more, just for fun!
Two days ago I was at the Wimbledon tennis, and the location service and/or weather widget decided I was in Boulogne-Billancourt (Paris) instead! I then opened and closed Maps, refreshed the widget and it changed to the correct location!
..
Hi,
I'm trying to install the current build using TWRP 3.0.2-1, but it gets stuck at the "Patching system image unconditionally..." step with the progressbar at around 40%. It's been sitting there for about 10 minutes. Does anyone know how that'd be fixable?`
Cheers
Latest build is ok for me. I've flashed it using TWRP 3.1.0 build from rgib
https://drive.google.com/drive/folders/0B7pwslEEF0l4Yzk2Nm1jOGRDQVU
It seems that contributing to LOS building ROM is not anymore tolerated, this post is deleted.
Maybe @Scavenger87 wants to take a look here ;-)
I guess it's better to have an own dedicated thread.
Thanks for setting up a distinct thread. Things were getting confusing!
john_matrix said:
Maybe @Scavenger87 wants to take a look here ;-)
I guess it's better to have an own dedicated thread.
Click to expand...
Click to collapse
Hey John great idea with opening a new Thread because i also think its really confusing already
john_matrix said:
@Scavenger87: Steel01 advised to let 15.1 (I think he is right because it's too old and because lot of changes have been done between 15.1-16.0)
Also have found this during LOS 16.0 debugging and when application is crashing:
Starting from Android 9, LMK can be implemented in userspace and needs new optimization settings:
Low Memory Killer Daemon | Android Open Source Project
source.android.com
Will see if this new userspace LMKD can be tuned.
@Trevor_g: can't say... I don't have an Nvidia controller to test.
Click to expand...
Click to collapse
Ok yeah i think he's right for multiple reasons
- 15.1 had still unsolved issues aside of broken omx like the crashing nv games app and not working screen mirroring which is working so far on 16.0
- 16.0 is Android 9.0 based which is the same as the actual Software for the Shield TV. That means there is maybe a chance they can use some Codes or even Apps like the Shield Accessories to makes things like the First Controller working again over WIFI.
I even found a lot Nvidia OEM Apps here on APK Mirror : https://www.apkmirror.com/apk/nvidia/
I think i start testing around with those apks as soon i installed the lasted 16.0 build
@Trevor_g
For your question i have to check that again on 16.0 with the old Controller but i think its still only working over a OTG Adapter.
Like i mentioned above maybe the Shield TV Accessories App is working.
mirhl said:
https://gist.github.com/webgeek1234/8ef1bd105d2add3aa9c29028c2befbb0
https://github.com/vartom/drivers-kernel-nvidia-49/tree/smaug49/drivers/hid
https://github.com/devmapal/nvidia-shield-controller-driver
Click to expand...
Click to collapse
Someone even mentioned this Linux Driver for the Controller
But to be honest dont suspect too much on lets say all this bonus functions because first the LOS Team have to work on the base build to make it stable and running right
Ok i installed the latest build (4/1/21) yesterday on my LTE Tablet over sideload because i had no extra SD Card to format it to FAT32 and with the new TWRP 3.5-9.0.
I installed also the Pico Gapps and then TWRP said when i was about to Restart that there's now OS installed.
But thats seems to be a bug with TWRP itself because after the restart there was the LineageOS screen waiting for me and after a freeze for about a minute or two i was able to complete my installation.
After this i now can say its the most stable LOS 9.0 Rom so far !
It has very less apps crashing so far i only had to start them twice sometimes and also the hw acceleration working now most of its time at Chrome and on the Youtube App.
I can really see there has going again a lot of work into this Rom and its really a pleasure now to see how it get more stable everytime.
Big thanks to @Steel01, @npjohnson, the whole LineageOS Team and of course to @john_matrix
Btw @john_matrix did you change anything on the partitions you mentioned earlier on this build ?
@Trevor_g
I did a short test yesterday with the controller and as suspected it doesnt recognize by the tablet. I soon test out those Android 9.0 based Accessories App from the Shield TV
Thank you for the rom
Can I just flash this over Lineage 14.1 or do I need a factory wipe?
Did anybody test gamepass streaming yet?
danielandross said:
Thank you for the rom
Can I just flash this over Lineage 14.1 or do I need a factory wipe?
Did anybody test gamepass streaming yet?
Click to expand...
Click to collapse
Yes you have to wipe the device first in TWRP to install this rom.
Maybe a little general guide for everyone here who want to try this build in this early state and help tracking bugs
For an clean Installation its important to wipe the device first with TWRP like shown on the first Screenshot.
After this go to Advanced and choose everything choosen on the second Screenshot.
Now you shutdown the Tablet and insert the SD Card or plug in the cable for sideloading.
After turning on the Tablet and choose Recovery Mode again, first install the Rom of course then choose Wipe cache/dalvik.
Now you have to install Gapps if you want to use it. Its recommend to use only the Pico Package.
Wipe cache/dalvik again and restart the device.
If you use Sideload it might says in the Shutdown Menu :
No OS installed !
Which is a bug in my opinion of the new TWRP 3.5-9.0 Package but please use this Version of TWRP in any case that the basement of the installation is everywhere the same !
This is IMHO the way to install a Rom in a clean way and helps tracking down bugs better when everyone used the same methodes.
@john_matrix
I installed the Rom today on a K1 16GB with the methode i described above and did it with my regular SDCard i use in all my Tablets. In comparsion to installing over sideload it didnt get the No OS installed! message at TWRP and i didnt had that 1 minute freeze at begin of the install-wizzard after the LOS Logo.
Also the Rom seems to be same stable as the one on the 32GB model.
But i have to test it a bit more side by side to make valid statements
Also Nvidia Games working nice as you can see on the Screenshots
Hi guys, so, long story short i got scammed on a dutch advertising portal and ended up with one of them shield tablets which were recalled a few years ago. Yep, those with the defective battery that may burst in flame one day
Anyways, i figured that since it hasnt happened until now, i might just be lucky and give it a shot.
Its great to see that there is still some active development of this device! flashed this rom and i gotta say im positively surprised. Its running nice and smooth and even though it crashed on me a few times after the first boot, but a few reboots later and its running like a charm! i didnt bother with gapps, root or anything yet though. really great job devs!
Scavenger87 said:
I installed the Rom today on a K1 16GB with the methode i described above and did it with my regular SDCard i use in all my Tablets. In comparsion to installing over sideload it didnt get the No OS installed! message at TWRP and i didnt had that 1 minute freeze at begin of the install-wizzard after the LOS Logo.
Also the Rom seems to be same stable as the one on the 32GB model.
Click to expand...
Click to collapse
My tablet was completely wiped with no OS so I just pushed the ROM, pico gapps, and magisk over USB onto internal storage with MTP/TWRP. Flashed it all from there and it worked fine. No issues or errors. I don't think it's at all necessary to sideload to use an external SD.
Jackill said:
Hi guys, so, long story short i got scammed on a dutch advertising portal and ended up with one of them shield tablets which were recalled a few years ago. Yep, those with the defective battery that may burst in flame one day
Anyways, i figured that since it hasnt happened until now, i might just be lucky and give it a shot.
Its great to see that there is still some active development of this device! flashed this rom and i gotta say im positively surprised. Its running nice and smooth and even though it crashed on me a few times after the first boot, but a few reboots later and its running like a charm! i didnt bother with gapps, root or anything yet though. really great job devs!
Click to expand...
Click to collapse
In this Thread beginning from here i share my informations so far about the two type of batteries and changing them out if you interested:
Finding Replacement Battery in 2017?
Anybody know where to find a battery that will fit in the Shield Tablet? I know there are several threads online (here on xda, on GeForce forums, and other places) that discuss replacing the shield tablet battery and a few different part numbers...
forum.xda-developers.com
airtower said:
My tablet was completely wiped with no OS so I just pushed the ROM, pico gapps, and magisk over USB onto internal storage with MTP/TWRP. Flashed it all from there and it worked fine. No issues or errors. I don't think it's at all necessary to sideload to use an external SD.
Click to expand...
Click to collapse
I did these two type installation because @john_matrix mentioned to use a SD Card which is formated with FAT32 instead of exFAT. I didnt had one lying around so i used sideload this time.
Thank you everyone and Scavenger87 for your feedback! ;-)
About stability, I guess the culprit is the fact I have played with the new userspace LMK but for me it's not stable enough to be used as daily.
For example, Youtube often continue to play videos greeny and blocky and this is annoying
I will try to fine tune the best settings for LMK.
About battery, I have changed mine too with this one:
https://fr.aliexpress.com/item/32807531204.html
It works good but require to use the board of the original battery.
Seems to be going well so far for me, battery life seems good and for the general use I have had time to do it's worked well.
One crash that caused a reboot, after testing the hdmi output the tablet rebooted when I unplugged the hdmi cable from the tablet.
john_matrix said:
Thank you everyone and Scavenger87 for your feedback! ;-)
About stability, I guess the culprit is the fact I have played with the new userspace LMK but for me it's not stable enough to be used as daily.
For example, Youtube often continue to play videos greeny and blocky and this is annoying
I will try to fine tune the best settings for LMK.
About battery, I have changed mine too with this one:
https://fr.aliexpress.com/item/32807531204.html
It works good but require to use the board of the original battery.
Click to expand...
Click to collapse
Ok that means there is still some kind of memory leak problem with our tablets or is the memory managment on android 9 and higher not really suited for our low ram devices ?
I also read something about drawbacks with the in-kernel LMK as you can see here :
Drawbacks of in-kernel LMK driver
Android deprecates the LMK driver due to a number of issues, including:
Low-RAM devices had to be tuned aggressively, and even then would perform poorly on workloads with large file-backed active pagecache. The poor performance resulted in thrashing and no kills.
The LMK kernel driver relied on free-memory limits, with no scaling based on the memory pressure.
Because of the rigidity of the design, partners often customized the driver so that it would work on their devices.
The LMK driver hooked into the slab shrinker API, which wasn't designed for heavy operations such as searching for targets and killing them, which slowed down the vmscan process.
Is the zRam function now activated by standart on Android 9 and higher to compress amount memory is needed ?
I try to stresstest it today with a website that have a lot pictures sadly i cant use instagram anymore because you need a account now
Shield Tablet can't be considered as a "low ram device" as Google defined them with up to 512MB (Android Go?)
Android Performance Optimization | Android Open Source Project
source.android.com
I also have devices with 2GB that are currently performing Lineage 17.1 very well (Sony Z3C and Nexus 4)
I don't know if zRAM is activated by default in Android but you still have the choice to activate it or no (in the kernel or in the fstab.
Additionnally, I don't know what is the policy to activate zRAM (my Mi9 have 6GB RAM and have zRAM activated by Xiaomi so...)
Another thing about zRAM is there are lot and lot of options you can activate such as compression, lz4, clear caching, etc... depending of your needs and I am not skilled enough to say exactly what will be the consequences of these options (but it cost nothing to try).
You also have to keep in mind that zRAM will consume more CPU times (as KSM).
Similarly, you can fine tune the CPU governor and IO scheduling (often I see CFQ by default but on the other way I have saw that Noop and Deadline gives best results).
Feel free to share your experience and if you have other ideas on what you would like to integrate in this ROM (as the best possible).
You are right to stress test the OS, you can also debug the memory and the weight attributed on the processes.
Ok but 2GB is really not much these day also this article from android source is really old i think i read there something about kitkat or so
But your right i also was suprised to see that my xperia z3 compact i have lying around is able to run lineageos 17.1 and even is supported by the LOS Team
Which leads me to the question is the memory managment on the Qualcomm SOC so much better ? Ok the Ram there is on the SOC itself instead of external like on our Tegra based devices.
I think i install tonight Triodexes 15.1 with zram to compare the effect it has.
I also noticed the hw acceleration crashes the most on the firefox browser like i told in the 15.1 Thread you can start one video and it runs if you leave everything untouched but your not able to start a second one even with autoplay.
Btw about the LMK i know its maybe a dumb question but did you try the original settings from the Oem Rom ?
Edit : The original values in minfree are: 18432,23040,27648,32256,36864,46080
And zRam is already activated on the LOS 16.0 Build with 511MB same like the oem rom
Scavenger87 said:
I did a short test yesterday with the controller and as suspected it doesnt recognize by the tablet. I soon test out those Android 9.0 based Accessories App from the Shield TV
Click to expand...
Click to collapse
Thanks SO much for looking into this for me! You mentioned later that the controller wasn't recognized by the tablet, however I'm also curious if the Accessories app from the ShieldTV might help. Thanks again, in advance!
Fwiw, there's a bunch of framework patches needed for the wifi direct controller to work. I've yet to get them all straight. Haven't had that working since cm-12.1. See the incomplete set for 16.0 here:
https://review.lineageos.org/q/topic:shield-blake-p
That's on top of:
https://review.lineageos.org/q/topic:nvidia-shieldtech-p
And there's no nvidia pairing app that works with a touch interface. It's a mess atm. I did get blake to pair to foster on 15.1, but only while the pairing wizard was open. As soon as I hit back to close it, the autonomous group goes down and the connection is lost. And now, it's close to impossible since nvidia didn't release the nvwifi prebuilt jar to link against. And the one from O doesn't work on P.
Hi @Steel01
Thank you for keeping us updated on your work with the controller and also for your work for this device in general
I already tought its not easy to bring wifi support back for the old controller but i think also there is no high priority since the second gen is working fine over bluetooth and they already cheap to buy used.
Other than this the rom is suprisingly good running for this early stage and most of the stuff is working
Is there something that needs special attention for testing at the moment to help you developing ?
Like i mentioned in a other Thread i have every generation of the Shield Tablet and Controller. Only on my LTE Modell the SIM Card Reader is unfixable broken
But i still hunting for a fully working device.
Before I flash this Rom: Why do I habe to wipe internal storage?
danielandross said:
Before I flash this Rom: Why do I habe to wipe internal storage?
Click to expand...
Click to collapse
Well i dont know if its really needed to wipe the internal storage but i think by the reason we testing here a new Rom in a really early stage we should give it the cleanest basement as possible to exclude problems that might caused by left over data that interference with the Rom