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.
Related
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
Hello.
This is where you can look at the tutorial and get the files to install if you feel like jumping into it ...
ICS Step by step and files
Note: if you do flash this and it hangs at the boot screen, pull the battery and flash it again and it should work. Some have had to do it 3 times.
I take no credit for this ROM and full props go to the developers of the above post and all those working to make this happen.
First the look and feel of ICS is nothing short of superb. The speed as of now is similar to all the other ROMS I have tried with a little chop here and there but nothing major.
Yes lots of little issues and items that do not work like the camera and GPS but not a huge deal for me so I am willing to stick to it.
Battery so far is decent. 13 hours and 43 min. on the first charge to calibrate and sitting at 24% still. This included allot of playing with the phone and reboots to test jigs
As for the issues that are somewhat bothersome, they include the following.
1. No home or search button. I know same as usual when installing an i9000 ROM but the key mappings from the GB ROMS does not work.
2. BLN (issue all around) will remain lit until you wake the phone to get the notification.
3. They had to do some funky stuff to get 3G to work so it lags to start. Not a huge deal cause it does start and remain working.
I will be continuing to use this ROM and hopefully everything will be working soon (these guys are flying. Also I have been told that the folks over at Glitch are already working on the kernels for the ICS port so that is promising as well.
If there are any other out there running this on our phone chime in with your thoughts or fixes if you have any.
Thanx
Bucky
Thanks for starting this thread. Can't wait to hear about your progress.
Alpha 7
Hey here is the update ...
Installed the Alpha 7 update today and I have to say this rom is fantastic.
1. Camera is fixed and works like a charm.
2. GPS locked in seconds and accurate indoors!! Big improvment over all other roms I have used.
3. HW Acceleration is fixed and working from what I can tell
4. You Tube is fixed and can watch video
Still on the not working list
1. Can not plug the phone in while off as it just restarts. this is a work in progress and known issue
2. Can not record video
3. Will not read a SIM card for contacts and so on (thank god for Google sync)
4. Still no home or search buttons (I think I may need to work on that on myself unless a kernel is released)
SO my review so far ...
No real issues with the general use of the phone. Text, phone, email and web are solid, I have installed apps from the market with no issues and not one FC yet. Battery life is good and nothing is taking over. I have been able to use the phone all day and still have lots left over before going to bed and plugging in. I have not been through a full battery as of yet but that is what I am working on now.
Memory - Last I looked I had 174MB of memory remaining which is the highest I have seen.
ICS is really smooth and fast while moving around. I am going to continue to play with it and report back here for everyone.
I don't use a whole lot of apps so there won't be much regarding those.
Thanx for stopping by and I will post pics when I can.
Bucky
Nevermind
Sent from my SCH-I500 using XDA App
Thanks for the update. From your review, it sounds like an awesome rom. Can't wait to try it but need them to fix the video recording first. Although I might just cave and try it out just to see what the fuss is all about
Can always restore my current setup... lol.
Update ...
been getting the SOD today and not sure why, I mentioned above that the HW acceleration was working, I misunderstood and it is not fully working yet.
I found that the system partition is very small. There was an update which required copying libs and there was not enough space left to do this (2MB). Not too sure if this is due to coming from MIUI or just a ROM issue.
Alpha 8 was released but had quite a few issues so not flashing that one.
Daily use has been great so far (except for the SOD) with no reception or data issues.
I am still working on the home and search buttons but I think that will get fixed with a kernel update. I tried the keymap file but these buttons do not even register in recovery so I get nothing in the ROM either.
More to come ...
Haven't tried this (likely won't as I need the phone for work) but buck have you tried the manual key fix - some directions in our thread on putting on Darkys 10.3.
Sent from T959D running Miui
Yup been there done that no go
Sent from my GT-I9000 using XDA App
Hey buck , was doing some searching in teamhacksung's thread about their ICS port, and someone suggested to change the following and then the key mapping for our phones will work properly. Not sure if the file system is the same for both, but definitely a bit of info if it isn't!
All you have to do is change this part on**arch/arm/mach-s5pv210/mach-aries.c*
*Original**(line 1216~1221)
static const int touch_keypad_code[] = {
#if defined (CONFIG_SAMSUNG_GALAXYS) || defined (CONFIG_SAMSUNG_GALAXYSB)
KEY_MENU,
KEY_BACK,
*0,*
*0*
----------------------------------------------------------------------------*
*Edited*
static const int touch_keypad_code[] = {
#if defined (CONFIG_SAMSUNG_GALAXYS) || defined (CONFIG_SAMSUNG_GALAXYSB)
KEY_MENU,
KEY_BACK,
*KEY_HOME,*
*KEY_SEARCH*
Sent from my GT-I9000 (T959 mod) using XDA App
Thank for the input. After flashing bata 1 all the buttons are working. More to come: )
Sent from my GT-I9000 using XDA App
Hey, have a telus fascinate too. Know how to flash and all that fun stuff. Just don't fully follow where you make the changes for key mapping...if you could just guide me in the right direction, I can figure the rest out...
changes in the kernel zip? the beta zip? after flashing? something completely different?
thanks a lot!
There are no changes to be made with this ROM, they are built in. Just flash and all good.
I will post update tonight after work.
Sent from my GT-I9000 using XDA App
yeah sorry realized that immediately after posting / flashing to the new rom.
have you tried out BT audio? I can connect to different devices but audio won't stream
havoksupertwit said:
yeah sorry realized that immediately after posting / flashing to the new rom.
have you tried out BT audio? I can connect to different devices but audio won't stream
Click to expand...
Click to collapse
There are allot of BT related posts in the QA. I personally do not use any BT but I do have a headset that I will try when I get home.
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.
bucknetbucky said:
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.
Click to expand...
Click to collapse
Calibrated my phone this morning. Heavy use today configuring everything but about 52% now (sooo 5 hours or use?)
Why god! Whhyyy!!
bucknetbucky said:
There are allot of BT related posts in the QA. I personally do not use any BT but I do have a headset that I will try when I get home.
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.
Click to expand...
Click to collapse
AT LEAST YOU GUYS HAVE IT RUNNING!!
I am having a hell of a time trying to get it to work. I have tried so many different ways to get it up and running but no luck.
I've tried installing it from MIUI 3 times but all I get when trying to boot into ICS for the first time is a Black Screen after the FuguMod boot screen.
The funny thing is that the 4 soft buttons at the bottom light up still.
So I then decided to try the JVT way:
-Flashed JVT DARKYROM (ODIN)
-Lagfix OFF
-FULL WIPEs (factory reset, cache, dalvik)
-FLASHED CM7.1 STABLE
-FULL WIPEs (factory reset, cache, dalvik)
-Flash ICS BETA1
-Flash kernel
-FOR THE SECOND TIME:
-Flash ICS BETA1 AGAIN
-Flash kernel AGAIN
Same issue, black screen after the FuguMod boot screen, buttons still light up.
So i tried a couple more times in a few different ways based off what I have already tried, but this time, before booting into ICS for the first time, I installed the 'Superuser-3.0.6-efgh-signed.zip' package.
Same issue. I'm not having any luck here.
iwebsource said:
AT LEAST YOU GUYS HAVE IT RUNNING!!
I am having a hell of a time trying to get it to work. I have tried so many different ways to get it up and running but no luck.
I've tried installing it from MIUI 3 times but all I get when trying to boot into ICS for the first time is a Black Screen after the FuguMod boot screen.
The funny thing is that the 4 soft buttons at the bottom light up still.
So I then decided to try the JVT way:
-Flashed JVT DARKYROM (ODIN)
-Lagfix OFF
-FULL WIPEs (factory reset, cache, dalvik)
-FLASHED CM7.1 STABLE
-FULL WIPEs (factory reset, cache, dalvik)
-Flash ICS BETA1
-Flash kernel
-FOR THE SECOND TIME:
-Flash ICS BETA1 AGAIN
-Flash kernel AGAIN
Same issue, black screen after the FuguMod boot screen, buttons still light up.
So i tried a couple more times in a few different ways based off what I have already tried, but this time, before booting into ICS for the first time, I installed the 'Superuser-3.0.6-efgh-signed.zip' package.
Same issue. I'm not having any luck here.
Click to expand...
Click to collapse
OK so here is what I did ...
Started from MIUI 1.11.18
1. Do a nandroid backup
2. download all the files to the SD card. This includes the ROM, Kernel and super user fix
Links:
Kernel:http://ice-cream-sandwich-sgs.googlecode.com/files/FuguModICS_GT-I9000_update.zip
ROM:http://ice-cream-sandwich-sgs.googlecode.com/files/ICS_4.0.1_r1-Beta1-i9000.zip
Super User:http://ice-cream-sandwich-sgs.googlecode.com/files/Superuser-3.0.6-efgh-signed.zip
3. Boot to recovery and do factory reset, wipe cache and davlik cache
4. Install the Kernel first and reboot now
5. Boot into recovery factory reset and wipe cache and Davlik and Install the ROM then reboot now
6 Boot back to recovery and install the Kernel again with out the wipe
7. If after reboot you do not have root then boot to recovery and flash super user fix
8. reboot and it should be working at least it was for me
It seems to me that you are missing the first flash of the kernel before the ROM. It sets up the file system from what I gather
Note: If needed flash the kernel and rom then kernel again with all the wipes as mentioned above.
I know there are allot of folks having issues getting it to run. Not too sure if it was the way I installed MIUI that might have made the difference.
My battery is charging now so I can calibrate it and see how it goes after that (it drained pretty quick today) lol.
I hope you can get it going cause it truly is awesome
Still not working:
Can not charge with the phone off
Google TTS stops working
Phone will not vibrate for SMS or email when in silent mode
BLN stays on for notifications until the phone is taken out of sleep (can be turned off)
Compass is why off (have not attempted to calibrate yet though)
11 MB left in the system partition (not much but I do not think there will be many changes there)
Video play back is choppy and some will not play
Bucky
regarding the black screen:
- had that too... I let it sit on the black screen for 2-3 minutes and then it went to the boot screen animation (a multi-coloured )...that for a few minutes...then finally booted.
How i got it working:
a) Started on MIUI...booted into clockwork
b) Backup
c) Wipe data / factory reset and cache and dalvik cache
d) Install rom and then kernel
e) Restart
f) Install rom and then kernel
g) Restart and wait very patiently for a little while
h) Once it all works, can reboot into clockwork and install superuser
Good luck! I really think the rom is nearly stable enough for daily use...
-------
Also have the no vibrate on silent... haven't tried the other stuff yet.
Oh and TTS hasn't crashed on this version yet for me...
Astrid glitches a little to a lot.
Changing from google tts to picco tts solves the problem there. As for the other stuff it is all reported as known.
I am using as a daily on my phone and no issues with general use. Still testing battery and that seems to be a bit of an issue with regard to Android OS as usual
Sent from my GT-I9000 using XDA App
So to install this ROM I would just have to install it as per totallydubbed's instructions? I don't want to flash miui if I don't have to to try this out.
Sent from my GT-I9000 (T959 mod) using XDA App
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:
I've been using Quarx's CyanogenMod 11.0 (KitKat 4.4.2) since its January 20 release. However, my phone starting to become slow with the time (nothing related to the build but the extensive device use & data exchanging). Today i decided to upgrade to most recent build (NIGHTLY 23/03). Of course i wiped everything before. I installed the build directly from TWRP with no big problems, however, i disliked this "new"? recovery interface (this one that shows two options (RECOVERY) and (ANDROID) and this "Press search to load the system" thing. I Would like to disable it and return to the old M logo, where i had the blue led to warn me about the recovery thing. Is this possible? I mean, take this thing out?
Now the most important. As i said, i've been on the development thread since the beginning, but i didn't found any working answer to my situation. After trying both GAPPS 4.4.2, i see a black screen on first boot with the Standard GAPPS and only a "Choose your laguage" with Minimal, after chosen i get a "Launcher stopped working".I cant add the google account without the GAPPS, as some peoples suggested to another on that topic. I remember that i read something related to install the previous working build (20/01) and then upgrade to the newer, after setting the account on the older build. But theres no january 20 on quarxs ftp, what now? HELP PLS
System + data + cache wipe, use core gapps 2-26. If you encounter issues, then again install rom after full wipe, but don't install gapps immediately. Reboot, and delete unwanted system apps to free up space, and then flash gapps and wipe cache
No easy way to backport safestrap (replacement for boot menu)
Sent from my MB526 using Tapatalk
johnaddams83 said:
I've been using Quarx's CyanogenMod 11.0 (KitKat 4.4.2) since its January 20 release. However, my phone starting to become slow with the time (nothing related to the build but the extensive device use & data exchanging). Today i decided to upgrade to most recent build (NIGHTLY 23/03). Of course i wiped everything before. I installed the build directly from TWRP with no big problems, however, i disliked this "new"? recovery interface (this one that shows two options (RECOVERY) and (ANDROID) and this "Press search to load the system" thing. I Would like to disable it and return to the old M logo, where i had the blue led to warn me about the recovery thing. Is this possible? I mean, take this thing out?
Now the most important. As i said, i've been on the development thread since the beginning, but i didn't found any working answer to my situation. After trying both GAPPS 4.4.2, i see a black screen on first boot with the Standard GAPPS and only a "Choose your laguage" with Minimal, after chosen i get a "Launcher stopped working".I cant add the google account without the GAPPS, as some peoples suggested to another on that topic. I remember that i read something related to install the previous working build (20/01) and then upgrade to the newer, after setting the account on the older build. But theres no january 20 on quarxs ftp, what now? HELP PLS
Click to expand...
Click to collapse
do not use standard gapps..system partition not big enough to store standard gapps..install core gapps
I've had the trouble described in
http://forum.xda-developers.com/showpost.php?p=49962954&postcount=1775
What's worse, more recent builds have a kernel that bootloops for me. This thread has a solution.
Originally I was unsatisfied with CM11 nightly, because the camera crashed with a hard reset - heavy use of the gallery or taking a photo after a long time had triggered this hard reset reliably. So this problem was reproducable.
I upgraded CM11 nightly to latest 2014-03-30, just to find out recent kernels won't start at all or bootloop the green lense defy.
After that I wiped anything - flash SBF, Framaroot, 2ndinit, twrp_recovery_2.6.3.0.zip.
To confirm the device was working I flashed a couple of roms (CM9, CM10) builds from October 2013, they worked.
While testing I realized that these roms were a lot snappier than the CM11 one I was dissatisfied with, noticing that besides hard reset on camera usage I also had a lagging UI. I assume that SELinux might be one of the reasons for the camera hard resets I experienced, but have no proof for this..
Then I spent a couple of days debugging the problem and it turns out, that all of the problems arise indeed from the kernel used.
Atm, I run a butter smooth CM10.2 nightly rom dating 2014-03-31, but running on a kernel dating 2014-01-20 (ripped out of CM11-nightly!).
For this to happen, simply exchange zImage under /system/bootmenu/2nd-boot/
Extract zImage from 2014-01-20 rom beforehand, put it on sdcard.
After installing the latest rom, before rebooting, do
- Mount /system with TWRP
- Go to Tools > Filemanager
- Select the 2014-01-20 zImage in TWRP Filemanager
- Let TWRP copy it to /system/bootmenu/2nd-boot/ (overwriting the one that's in there)
- Wipe cache/dalvik
- Reboot
I have tested this setup and it runs amazingly! I tested GPS turning on an off, Camera works (except video with stock app), Wifi works - no reboots and the UI is a breeze. It simply behaves as it should. Neither zRAM or zCache is activated, battery consumption is low, as is CPU usage.
Conclusion: The latest nightly kernels suck hard for green lense defy, but I still do not know exactly why.
Fazit: Can confirm that zImage from 2014-01-20 is tried and tested.
===================================
How solution was found: I read in the forums, that update-recovery.zip contains a kernel. Since after flash of CM10.2-2014-03-31 I had bootloop problem, I went to TWRP recovery on blue led, which still worked, and installed update-recovery.zip AFTER rom. Normally, you do not do this, since this DOWNGRADES kernel. But if latest kernel does not work, there is a chance succeeding with this method.
Ok, after flashing update-recovery.zip zImage dating 2013-11-07 was in place and phone booted with CM10.2-2014-03-31 image. I thouhgt I had found the solution, but soon noticed, that this kernel had issued with GPS (it would hang and not turn off, once activated). The immediate next step was to look for a kernel built after 2013-11-07 - I tried with 2014-01-20, since this was the latest version offered by defy.bytekiste.de here:
http://defy.bytekiste.de/cm11-nightly-defy+/
Since, on defy.bytekiste.de CM10.2 listing stopped at 2013-10-30, and with update-recovery.zip I already had a kernel from 2013-11-07, I jumped to CM11 roms, as I did not know about existence of defy.svolkov.name at that time.
defy.svolkov.name lists CM10.2 nightly builds from 2014-01-09 on. One could probably try the kernels directly from these roms. However, I think the difference in kernels between CM10.2 and CM11 is neglectible. What matters is the timestamp of the builds - different timestamp, different kernel config and that seems to decide whether it's working on defy green lense or not.
===================================
I did not further bisect the problem yet, i.e. trying each nightly kernel built after 2014-01-20 in succession to see which build first caused the bootloop problem. However I've checked some of the roms and the file structure on quarx2k.ru and defy.bytekiste.de (you can find complete structure of both on http://defy.svolkov.name/), it's borked:
versions for cm-11-20131229-NIGHTLY-mb526.zip
886b1bfdeadada2f45c695e34e126d0c http://defy.bytekiste.de/cm11-nightly-defy+/cm-11-20131229-NIGHTLY-mb526.zip
886b1bfdeadada2f45c695e34e126d0c http://defy.svolkov.name/quarx2k.ru/cm11.0-nightly-defy+/cm-11-20131229-NIGHTLY-mb526.zip
versions for cm-11-20140117-NIGHTLY-mb526.zip
a936c82ad55fa488079b2a8796838678 http://defy.bytekiste.de/cm11-nightly-defy+/cm-11-20140117-NIGHTLY-mb526.zip
a936c82ad55fa488079b2a8796838678 http://defy.svolkov.name/quarx2k.ru/cm11.0-nightly-defy+/cm-11-20140117-NIGHTLY-mb526.zip
6e05a8e9205f30a212be5aafc6e4bc01 http://defy.svolkov.name/quarx2k.ru/roms/defy-cm11.0/cm-11-20140117-NIGHTLY-mb526.zip
now, from the above, if you thought
"defy.bytekiste.de/cm11-nightly-defy+" and
"defy.svolkov.name/quarx2k.ru/cm11.0-nightly-defy+"
were mirrors wrt same-named files, think again.
versions for cm-11-20140120-NIGHTLY-mb526.zip
0602c6090ffa169dcf249b49f3c1d2be http://defy.bytekiste.de/cm11-nightly-defy+/cm-11-20140120-NIGHTLY-mb526.zip (appears to have a different ramdisk-recovery, other files in 2nd-boot dir are identical to rom below)
d9a88dde07c06474d60dc353c53babc8 http://defy.svolkov.name/quarx2k.ru/cm11.0-nightly-defy+/cm-11-20140120-NIGHTLY-mb526.zip
also note,
"defy.svolkov.name/quarx2k.ru/roms/defy-cm11.0/"
holds the most recent list of nightlies, while the listing starts with
20140109 version, and continues until
20140117 version (see versions above)
it omits 20140120 completely, and then continues from
20140123 version.
===================================
I actually wanted to post this in dev forums CM10.2 on defy thread, but do not have more than 10 posts on xda-dev, so are not allowed to. This is why I post it here.
Thanks!
cmuelle8 said:
...
- Let TWRP copy it to /system/bootmenu/2nd-boot/ (overwriting the one that's in there)
...
I tried with 2014-01-20, since this was the latest version offered by defy.bytekiste.de here:
h t t p : / / d efy.bytekiste.d e/cm11-nightly-defy+/
...
Click to expand...
Click to collapse
Thanks for posting your findings. I first thought "it will be fixed soon" when my camera didn't work after a update. Then, because no one was complaining, i thought the camera in my Defy is broken.
I have almost done the same and now the camera is working again
1) extracted the zImage from 2014-01-20
2) "adb push" it to the sdcard
3) mount -o remount,rw /dev/block/mmcblk1p21 /system/
4) cd /system/bootstrap/2nd-boot
5) cp /sdcard/zImage .
6) reboot
7) happy
Any later kernels that show the same stability?
Edit: My Defy will not boot after replacing the kernel. I'm on cm-11-20140611 now.
I think you are refering to camera bug #44?
I have the same with my Defy green lense (MB525). I've found out that the bug was introduced in CM11 with the ROM from 2014-03-15. So the camera worked for me without problem until the ROM from 2014-03-13. Since then I have to set the minimum frequency at least to 600MHz. Below that value e.g. 500MHz I get indeed bootloopss when using camera or gallery. Disabling the HWA settings for the most apps (besides the camera) delayes only the unavoidably bootloop for some seconds.
Do you think it's possible to use the newest CM11 nightly ROM together with the last working ROM from 2014-03-13?
The camera-bug #44 still exists since the ROM_2014-03-15. But I think I could narrow down the problem a little. It seems to be the kernel, means the file "zImage" under /bootstrap/2nd-boot. When I took that file from the last working ROM_2014-03-13 and apply it to a later problematic ROM, then the bug #44 is gone (for me). I've successfully tested this workaround until the ROM-version from 2014-03-25. Since ROM_2014-04-01 and later this doesn't work because the phone wont start, maybe to much has changed within the ROM. The replacement (camera2.apk, MediaProvider.apk) or the deletion (wallpapper, etc.) of some system-apps leads to no success. Deactivating the autofocus-function or the GPS-tagging for the pictures doesnt help either. However, until now the phone reboots fairly fast when I scroll the taken pictures within the camera-app. Maybe it has something to do with my sdcard (read performance, whatever)?!?!? But the chance is very small, because it had worked outstanding until the ROMs before 2014-03-14 ;-(