Related
For the last couple of days I've been trying to get Eclair 3D acceleration running on 32A with old radio. I was somehow succesful so I decided to release one Sense based ROM port and one "plain" Eclair. I had succes with other ROMs though (not all of them, but a few). Edit March 2nd - It now seems that it works on 32B/G1 as well, so I've added the porting package for those phones, see below.
This ROM is highly experimental! So bear that in mind. The only testing I've done is here on my own Magic - I am not using any ext3/ext4 partition for app2sd, for example, so I'm not sure how it behaves if you use one.
I've added a few things here and there that are essential to me like Market Enabler, More Locale 2, some ringtone and notification files and mixed in a few files from other Eclair ROMs to get a few things working. I've also changed the default analog clock (the Android widget, not HTC widget) to Pulse clock.
Thanks to:
ahmgsk (obviously), Kingclick, Cyanogen and all the other devs working on his kernel source, Amon_RA, all OpenEclair devs, polyrhytmic, dzo, vilord and many others.
What seems to work:
- 3D acceleration seems to work fine. I can get about 20fps in Neocore benchmark. I've also tested Radiant, Armadillo Roll and iDracula and they all seem to work. 3D Gallery works as well.
- Multitouch works
- Camera works, mostly - no video recording, though. If you take picture, it shows a garbled screen for a moment, but the picture itself is taken just fine.
- GPS and accelerometer work
- LED notifications work, all colors
- Bluetooth MIGHT work, needs testing. But you can enable it.
- Google Sync seems to work just fine
What seems not to work:
- YouTube and video playback in gallery doesn't work at all for now. Sorry.
Known Issues:
- Rather slow on startup. Give it time to start up fully, even after you see the home screen. You may even get a few "App not responding - FC/Wait?" warnings - just click on Wait and give it more time. But after it starts, it seems pretty fast to me. It's no SuperD, but still quite fast, I'd say.
- Live wallpapers are problematic and I'd recommend staying away from them. Some work (not very fast, though), some don't.
- Launcher 2 is problematic. I've kept it in the ROM and it certainly looks nice, but I've had all sorts of problems when I had it enabled, including long phone freezes, terrible lag in applications and other. I'd HIGHLY recommend just using the "normal" launcher (it's "Nexus style" anyway).
Note:
Take this port "as is" 'cause I probably won't support it much. I think of it more as a "proof of concept" that seemed too cool to me not to share it with others, but I don't have enough time to offer full support or work on it much these days. Maybe I'll release another version someday, maybe not. Sorry. I'm just being honest here.
Download:
v1.0 - md5 1d52c09ac080abd6f1620a00afb96d30
Rapidshare mirror
Mediafire mirror
Porting package for 32B - Warning: potentially unstable in many different ways! (see the thread comments first) - md5 506d30b69186059abc2a22804952e7a8 (Flash over the main ROM without rebooting the phone)
Rapidshare mirror
Mediafire mirror
(reserved just in case)
I will check it inmediatly...
but this driver 3d not work on magic 32b??Why not come out yet for the ROM 32b?
It might, as I don't think the solution here is specific to 32A. I'll maybe try to make a 32B kernel soon and let someone test it. Right now, I've yet to hear about this working for someone else on 32A other than me
Im flashing it ATM.
Give me a few minutes
ok when you relase a 32b Kernel,Warn
Well, i flashed it.
You're right, 3D is working
I tried it with SpeedX and Hyper Space, and they both are working. Not as fast as it would on a donut based rom (looks like the frame rate is a little lower) but they are absolutely working.
Launcher2 is still a bit laggy.
Some Live Wallpapers aren't working, they forced the phone to restart.
The gallery is working.
There are some bugs (like pressing the home button while in an app, will sometimes block my phone) that forced me to remove the battery.
This rom is not working enough for a daily use, but you did a great job.
Waiting for a bug fix Imma try the hero port now
Good to know, thanks!
BTW, as I've mentioned in the first post, I don't recommend using Launcher 2, it causes all sorts of weird issues with this ROM. And I also mention that live wallpapers are problematic and you should just stay away from them
Oh, and as for the framerates in 3D - in my experience they're actually slightly higher on average than with my own SuperD port I'm now using as a day-to-day ROM (I miss Sense UI, but 1.5 is starting to lag behind on all the interesting stuff, so...).
Case_ thx for working on this
i could not work becoz my tester was on new radio
i hope u get my hero 2.1 working too
From what I gather, this is a KERNEL modification that makes the HERO drivers work with this "old radio", correct?
Could you please provide the kernel diff (patch)?
ahmgsk: You're welcome. I'm always somehow uneasy as to what the reaction of the original dev would be when I'm using and perhaps modifying someone else's work, so thanks for this
I'll try to follow the progress of most Eclair ROMs but I'm gonna be quite busy for at least the next week or so, so no promises on any other updates or more ports (but I'd LOVE to have a reliable Sense UI ROM with Android 1.6 or higher, I can tell you that - Kinglick's Eclair Hero is close, but still not close enough to rely on it on day-to-day basis). I'm glad I managed to at least steal the weekend for Android for once and got this working, more or less.
lbcoder: Actually, there's really not much to patch. I've spent countless hours trying to port parts of the Kaiser kernel as discussed in one of the G1 forum threads, yet in the end I've ended up using pretty much just the plain vanilla Cyanogen Eclair kernel sources with only the camera code backported from the Donut sources to get the camera working (but I can certainly provide some kind of diff if need be).
Then there's the permission problem with /dev/msm_hw3dc and /dev/msm_hw3dm that on most Eclair ROMs needs fixing (chmod 666 and chmod 660 in init.rc, respectively).
And then it might or might not be an issue with the contents of /system/lib/egl and /system/lib/hw (and perhaps some other libs as well) which, I'm sorry to say, I've yet to fully test. Those from ahmgsk's AME Eclair seem to work, but looks to me like it's not exclusively just those, that it might work with some others as well. I know it's not very professional (but I've said it many times, I'm no dev and certainly no coder, I'm just determined and persistent ), but I honestly didn't have time to test those different libraries fully, sorry. I was just trying to get something as usable as possible and share it with others so they may perhaps investigate further. Though it somehow amazes me that I of all people got it working when there's so many people with coding and Android knowledge WAY beyond my own here (which is not that hard to achieve, anyway)
Case_ said:
ahmgsk: You're welcome. I'm always somehow uneasy as to what the reaction of the original dev would be when I'm using and perhaps modifying someone else's work, so thanks for this
I'll try to follow the progress of most Eclair ROMs but I'm gonna be quite busy for at least the next week or so, so no promises on any other updates or more ports (but I'd LOVE to have a reliable Sense UI ROM with Android 1.6 or higher, I can tell you that - Kinglick's Eclair Hero is close, but still not close enough to rely on it on day-to-day basis). I'm glad I managed to at least steal the weekend for Android for once and got this working, more or less.
Click to expand...
Click to collapse
i hav no problem when u use my rom
its no probs -> but i m glad 32A (old radio) users are getting this. i m working on hero rom i think i can try to get everything working
for now videos and all are working
now some widgets n network is remaining (mostly solved) v2 coming soon
YouTube and video playback in gallery doesn't work at all
Click to expand...
Click to collapse
Why? I remember in the original ahmgsk 's ROM they are working as well...
What has been changed from the old to the new Radio/SPL to break the YouTube/Gallery video playback?
As for the "why?", that's a very good question I'd really like to know the answer to.
As for "what has changed" - the kernel has changed (had to for the ROM to work with the old radio) and with it all the "drivers". I'm not happy that YouTube and video doesn't work, but I don't have much time to investigate further right now. And until now, neither did Eclair 3D acceleration with the old radio, so I guess it's still progress.
I'm sure someone will figure it out eventually.
Added links for 32B/G1 porting package. Yes, 3D really seems to work on those phones as well.
how do I apply the 32B patch?
just replace the files with the once from teh original zip file , repack it, and then apply the new zip?
stefanero313 said:
how do I apply the 32B patch?
just replace the files with the once from teh original zip file , repack it, and then apply the new zip?
Click to expand...
Click to collapse
yeah how do us g1 owners do this thang ...
?????????????????????????????????????????
I guess I figured it out,
download both zip files, apply zip one, then apply the 2nd one other the other.
replacing files wont work because of the files within the "META-INF" folder
FOR 32A, RADIO 6.35 and SPL 1.76
CAUTION: for daily use, I feel this port are stable enough for many people. but it may not suitable for others. and it is a bit slow at sometime. I won't optimize it at current, since the speed is acceptable, and I must keep it "clean" to avoid any hidden bugs before we can get all things working properly.
plz don't touch your phone until everything have been loaded completely. I also can't suffer the speed during something are loading after boots. after everything have been loaded and use the phone for a while, I feel the speed is fine personally.
wipe and flash in recovery, and you should delete the generated files (by android) in your sd card.
Eris v0.4 & Legend V0.4[UPDATED at June, 16th] :
latest update [Jun 26]::
OC: http://forum.xda-developers.com/attachment.php?attachmentid=349885&d=1277499752
non-OC: http://forum.xda-developers.com/attachment.php?attachmentid=350638&d=1277631885 , under testing, plz report bugs.
though they were developed with HERO port, but I think it could be used in all my ports.
eris port is stable enough (but it is still a leaked and undone version, so maybe it has some hidden bugs.). and it is faster than legend one. but it looks rather old, and features are less. it doesn't have apps like friend stream; the browser doesn't have some functions; etc. it is for CDMA phone, so simcard operations are missed. i.e. you couldn't disable simcard contacts.
for MMS, you can use MmsZap which has been included in the ROM, set the fields (you could copy them from your APN) then press "back", MmsZap will save your settings into system automatically. after this, don't forget uninstalling it, this software isn't made very well.
works:
should be all now
HTC Sync will work with with http://www.easy-share.com/1909610034/HTCSync2.0.25.exe , thank beetleman and hanserson1 who uploaded it, thank capychimp who figured out this.
if you have troubles with your gps: shutdown with gps enabled (whether if it works or not). the gps will initialize properly when next time the phone boots. or maybe you could use the libgps.so from 0.34pre (it have other problems with some device).
download:
legend: http://www.multiupload.com/EM9MJRQKKP , thanks capychimp (as always )
eris: http://www.multiupload.com/3Z6506MF9F
caution: you must read texts below before you download it.
you could download it, if, and only if, you have become a tester of these works: kernel binaries and lib binaries which are made by me. as a tester, you do not have any rights (i.e. ownership) with these files.
certainly, you could use it as before or as using any other ROM .
if you click any download link in my posts, it means that you volunteer for testing these works, to speed up the progress of development and final release.
in this situation, you will become a tester of this ROM automatically.
if you don't want to be a tester, but you want to be a user: at current, you are not allowed to download any files from my posts. you shouldn't download them, because they are just for internal tests. please wait for a public release.
Click to expand...
Click to collapse
addition:
for JIT, download this: http://forum.xda-developers.com/attachment.php?attachmentid=345213&stc=1&d=1276842897
you have to set your Home Wallpaper and Lockscreen Wallpaper to something on sdcard before the first boot with JIT enabled, (and you can set them back after that: I have tried other HTC wallpapers except default). the workaround is found by klothius, thx .
if you encountered any trouble, and want it disabled, flash this: http://forum.xda-developers.com/attachment.php?attachmentid=345214&stc=1&d=1276842897
capychimp's ROMs:
they include many useful things, (and all my ROMs are pure ports), you can find them here:
http://forum.xda-developers.com/showthread.php?t=671847
other words for rom dev:
please upgrade to .32 kernel, i have stopped my works on the .29 kernel.
the kernel someone called "eli" or "ELI" is the sanpei's one too, so if you find bugs or have some thoughts on it, plz let me know.
and you are welcome to make your own mod based on my works.
Nice work. I don't have a rooted Magic but I'm excited to see this.
Does the bluetooth problem have to do with changing the line. I've seen Cyanogen talk about this fix for some Eclair ROMs:
-n -s 115200 /dev/ttyHS0 texas 4000000 flow
to
-n -s 115200 /dev/ttyHS0 texasalt 4000000 flow
in init.sapphire.rc ?
old info:
please make sure that you have installed driver properly. adb won't work if you install Google driver as a single device driver, and if you install HTC driver as a single device driver, DiskDrive will freeze your phone (but adb works directly). a little more details: http://forum.xda-developers.com/showpost.php?p=6180261&postcount=986
our phone is "USB Composite Device", and windows has this driver included. you can try install it. after that, your PC will find new devices: one for adb (both Google and HTC's drivers will work), another for USB mass storage, and others don't have drivers (I will remove them if these two devices cause troubles) .
battery tips: you should make sure that services/apps like gps/maps could get data from internet properly. they may prevent the phone going to sleep when they think that the jobs are not done yet. and in some cases, they would forget to tell our phone "you can sleep now", so the phone would never sleep properly. if you encounter these problems, the only workaround is a reboot (as far as I know).
latest changes:
--> a new ERIS port based on latest dump*
--> fix: battery drains by BT
--> fix: no sound or freezes after using camera in footprint
--> some patches from google
--> modified: DSP driver, it looks more similar to HTC's driver now (testing)
--> a far more better superuser 2.03
info about previous versions
changes 0.36pre
market fix
rosie hacks for speed
changes 0.35pre
battery life fix
changes 0.34rc
--> speed improved with blue sun fix (if it isn't my imagination )
--> camera fix for some apps
--> libgps.so from another leak
--> modules update for OpenVPN
changes:
--> .32 kernel *
--> a new libcamera.so **
--> VGA(640x480) recording
--> rndis support (USB tethering) ***
--> default DiskDrive ****
--> others
* let us check if the sleep death which caused by sdcard operations can be fixed by the new kernel
** it was made for avoiding grayscale preview and memory leaks. it may contains bugs at current, please report if you encountered one.
*** default internet sharing won't work, I have tried it with wired tether 1.2 under linux, but I don't know how to use it under windows (my windows: Windows 7 64bit)
**** it works like a charm under linux. for windows, you may have some trouble with drivers, please read the texts under "working" section.
the eris ROM contains files from the RiverRunner(or others?)'s dump, maps from brut, superuser built from ChiansDD's sources.
Q & A:
Q: what about your others work, like bug fixes of your aosp build, your kernel, the opensource progress of your kernel?
A: i have few time these days, no big steps on ROM development.
for the aosp ROM, i build some version and test them myself, but none of them are better than my last one, since I don't have time to tweak them. but if I found a big improve in the future, I will release a new one.
for the sources of kernel, i lost some key files of my modification of kernel .29, and I was working on kernel 2.6.32 when I had some little time these days. i think that i won't work on the .29 kernel again if I don't encounter big problems on .32.
so there is no sources I can post at current. and for .29 kernel, there isn't any changes after it was released. I use the same binary file in all my ROM too as you.
Q: why .32 (next release)?
A: I hope that .32 could fix most kernel and driver bugs in previous releases. if not, .32 will still be better than .29. btw, this ROM uses .29 (as same as previous) since .32 jobs are not done yet.
Q: will you update this SenseUI ROM ?
A: I think my friend ahmgsk will make a better one for you.
so when any other ROM that are good enough appear in next 2~3 days, I will stop to update. this one just shows what we could have.
my plan is, I will work on some programming and kernel jobs, and ahmgsk will make good ROMs.
-------------------------------
xaueious said:
Nice work. I don't have a rooted Magic but I'm excited to see this.
Does the bluetooth problem have to do with changing the line. I've seen Cyanogen talk about this fix for some Eclair ROMs:
-n -s 115200 /dev/ttyHS0 texas 4000000 flow
to
-n -s 115200 /dev/ttyHS0 texasalt 4000000 flow
in init.sapphire.rc ?
Click to expand...
Click to collapse
not this one.
it's some other problems with HTC things. I don't know this problem exactly, hope others can figure out how to fix it.
but thank you also.
thank you so much, i will however wait for a confirm if the root feature works before flashing this ROM.
best 2.1 sense i've ever tried. you're the man sanpei! thanks a lot for the job!
stgeorge88 said:
best 2.1 sense i've ever tried. you're the man sanpei! thanks a lot for the job!
Click to expand...
Click to collapse
can you report what works and not for you?
It's an official HTC Sense port so it should be very smooth. But there are things that are not going to work right away since it is from the Eris. So reports are appreciated.
Em ne chance that these very drivers will work with other stable eclair roms ?
Facebook+Contacts don't sync right away, I haven't figured out a way to sync it. Might have to do it manually?
I couldn't use Titanium back up, it said I didn't have root access. Installing busybox didn't work either.
No Live Wallpapers?
Pretty much it for me. I haven't tried the camera/camcorder
WiFi works though, which is great.
Thanks a lot for having a look inside whats coming :-D things not working besides those already mentioned: GPS + all Kinds of LED's besides sync works without Problems.
capychimp said:
can you report what works and not for you?
Click to expand...
Click to collapse
BT not working. can't even turn it on
LED light either? not sure on this one.
also as reported by sanpei, the preview after taking a picture appears weird but no biggie for me since the picture is correctly recorded
overall super, super, super smooth. got one freeze when flickering around settings and a sms comes in but other than that haven't got any issue in the past ... 5 hrs.
edit1: LED not lighting up even when charging.
edit2: forgot to mention that there's no Mount USB option when plugged.
Thanks for the quick work getting a 32A port of the Eris 2.1 dump.
Some noted bugs:
1.) 3G connection does NOT work for me. It shows the 3G icon but will act as if no connection is available. WiFi works, however.
2.) LED sensors not working (as said earlier)
3.) Screen issue when taking pictures with HTC Camera (also noted)
4.) When first starting up phone on first boot, when I reach HTC Setup Wizard I get a force close on android.process.media. Doesn't seem to affect anything though.
EDIT: for Issue 4, my 3G connection issue was fixed when I flashed HeroDroid's WiFi/LED Sensor fix from his Hero port (no, LED lights still don't work).
well doneļ¼ i hope to see the screenshot pics
it is based off the eris dump. u can find screenshots in the eris forum, there's a lot of them and a video too
WOW you guys are fast. i smoked a spliff and came back..i see its here already
thanks im gonna try it right now..be back with some feedback
For a quick port, this is really quite good Sanpei. Now it's got me 100x more excited for what wonders ahmgsk will be able to cook up real soon..
MagicXB said:
For a quick port, this is really quite good Sanpei. Now it's got me 100x more excited for what wonders ahmgsk will be able to cook up real soon..
Click to expand...
Click to collapse
just finished flashing it.. "quietly brilliant"
mann i cant wait for it to start
EDIT: android.process.media got a forceclose..
I'll trying it all and post as most bug i had found
Everything works great! However, I too had a problem with 3G and WiFi after installation. But I was in a rush, so I never tried to fix it.. Turns out, it fixed itself sometime over the course of 30min.. Not sure what's up, though.
grimey01 said:
just finished flashing it.. "quietly brilliant"
mann i cant wait for it to start
EDIT: android.process.media got a forceclose..
Click to expand...
Click to collapse
nothing else went wrong so far(except what was mentioned)..this is amazing, i cant wait for the official 2.1 sense for magic
im having too much fun here loll
google earth doesnt load though..
i was really lookin forward to trying this app
UPDATE: im unable to connect to my PC.. ive tried htc sync and diskdrive both dont show up even after waiting 5 minutes..
Hi everyone
I've managed to get a fairly good working build now of FRF91 from AOSP. I was inspired mainly by both AdamG and meLIanTQ for there excellent work on both there AOSP built ROM's, so thought I'd have a go at it myself, so here is the result
I'm building this ROM to suit my own personal needs, with various little things thrown in for good measure, but it will remain 100% AOSP source. No APK's will be modified *after* the build, all customisation on my part will be done via the overlay.
THIS IS NOT A SENSE-BASED ROM
ROM Details
Built from latest AOSP source. (FRF-91 2.2-r1.1)
2.1Mb Kernel Image Size so hopefully no problems for people with Bad Blocks
Kernel Base - 2.6.32.9 configured and compiled by myself (UV Support, no OC)
Self-modded Kernel Fix to keep phone charged at 100% while plugged in (used to drop to 89% and charge) (details >here<)
ext2, ext3 and ext4 support
cifs.ko, tun.ko and openvpn
Classic A2SD+ from my original dalvik-cache mod from Rooted 2.1 Eclair for Desire (details >here<) Copies Apps, App-Private and Dalvik-Cache to SD.
A2SD Fixed to help prevent White Screen Hangs (working with ext2 and ext3 partitions, needs testing with ext4)
Latest BusyBox (1.16.2)
Rooted with latest SuperUser 2.2 apk
Massive APN List
h264 Camcorder
Latest FRF91 Google Apps
3G/H Icon Fix to display H during HSDPA connection.
Default Launcher is LauncherPro Beta
WaveSecure installed to /system/app
setcpu.txt copied to sdcard JUST incase you want to use SetCPU to ramp down the CPU Speeds to help conserve battery life (remember, no OC or UV support in kernel, but I do intend to patch UV support in future releases)
The following items have also been removed:
Facebook (Installable from Market)
Twitter (Installable from Market)
Original Android Launcher
Amazon MP3 (Installable from Market)
Whats Working (currently from what I can tell as its what I use)
Facebook Sync (including profile pictures displaying in Phone App and Message App)
WiFi
USB & WiFi Teather
Notification LED's
Camera
NO ECHO
I've also not included items such as SpareParts, or LeoParts... SpareParts and LeoParts can be had from the Market.
Please refer to the 2nd post for a breakdown of changes/fixes/known issues with the ROM
Installation
Fresh Install
I recommend you do a FULL WIPE before you install this ROM if you are coming from another ROM.
Future Upgrades
No wipe is explicitly required in order to use this ROM, however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Just to say. Whenever I release a new Update, I always just "flash over" the existing one without a Wipe and go from there. I'm building each release with this ethos in mind, as its pretty annoying having to do a Wipe on each update!
DOWNLOAD
YOU WILL NEED THE 5.xx RADIO ROM FLASHED TO USE THIS ROM - 4.xx RADIOS ARE NOT, AND WILL NOT BE SUPPORTED SORRY!!
Get the latest RADIO's >HERE<
Also, remember this is a ROM I'm making for myself and a few friends, so I will try to sort out bugs as-and-when they are found, but as I'm still learning how to do this well, it may take a little time for me to sort!
Also during the FIRST initial boot after a fresh install, it can take about 30 seconds for LauncherPro to start responding. THIS IS NORMAL. Any further reboots by yourself, or upgrades in future (without wipes) don't have this issue.
FroYo-Desire 0.4b
Thanks & Credits
st0kes for all the info and tips in the Building Android from AOSP thread.
deovferreira/Kali- for the vendors which make all of this possible.
meLIanTQ for the invaluable help when I ran into a few issues during my initial build
AdamG & meLIanTQ for there inspiration
IntersectRaven for his HAVS Kernel Modifications
Anyone and everyone else who I've forgot to mention
Want to buy me a Toastie?? Can if you want But I'm not in it for the food
Future Additions
Add support to dynamically check and change the keys binded for unlocking the phone
Current Known Issues
Auto Brightness may not be to everyones taste.
Version History & Changelog
0.4b
Kernel UV Values tweaked to 925mV min, 1225mV max.
Conservative Power Governor now set on boot. (can be changed using SetCPU)
Updated LauncherPro to latest release
0.4a
Removed HAVS Additions from Kernel - caused problems with Trackpad & Light Sensor (CM3602).
New Kernel UV-Only based on Pershoots N1 Modifications. 950mV - 1275mV (for stability)
0.4
Recompiled Kernel with HAVS Support (925mV MIN, 1250mV MAX) - Credit >IntersectRaven<
0.3
Added SIM Toolkit
Final 100% Battery Charging Modification in place (keeps battery at 100% while plugged in)
WiFi Sleep now fixed (using own method based loosely on the official Google patch)
WiFi Sleep also fixed in respect to extremely high pings and regular dropped packets still compared to being in a Woken state (pings and packet consistency will remain constant regardless of screen being on or off)
AutoBrightness now set back to original FroYo values. Sense values used in 0.2 were draining the battery and keeping the screen far too bright in dark conditions.
0.2
Re-synced against latest AOSP Release & Kernel_MSM
Further-optimised Charging functions in Kernel
Fixed button backlight (full brightness)
Fixed Notification LED
Fixed Auto-Brightness
0.1b
Re-compiled Kernel enabling "Conservative" mode for (hopefully) better battery saving! (use SetCPU to enable this)
Added fixes to try get 3G working on Orange networks (for those who are fully unlocked with latest Radio's ONLY)
Corrected the order at which kernel modules load. Also sorted out module issue with FileSystem modules loading in the proper order.
No longer clear Vendor cache from Market (causes slowdown on initial use after flashing as upgrade)
0.1a
Initial Public Release
0.1-prerelease
First Initial Build
Fixed LED's
Added Camera Profiles
Fixed Facebook Sync
Fixed Teather
i dont suppose you can tell me where i can get the kernel fix that stops the battery from draining while charging? that is a HUGE problem for me
i will flash your ROM asap but i dont have enough time atm
thanks very much for your ROM looks really good
cgrec92 said:
i dont suppose you can tell me where i can get the kernel fix that stops the battery from draining while charging? that is a HUGE problem for me
i will flash your ROM asap but i dont have enough time atm
thanks very much for your ROM looks really good
Click to expand...
Click to collapse
Updated first post with a link to the modified source file
You sir are an absolute saint
Thanks so so much
5 STARS!
very very nice work.. good job.. i love AOSP rom.. i'll try it tomorrow.. one question. the biggest problem is wifi on OD and AOSPDesire (sleep mode). wifi is working on this rom when goes to sleep? Thanks
How would we go about manually installing the kernel fix? do we flash it?
Thanks again and sorry for my ignorance
cenkaan - What exactly is the WiFi sleep problem? I go into Settings -> Wireless & Networks -> Wi-Fi Settings.
Press Menu key, choose Advanced
Set Wi-Fi sleep policy to Never... Doesn't disconnect for me, but it does run in a low-power mode.
I've noticed using something like SpareParts, has *no* effect on this setting what-so-ever. It only works for me by doing it this way.
cgrec92 - thats the source file for the battery driver which must be compiled in with the kernel from source. As far as I know, the boot.img (my kernel) is compatible with OpenDesire (used it on there myself). It is already included in DeFrost, AOSPDesire, and I think AdamG might be adding it to his future updates as he did ask me where he could obtain the mod
i use wifi policy and set to never but this is not solution for me on other AOSP mods. Thanks for the quick reply
Well I've had the desire running all night and it kept its connection But if it is an issue, please let me know what you do for the issue to show (any other apps used to manage it) and I'll see what I can do
can't wait and i'll try it now
Last question I promise
So the boot.img contains the kernel (you have modified this)
I can use your boot.img on other ROMs such as AdamG's seeing that yours is based on this?
no it's not working...full wipe and later set to never but it's not working..
-sleep mode-
Destination address 192.168.1.86
Packets sent 10
Packets received 0
Average round-trip time 0.000 ms
in the meantime rom is very nice. great job.. Pls help me.. I want to use this rom. i loved it
cgrec92 said:
Last question I promise
So the boot.img contains the kernel (you have modified this)
I can use your boot.img on other ROMs such as AdamG's seeing that yours is based on this?
Click to expand...
Click to collapse
I modified the *source* at which the kernel is compiled and built from. I then configured the base options for the kernel, compiled it, modified the various init scripts (which are supplied via the AOSP source build), and made the ramdisk, packed the boot.img... etc etc
If you wish to use this kernel on another rom (such as OpenDesire), then you will also need to copy the folder /system/lib/modules from my ROM to OpenDesire also. You will also need to manually edit /system/etc/init.d/**** script (whatever it is loading modules) or if there isn't one, create one to load ext2, ext3, ext4 and ipv6...
Bit more involving than I first made out really lol! Sorry...
cenkaan said:
no it's not working...full wipe and later set to never but it's not working..
-sleep mode-
Destination address 192.168.1.86
Packets sent 10
Packets received 0
Average round-trip time 0.000 ms
in the meantime rom is very nice. great job.. Pls help me.. I use this rom. i loved it
Click to expand...
Click to collapse
Strange indeed...
I've been reading a bit in other threads, does your WiFi MAC start with something other than 00:23?? As from what I read in AOSPDesire thread, it occurs to phones whose MAC starts with different numbers to that... Again, sorry its not working for you...
Did some digging, looks like a fault which is also apparent on other HTC devices, including the N1
http://code.google.com/p/android/issues/detail?id=9781
According to that (or so I think it makes out) it's also dependant on the make/model/type of Router which you also use...
So us Desire owners are most definitely not alone...
Ok that's enough hassle for you
Thanks so much for all your help
Fantastic developer will download your ROM as soon as i get home, thanks
thanks for the help and great rom.. and yes, what a pitty my wifi mac address is begin with 38:E7..
PaulW21781 said:
Strange indeed...
I've been reading a bit in other threads, does your WiFi MAC start with something other than 00:23?? As from what I read in AOSPDesire thread, it occurs to phones whose MAC starts with different numbers to that... Again, sorry its not working for you...
Did some digging, looks like a fault which is also apparent on other HTC devices, including the N1
http://code.google.com/p/android/issues/detail?id=9781
According to that (or so I think it makes out) it's also dependant on the make/model/type of Router which you also use...
So us Desire owners are most definitely not alone...
Click to expand...
Click to collapse
The same issue does NOT occur on any HTC ROMs so am wondering what HTC has done specifically to address the problem...
hello sorrry i'm new.... (sorry for my bad english)
in this rom is not sense installed? Can someone upload pictures.
bobo26 said:
hello sorrry i'm new.... (sorry for my bad english)
in this rom is not sense installed? Can someone upload pictures.
Click to expand...
Click to collapse
Sense is not installed, no...
Pictures - couple are in the first post of this thread (at the bottom of it)
*update*
Updated to v0.1b, enabled new "Conservative" power governor for the CPU in the Kernel. Use SetCPU to enable this in the phone itself, will hopefully improve battery life, but will have a slight effect on performance when this option is enabled.
DO NOT POST IN THIS THREAD UNTIL YOU HAVE COMPLETELY READ THIS POST AND THE FAQ.
Since jt1134 is no longer supporting his CM9 releases here on XDA and asking people to go elsewhere for support, I have decided to start building CM9 for the Infuse.
Much of the credit goes to him for doing the initial ICS bringup for Infuse, I'm working on fixing some of the things that are not yet working. Even more goes to LinuxBozo - without his CM7 work we would be nowhere.
http://d-h.st/vN1 - 06/20/2012 build
http://d-h.st/ahW - 06/27/2012 build
http://d-h.st/Pfr - 07/28/2012 build
Installation instructions-from a Gingerbread firmware with "red CWM":
Place this release and an ICS gapps release on your SD card.
Flash this ZIP in CWM
Reboot - you will get stuck at the Samsung screen
Reboot to recovery again using the three-finger salute - hold down VolUp+VolDn+Power until the device reboots, release Power after the reboot, continue holding VolUp+VolDn
Go to Mounts and Storage and format: system, data, cache
Flash this ZIP a second time, then flash gapps
Reboot and enjoy
Coming from any AOSP-based firmware with "blue CWM":
Flash this, flash gapps, wipe. That should be all you need.
What is working:
Calls
GPS
Sound
Video playback
What is partially working:
Camera (minor flakiness, but mostly working)
Car dock audio (possibly desk dock too, untested) - Some issues with ringtone playback when docked - This is native dock audio, not using the Car Dock Redirector app workaround. Thanks go to StevenHarperUK of the GT-I9100 community for reworking CM9's dock audio code to permit this to work.
Wifi - It frequently loses connection when the device is asleep. Most likely needs some SDHCI driver tweaks to match the N7000 wifi driver.
Wifi Direct - A little glitchy but mostly working with I777/N7000. Won't talk to a P7510 (Tab 10.1) though.
Bluetooth - A2DP (music) and SCO (call audio) now works. However BT power management (LPM) is currently disabled, so BT may eat your battery when on.
Not working:
TV Output - No one has gotten MHL fully working on any Samsung device yet to my knowledge. There's some promising results from the I9100 community but it's not there yet.
Known issues:
SetCPU seems to be unable to set the minimum frequency to 100 MHz. This is one of the main reasons for holding off on OC - even stock clock code isn't working quite right
Facebook contact sync has been blocked by Google in ICS - this is universal to ICS on all devices I'm aware of. Facebook got what they deserved here.
Building - Use the Source, Luke
Kernel source is at: https://github.com/teamhacksung/android_kernel_samsung_dempsey
Device repo at: https://github.com/teamhacksung/android_device_samsung_infuse4g
To build, first prep your system for a Cyanogenmod build by following the instructions at:
http://wiki.cyanogenmod.com/wiki/Building_from_source
Once you have done the first "repo sync", at the two following lines to .repo/local_manifest.xml
Code:
<project path="device/samsung/infuse4g" name="teamhacksung/android_device_samsung_infuse4g" remote="github"/>
<project path="kernel/samsung/dempsey" name="teamhacksung/android_kernel_samsung_dempsey" remote="github" />
Run "repo sync" again
Sync https://github.com/TheMuppets/proprietary_vendor_samsung/ into vendor/samsung
Drop the contents of the attached tarball into vendor/samsung
(I really need to clean that process up...)
Run:
Code:
. build/envsetup.sh && brunch infuse4g
FAQ
Q: I get weird rainbows in recovery and when my device boots? What gives?
A: This is what happens when a Gingerbread or ICS kernel is booted on a device with Froyo bootloaders. You will need to either live with the rainbows (recovery is at least partially usable with the rainbows now) or flash Gingerbread bootloaders. Stay tuned for more info on bootloader flashing.
Unfortunately, the classic "rainbow fix" we used for Gingerbread is not compatible with how video acceleration is set up in ICS. The rainbowfix will just cause the device to crash immediately on boot. (I think this is why jt was not successful with LinuxBozo's CM7 source.)
Q: I'm getting rainbows, how do I flash Gingerbread bootloaders?
Flash the bootloaders from the file attached to this post using Heimdall as follows:
Code:
heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin
DO NOT do this unless you are experiencing rainbows, and DO NOT do this until you have confirmed you can flash less dangerous stuff (like kernels) with Heimdall. If the flash fails you will hardbrick!
Thanks to LinuxBozo for confirming, way back in the days of UCKJ2, that Heimdall can safely flash bootloaders from leaks. http://forum.xda-developers.com/showthread.php?p=18539754#post18539754 - Be warned, once you do this step there is no going back. For whatever reason the Infuse won't flash dumped bootloaders, so there is no known way to return to Froyo and Rogers Gingerbread bootloaders.
Change Log
7/28/2012:
Removed 1000 MHz cpufreq step - the extra frequency step was causing all sorts of weird derpage.
Fixed 1200 MHz step (it was using the wrong PLL settings)
Moved to open source sensor HAL
7/22/2012:
Major improvements to camera flash functionality - torch is still broken but most other flash functions work
EXIF info (including rotation) is now saved. However I had to disable JPEG thumbnail generation, which slows down viewing of images in gallery
Structural changes to the repos to make things cleaner - Once two patches get merged by CM I plan on submitting Infuse for official nightlies
CPU clock handling for GPU bus frequency was changed from a policy change (min freq bumped to 200 MHz in policy, which would cause some apps to "stick" the min at 200) to a DVFS lock. Min no longer bumps up to 200 - however any time the GPU is active it'll still lock to 200 MHz.
6/27/2012:
Discovered our device has a Broadcom BT chipset - the CG2900 is NOT used for Bluetooth. BT is now fully functional other than possible power management issues
6/20/2012:
Various upstream stuff
Wifi Direct support added - partially glitchy (see OP)
Bluetooth support brought up to CM7 levels (Audio stuff is still broken)
5/27/2012:
New wifi driver from GT-N7000 Update3 source drop: Hopefully will improve wifi for those with issues
New LPM (charging while off) code from I9100
All upstream changes since last build, including lockscreen weather
5/19/2012:
Lots of upstream CM9 changes, including theme engine and customizable lockscreen
Settings->Advanced now works. mDNIE settings (tested) and HSPA+ control (untested)
A small patch that might help wifi driver loading issues, but not guaranteed (gokhanmoral reverted it within a day in his case...)
5/2/2012:
Pulled in a few wifi fixes from gokhanmoral's I9100 SiyahKernel tree. May help those who are having wifi issues.
4/23:
Fixed wifi MAC address getting set randomly on every boot
4/22:
Misc stuff from CM9 upstream
New wifi driver backported from the I9100 update4 sources and pershoot's Tab 10.1 kernel - Fixes wifi tethering!
USB tethering removed until I can make the RNDIS driver play with the new net/wireless code - not even sure if it was working to begin with.
4/19:
No more banding in recovery (thank codeworkx for this one, exact same fix as for I9100)
FFC is no longer cropped to one corner of the sensor. Full resolution support for FFC still not implemented
Various upstream changes
Very nice any idea on how to get mtd to work? Also would that improve speed ? Thx
Sent from my SGH-I997 using xda premium
Thanks for taking this on for all of us here in the xda community.
Sent from my MB865 using xda premium
The_Zodiac said:
Very nice any idea on how to get mtd to work? Also would that improve speed ? Thx
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
I believe that was primarily used to eliminate the need for Samsung's proprietary RFS/FSR modules.
It doesn't carry a speed benefit, but it's beneficial in the long run for kernel developers.
Current differences between my build and jt's last:
1) I haven't put AriesParts in yet - half of the features don't work
2) Overclock is not in yet - The overclock code from netarchy/LB is ancient and needs to be reworked. Voltage control is in there though
3) Car dock audio redirection is working, using a built-in CM9 approach instead of a separate dock audio redirector app. I had to make some changes in libaudio of aries-common to fix this. Probably some more work needs to be done here - ringtones when docked are iffy.
Great work... blindly flashing now based on developer name.
Sounds great.. I just got jt1134's build 2 installed and working..
Looking forward to seeing what you put together for us. Always great stuff coming from you!!
Entropy512 said:
Since jt1134 is no longer supporting his CM9 releases here, I have decided to start building CM9 for the Infuse.
Much of the credit goes to him for doing the initial ICS bringup for Infuse, I'm working on fixing some of the things that are not yet working.
http://d-h.st/x53 - 4/15/2012 build
Installation instructions-from a Gingerbread firmware with "red CWM":
Place this release and an ICS gapps release on your SD card.
Flash this ZIP in CWM
Reboot - you will get stuck at the Samsung screen
Reboot to recovery again using the three-finger salute - hold down VolUp+VolDn+Power until the device reboots, release Power after the reboot, continue holding VolUp+VolDn
Go to Mounts and Storage and format: system, data, cache
Flash this ZIP a second time, then flash gapps
Reboot and enjoy
What is working:
Calls
GPS
Wifi
Sound
Camera
Video playback
What is partially working:
Camera (front camera is zoomed in excessively)
Car dock audio (possibly desk dock too, untested) - Some issues with ringtone playback when docked - This is native dock audio, not using the Car Dock Redirector app workaround. Thanks go to StevenHarperUK of the GT-I9100 community for reworking CM9's dock audio code to permit this to work.
Not working:
Wifi tethering - We need far more than the HIDDEN_SSID fix CM7 required unfortunately
Bluetooth - Not working at all, not even to CM7 levels
TV Output - No one has gotten MHL fully working on any Samsung device yet to my knowledge. There's some promising results from the I9100 community but it's not there yet.
Click to expand...
Click to collapse
Are you saying that he's not building any more releases, or that he just won't be releasing them here on XDA, but on rootzwiki instead. I'm confused.
Thanks for this! Did you fix/attempt to fix the problem with music coming out of the speaker when you get a notification with headphones plugged in? That's the only thing keeping me from loving ICS, since it's preventing me from listening to music at work.
kirin0ichiban said:
Are you saying that he's not building any more releases, or that he just won't be releasing them here on XDA, but on rootzwiki instead. I'm confused.
Click to expand...
Click to collapse
I don't know what he's doing... All I know is he released his first build here but refuses to post any subsequent builds here, even though this is where all other Infuse development occurs. It's unreasonable to ask users to go to another forum just for ONE firmware, especially a forum with broken CSS stylesheets and a horrifically immature/irresponsible userbase. jt1134, imnuts, and Ezekeel are the only RW fans I've met that weren't complete douchebags and had technical skills to back up their bravado. Others think it's "kewl" to tell users to flash bootloaders all the time and then laugh at them if they hardbrick.
Frooty said:
Thanks for this! Did you fix/attempt to fix the problem with music coming out of the speaker when you get a notification with headphones plugged in? That's the only thing keeping me from loving ICS, since it's preventing me from listening to music at work.
Click to expand...
Click to collapse
Not yet... I'm just starting to mess with libaudio.
Awesome finally in the Dev section thanks Entropy!
Sent from my SGH-I997 using xda premium
kirin0ichiban said:
Are you saying that he's not building any more releases, or that he just won't be releasing them here on XDA, but on rootzwiki instead. I'm confused.
Click to expand...
Click to collapse
1st must you quote the entire op?
Yes and no...yes jt is still building...no he is not posting on XDA...jt prefer the rootzwiki site that's where he is posting....
Check or Hold??
Entropy512 said:
I don't know what he's doing... All I know is he released his first build here but refuses to post any subsequent builds here, even though this is where all other Infuse development occurs. It's unreasonable to ask users to go to another forum just for ONE firmware, especially a forum with broken CSS stylesheets and a horrifically immature/irresponsible userbase. jt1134, imnuts, and Ezekeel are the only RW fans I've met that weren't complete douchebags and had technical skills to back up their bravado. Others think it's "kewl" to tell users to flash bootloaders all the time and then laugh at them if they hardbrick.
Not yet... I'm just starting to mess with libaudio.
Click to expand...
Click to collapse
Alright, well thanks for the quick reply. I didn't/don't know whats going on either. I'll just continue to monitor both threads and eventually things will become clearer on what he's doing. Great work on the ROM by the way! Keep it up.
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
bigjoe2675 said:
1st must you quote the entire op?
Yes and no...yes jt is still building...no he is not posting on XDA...jt prefer the rootzwiki site that's where he is posting....
Check or Hold??
Click to expand...
Click to collapse
Obviously I needed to quote the first OP, because that where my question originated from. And thanks for giving me the information that I was basing my question on, I know he's posting his builds on Rootzwiki, and has several threads opened up for his builds where everyone is saying something different about what he'll be doing with his releases.
He and I clearly also have differing opinions on how to go forward. My opinion - fix what's broke until you hit something insurmountable (like fully working Bluetooth on CM7).
Then add shiny destabilizing features like overclocking...
kirin0ichiban said:
Alright, well thanks for the quick reply. I didn't/don't know whats going on either. I'll just continue to monitor both threads and eventually things will become clearer on what he's doing. Great work on the ROM by the way! Keep it up.
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
Obviously I needed to quote the first OP, because that where my question originated from. And thanks for giving me the information that I was basing my question on, I know he's posting his builds on Rootzwiki, and has several threads opened up for his builds where everyone is saying something different about what he'll be doing with his releases.
Click to expand...
Click to collapse
No need to be rude to mister Joe he was only trying to help!
I'm glad its finally on XDA makes it easier to know when an update is since I only check this site
Sent from my SGH-I997 using xda premium
kirin0ichiban said:
obviously I needed to quote the first OP, because that where my question originated from. And thanks for giving me the information that I was basing my question on, I know he's posting his builds on Rootzwiki, and has several threads opened up for his builds where everyone is saying something different about what he'll be doing with his releases.
Click to expand...
Click to collapse
Actually you didn't but YW for clearing up your confusions....
Runs beautifully as advertised!
I spoke with Entropy.. I would like everyone to take note:
Your phone is lying to you when it says you are on H+ all the time. That would kill your battery. It will jump to H and 3G all the time. CM9 does not display H+, only H.
I found Alarm Free (HD) does the same thing as Touchwiz Clock (Alarm, Stopwatch, and Countdown). I rely on Touchwiz clock at work for testing devices times and at home for timing punishments and waking up in the morning... I felt this was important to mention.
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?