It seems no matter which version of the kernel i use (other then stock), i get reboots.
I'm to the point where i don't even have to overclock. I load the new kernel and i will reboot about once an hour (of constant use).
Does this mean i just have a sub-par CPU? Can i expect this behavior with all future roms?
Just curious. I'm otherwise completly happy with my xoom, but this does cornor me if i can't do other future kernel related modifications.
I have NO reboot issues with the stock kernel and wifi drivers.
Thanks.
Related
I have been 'trying' to enjoy using my Nook Color, but truth is that so far I am disappointed with the results. I stayed on stock 1.0 for the best part of the day. I found it sluggish and dissapointingly narrow in its use.
I then became a CM7 and subsequently Phiremod user. Things were definately better, but the device would become 'slow' after a few hours or days of use. It was definately not the 'stable' experience I expected -- especially coming from an HTC Desire background.
I tried Honeycomb SDK ports several times in the past, and they were very sluggish and unstable -- understandbly so. Now I have tried giving the latest HC Hybrid RC1 a spin and it seems a huge improvement over previous SDK ports RCs.
But of course, the Nook Color is still slow, sluggish and unstable. I get FCs all over the place, things slow down, applications fail to load.
I would like to ask a couple of things:
1) How do I flash a custom (OC or OCable) kernel that is compatible with HC Hybrid RC1? I tried flashing what seemed to be the correct kernel, but I get a bootloop.
2) Do I use SetCPU to control CPU on HC, or is there another method? I can't seem to find anything in the settings that points to overclocking or CPU settings.
3) Which ROM + Kernel combination is the best for you?
4) Is it normal that I can't access the Market in HC Hybrid RC1? I get force closes everytime I try it.
5) I seem to have 'lost' access to SD card storage AND most of my internal storage. Is this expected behaviour?
Thank you for your time.
1. How if you flash the kernel and then reinstall HC Hybrid ...
5.Have you tried this updated ramdisk made by Racks11479 : http://forum.xda-developers.com/show...&postcount=483
http://www.multiupload.com/3D9WSPUAUZ Supposedly it fixes the issue but I haven't tried it yet
My phone is getting a bootlóop without me flashing anything. This has happened multiple of times. Im using my phone normally and then after i reböot it decides to bóotlóop with a broken recovery??!! How is it possible to bóotlóop that much without flashing anything or of that sorts???
I was using aokp b35 and devil kernel 2 big memory
surely im not the only 1?
that bug happens on every huge mem config kernels*.no one still found fix.
*since Devil2 0.70 Semaphore 2.9.7.devil 1.1.6 kernel not bootlooping
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:
Hey all,
I'm on 4.4.2 stock with Xposed (gravity box).
Using Trickster mod and have tried both M-Kernel (latest) and Faux kernel (latest).
With both, after using the tablet for 1-2 days, the max frequency seems to be stuck on 666mhz (for M-Kernel) and 700mhz (for Faux). I have to manually make it 1.2ghz and apply. Turning screen off/on doesn't fix the problem either. I've tried to remove trickster/clear data but same results. I think it's the same with other kernel manager apps too.
Does anyone have any idea what could be causing this? It's quite annoying
Hi. I have random reboot problem on my note 3. Screen freezes (gaming, settings, menu or idle) and reboots when i have installed ANY costom ROM or Kernel. I noticed screen freezes mostly when Synapse app is installed with Kernel, second notice phone freezes then my favourite PegasusQ governor is applied. Phone was working perfectly without any issue on official 5.0 with Minimalistic kernel, no issues about whole year (no synapse). Phone was two times in warranty. First time they instaled stock KK firmware and replaced micro usb port (that whole part in note3 ) ?? , second time simply installed stock Lollipop. And then everything starts from beggining...
Yesterday I zipped all LOGS with SysLog app when random reboot appeared (i was on synapse changing governor from interactive to precognition). If it helps reboot happened yesterday after 02:00 hour.
Zip here: https://www.dropbox.com/s/a3svst1yhhtj23u/2016-02-08_11.20.zip?dl=0
Warranty didn't fixed that so I hope real developers will detect what couses this RR.
Sorry for bad English
My phone is now on Phronesis ROM, CivZ_Xplorer-9005-Rev5.0.3-note5port Kernel
Do you have an SD card installed? If so remove it from the phone and see if the phone is stable
I was using external sdcard on official 5.0 lollipop with minimalistic kernel and phone was working without random reboots whole year.... Reboots only on costom roms and kernels with synapse.... I never used costom voltages and higer cpu freequency than 2.5 ghz... no gpu overclocks more than 450mhz, never played with performance governors, no overheating...
Reflash different stock firmware it worked for me
Sent from my SM-N900 using Tapatalk
bump
??