Database Users

Elelinux-7.0.0-Hero-v2.0 - issues

I am writing on this thread as i still cannot add to the development thread yet
I am using Elelinux-7.0.0-Hero-v2.0. Thanks Ele for a great rom.
So far the only problem i have had is once the unlock screen went invisible on me.
I had to use the patch which worked fine. no black screen. everything else works great so far.
Just trying to contribute to the developers what i can to help.
Any one else has any issue yet.
Elelinux-7.0.0-Hero-v2.0
RADIO VERSION:63.18.55.06SU_6.35.17.03
Kernel: Herokernel-12a

I've had the same issue with the lockscreen but like yourself it was a once off.
Generally the ROM is great (however, this is the first ROM that I've flashed to my hero)
The only other issue im getting is with linking facebook with my contacts; for some reason FB keeps crashing. But keep in mind that I'm a retard in comparison to what you lads know about custom roms etc..... but slowly learning!
Sent from my Hero using XDA App

same problems
I have had the same problems as you. lock screen went invisible a couple of times. and my facebook does not work quite right.
Apart from that has been very stable. no problems or reboots. works great.
Running gingerbread with honeycomb theme on my hero. running at 691mhz is well good.
I have got widgets running on every screen to.
Elelinux RC4 version 7.0 V2.0
kernel 12a
691mhz
clockworkmod.
Thanks Ele for a great rom

After installed 2.0 patch, I still get blank screen (wall paper ok, no any widgets).
The only way to solve is restart
Any thing wrong with my installation? (same spec as above post)

The Bug seems to affect some phones and not others. Might be due to different hardware but not sure.
I am a network engineer. Not a developer.
There is a patch that fixes the black screen bug which might help. You might have to delete dalvik cache first though. But as said not a developer.
I just wanted to try some different roms and loaded cronos rom yesterday and is very good. So running that at the moment.
It is really fast and stable. The fastest i have used so far. But i have not tested everything yet like GPS. But admit i am becoming a cronos fan.
Cheers.
P.s i always backup my phone first and do a complete wipe before trying a new rom. Otherwise could get problems.
I use clockwork mod.

Unfortunately the bug your getting with black screens, invisible menus etc.. is an aosp bug that affects some devices which Google are unable to fix, if you had read through the thread you would have seen this. Ele is working hard on a fix for this but as CM no longer support the hero, its unlikely many cm7 roms will see many updates.
Sent from my HTC Hero using XDA App

Everyone is hoping that Google will fix the memleak and invisible manus problem. To fix it, one needs to undersatand the big picture on how these things are managed. I think it can be done only by experienced coder.

It's a real shame. i love gingerbread and did not want to go back to 2.1 or 2.2.
But might have to if they do not fix it.
I know Ele is working hard on a fix. using his rom at the moment. Was using cronos. But suddenly started getting random reboots and battery started only lasting a few hours and could not find out why.
Thanks to all devs and help.

Elelinux 7.0 v2.1 GPS reboot issue
Hi all,
I found Elelinux 7.0 v2.1 to be almost perfect.
The only major issue so far for me is that when running applications such as sportstracker that use GPS and are running in the background, that as soon as the GPS connection is lost (for whatever reason) the phone always seems to crash.
I wonder whether anyone else has seen this issue and whether there's a way to investigate it.
E.g. is it possible ot redirect logcat to the sdcard and then analyze the log file?
Regards,
MJ

Her0 V2.1 - USB problem
This is a weird one...
I flashed to Elelinux 's fab 2.1 the usual way....
I booted into the ClockworkMod Recovery V2.5.0.7
-- wipe cache partition
-- Advanced - Wipe Dalvik Cache
-- reboot
Then again within Clockwork Recovery I choose 'Install zip from sdcard'
I select the Hero rom and it flashes perfectly...
Now the problem ----> I cant get the usb port working to enable transfer of files?
When the phone boots up it shows 'preparing sd card'
Then when i connect usb lead to pc it shows 'usb connected'
When i then pull the screen down, i see 'usb connected - select to copy files to/from your computer'
When i select that tab, it just crashes back to the home page?
I see the icon at the top of the screen but when i pull down the screen and select as above, it crashes back to home screen again?
In settings, i have both USB debugging and USB debugging notify - all enabled.
Can anyone provide a solution to this issue for me..
thank you

The only way around this problem i think is to mount usb storage from recovery.
Sent from my HTC Hero using XDA App

Is CM7 7.0.2 fully functional ?

Hi,
I spotted an Ebay Dealer who sells Blades with Clockwork/CM7 preinstalled. It's version 7.0.2 and 7.0.3.
Since I don't like rooting/ flashing my phone (too risky) I would have to stick with this version permanently.
So my question is: Are these versions of CM7 fully functional/ completely bug free ?
THX

Well if it has 7.02 it's probably already rooted.
And 7.02 is far from bug free, only the latest nightlie N9x onwards are what I'd consider stable.
It's not risky if you follow the instructions and just be careful and backup.

Well I'm planning to get either the Blade with CM7 from Ebay or a Motorola Defy with regular 2.2 Froyo...
However the Defy cost about 80$ more and it doesn't have any andvantages over the Blade that I consider important.
So the only question is wether the blade is gonna be a buggy annoying unfinished experience with Cyanomod...
What do you mean with "far from bug free" ? Are there issues in daily use or just a few minor bugs ? The Defy also has some bugs in stock froyo...

I mean there were issues with Accelerometer lag, battery drain due to dialer, reboots while charging on USB, Proximity Sensor's not working etc. but these were mainly present on the stable builds i.e. 7.0, 7.0.2, 7.0.3. But they've been cured in subsequent nightlies.
See here: http://code.google.com/p/cyanogenmo...work+Owner+Summary+Stars+Priority&cells=tiles
But now all of these bugs are fixed. The main 'bug' that remains is that the FM Radio isn't working. But a patch has been submitted to rectify that. After that, it seems everything is fully functioning.
For me CM7 N98 works perfectly, I use it for daily use. Battery life is good, it's stable and quick.

So let's assume the phone comes rooted and with CM 7 7.0.3.
Could I easily update to the latest nightly build 102 ? What would be the necessary steps to do so ?
*edit*
Is the following correct ???
As the Blade comes with CM7 and Clockword preinstalled I only have to install the Rom Manager (probably also included) and give it root rights. This would also show me if the phone is rooted (which according to the sellers description it is). Next I can easily choose a nightly build in the ROM MANAGER and install it with a single click...
How long would this process take (so that I don't panic) ? Is there a risk of bricking the phone using only the ROM MANAGER method ?

Very easily.
Begin by placing the latest build & the 'Gapps' package on the SD Card.
Go into recovery via ROM Manager or Power on while holding the Vol+ button.
Then once you're in recovery scroll using the Vol- and Vol+ buttons and use the Home Key as enter. Select 'Backup And Restore' and hit 'Backup'. This is just precaution.
Then Press Back and hit Wipe/Factory Reset. Then scroll down to mounts and storage hit home and then 'format system'.
Then go back and choose 'Install Zip from SD Card', scroll down to the ROM and press home. It will then flash it. Press reboot now.
Let it boot up.
Hold the Power button and hit recovery. Do the same steps you did to flash the ROM to flash the Gapps package.
Reboot.
Now setup your phone as you would normally.

Thanks, I assume Google Apps are optional.
Also is there any good thread on overclocking the Blade ? Would it make sense to oc it for daily internet/ app use (no games) ? Is cpu overclocking bound to gpu overclocking and would the cpu's function to automatically shutdown when idle suffer from oc ?
One last question:
You said to wipe the phone in clockwork recovery: Is that step necessary or just to avoid possible problems ?

That Gapps package has the Google apps that are required for the Market and stuff so I'd definitely install it.
Not really, it's not worth the loss in battery life. There are no noticeable benefits. BTW CM7 has a built in overclock feature so you can try it, it's under Settings > Cyanogenmod > Performance > CPU.
It's necessary since there have been a lot of changes since 7.0.3.

Ah ok, I thought Gapps were actually Google Market Apps, it's the proprietary google software apparently.
Will ask back if something funny happens during update... thx so far...

No Problem.

had lite'ning 1.4, updated to 6.1, now wifi issues

ok basically i bought the phone second hand with lite'ning 1.4 on it and the wifi worked perfectly ok all the time. Since it was very old i updated it to 6.1. ever since then I have had issues with the wifi. it will connect perfectly fine to the router but i have no connectivity from it, nothing will get any net access at all. This is also not 100% of the time, its MOST of the time but not all, i do have moments where it does work fine. very very odd.
I have since tried updating the kernel to ninpho 2.1.3 from the 2.0.5 that comes with lite'ning 6.1, but that made no difference.
Someone suggested i try a wifi fix app from the market so i downloaded "FXR wifi fix and rescue" and ran that. It ran ok, wiped all my wifi settings and i restarted, but it has not solved the problem at all.
i find it very very odd since if it was a problem with the kernel OR the rom then everyone would surely have exactly the same problem. I know some people report wifi issues but most dont seem to.
anyone have any other ideas?

The odd thing is that it worked before the update. That means that it will most likely be software related.
You could try flashing something totally different like MIUI or CM. They provide kernels too, so this might resolve it, if your kernel and rom don't "like each other". This usually shouldn't happen, but updates breaking wifi shouldn't too. So it might be worth a try.
Sent from my GT-I9100 using XDA App

if i went to something completely different i assume i would have to factory reset the phone to wipe it first? (or factory reset it AFTER installing the new rom?)
was trying to avoid wiping it as i dont want to spend endless hours setting up everything again. i have backed it up with the free titanium but id still like to not have to find out whether the restore actually puts everything back properly
its very odd as its not completely broken, sometimes it does actually work, and it always connects to the router itself without any problem.

Probably wrong modem for you, flash another one. You can find modems in the developement section.

ok thanks I will have a look at that. It is currently on XXKH3 which is what came with lite'ning 6.1. i am confused though, all SGS2 hardware is identical so if this modem in 6.1 is causing this issue, wouldnt it affect every sgs2 that uses that modem?
I found the "shipped modem collection" post in the original development thread so have asked in there which modem i should try.
ok apparently i should try XXKI3. for o2 UK provider.
although i have now read that wifi is not managed by modem but by kernel only. if this is true then modem will not help me

Well, if the wifi is not managed by the modem, try what I proposed you earlier. The simplest would be to flash CM. Make a backup of your current rom, then do a full wipe and install CM.
As for your data:
1. Titanium backup restores your apps with their data (if you wish). That means that, for example, your games will keep their saves, other apps their settings and so on.
2. Assuming that you have a google-account, you don't have to worry about your contacts, calender,... Just sync it before you flash.
3. The backup you make in CWM will backup everything in case CM doesn't work for you.
In case it does work and you'll want to keep it, the other two other parts of your backup will minimize the remaining work. Note that you shouldn't restore "standard"-apps like the media-player or the SMS-app if titanium backup tells you that the app is not currently installed on your fresh CM. This means that CM uses it's own media player or SMS app. It could lead into problems to mix TouchWiz apps with CM.
A side-note:
Don't use the "stable" version. It had more bugs than expected and they made it a RC again. However, it is still in the stable folder. Get the latest nightly.
Sent from my GT-I9100 using XDA App

yep i think it is kernel. just noticed that 1.4 had cf-root, 6.1 had ninph 2.0.5 and i then tried ninph 2.1.3 and both ninph's have had the issue. i just tried speedmod k2-13 as i already had that downloaded and so far the wifi has been ok so hopefully thats it fixed. i guess it was something to do with ninph (i am thinking that because i have it set to sleep the wifi when the screen is off that somehow ninph is not handling this properly).
possibly one good thing to come of it all, ive updated the modem to KI3 which is supposedly the best one for o2 UK so i may even save more battery and speedmod is meant to be really good for battery too. I still have lite'ning on it at the moment.
i might have a look at CM anyway but i do kinda like lite'ning (although i havent actually used anything else since the phone came with it!)
also need to look at wakelocks to see if i can save some more, although not sure how i go about 'fixing' them at the moment

The choice between CM, MIUI and the stock mods is the choice between three different UI's.
I've had all three of them for some time. As you got CWM, you can just create a backup and do a sightseeing tour through the world of custom roms. Believe me, it's absolutely worth it. To get an idea of the main differences, I've written a short overview for you:
Stock mods use Samsung's TouchWiz. The default user interface that you get when buying a Samsung Android phone. So it mostly looks and "feels" the same and you can't do much about it.
CyanogenMod gives you the pure Android user interface. It's the closest to the Nexus phones by google, but gives you some extras. It is much more customizable than stock roms. It's sleek and fast.
MIUI is a whole different story. They're "Redefining Android". I think calling MIUI an "Android custom rom" is an understatement. It's an entire OS. The result of putting the best from iOS and Android into one powerful OS. It adds tons of useful(!) features. If you've ever used Windows Phone 7 or an iPhone, you know what a big step forwards Android is when it comes to features. Switching from Android to MIUI is just like that. There is just so much more. It is BY FAR the most customizable Android you can get.
Wow. If I look at how long the texts are, I see that I'm pretty biased. :O
Well maybe because I've switched so often between them. The stock roms had no chance, because after I used one of the others I found out that TouchWiz doesn't cut it anymore. I hate how "iPhone-ish" MIUI is, but if I flash CyanogenMod I just miss so much. Giving you a list of what MIUI adds would be another long post of this length.
Sent from my GT-I9100 using XDA App

cool thanks will have a look at MIUI at some point.
spoke too soon earlier, the wifi is maybe slightly better on this speedmod kernel BUT when i wake the phone from sleep, it takes about 30 seconds before i can connect to the net with anything. the phone connects to the wifi straight away, but i have no connectivity for a good 30 seconds and then it starts working. (its not the router, i am getting a connection and an IP pretty much as soon as i wake the phone). also the 30 seconds or so only STARTS once i try to connect to something. if i wake the phone and do something that does not want net access for a few mins and THEN try to get on the net via wifi (which shows as connected the entire time) then again i have to wait about 30 seconds from when it first tries to connect before it will start working.

ok slightly confused again.
I have lite'ning 6.1, speedmod k2-13 kernel and XXKI3 modem. I am trying to get cwm installed so i can make a full backup image of the entire phone while i try to sort out the wifi issues. i downloaded rom manager from market, and selected the firstion option in the app 'flash clockworkmod recovery'. it brings up a menu saying 'confirm phone model' with AT&T galaxy S2, a coulpe of i9000s and a plain "Samsung Galaxy S2" which is the one i selected. it downloads something and says successfully downloaded clockwork mod recovery.
i then choose reboot into recovery. when rebooting it attemps to install something but then says "failed to verify whole-file signature" and aborts. so im just stuck with the standard recovery instead.
so now im confused, have i missed something?

Ehhhhm, you don't need to do it.
Have a look at the features of the speed-mod-kernel:
Current features:
Root and CWM:
- Automatically installs root (su)
- CWM 4.0.1.5 recovery
It already installs it right away.
Just in case you messed something up. You should flash the kernel again.
Besides that you don't need the RomManager at all. Just shut your phone down and boot into the recovery with the key-combo. Create and restore backups from there.
Sent from my GT-I9100 using XDA App

Low memory? Random reboots? Battery?

a) Random reboots. We've all experienced them; Mine seem to come up quite often, no matter what rom I have installed. Whether it be CM7, CM9, MIUI, etc... it usually happens after returning from "sleep mode" (locking the screen)
b) Also, is there a way to make the nook run SMOOTH (for christ's sake...)??
I've tried V6 supercharger, and I haven't felt that much of a difference.
As for specs, I have my nook overclocked to 1200mhz, with the governor on "interactivex".
c) BATTERY LIFE. I've heard people using there nooks for quite a long period of time before needing to recharge.. is there any trick to this? I'm getting 3-5 hours of use on a normal day. It's supposed to have the same battery as the Nook Tablet... and same screen resolution.. sigh..
solutions anyone?
Thanks in advance.

Well, I'm currently running the MiRage rom and it runs fine. No random reboots. Do you use a time/weather widget? Sometimes these can cause occasional problems. I wouuld think it might be an app that is causing these problems, as I've used many roms on my nook, including MIUI, without the problems you are describing.
As for low battery, how high is your display brightness set? I have found that to be a big battery hog. Or again, it could be due to certain apps.
I would also suggest doing a clean install of your rom - wipe and reformat. If you are not sure of the procedure, please post.
My nook gets very heavy use on a daily basis and I get a full day after a nightly charge. Look for a thread in the general section for the nook by mr72 - a guide for CM 7.10 setup. Lots of useful info there.
Sent from my NookColor using xda premium

How many updates have you installed on your nook color? I have found that you should only update a few times before you will start seeing problems with your cyanogenMod builds.
CyanogenMod uses modified kernels so you should wipe both your data and your caches after a few updates to keep from corrupting your kernel base. Make sure to backup first with a nandroid backup so you can restore your apps and settings afterwards. Constantly re-flashing and updating your cyanogenmod builds just leads to problems without doing a full data wipe once and awhile. ALWAYS wipe your dalvik caches on each update.
The easiest way to wipe both your data and caches is to use clockworkmod in your included ROM manager.
~~~~~~~~~~~~~~~~
I have not experienced any of the issues you are claiming with the latest stable of cyanogenMod 7.2 on the nook color, but I make it a issue with myself to wipe both the data and the caches on the eMMC of my nook color , which is the way I am using cyanogenMod, after a couple of updates. YOU will especially will have to wipe both the data and caches when you upgrade from gingerbread ported versions of cyanogenMod to the ICS versions, those kernels are way modified. I have worked on some through the github.

I tried many CM7 nightlies and newer CM9 also.
Very rarely to have a restart (freeze up are bit more often) and battery lasts for 9–10 hours with full use.
Something might be wrong with your hardware or no good install of Roms.
How long do you have it? Did you get it new or used?
Produced by NookColor at ICS 4.0.4

Upgrading Sammy 4.1.2 to Sammy 4.3 and kind of dual booting

OK, as you know an official 4.3 is out and after Wanam got a NON-WIPE version based on it the temptation was too big.
I was running for a very long time a dual-boot system based initially on Siyah kernel and lately on Googy-Max kernel, and the main ROM was a Sammy 4.1.2 (which also happens to be quite customized, with a lot of bloatware removed and the rest frozen in Titanium or Greenified; also using Apex as launcher and DialerEx as dialer).
FIRST STEP - make a good EFS backups (as in save it in more than in one place) - I was running with an older EMF1 modem (which I found to be VERY power-efficient for my needs) using the old EFS format, (for the moment) it is said that 4.3 Sammy ROMs will need the newer EFS format and will upgrade you (probably by installing the new modem). Also in this step it is a good idea to backup your ROM(s) from recovery (and direct that to the external SD). It is also a good idea to have around "just in case" the kernel(s) and whatever else you think you might need to restore things in case something goes wrong. Also having a Titanium Backup of your LATEST stuff on the external SD is a very good idea.
2nd STEP - get a NON-WIPE ROM based on the Sammy 4.3 - I used GT-I9300_WanamLite.XXUGMJ9.V7.2.NO-WIPE.zip
3rd STEP (optional stuff) - in case you want to keep your old Sammy configuration and/or dual-boot - copy (in the special dual-boot recovery) your Sammy main ROM on both slots - I normally have my main 4.1.2 as the 2nd ROM (which is set as default = primary), and I do all the tests on the 1st ROM (mostly since some aroma installers work best on 1st ROM). So I kept my main 4.1.2 as the 2nd ROM and I made a copy of it to 1st ROM.
4th STEP - install the NON-WIPE 4.3 (in my case from Philz Recovery over the 1st ROM as an upgrade). It worked pretty well but it took a rather long time (10+ minutes). At the end I encountered 2 minor problems - during the upgrade of the Sammy Calendar items it kind of remained forever there (with the circle rotating but after 10 more minutes I decided it was a little too much and I forced a power off by keeping the power button pressed 7-9 seconds; after restart it went over OK; at a later time I got a message that media scanner crashed but after updates it seems OK).
5th STEP - update everything in the new ROM and configure it to your taste. IMHO you MUST try Xposed + Wanam Xposed - that one is great.
After a large number of updates, restarts, Wanam-related configurations + obligatory restarts and Greenify-related stuff I got EVERYTHING to work PERFECTLY in the new 4.3, so a few impressions on that:
- things are definitely a little snappier in 4.3
- the new settings are kind of different but not that much
- for me it was a major point that EVERYTHING was kept/upgraded - all my contacts were still there (with the custom pictures), Sammy calendar items and so on; the one thing that I had to restore manually were the custom ringtones;
- this version does not repartition and does not change your bootloader/recovery, but the Sammy official one is said to do that and to replace your bootloader; the free space is kind of low in /system without the repartition but IMHO is still perfectly usable;
- battery life over night looks OK for a Sammy kernel but is a far cry from what I was getting with custom kernels in 4.1.2 - about 8% discharge over night vs. only about 2%
- the best two new features for me - the torchlight in lockscreen (with volume up 2 seconds) and the 3-tap-zoom (standard Android stuff since 4.2.x)
- there is a very tiny delay when unlocking - some people claimed it was like 2 seconds but they are delusional, it is well under 0.5 seconds and I am not bothered by that AT ALL; EDIT: OK, I have now seen a few times something clearly longer than one second, it seems to be a little variable, I have yet to determine on what
- what bothers me a little is the PIN-unlock dialpad - I have seen the same in CM/AOSP before and it is kind of ultra-laggy (and pretty small) compared to the 4.1.2 Sammy PIN-unlock dialpad; on the other hand the 4.3 Sammy keyboard feels a lot better/faster than the ported Note2 keyboard that I am using in 4.1.2 :good:
- camera also works OK, the new Sammy media player is also OK (but voice commands are tricky on it); for the moment the lockscreen for me is "stuck" in the 'safe mode" enforced by Sammsung by some setting of policy; for me is not a problem but I would like to know more about this.
KIND OF DUAL-BOOTING
Googy-Max is not yet fully dual-booting the new Sammy 4.3 (but IMHO is VERY close - 4.3 boots and seems to be seen over USB, only the video driver is not correctly initialized), but there still is a way to get a kind of dual-booting - it is no longer a 2-click 10-seconds thing but instead a 10-click 50-seconds thing but still works - I have Googy-Max-Kernel_1.7.8_CWM.zip and Archi_Flasher_Repacked_Wanam_Stock_XXUGMJ9_Kernel.zip in the root of the internal SD and I only need to restart to recovery and write the 6-8 MB of kernel; when the Sammy stock 4.3 is written it automatically starts the 1st (standard) ROM = 4.3, when Googy-Max is written it was set as default for the 2nd ROM so it goes automatically to my old 4.1.2
REMEMBER - everything on internal SD is the new "4.2.x and newer" style - in 4.3 it goes to /data/media/0 and in 4.1.2 it goes to /data/media. Eventually specific configuration for that must be done in Philz Recovery and Titanium Backup.
I am still doing some battery tests over the next days - this night I want to test if the new BUUGMJ3 modem is part of the power-consumption differences so I will test it in the old 4.1.2 and with Googy-Max. There are many other small things to test, I will eventually add those here once done.
EDIT: A BETTER KERNEL FIXES THE LAGS
I have now tried a beta kernel (different than the stock one) and the lags are gone, tomorrow I will report on battery life.
http://yank555-lu.net/viewtopic.php?p=4594#p4594
Also it might not be impossible that a true dual-boot Googy Max might be ready after the weekend or so.

Quite confuse here
How you dual boot for stock 4.3 as primary Rom & stock 4.1.2 as secondary Rom?
I know latest googy kernel not supporting stock 4.3 yet
Sent from my GT-I9300 using XDA Premium 4 mobile app

MsElise said:
Quite confuse here
How you dual boot for stock 4.3 as primary Rom & stock 4.1.2 as secondary Rom?
I know latest googy kernel not supporting stock 4.3 yet
...
Click to expand...
Click to collapse
It is not the very easy "2-click 10-seconds" dual-boot with a special dual-boot kernel, it is the more complex "10-click 50-seconds" dual-boot where you have two kernels as zip that you can install from recovery (it still takes like 10 seconds to write the kernel but since you must boot in recovery you are going to lose closer to 50 seconds when you decide to switch) - the stock Sammy 4.3 kernel (pre-rooted and processed by Wanam and repackaged by Archi) will always boot to the 1st ROM, while the existing Googy-Max (1.7.8 as we speak) will go to whatever is set as default for it - and in my case I have Sammy 4.1.2 set as default in 2nd ROM slot.

A BETTER KERNEL FIXES THE LAGS
I have now tried a beta kernel (different than the stock one) and the lags are gone, tomorrow I will report on battery life.
http://yank555-lu.net/viewtopic.php?p=4594#p4594
Remember that if you encounter root-related problems (or eventually you are left at the Samsung boot logo) you probably need to write this from your recovery:
http://download.chainfire.eu/345/
Also it might not be impossible that a true dual-boot Googy Max might be ready after the weekend or so.

xclub_101 said:
...
I have now tried a beta kernel (different than the stock one) and the lags are gone, tomorrow I will report on battery life.
...
Click to expand...
Click to collapse
OK, I am now really impressed with the latest yank.lu kernel :good:
With the default (zzmove) governor and almost all default settings from the beta2+ aroma (except no quick charge and only 400 MB zram) I got about 1% over night, I am now keeping this configuration for extra testing for a few more days :good:

can run the stock rom 4.1.2 and **** rom with 4.3 ????? :fingers-crossed: