Hi All,
I'm new to LOS and have a basic question. How often should I update? I was taught don't mess with anything that ain't broken!
Now if I wait too long, for example, updating from 17.1 to 18.x one of these days, would the built-in updater still be able to do a seamless update, or would I end up reinstalling everything for such a big jump? Seamless for me means I can flash the new one over the old one in TWRP without a wipe, and all my config would remain and apps still work!
Any thought is highly appreciated. Thank you
luckysoul777 said:
Hi All,
I'm new to LOS and have a basic question. How often should I update? I was taught don't mess with anything that ain't broken!
Now if I wait too long, for example, updating from 17.1 to 18.x one of these days, would the built-in updater still be able to do a seamless update, or would I end up reinstalling everything for such a big jump? Seamless for me means I can flash the new one over the old one in TWRP without a wipe, and all my config would remain and apps still work!
Any thought is highly appreciated. Thank you
Click to expand...
Click to collapse
Hard to say...
For me... mor or less once a month with security patches. Or I see interesting changes.
And only to next version if at "known bugs" is nothing which stops me at daily usage and only if it os "official"
Gesendet von meinem POCO F1 mit Tapatalk
youvedone said:
only to next version if at "known bugs" is nothing which stops me at daily usage and only if it os "official"
Click to expand...
Click to collapse
Do you just install the new one over the old one and the LOS built-in updater would sort it out without wiping the old installation? Thanks
luckysoul777 said:
Do you just install the new one over the old one and the LOS built-in updater would sort it out without wiping the old installation? Thanks
Click to expand...
Click to collapse
Yes normally that works pretty fine, just be sure if your using magisk, there are modules which can cause problems in that process
Gesendet von meinem POCO F1 mit Tapatalk
youvedone said:
if your using magisk, there are modules which can cause problems in that process
Click to expand...
Click to collapse
Is it as simple as turning them off before the update and turning them back on afterward? Or should I uninstall these modules first and reinstall them afterward? Thanks
luckysoul777 said:
Is it as simple as turning them off before the update and turning them back on afterward? Or should I uninstall these modules first and reinstall them afterward? Thanks
Click to expand...
Click to collapse
Disable / enable
Gesendet von meinem POCO F1 mit Tapatalk
Related
Hello guys,
I using the lordmod ics rom 7.5 on my desire hd. And I get random reboots and everytime it reboots it says sim card inserted and proceeds to reboot again. Had this on 7.4 and 7.5 test 1.i had Made a full wipes.
First I had Using the default kernel and then the cfs kernel. The problem occurs randomly. Probably once everyday. Anyone else can help me?
Sry for my Bad english i am a german guy )
thank you...
Gesendet von meinem Desire HD mit Tapatalk 2
ciddi89 said:
Hello guys,
I using the lordmod ics rom 7.5 on my desire hd. And I get random reboots and everytime it reboots it says sim card inserted and proceeds to reboot again. Had this on 7.4 and 7.5 test 1.i had Made a full wipes.
First I had Using the default kernel and then the cfs kernel. The problem occurs randomly. Probably once everyday. Anyone else can help me?
Sry for my Bad english i am a german guy )
thank you...
Gesendet von meinem Desire HD mit Tapatalk 2
Click to expand...
Click to collapse
Dont know if you flashed a lot on your phone but if youd like you can do a complete wipe of your phone and sd card for a complete fresh install. Just copy all your pics and music and stuff like that from your sd to folder on computer and try this out. Just use the 4EXT touch recovery we already have from ice cold and follow the steps. Remember this forum will erase absolutely everything on phone and sd. If issue perist after this it could be a hardware issue.
http://forum.xda-developers.com/showthread.php?t=1515387
Reinaldo33897 said:
Dont know if you flashed a lot on your phone but if youd like you can do a complete wipe of your phone and sd card for a complete fresh install. Just copy all your pics and music and stuff like that from your sd to folder on computer and try this out. Just use the 4EXT touch recovery we already have from ice cold and follow the steps. Remember this forum will erase absolutely everything on phone and sd. If issue perist after this it could be a hardware issue.
http://forum.xda-developers.com/showthread.php?t=1515387
Click to expand...
Click to collapse
Thanks for you answer. Before i flashed the ics Rom, i had runnydroid on my phone and doesn't do a full wipe of my System.
I will tested it later. I Hope then is better.
Gesendet von meinem Desire HD mit Tapatalk 2
I think i have found the Problem. It's only when my lockscreen Theme "honeycomb" is. Today at the morning, i had change it to "default" and no restarts until now otherwise i had 4-5 restarts on one Day .
Gesendet von meinem Desire HD mit Tapatalk 2
If the same issue persist, one recommendation that I would like to give you will be to re-flash the same rom again but doing a Full Wipe in the phone first.
Then restore the application again and you will be up and running!!
ciddi89 said:
I think i have found the Problem. It's only when my lockscreen Theme "honeycomb" is. Today at the morning, i had change it to "default" and no restarts until now otherwise i had 4-5 restarts on one Day .
Gesendet von meinem Desire HD mit Tapatalk 2
Click to expand...
Click to collapse
i've been having the same issue, and I am also using honeycomb lock screen. Did this fix your issue or has it persisted since you set it back to defult?
Try the latest 7.5 test 9 version (look through the last 10 pages of the IceColdSandwich thread to find links, the link in the main post is down). It's the smoothest version yet. Lord's 9.7.5 kernel is giving kickass performance, and a lot of random reboot/freezing issues have disappeared in this version.
NoobDude said:
i've been having the same issue, and I am also using honeycomb lock screen. Did this fix your issue or has it persisted since you set it back to defult?
Click to expand...
Click to collapse
I get the same issue with octo lock screen
Sent from my Desire HD using XDA
Installed this rom today. Finding it a little laggy so any solutions, ways and etc?
Whaaat? Normaly its the smoothest rom!!
Governor Pegasusq and scheduler sioplus?
Performance - 16bit transperancy? (Dont forget to reboot!)
Developeroptions - gpu rendering?
Did you make a Clean Install?
Gesendet von meinem GT-i8160 (CM 10.2 Team Canjica)
HCDanny24 said:
Whaaat? Normaly its the smoothest rom!!
Governor Pegasusq and scheduler sioplus?
Performance - 16bit transperancy? (Dont forget to reboot!)
Developeroptions - gpu rendering?
Did you make a Clean Install?
Gesendet von meinem GT-i8160 (CM 10.2 Team Canjica)
Click to expand...
Click to collapse
You mean by factory data reset, flash rom then gapps? And what do you mean clean install? I only did a factory reset like it showed on the page. after about 6 hours or so of using it, phone kept turning off at random points
AndroidOwnsAll said:
after about 6 hours or so of using it, phone kept turning off at random points
Click to expand...
Click to collapse
It shouldn't be THAT bad, but every 4.3 ROM has known memory leaks if you play too much with the notification bar (wastes RAM every time you touch the statusbar)... but your case sounds more like a bad compile
I would say you should flash stock jellybean via odin xxmg2 and then flash cm 10.2. So it should run normaly
Gesendet von meinem GT-i8160 (CM 10.2 Team Canjica)
Ryccardo said:
It shouldn't be THAT bad, but every 4.3 ROM has known memory leaks if you play too much with the notification bar (wastes RAM every time you touch the statusbar)... but your case sounds more like a bad compile
Click to expand...
Click to collapse
What do you mean bad compile? I'm a bit of a noob
HCDanny24 said:
I would say you should flash stock jellybean via odin xxmg2 and then flash cm 10.2. So it should run normaly
Gesendet von meinem GT-i8160 (CM 10.2 Team Canjica)
Click to expand...
Click to collapse
How about XXNA1?
AndroidOwnsAll said:
What do you mean bad compile? I'm a bit of a noob
Click to expand...
Click to collapse
An error or just something unfinished creating a ROM with some issues
AndroidOwnsAll said:
How about XXNA1?
Click to expand...
Click to collapse
All except MB2 are probably the same if you're going to install another ROM over it
Has anyone been able to build this kernel from the p8000_defconfig ?
I've tried to build it with linaro, but failed (I'm a newbee though).
i have ordered the phone. have to wait 3-4 weeks ...i will start developing for it soon
that's great news! can't wait
skeleton1911 said:
i have ordered the phone. have to wait 3-4 weeks ...i will start developing for it soon
Click to expand...
Click to collapse
Sounds great, I'm gonna do the same as soon as I get my device. Should be around 26th August - perhaps we could collaborate sometimes!
Greetz to Muenster - I grew up in Soest, lol
BlueFlame4 said:
Sounds great, I'm gonna do the same as soon as I get my device. Should be around 26th August - perhaps we could collaborate sometimes!
Greetz to Muenster - I grew up in Soest, lol
Click to expand...
Click to collapse
Nice.
Werde eventuell drauf zurück kommen.
Maybe we will speak later
Gesendet von meinem HTC One M9 mit Tapatalk
Tried to build the kernel as well. The sources seem to be incomplete, though. I'm pretty sure the MT6753 platform specific sources are missing. But might just be my lack of experience...
jott_st said:
Tried to build the kernel as well. The sources seem to be incomplete, though. I'm pretty sure the MT6753 platform specific sources are missing. But might just be my lack of experience...
Click to expand...
Click to collapse
I was actually expecting some problems - we're still talking about MediaTek. What error message do you get?
BlueFlame4 said:
I was actually expecting some problems - we're still talking about MediaTek. What error message do you get?
Click to expand...
Click to collapse
I don't remember. I think there were missing dependencies. So I tried to use the provided build.sh and there was a reference to ../mediatek/build/shell.sh. Google lead me to this git-repo: https://github.com/wiko-sources/cink-slim ; I figured we might need the same folder structure for the MT6753.
I succeeded in building the Kernel with the aarch64-linux-android-4.9 toolchain and the p8000_defconfig.
To make it work, I only had to do a few minor changes:
-The p8000_defconfig file somehow has a trailing whitespace... I don't quite get why there is a whitespace there, but this isn't really a problem
-A few of the files in drivers/misc/mediatek have a few include errors. Mostly <> was used instead of "" to reference a local header file, changing this fixed all but one problem.
-In drivers/misc/mediatek/dispsys/mt6735/ddp_dsi.h there is a reference to "fbconfig_kdebug_k2.h". But the referenced file is not in the same directory. Changing the include to "../../videox/mt6735/fbconfig_kdebug_k2.h" did the trick.
Sadly, the Phone is not there yet so I couldn't test anything and I'm also a newbie concerning Android development. But I hope this might help someone.
D4RE said:
I succeeded in building the Kernel with the aarch64-linux-android-4.9 toolchain and the p8000_defconfig.
To make it work, I only had to do a few minor changes:
-The p8000_defconfig file somehow has a trailing whitespace... I don't quite get why there is a whitespace there, but this isn't really a problem
-A few of the files in drivers/misc/mediatek have a few include errors. Mostly was used instead of "" to reference a local header file, changing this fixed all but one problem.
-In drivers/misc/mediatek/dispsys/mt6735/ddp_dsi.h there is a reference to "fbconfig_kdebug_k2.h". But the referenced file is not in the same directory. Changing the include to "../../videox/mt6735/fbconfig_kdebug_k2.h" did the trick.
Sadly, the Phone is not there yet so I couldn't test anything and I'm also a newbie concerning Android development. But I hope this might help someone.
Click to expand...
Click to collapse
Thanks . saves me a lot time
I hope i get the phone. I bought it via comebuy. Someone knows that side?
Gesendet von meinem HTC One M9 mit Tapatalk
skeleton1911 said:
Thanks . saves me a lot time
I hope i get the phone. I bought it via comebuy. Someone knows that side?
Gesendet von meinem HTC One M9 mit Tapatalk
Click to expand...
Click to collapse
Yep, I also ordered it there. They told me it will arrive around 26th of August.
Thanks a lot @D4RE!
BlueFlame4 said:
Yep, I also ordered it there. They told me it will arrive around 26th of August.
Thanks a lot @D4RE!
Click to expand...
Click to collapse
Me too. But they told me that is is available at the 31th of August . it will be send from a german central warehouse..
Gesendet von meinem HTC One M9 mit Tapatalk
D4RE said:
I succeeded in building the Kernel with the aarch64-linux-android-4.9 toolchain and the p8000_defconfig.
To make it work, I only had to do a few minor changes:
-The p8000_defconfig file somehow has a trailing whitespace... I don't quite get why there is a whitespace there, but this isn't really a problem
-A few of the files in drivers/misc/mediatek have a few include errors. Mostly <> was used instead of "" to reference a local header file, changing this fixed all but one problem.
-In drivers/misc/mediatek/dispsys/mt6735/ddp_dsi.h there is a reference to "fbconfig_kdebug_k2.h". But the referenced file is not in the same directory. Changing the include to "../../videox/mt6735/fbconfig_kdebug_k2.h" did the trick.
Sadly, the Phone is not there yet so I couldn't test anything and I'm also a newbie concerning Android development. But I hope this might help someone.
Click to expand...
Click to collapse
Thank, save me a lot of time too.
After compile, repack + flash.
Phone boot up, without SIM Card slot detected. Both SIM Slot 1 & 2 missing.
skeleton1911 said:
Me too. But they told me that is is available at the 31th of August . it will be send from a german central warehouse..
Gesendet von meinem HTC One M9 mit Tapatalk
Click to expand...
Click to collapse
FYI: There are now shipping dates listed on their site. http://www.comebuy.com/handys-om000391.html
BlueFlame4 said:
FYI: There are now shipping dates listed on their site. http://www.comebuy.com/handys-om000391.html
Click to expand...
Click to collapse
Storniert. Lol
I ordered it from amazon. They send it me last Thursday. . rooted it already its really nice phone.
Soon I will start to build my custom ROM
Gesendet von meinem Elephone P8000 mit Tapatalk
Clust3r said:
Thank, save me a lot of time too.
After compile, repack + flash.
Phone boot up, without SIM Card slot detected. Both SIM Slot 1 & 2 missing.
Click to expand...
Click to collapse
I can't get it to boot at all. How did you do it? Do we need to add the meditek kernel-header?
I had a quick look at the sources - there seems to be a lot of stuff in there that is definitely not needed on the P8000. Different architectures and drivers for components that are not present in the P8000. Is this some kind of generic kernel they use in different configurations for all their phones?
jott_st said:
I can't get it to boot at all. How did you do it? Do we need to add the meditek kernel-header?
Click to expand...
Click to collapse
Using abootimage tools for upgrading kernel in the original boot.bin file.
abootimg -u boot.img -k P8000-Kernel/arch/arm64/boot/Image.gz-dtb
Brewn said:
I had a quick look at the sources - there seems to be a lot of stuff in there that is definitely not needed on the P8000. Different architectures and drivers for components that are not present in the P8000. Is this some kind of generic kernel they use in different configurations for all their phones?
Click to expand...
Click to collapse
yep, I think so, too.
Clust3r said:
Using abootimage tools for upgrading kernel in the original boot.bin file.
abootimg -u boot.img -k P8000-Kernel/arch/arm64/boot/Image.gz-dtb
Click to expand...
Click to collapse
Thanks, I'll try that.
So it might be a good idea to remove all the stuff that's not needed to keep the kernel and modules small... this is probably a lot of work though.
I know various camera problems have been discussed but I have not seen any solutions. I have Eragon 6.5.1 and I am using the "Open Camera" app as the primary camera (I like it) which is built in to the ROM. My banking app allows me to e-deposit cheques but I find when trying to capture images the autofocus usually does not work. I can sometimes get a clear image by taking a fuzzy shot, then discarding and trying again. The camera is great as a camera but it just seems autofocus refuses to kick in on my banking apps. The banking apps app work like a charm on other phones and it seems I am reduced to using my old phone to do my banking while my shiny new P8000 sits on the desk and watches. Suggestions please.
This is a bug with the kernel version shipped - I forgot to set some flags there. Use my kernel or go back to stock and it will work. This is actually my fault :/
BlueFlame4 said:
This is a bug with the kernel version shipped - I forgot to set some flags there. Use my kernel or go back to stock and it will work. This is actually my fault :/
Click to expand...
Click to collapse
Thanks, will give it a shot and report results.
BlueFlame4 said:
This is a bug with the kernel version shipped - I forgot to set some flags there. Use my kernel or go back to stock and it will work. This is actually my fault :/
Click to expand...
Click to collapse
Sorry, I am a little confused, I am on Eragon rom 6.5.1 and kernel is reported by phone as 3.10.65. I previously had the Eragon beta build which included your kernel (dt2w is nice) but I believe the official 6.5.1 has reverted to the stock kernel so therefore I would not experience the third party camera bug would I ? Or does the current Eragon 6.5.1 flash somehow retain the bug, ( I use Philz recovery clean to install new rom function)?
bluiis48 said:
Sorry, I am a little confused, I am on Eragon rom 6.5.1 and kernel is reported by phone as 3.10.65. I previously had the Eragon beta build which included your kernel (dt2w is nice) but I believe the official 6.5.1 has reverted to the stock kernel so therefore I would not experience the third party camera bug would I ? Or does the current Eragon 6.5.1 flash somehow retain the bug, ( I use Philz recovery clean to install new rom function)?
Click to expand...
Click to collapse
If @skeleton1911 didn't remove it Eragon ships with a custom visi0nary's kernel I compiled for him (and which unfortunately contains a bug I don't have time to fix now...). The original visi0nary's kernel doesn't have this bug though.
BlueFlame4 said:
If @skeleton1911 didn't remove it Eragon ships with a custom visi0nary's kernel I compiled for him (and which unfortunately contains a bug I don't have time to fix now...). The original visi0nary's kernel doesn't have this bug though.
Click to expand...
Click to collapse
Much appreciate the clarification and lightning response, will be guided by this advice.
BlueFlame4 said:
If @skeleton1911 didn't remove it Eragon ships with a custom visi0nary's kernel I compiled for him (and which unfortunately contains a bug I don't have time to fix now...). The original visi0nary's kernel doesn't have this bug though.
Click to expand...
Click to collapse
bluiis48 said:
Much appreciate the clarification and lightning response, will be guided by this advice.
Click to expand...
Click to collapse
Yep. In my latest v6.5.1 Rom i have removed it again because of that bug and fingerprint issue. V6.5.1 has the stock kernel on board.
Bluiis48 we already talked about it in my thread [emoji14]
Gesendet von meinem Elephone P8000 mit Tapatalk
skeleton1911 said:
Yep. In my latest v6.5.1 Rom i have removed it again because of that bug and fingerprint issue. V6.5.1 has the stock kernel on board.
Bluiis48 we already talked about it in my thread [emoji14]
Gesendet von meinem Elephone P8000 mit Tapatalk
Click to expand...
Click to collapse
Yes, my apologies, I had posted the question in the general Q & A section, before I was allowed to post in this section and BlueFlame4 responded today so I thought that it may be some new advice. I will give up on this issue and use my old Riv R55 with the "tiny" 8mp camera that does work for me.
Again, much appreciate your time and the huge effort you put in to this rom.
bluiis48 said:
Yes, my apologies, I had posted the question in the general Q & A section, before I was allowed to post in this section and BlueFlame4 responded today so I thought that it may be some new advice. I will give up on this issue and use my old Riv R55 with the "tiny" 8mp camera that does work for me.
Again, much appreciate your time and the huge effort you put in to this rom.
Click to expand...
Click to collapse
Your welcome mate. Its fine. And sry that we cant help.
Gesendet von meinem Elephone P8000 mit Tapatalk
the focus works well for me. i do not see a issue
aprovis83 said:
the focus works well for me. i do not see a issue
Click to expand...
Click to collapse
Thanks for the input, may I ask what banking app you are using ? My camera also focuses pretty well when used as just a camera but the problem is in apps that use the camera for image capturing such as depositing a cheque electronically within a bank app.
Hi guys, this is the MM version of my previous kernel.
Features:
- autoroot;
- init.d support;
- busybox;
- kppd by @savoca ( to control display parameters);
- Selinux permissive;
- all core unlocked and managed by mpdecision;
- vibration strenght control;
Changelog:
Version 1.1:
- fix for kppd;
Check THIS thread for more info;
A BIG "thank you" to the following guys that supported my work! :
@RngrYogi
@satanix
@mallman
@brotbuexe
@Supercutetom
...really, really thanks!
SOURCE
To control RGB channel of the display and to support my work you can use this:
https://play.google.com/store/apps/details?id=com.skin1980.displaycontrol
Thank you guys.
Great! Thnx for your hard work! I'll provide some feedback when I have it installed.
how to control vibration?
edit: just use this one again http://forum.xda-developers.com/huawei-watch/orig-development/set-vibration-strength-boot-t3272978
Thank you very much!
Could you look into flickering while in ambient mode problem? If you need a watch to test, ask me for team viewer.
Thank you so much Skinz! We all appreciate it!
Skin1980 said:
- kppd by @savoca ( to control display parameters);
Click to expand...
Click to collapse
what's this?
MuF123 said:
what's this?
Click to expand...
Click to collapse
Lets u control RGB channels. I'm releasing an app to easy configure it.
Battery life is kinda bad. 10% an hour.
Motawa88 said:
Battery life is kinda bad. 10% an hour.
Click to expand...
Click to collapse
I don't have a battery problem
Motawa88 said:
Battery life is kinda bad. 10% an hour.
Click to expand...
Click to collapse
I'm also experiencing rapid battery drain and I have always-on off and tilt-to-wake off. I did flash the test02.img MM kernel that Skin1980 posted before releasing this version - I don't know if the dirty flashing could be a factor.
Sent from my LG-H900 using Tapatalk
acultr said:
I don't have a battery problem
Click to expand...
Click to collapse
ditto, seems very good to me actually
Is this kernel faster than stock kernel?
Gesendet von meinem SM-G925F mit Tapatalk
I've flashed Skin1980's kernel v. 1.1 yesterday. In a few hours without any unusual activity the watch was stuck with "Android Wear is not responding" message 2 times, completely froze with "Android Wear shut down" error once, rebooted suddenly by itself once. Had to flash back original kernel. Maybe I should have done a full wipe immediately after flashing? Could this be the cause of the problems?
Alexander B said:
I've flashed Skin1980's kernel v. 1.1 yesterday. In a few hours without any unusual activity the watch was stuck with "Android Wear is not responding" message 2 times, completely froze with "Android Wear shut down" error once, rebooted suddenly by itself once. Had to flash back original kernel. Maybe I should have done a full wipe immediately after flashing? Could this be the cause of the problems?
Click to expand...
Click to collapse
Working fine for me after installing i boot twrp through adb wipe caches and reboot watch and factory reset and all was fine.
Nice work ! I will install
cobra11111 said:
Is this kernel faster than stock kernel?
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
exponentially
cobra11111 said:
Is this kernel faster than stock kernel?
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
Faster than a speeding bullet!
Could we get volume boost support?
autoroot?
anyone else having problems with root? I can´t get root permission for greenify and kernel adiutor.
Already reinstalled the kernel a few times
//EDIT: Sorry, got it to work with WinDroid Toolkit.
keydogg said:
anyone else having problems with root? I can´t get root permission for greenify and kernel adiutor.
Already reinstalled the kernel a few times
//EDIT: Sorry, got it to work with WinDroid Toolkit.
Click to expand...
Click to collapse
Hi there could you tell me where you grabbed the Grennify app for wear from many thanks.