Google just moved out the 2.6.32 kernel from the experimental git repo to the msm repo. This means that google thinks they are stable now.
There are currently two 32 branches:
android-msm-2.6.32-nexusonec
http://android.git.kernel.org/?p=kernel/msm.git;a=shortlog;h=refs/heads/android-msm-2.6.32-nexusonec
android-msm-2.6.32
http://android.git.kernel.org/?p=kernel/msm.git;a=shortlog;h=refs/heads/android-msm-2.6.32
I've compiled both and I'm finding the nexusonec branch more stable than the 32 branch. The 32 branch causes issues with the gallery and camera app not recognizing the sd card. Everything seems to work fine in the nexusonec branch (sdcard, wifi, BT, camera, etc). Speed is definitely faster than 29.
For those who are interesting in flashing the 32 zimage, they can d/l it here:
http://drop.io/xdp6104#
Right now the kernel is just a stock config, meaning no tethering or anything else. Only change I've made from stock is to use the deadline I/O scheduler. I'm sure cyanogen will add those other goodies when he releases a new version.
Very nice: cant wait for a Enomther rom with this new Kernel
nice....
ive compiled a nice cyanogen kernel 2.6.32 already
just need to get the wifi module compiled correctly and we are gtg!
Does this mean that they've fixed some of the power saving regressions people were seeing with 2.6.32 before?
Installed on my Nexus with enomther 1.61: works nicely
Tot mem 395448K, Free 265916K
Does this still have the charging issue that blocks the battery to charge when it goes under 90%...???
eug89 said:
Does this still have the charging issue that blocks the battery to charge when it goes under 90%...???
Click to expand...
Click to collapse
86% now and charging..
eug89 said:
Does this still have the charging issue that blocks the battery to charge when it goes under 90%...???
Click to expand...
Click to collapse
It wasn't an issue per-se it was a 'feature'
The problem was caused by downgrading to older kernels after using 2.6.32. Certain hardware states that were set by the new kernel telling the battery not to charge weren't being un-set by the new kernel, and the older kernel didn't even know about them. They patched the newer kernel pretty quickly after getting feedback so that it removes the hardware state when shutting down, I believe. So, yes, it's 'fixed'
FettsVett said:
It wasn't an issue per-se it was a 'feature'
The problem was caused by downgrading to older kernels after using 2.6.32. Certain hardware states that were set by the new kernel telling the battery not to charge weren't being un-set by the new kernel, and the older kernel didn't even know about them. They patched the newer kernel pretty quickly after getting feedback so that it removes the hardware state when shutting down, I believe. So, yes, it's 'fixed'
Click to expand...
Click to collapse
Thanks, i called it issue because i didn't know how to call it but i knew that it was meant to be a sort of new feature of the 2..6.32 kernel and I wanted to write above 90% and not under 90%... did a bit of a mess
woahhh its way faster
thanks dwang
will do some thorough testing and post back soon.
edit: Hmmm having some trouble with fastboot... unable to push wifi via adb?
anyone else encountering this?
Are you trying to push the ko module on fastboot mode?
This kernel is FAST and SNAPPY! HIGHLY RECOMMENDED!
boqonx said:
Are you trying to push the ko module on fastboot mode?
This kernel is FAST and SNAPPY! HIGHLY RECOMMENDED!
Click to expand...
Click to collapse
yeah. iirc thats where you do it right?
Let the OS run, then push through adb. Can't do it when it's on recovery either because the /system/lib is not mounted. Wifi should work even without a restart.
yep just did that
i think i was just confused on where to use adb
it still works so all good. this kernel is zippy.
Damn right This thing flies now! Scrolling through messages is MUCH smoother. Seen a lot of tearing when scrolling on CM's kernel.
I released my undervolted version of CM's in the other thread. He changed the scheduler from anticipatory to deadline as well.
Will try! Had any reports on instabilities yet?
Dwang: great job on the deadline scheduler suggestion. It really does make the whole experience smoother.
Can someone write the exact adb command to push it?
Code:
adb remount
adb push ./bcm4329.ko /system/lib/modules
himmatwala said:
Can someone write the exact adb command to push it?
Click to expand...
Click to collapse
Related
Just compiled AOSP master. It boots OK - however it looks like the screen driver and the radio are not working. I get excessive screen flicker and radio doesn't work at all.
Any ideas? Do I need to pull the proprietary drivers from the phone itself like we used to have to if using cyanogen's passion vendor overlay?
riddelln said:
Just compiled AOSP master. It boots OK - however it looks like the screen driver and the radio are not working. I get excessive screen flicker and radio doesn't work at all.
Any ideas? Do I need to pull the proprietary drivers from the phone itself like we used to have to if using cyanogen's passion vendor overlay?
Click to expand...
Click to collapse
I would suggest checking out Cyanogen's IRC. There are a number of people in there who could help you with this.
You need to run the extract-files script or the unzip-files scripts in devices/htc/passion before you can build. the product should be "full_passion"
After that step there are some things still not working such as camera and playing videos. Logcat says that the permissions in /dev are not correct and they cannot access the /dev/vdec and audio as well. I havnt got past that part yet using either 2.6.32 or 2.6.34 kernels.
Hi.
I'm facing a "hard to solve" issue with my Atrix 4G...
It is a non-ATT (international). Using RSD Lite, I flashed the Retail SBF and it worked OK, battery life was "normal" and the phone was cold most of time.
I then unlocked the bootloader flashing the IHOP SBF then using moto_fastboot method. Installed Clockworkmod Recovery and flashed the HomeBase rom with the updates.
What happen is: The phone starts to get very warm and the battery is drained very quickly (couple of hours).
Using the SetCPU, I could verify that the CPU does not scale down automatically. It's always at 1300Mhz, it doesn't matter if the phone is idle or not.
I can reduce the CPU speed using the SetCPU but the processor is with the two cores active all the time and it never reduces the speed below the limit set in SetCPU.
I thought it may be a problem with my phone, so I flashed the retail SBF again and I could verify that, bakc with the retail rom, CPU is scaling down correctly. It goes up to 1000Mhz when requested but stays ~300Mhz when phone is idle.
I did the BL unlock/motofastboot/clockwordmod/ procedure again and tried with different roms (Aura, Alien, RedPill, etc) always cleaning up the Cache/UserData/Dalvik and using the faux 1.3Ghz unified kernel but got no result, on every 2.3.4 rom I flash, the CPU is always at the maximum speed set by the kernel or limited by the SetCPU.
I've found a similar problem on this thread: http://forum.xda-developers.com/showthread.php?t=1190634. and did the same investigation but I was not able to identify any aplication that is making the CPU usage to be constantly high (even tried killing all Apps, not result).
Any ideas what I can do/try to solve this issue?
Thanks a lot.
That happened to me too!! I just reflash the rom wiping everything and the cpu started acting normal
Try to use fastboot to wipe if ur using CWM
Sent from my CM7 Motorola Atrix 4G
For me turning off the phone and back on worked, if not for you then try wiping the usual stuff before reflashing a rom or back up
Feom what I've seen, this is often caused by the webtop. Most ROMs don't touch the webtop, and it seems for some people, this causes problems. I fixed my issue by installing a ROM that (I believe) wiped the webtop. That ROM was deprecated a long time ago so I don't know if it's still available. I'd take a look at the Developer forum. There are some webtop files you can download that reportedly fix the issue. You might also try using fastboot to erase the webtop.
Sent from my MB860 using XDA App
@vibrantuser
Thanks. Yes, I tried flashing and re-flashing couple of times, no luck whatsoever...
@Ilkinansr92
Thanks for the tip. Will try that and see how it goes.
@ronii1123
Will try that this weekend I'll report about progress.
@frelnik
Thanks for the tip. It makes sense as the retail SBF re-flashed the Webtop area and all roms I tried doesn't touch it. I'll try to get a webtop image and flash it using the fastboot or the CWM method. If you can point a link to any that may work, I'll really appreciate it.
Thanks a lot.
I installed the ROM from here to fix my issues. Every ROM thereafter was fine:
http://briefmobile.com/download-android-2-3-4-gingerbread-for-motorola-atrix-4g
I believe I've heard some people had success with the webtop CWM from here:
http://forum.xda-developers.com/showthread.php?t=1169457
I do wonder if erasing the webtop would be enough. You could try
fastboot erase webtop
faux123 said:
Just a quick Info dump:
Just going through the code and realized why SetCPU failed to keep the clock frequencies set properly. SetCPU has NOT been designed to work with dual core properly. It only sets the scaling_max_frequency for cpu0 (master CPU) and not for cpu1 (slave). When under load, cpu1 gets awaken by the system, but it's frequencies are still the old 1.3 GHz and since Tegra2 is a synchronous SMP design, the scaler would use the highest frequency again (this case 1.3 GHz). This is why after playing games, or apps that needed the 2nd cpu would cause the system clock to revert to original default 1.3 GHz even when you set it via SetCPU to something lower.
This is not easy to fix, when SMP is involved. I have tried a few hax already and still unable to tame the 2 headed beast. I will continue to work on it or find an alternative solution to SetCPU's issues
Click to expand...
Click to collapse
quoted from Faux himself, there's a bug in his kernel that prevents us from underclocking it. should be fixed in the next release.
Alcapone263 said:
quoted from Faux himself, there's a bug in his kernel that prevents us from underclocking it. should be fixed in the next release.
Click to expand...
Click to collapse
That's a separate problem, I think. My understanding is that the OP's issue is the CPU is always running at the maximum speed. It never clocks down to the slower speeds when idle. The issue with Faux's kernel and SetCPU is that no matter how you set it, when stressed, the CPU runs at the maximum speed the kernel is capable of, not the speed you set in the app. The CPU does clock down when idle, but will ramp up to 1.3 GHz even if you set it to only 1 GHz in SetCPU. I've experienced both issues.
You have to set it at 800 mhz for it to stick. For some reason setcpu only recognizes under clocking under 1 GHz, otherwise it presumes that it's running at the 1 GHz stock speed without registering the overclock, therefore thinking the stock is 1.3 GHz! I'm not sure but I would have a guess and say that it's something to do with the unchangeable governors? Hope this makes sense lol
Sent from my OC Atrix running homebase 4.7, simplicity themed using xda premium
[SOLVED] CPU not Stepping Down - Warm Phone
frelnik said:
I installed the ROM from here to fix my issues. Every ROM thereafter was fine:
http://briefmobile.com/download-android-2-3-4-gingerbread-for-motorola-atrix-4g
I believe I've heard some people had success with the webtop CWM from here:
http://forum.xda-developers.com/showthread.php?t=1169457
I do wonder if erasing the webtop would be enough. You could try
fastboot erase webtop
Click to expand...
Click to collapse
Hey freinik.
I cleaned up the webtop and reflashed the Home Base rom I was using.
Perfect!
CPU is now scaling correctly. Your suggestions was exactly what was needed.
After cleaning the webtop (using the fastboot erase webtop) the issue was solved.
Thanks a lot.
Think in having the same issue with my international atrix alien rom.
Can you provide clear instructions on how to remove webtop and what will it affect if any by removing it?
Hope you can help.
Sent from my mobile
@ultim
Hi, Thanks for asking.
I erased my webtop using the moto fastboot command line, you can get it here:
http://forum.xda-developers.com/showthread.php?t=1138092&highlight=fastboot
After installing, reboot you phone and enter the "fastboot" mode (holding volume down until the "fastboot" text appears, then press volume up.
Once on fastboot mode, connect your phone to the USB port and run:
moto_fastboot erase webtop
It should erase your webtop partition.
It normaly helps to clean the cache/data, you can do that by running:
moto_fastboot -w
You can then, reboot the phone.
moto_fastboot reboot
If you're using Linux, moto_fastboot should be run as superuser, you can do that by using sudo, ie. sudo moto_fastboot reboot.
Hope this helps.
@Nyx_ Thank you for the instructions. My battery life is so much better now. Before application 'X' (i assume its webtop) would use about a third of my battery all the time.
Thanks for this. I recently discovered the same thing was happening to my phone and deduced that the webtop was causing this. I was using faux's newest kernel. I then related the stock kennel and everything was file after that, no cleaning of the webtop was needed.
Sent from my MB860 using xda premium
Hi all,
Since i'm unable to start a thread in the android development forum I try here. Hopefully Arrrrgh won't get Arrrrgh'd at me for posting this..
I have a problem which I hopefully get support for. I have tried all Android roms for the touch pro2 which none will boot or get past the ACL bootlogo.
I've tried every imaginable way to get it working but all are resulting in a kernel panic. I tried the NAND versions and the SD versions but both options results in the same kernel panic.
First I thought it was the SD formatting problem but after trying 4 different sizes and brands I excluded this as a possible cause.
It seems after looking at it a bit more thoroughly I got a Vario V version of the TP2 - Rhodium 100 (please correct me if i'm wrong)
I'm able to pull logs i'm ready and willing to pass the logs for supporting this device. I've found a similar thread by Z!nk / Z1nk but he gave up on the device before the developers could get to it.
So hopefully there is a developer willing to add this version to the android roms.
Thanks for reading and hope to hear from anyone soon.
Cheers,
Alchedin
[edit] The device has security unlocked and is HSPL'd [/edit]
Alchedin said:
It seems after looking at it a bit more thoroughly I got a Vario V version of the TP2 - Rhodium 100 (please correct me if i'm wrong)
Click to expand...
Click to collapse
How can we correct you if you're wrong - you need to tell us what phone variant you have. There's a surefire way to know as well...
It's kind of the first question in the FAQ...
Either way, the fact that you can't boot either makes me think you have a clone. There was another fellow with a clone (perhaps the one you mentioned?) that was unable to boot XDAndroid because he didn't have the same hardware. If you run HaRET.exe with no startup.txt, what does it say?
Edit - Regardless, I would focus on one build and try to get that to work. FRX07.1 is probably the "simplest" from that perspective.
Edit2 - Also, you seem to indicate it's a kernel panic. Why no logs?
Dear Arrrghhh,
Thanks for replying.
Ok, looking at the faq it states my phone should be a Rhod100 (complete: NM8RHOD100) which seems, when googeling, to be some kind of T-Mobile version. At the moment i'm running a deepshining
I ran the rom without a startup.txt and it gave me the following message: Found machine Rhodium. Hope this is the info you needed?
Placed in the Rhodium100 startup.txt a started haret again, which resulted in a kernel panic.
Will keep you informed since I'm not at home.
Alchedin said:
Placed in the Rhodium100 startup.txt a started haret again, which resulted in a kernel panic.
Click to expand...
Click to collapse
Logs? How do you know it's a kernel panic? What kernels have you tried?
arrrghhh said:
Logs? How do you know it's a kernel panic? What kernels have you tried?
Click to expand...
Click to collapse
Hi Arrrghhh,
Attached are the adb logs, which I hope is the info you need. This is what I get when using FRX07.1 like you advised.
But I have three questions if i'm not too bold:
1. Did you advise this version because it's more thoroughly when it comes to finding a issue?
2. When looking at the logs, is there something wrong with sound or something?
3. I'm able to pull logs of NAND builds if you like? They seem to be more complete when it comes to information on boot.
Cheers,
Alchedin
Today I tried the GBX0C version of XDandroid and this is the first working android on my phone. Boot-animation started and it just worked! Still can't believe it.
Any idea how this rom differs from the FRX07.1?
Cheers
Alchedin said:
Today I tried the GBX0C version of XDandroid and this is the first working android on my phone. Boot-animation started and it just worked! Still can't believe it.
Any idea how this rom differs from the FRX07.1?
Cheers
Click to expand...
Click to collapse
Well there's a few things, besides the whole FroYo vs. Gingerbread. The acoustic code/routing is the 'main' one. Not sure what else off the top of my head, but there's changelogs in the GBX0C thread. There's not a huge difference since some of it was backported to FRX...
Either way, glad GBX is working.
Edit - the logs you posted from the FRX failures don't really give me much to go off of either, unfortunately.
arrrghhh said:
Well there's a few things, besides the whole FroYo vs. Gingerbread. The acoustic code/routing is the 'main' one. Not sure what else off the top of my head, but there's changelogs in the GBX0C thread. There's not a huge difference since some of it was backported to FRX...
Either way, glad GBX is working.
Edit - the logs you posted from the FRX failures don't really give me much to go off of either, unfortunately.
Click to expand...
Click to collapse
Today I tested different kernels using GBX0C and found out the following:
2.6.27.46(original GBX0C) - boots up
2.6.39.3 - boots up - Buttons / keyboard not functioning correctly
3.0.18 - boots up - buttons / keyboard not functioning correctly
3.3.8 - Not booting - Stuck on calibration (message: X & Y the same)
3.4.3 - Not booting - Stuck on calibration (message: X & Y the same)
Hope I did it right, replaced the zimage and module with every kernel switch. Also created a new data.img every time.
Cheers,
Alchedin
Alchedin said:
Today I tested different kernels using GBX0C and found out the following:
2.6.27.46(original GBX0C) - boots up
2.6.39.3 - boots up - Buttons / keyboard not functioning correctly
3.0.18 - boots up - buttons / keyboard not functioning correctly
3.3.8 - Not booting - Stuck on calibration (message: X & Y the same)
3.4.3 - Not booting - Stuck on calibration (message: X & Y the same)
Hope I did it right, replaced the zimage and module with every kernel switch. Also created a new data.img every time.
Cheers,
Alchedin
Click to expand...
Click to collapse
Sounds like for one reason or another, your device is different from all other RHOD's. There seems to be an infinite number of RHOD100 variants, and supporting all of them equally is impossible.
Unfortunately you're going to have to troubleshoot these issues. We don't have a lot of devs left, and without having the device in hand, it makes such development 1,000x harder. Good luck.
arrrghhh said:
Sounds like for one reason or another, your device is different from all other RHOD's. There seems to be an infinite number of RHOD100 variants, and supporting all of them equally is impossible.
Unfortunately you're going to have to troubleshoot these issues. We don't have a lot of devs left, and without having the device in hand, it makes such development 1,000x harder. Good luck.
Click to expand...
Click to collapse
If I supply you with the information you need through video, logs, dmesg, logcat etc. you can implement it correct? Too bad you're in the USA so shipping it will be costly.
Walter79 lives in Germany which country is next to where I live, maybe he can/is willing to extract the required info from the phone? I'm willing to go the extra mile if it helps the whole TP2 community.
Thanks a lot anyway :good:
Cheers,
Alchedin
Alchedin said:
Today I tested different kernels using GBX0C and found out the following:
2.6.27.46(original GBX0C) - boots up
2.6.39.3 - boots up - Buttons / keyboard not functioning correctly
3.0.18 - boots up - buttons / keyboard not functioning correctly
3.3.8 - Not booting - Stuck on calibration (message: X & Y the same)
3.4.3 - Not booting - Stuck on calibration (message: X & Y the same)
Hope I did it right, replaced the zimage and module with every kernel switch. Also created a new data.img every time.
Cheers,
Alchedin
Click to expand...
Click to collapse
Have you tried plugging a known working calibration file into the rom and using the kernels that are giving a calibration error?
Alchedin said:
If I supply you with the information you need through video, logs, dmesg, logcat etc. you can implement it correct? Too bad you're in the USA so shipping it will be costly.
Walter79 lives in Germany which country is next to where I live, maybe he can/is willing to extract the required info from the phone? I'm willing to go the extra mile if it helps the whole TP2 community.
Thanks a lot anyway :good:
Cheers,
Alchedin
Click to expand...
Click to collapse
I would not be a good candidate as I am far from a developer. As I stated previously, we don't really have any devs actively working on the project. walter79 just created the CM build, unfortunately he was not part of the original XDAndroid development team.
Again, your phone seems like it is a one-off, and development efforts for a one-off device are always difficult. I'd say you're going to have to pick up the effort yourself, or be happy with where the development is left at.
wizardknight said:
Have you tried plugging a known working calibration file into the rom and using the kernels that are giving a calibration error?
Click to expand...
Click to collapse
I used the same ts-calibration file that was created during the first boot of gbx0c. Like I stated earlier, I only replaced/removed the zimage, module and data.img file every time I switched kernel.
Should I also re-calibrate every time when switching kernels?
arrrghhh said:
I would not be a good candidate as I am far from a developer. As I stated previously, we don't really have any devs actively working on the project. walter79 just created the CM build, unfortunately he was not part of the original XDAndroid development team.
Again, your phone seems like it is a one-off, and development efforts for a one-off device are always difficult. I'd say you're going to have to pick up the effort yourself, or be happy with where the development is left at.
Click to expand...
Click to collapse
Many thanks for your interest and pointers arrrghhh, I will look into kernel stuff and such, maybe i'll get some of it working :fingers-crossed:
I have little to no development/linux/android skills but I can at least try to learn it.
Cheers
P.S: In a earlier stage playing around with NAND builds I managed to use the boot.img of the CM9-ICS_X1_testbuild1 in combination with the CM7.2 of walter79 and got it running in landscape mode, if this worked for me I can go from there.
Bit by bit i'm getting a hang of it.
Alchedin said:
Should I also re-calibrate every time when switching kernels?
Click to expand...
Click to collapse
No, as I state in all my threads about calibration - once you get a good calibration file, save 15,000 copies of it and re-use it constantly. There's no need to constantly recalibrate.
Ok here we go, sorry for the big read..
I hope I can be as precise as possible. This is about the NAND builds i've tested.
I installed ICS like in my last post again and made a CWM backup of the whole phone.
After this I did a new task29 and reflashed everything till I got back into CWM.
This time I installed the OMGB stable release with the kernelpatch + gapps.(seems the most advised build) Factory reset/data/cache/etc just to be sure.
Rebooted the device and let OMGB do it's thing, thus resulting in a kernel panic - can not sync issue. This is clearly a default message on this phone which I am in peace with. (log1)
Now for the fun part, I had this ICS testbuild backup up earlier and only did a restore of the boot part. Cleared the data/cache/etc again and rebooted.
This time it just boots fine into OMGB... (log2) previous attempts resulted in a landscape layout which i wasn't able to adjust myself, but this time I got the portrait mode correct! The only part which isn't working is the keyboard and hardware buttons.
Seems the "default" startup process is hanging in the part of the AudioFlinger? I compared the 2 logs but I can't see anything really which normally would result in a kernel panic.
Attached are the logs for the default OMGB boot (log1.txt) and the ICS modified boot + OMGB system (log2.txt)
Is this still different from any other Rhod100 or just a small adjustment? If this is really unknown I will break the phone to pieces and give up on it :silly:
I'll keep this config on the phone a bit longer since data and phone is working.
Thanks for reading
Cheers
-No sound
[Update]
Made a finding myself, the problem for my phone lies within the libhtc_acoustic.so removing this file made NAND boot up for the first time on this phone. Now looking for a compatible acoustic replacement which generates sound.
Going to try copying/pushing the file from FRX0.7 to NAND CM7.2 and see what it does. Including replacing my csv's from WinMo in the /system/etc folder.
[Update2]
Installed CM7.2 2.6.27 version today and used the FRX0.7 aucoustic.so, which resulted in a perfectly working android without sound...
now going after the csv's, which I hope gets me sound.
arrrghhh said:
[snip]...
Again, your phone seems like it is a one-off, and development efforts for a one-off device are always difficult. I'd say you're going to have to pick up the effort yourself, or be happy with where the development is left at.
Click to expand...
Click to collapse
I did a bit myself yesterday and today, the problem lies in the libhtc_acoustic.so, removing only this file made nand boot for me finally. See above post.
Alchedin said:
I did a bit myself yesterday and today, the problem lies in the libhtc_acoustic.so, removing only this file made nand boot for me finally. See above post.
Click to expand...
Click to collapse
Hrm, perhaps the new acoustic code jb started and detule 'finished' if you will isn't compatible with your device.
I don't know 'why'... on GBX0C did you copy the CSV's from your phone? I don't know how that build worked for you, because OMGB uses the same acoustic code.
arrrghhh said:
Hrm, perhaps the new acoustic code jb started and detule 'finished' if you will isn't compatible with your device.
I don't know 'why'... on GBX0C did you copy the CSV's from your phone? I don't know how that build worked for you, because OMGB uses the same acoustic code.
Click to expand...
Click to collapse
The interesting parts were the updates I posted. I did copy the csv's from the WinMo earlier, which were instructed by you (using total commander and such), but can't remember if it did produced sound.
But then...
I switched over to NAND CM7.2 by Walter79 and replaced the csv's in the CM7.2 zip file at location /system/etc (audioparatable.csv etc.)
Also I used the libhtc_acoustic.so from here
And ADB pushed the .so into the /system/lib folder.
When running logcat I see that the csv's are used and the audio routing is ok, but still didn't produce sound. Thought there were some other locations were the csv's are stored which I will also replace with mine. But didn't get to that yet.
Just tinkering with files really.. that's as far as I can go since I'm no developer.
What you mean by "perhaps the new acoustic code jb started and detule 'finished' if you will isn't compatible with your device" ?
Alchedin said:
What you mean by "perhaps the new acoustic code jb started and detule 'finished' if you will isn't compatible with your device" ?
Click to expand...
Click to collapse
I don't know how else to phrase that...
Although, I might have misread your statement. I thought you said you replaced a lib from FRX07.1 - which wouldn't boot for you. GBX0C did boot, so it seems the new acoustic code actually helps your phone.
So now I'm not sure what the deal is. I know OMGB uses the new acoustic, and I was under the impression that the CM ROM did as well. Did you try GBX0*? Basically the NAND version of GBX0C.
Hello friends. So I am officially stumped. I have an issue with my kernel bootlooping. The interesting thing is, eventually it boots. After about 5-10 minutes of bootloop, it just boots. Weird right?
See, I merged a lot of code with my kernel and I'm not sure what is causing the bootloop. Here is my source: https://github.com/Snepsts/kernel_e980
It started on the add intelli-plug commit (which also includes intelli-thermal) it is probably important to mention disabling intelli-plug and thermal (and only one of each) all have the same outcome. I have also tried wiping the board back to its original state. I'm assuming its one of the core changes or nr_running changes. But I cannot find any way to get a log of the issue as it is not in a stable state during bootloop to give me logs from adb. I also cannot compile intelli-plug without the changes I made. And I really want to have it. I have looked for code I may be missing but cannot find any. I have made many different test kernels and taken the ramdisk and config from the latest official cm build for my device. Does anybody have any ideas? If you need anymore info please let me know. Thanks for any help in advance.
Sent from my LG-E980 running Carbon KitKat & E980 Kernel+
Hey everyone! Got this thing on a super deal the other day ($50 brand new!) and couldn't pass it up. Naturally the first thing I want to do is tweak and mod it
To be completely honest, I didn't spend much time running stock on it to determine a baseline for battery/performance. I ran for a bit on kitkat and it seemed pretty laggy. With the mods I made it runs very smooth (for good reason, you'll see why).
Battery life seems on par with whatever everyone else is getting (on the short amount of research I did) http://i.imgur.com/vjefGL8.png
Check below to find out what version you should be running.
* download *
http://www.invisiblek.org/dory/kernel/
* install * -- must be OEM unlocked -- be sure to check your current version in settings and pick an image below that matches it
Download a zip from the link above and flash via TWRP (md5sums below)
OR
Download an img from above (md5sums below)
To flash:
Code:
adb reboot bootloader
fastboot flash boot <name of image file>
fastboot reboot
To test: (this doesn't actually flash it, just boots it to try out, simply reboot to get back to whatever kernel/ramdisk you have before)
Code:
adb reboot bootloader
fastboot boot <name of image file>
* changelog *
(img md5sum: 931830de150ca3c3ec83b8355c81abae)
v8 - 12/08/2016 - M1D64S
- [RAMDISK] Updated ramdisk from M1D64S
v7 - 11/16/2016 - M1D64K *** NOT COMPATIBLE WITH PRE-M1D64K ROMS ***
(img md5sum: b7879d15261d08920d0fb2445c08e03e)
- [RAMDISK] Updated ramdisk from M1D64K (so it actually boots with M1D64K). This will effectively make this image unusable on any build prior to M1D64K
- [KERNEL] Hack to force selinux in permissive mode in the kernel. This is necessary for mpdecision to work correctly
v6.1 - 02/22/2016 - MEC23G
(img md5sum: 04cf3b464be402fe3f393d94bb75066d)
- [RAMDISK] CPU governors set back to 'ondemand' until we get kernel source and can add custom governors
v6 - 02/22/2016 - MEC23G
(img md5sum: 96f4b59ea14dc9bf32966b602cffd72e)
- [KERNEL] Pure stock kernel image from google (we have to wait for kernel source)
- [RAMDISK] Merge in MEC23G ramdisk changes
- [RAMDISK] Remove install-recovery.sh service so twrp persists
- [RAMDISK] Fstab: support for either squashfs or ext4-formatted /system partition
- [RAMDISK] Added the necessary bits for systemless root (you can flash the SuperSU zip from Xmaster24's thread before or after the image)
v5 - 11/03/2015 - LCA43
(img md5sum: ab8b4d327682177bdfe984c0897696ff)
(zip md5sum: 02dedf601e47553ea87744cebc76019d)
- [KERNEL] Add adaptive low memory killer
- [RAMDISK] Enable adaptive low memory killer
v4 - 09-01-2015 - LCA43
(img md5sum: ce35db73d354c30b02b95feeaf0e8823)
(zip md5sum: cb6c08bfd1dcd2a12a7985d02fbfa8aa)
- [RAMDISK] Updates from LCA43
- [RAMDISK] Reverted to stock gpu governor/frequencies
v3 - 07-21-2015 - Never announced
(img md5sum: 81d2ee08e4ab2286c4062966a3041f34)
(zip md5sum: f09d69895fe1a47120b99350027690b8)
- [RAMDISK] Used msm-adreno-tz gpu governor and unlocked all frequencies. Never officially released because it wasn't tested too long and didn't really do much anyway.
v2 - 06-06-2015 - Initial 5.1.1 Release
(img md5sum: f5a6a61207968c31a2f0f6bcb84419b9)
(zip md5sum: 4bb6625a97e1ca11f0e03eeb355262b4)
- [KERNEL] Rebased v1 mods on aosp/android-msm-dory-3.10-lollipop-mr1-wear-release
- [RAMDISK] update to 5.1.1 ramdisk
- [RAMDISK] allow cpu to scale above 787mhz
v1 - 04-13-2015 - Initial 5.0.2 Release
(img md5sum: 127c036c629e0171ca64a4ea0b2e33f7)
(zip md5sum: e118f8f76a2b95685ae1e06a4588997f)
- [KERNEL] Based on latest aosp source
- [KERNEL] Compiled with Christopher83's linaro 4.9 toolchain
- [KERNEL] LZ4 compressed kernel
- [KERNEL] Couple MMC tweaks care of arter97
- [KERNEL] Disabled a bunch of debugging
- [KERNEL] maxwen's Smartmax Governor added and set as default after boot (performance gov while booting)
- [KERNEL] Increased vibe intensity care of arter97
- [KERNEL] Several misc security patches
- [RAMDISK] Enable all four cores and add mpdecision to hotplug them (see below for more info). mpdecision kanged from v4xx (g pad 7.0, same soc)
- [RAMDISK] Boot with Performance governor, all four cores and noop i/o scheduler (switch to smartmax/row/mpdecision after boot)
* mpdecision *
mpdecision is a daemon that runs on most (all?) qualcomm chips. Its job is to hotplug cores as they are needed. LG (or google?) forces cores 1-3 off on this device leaving just core 0 to fend for itself and no mpdecision to ever turn these other cores on. While this in theory should save battery life, it also makes your quadcore wrist computer run as a single core. I've taking the mpdecision daemon from the LG G Pad 7.0 (another device I own that has the same chip as the G Watch) and shoved it into the ramdisk so we can do hotplugging. You may ask: "won't this cause battery drain?". My answer is maybe. Since stock is forcing only one core usable, sure it seems like it would take less battery than being able to use all four, but what if everything you did on your device now takes 4 times as long (exaggeration, but say twice as long)? That, to me, could arguably cause more battery drain. In the end, I felt it was something worth trying, and from initial use I don't notice any major additional battery drain, plus the device runs buttery smooth. I've also added the smartmax cpu governor which should keep the frequency down and conserve battery life.
* source *
kernel: https://github.com/invisiblek/android_kernel_lge_dory/tree/invisiblek
ramdisk: https://github.com/invisiblek/dory_ramdisk
will flash in the a.m. glad to see work being done!
this is nice i have ben waiting for a kernel. im getting sick of the notificiation of update. so i was planing to return to stock. but now with a kernel ) yeah.
any one could make a easy noob installer? like the other rom/ kernel have?
So far kernel working great,
Thanks man for you work.
Sent from my SM-G900T using Tapatalk 2
Seems to run hot, also killed battery within only a few hours could be the mpdecision
This is awesome keep up the good work buddy
I'm just waiting on some more thoughts before trying this kernel as I use it extensively throughout the day and night. I have tried 4 cores with Gohma and noticed battery drain, however 2 cores worked great. If options for 2 & maybe 3 cores enabled were possible I would be very interested.
Moguledyouth said:
I'm just waiting on some more thoughts before trying this kernel as I use it extensively throughout the day and night. I have tried 4 cores with Gohma and noticed battery drain, however 2 cores worked great. If options for 2 & maybe 3 cores enabled were possible I would be very interested.
Click to expand...
Click to collapse
The thing is, with the kernel+mpdecision combo, you have 4 cores available, but they're only online if you need them. Just grabbed Gohma and it looks like he's forcing two cores on all the time, where even with the 4 cores available using my method, most often you're only going to have one online.
invisiblek said:
The thing is, with the kernel+mpdecision combo, you have 4 cores available, but they're only online if you need them. Just grabbed Gohma and it looks like he's forcing two cores on all the time, where even with the 4 cores available using my method, most often you're only going to have one online.
Click to expand...
Click to collapse
but would it be possible to have a version that has only 2 cores available? I am just curious if that would be possible, so that it's core1 on always and core2 comes on as necessary?
Moguledyouth said:
but would it be possible to have a version that has only 2 cores available? I am just curious if that would be possible, so that it's core1 on always and core2 comes on as necessary?
Click to expand...
Click to collapse
It probably is possible, but why would you want to? The watch will only use all four kernels when needed, and you likely aren't using your watch for any serious computing, so I doubt all four cores will be engaged for more than a second or two at a time.
Apoplectic1 said:
It probably is possible, but why would you want to? The watch will only use all four kernels when needed, and you likely aren't using your watch for any serious computing, so I doubt all four cores will be engaged for more than a second or two at a time.
Click to expand...
Click to collapse
Thanks for the info, I'll give this a shot tomorrow and put it through one of my average day's use and update here this weekend on my personal experience.
So I installed this kernel yesterday afternoon, I did notice a significant battery drain vs arter kernel. I use the tilt to wake feature and noticed that with this kernel the slightest arm movement was turning the screen on thus draining the battery faster.
More disturbingly, I now have found this morning that I can no longer connect to my watch through adb at all. I am still trying to figure out if I can get this back to any state where I can even connect to my watch at this point!
**Update** I was able to get back into fastboot mode manually using the pinout method, which enabled me to install the arter97 kernel again. After a reboot my watch connected to my computer as it normally should and adb registered my device again.
On the tilt to wake constant false responses, I know this sounds strange, but could this kernel be too fast and that is why it is turning on as much as it is or maybe some values can be changed to alter that? I'm not a developer by any means, so I do not know what is and isn't controlled or can be manipulated directly in the kernel. Also I'm not sure what needs to be fixed in the kernel to get proper adb support, but at least for me, the arter97 kernel has it but this one seems to need something.
Moguledyouth said:
More disturbingly, I now have found this morning that I can no longer connect to my watch through adb at all. I am still trying to figure out if I can get this back to any state where I can even connect to my watch at this point!
Click to expand...
Click to collapse
odd. i am able to connect via ADB with no problem.
drewski_1 said:
odd. i am able to connect via ADB with no problem.
Click to expand...
Click to collapse
Same here
Sent from my SM-G900T using Tapatalk 2
Hey, this seems interesting and promising! And since Ghoma does not update his ROM in the near future from what I heard (sadly) I hope this will be a great replacement.
I'll report how it went in a few days if I'm not so stupid to forget about this ;P (I know myself far too well, heh)
Awsome kernel man, i gat 3.5 days
Battery life is good man thanks for this gift.
Sent from my SM-G900T using Tapatalk 2
gavilan2010 said:
Awsome kernel man, i gat 3.5 days
Battery life is good man thanks for this gift.
Sent from my SM-G900T using Tapatalk 2
Click to expand...
Click to collapse
What are some of your settings for your watch (such as always on or tilt to wake)?
lyrical1278 said:
What are some of your settings for your watch (such as always on or tilt to wake)?
Click to expand...
Click to collapse
Screen off tilt to wake...yup yup
Sent from my SM-G900T using Tapatalk 2
For some reason when having this kernel installed and using the latest version of the Android Wear app on your smartphone new apps won't sync to the watch.
I now restored to stock with the Restore Tool and now it'll sync again but is laggy as hell again
EpicLPer said:
For some reason when having this kernel installed and using the latest version of the Android Wear app on your smartphone new apps won't sync to the watch.
I now restored to stock with the Restore Tool and now it'll sync again but is laggy as hell again
Click to expand...
Click to collapse
Yeah it does sync, but now u dont have the notification on your pull down notification background saying smartwatch is connected. U can open android wear and u will see is connected.
Sent from my SM-G900T using Tapatalk 2