Related
For some reason My Files folder won't work. It's not showing in my app drawer. I can find it with FolderOrganizer and make a shortcut but I get "error while launching activity" error. Any ideas?
I have 2.1, Baseband ver. I897UCJH7, kERNEL VER. 2.6.29 [email protected] #2, Build # Bugless Beast Teaser .UCJF6: p.ucjf6
Rooted and Unlocked.
I can't say for certain, but I thought I had gotten into the My Files after the update and Unleash the Beast.
I am noob on the case, I wonder am I at the right direction? any hint?
Q1: I can see my baseband by: Settings > About Phone > Baseband version (which report 1035.21_20110502, and yes I am on 502, from 218 stock using the fls)
Correct?
Q2: I can check my RIL by terminal
# su
# getprop gsm.version.ril-impl
getprop gsm.version.ril-impl
android lge-ril 1.0
(this is the part I am confused, is it correct? at all? I am on CM ROM nighty .46, and kernel from vorkKernel-OC/UV Kernel for CM[080611] http://forum.xda-developers.com/showthread.php?t=1059910 , I think I misses the parts of -flags when I flash the kernel, do I/should I reflash the kernel with flags on?)
Thanks!
Only way to check RIL that I know of would be to md5sum /system/lib/lge-ril.so and compare the value with known ones.
Rusty! said:
Only way to check RIL that I know of would be to md5sum /system/lib/lge-ril.so and compare the value with known ones.
Click to expand...
Click to collapse
Really thanks for the quick reply, will do that, but the problem is where do I find out the md5 of others to be compare?
any idea? thanks
Don't think there is a list anywhere, but you could download and DIY them.
Rusty! said:
Don't think there is a list anywhere, but you could download and DIY them.
Click to expand...
Click to collapse
Thanks, thinks I need to try to build a list...
here is a list of what I can find right now.....
lge-ril.so from CM nighty .46 md5: a43da11417c610829fdacddf96253a86
lge-ril.so from 502 md5: 572e907a2a67e9a908c6d038e9515572
lge-ril.so from 405 md5: 24ddcf4bee64be465de8a11756d78980
lge-ril.so from 606 md5: 91cabc9690e6deb4650d87e147e50929
lge-ril.so from 10c_may_coda_spain md5: 9d3400ef9fab0f4cc6ac92aa5b63e0d3
As the title says this patch is for updating the Samsung sources from version 2.6.35.7 to 2.6.35.14. Might be useful for some kernel developers. I was stuck at bootloop after updating the initramfs.cpio with the updated modules, but this has nothing to do with the patch itself. If wanted I can also upload the original incremental patches.
I hope this gets integrated in some kernels soon (I heard others expermented with this as well), as it will fix the Android OS bug.
Regards,
Diewi
Diewi said:
As the title says this patch is for updating the Samsung sources from version 2.6.35.7 to 2.6.35.14. Might be useful for some kernel developers. I was stuck at bootloop after updating the initramfs.cpio with the updated modules, but this has nothing to do with the patch itself. If wanted I can also upload the original incremental patches.
I hope this gets integrated in some kernels soon (I heard others expermented with this as well), as it will fix the Android OS bug.
Regards,
Diewi
Click to expand...
Click to collapse
Hey man,
Thanks, I need this
You can teach me howto make patches for kernels?
How to patch up the kernel for example? You are just legend
Netchip
Hey netchip,
of course I can
First you need to run this command for every incremental patch:
BZIP compressed:
Code:
bzip2 -dc patch-2.6.35.X-Y.bz2 | patch -p1
uncompressed:
Code:
patch -p1 < patch-2.6.35.X-Y.patch
The X stands for the minor version you already have, Y for the one you want to patch to - usually Y = X + 1 for "official" patches.
After every application of a incremental patch you need to check weather a "hunk" failed. Normally, this happens if you get a warning about parts of the patch already being applied. You will recognize the failed parts by their ending: .rej. You'll need to check those files against the to-be-patched source file and maybe do some changes to it.
After you gone through all patches, unpack the unmodified kernel again and compare both directories with the following command:
Code:
diff -uNrB GT-N7000_Kernel_orig GT-N7000_Kernel > SGN_2.6.35.X-Z.patch
Then you'll get a patch that includes all the single ones.
BTW, I'm assuming you're in a UNIX environment.
(@all)
In order to apply the patch you can simply take the commands listed in the beginning of the post. The patch uploaded in the OP (.7-.14) is uncompressed.
I'll just attach the incremental patchset for completeness (bzip compressed patches)
Diewi said:
Hey netchip,
of course I can
First you need to run this command for every incremental patch:
BZIP compressed:
Code:
bzip2 -dc patch-2.6.35.X-Y.bz2 | patch -p1
uncompressed:
Code:
patch -p1 < patch-2.6.35.X-Y.patch
The X stands for the minor version you already have, Y for the one you want to patch to - usually Y = X + 1 for "official" patches.
After every application of a incremental patch you need to check weather a "hunk" failed. Normally, this happens if you get a warning about parts of the patch already being applied. You will recognize the failed parts by their ending: .rej. You'll need to check those files against the to-be-patched source file and maybe do some changes to it.
After you gone through all patches, unpack the unmodified kernel again and compare both directories with the following command:
Code:
diff -uNrB GT-N7000_Kernel_orig GT-N7000_Kernel > SGN_2.6.35.X-Z.patch
Then you'll get a patch that includes all the single ones.
BTW, I'm assuming you're in a UNIX environment.
(@all)
In order to apply the patch you can simply take the commands listed in the beginning of the post. The patch uploaded in the OP (.7-.14) in uncompressed.
I'll just attach the incremental patchset for completeness (bzip compressed patches)
Click to expand...
Click to collapse
Thanks for your answer
Where can I get normally the incremental patches?
Kernel.org?
Also, if you are interested in building a kernel with me, send me a PM, and I will answer
Sent from my GT-I9100
Yes, usually at kernel.org. But lately they are only hosting the latest incremental patch for the longterm support kernels (2.6.32 and 2.6.33). Also the latest incremental patches (up to 4 minor versions in the past) for the latest kernel.
These particular patches I found using google that directed to some outdated mirrors. I just needed to adapt the version numbers of the patch and search for this string.
While waiting for my Note, I just have downloaded kernel sources and my linux box is cross compiling the sources with the recommended toolchain (4.4.0) as I write this post
I just noticed that the process reports quite a few warnings...
When I have my Note, I will try a few things like undervolt (already located the bit of relevant code for this) and will add "interactive" CPU governor which is far better than the default "on demand" for interactivity.
If everything goes well, I will add this upgrade too
Edit:
right. Done. Waiting for the phone to test this first almost stock kernel
Code:
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
Diewi said:
As the title says this patch is for updating the Samsung sources from version 2.6.35.7 to 2.6.35.14.
Click to expand...
Click to collapse
Have you tested the Patch? Which toolchain did you use for compiling the Note Kernel?
I have tried it the other way around: Take vanilla 2.6.35.14 sources and include the Samsung patches from 2.6.35.7. I found out, that Samsung uses a lot of Backports in his code. Also I had some problems with wrong applied fuzzy patches.
Meanwhile it works. Android OS is much lower with a 2.6.35.14 Kernel. But the battery lifetime is not much longer than before.
I had also some problems with the Runtime Powermanagement of USB Devices. I'm note sure if it was a problem of the patches or my compiler options. I have to test a little bit in the next days.
RiverSource said:
Have you tested the Patch? Which toolchain did you use for compiling the Note Kernel?
I have tried it the other way around: Take vanilla 2.6.35.14 sources and include the Samsung patches from 2.6.35.7. I found out, that Samsung uses a lot of Backports in his code. Also I had some problems with wrong applied fuzzy patches.
Meanwhile it works. Android OS is much lower with a 2.6.35.14 Kernel. But the battery lifetime is not much longer than before.
I had also some problems with the Runtime Powermanagement of USB Devices. I'm note sure if it was a problem of the patches or my compiler options. I have to test a little bit in the next days.
Click to expand...
Click to collapse
Dunno if it's making a huge difference, but your GCC is 4.5.4 whereas the recommended is 4.4.0
Code:
> cat Readme_Kernel.txt
################################################################################
1. How to Build
- get Toolchain
From android git server , codesourcery and etc ..
- arm-eabi-4.4.0
No, the Toolchain makes no big difference. I hoped the newer Linaro one optimzes better, but at least with CF Bench there was no big difference between 4.4.0, 4.4.3 or 4.5.4 (the results where slightly better than with stock kernel, 13300 points in stead of 13000 with stock).
RiverSource said:
Have you tested the Patch? Which toolchain did you use for compiling the Note Kernel?
I have tried it the other way around: Take vanilla 2.6.35.14 sources and include the Samsung patches from 2.6.35.7. I found out, that Samsung uses a lot of Backports in his code. Also I had some problems with wrong applied fuzzy patches.
Meanwhile it works. Android OS is much lower with a 2.6.35.14 Kernel. But the battery lifetime is not much longer than before.
I had also some problems with the Runtime Powermanagement of USB Devices. I'm note sure if it was a problem of the patches or my compiler options. I have to test a little bit in the next days.
Click to expand...
Click to collapse
How did you have included samsung drivers in a vanilla kernel?
I know now how to patch up, but how works your way?
No, I didn't test the patch very well. I just compiled the kernel with the patches and added CF's initramfs.cpio (packed) to the zImage file. It did boot up, but wlan didn't work, as the modules in the initramfs were not compiled for this build. The "about" page showed the minor version ".14".
I used codesurgery version 2010.09.51 for this test.
@netchip:
I found a good guide how to extract the samsung specific patches in this thread (bottom of OP):
http://forum.xda-developers.com/showthread.php?t=784270
Maybe we see a 3.1 kernel soon
Diewi said:
No, I didn't test the patch very well. I just compiled the kernel with the patches and added CF's initramfs.cpio (packed) to the zImage file. It did boot up, but wlan didn't work, as the modules in the initramfs were not compiled for this build. The "about" page showed the minor version ".14".
I used codesurgery version 2010.09.51 for this test.
@netchip:
I found a good guide how to extract the samsung specific patches in this thread (bottom of OP):
http://forum.xda-developers.com/showthread.php?t=784270
Maybe we see a 3.1 kernel soon
Click to expand...
Click to collapse
You have a dump of vanilla 2.6.35.7?
Compare these, and you have the drivers, hmm I go try.
Or you could use the patched Samsung kernel (2.6.35.14) and compare this to the vanilla kernel. I'm absolutely not sure if this would bring any benefits, but I think that way the patches backported by Samsung would get filtered out.
Sent from my GT-N7000 using XDA App
Diewi said:
Or you could use the patched Samsung kernel (2.6.35.14) and compare this to the vanilla kernel. I'm absolutely not sure if this would bring any benefits, but I think that way the patches backported by Samsung would get filtered out.
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
That's also a good idea!
Thanks.
The patched vanilla kernel (.14) can be found here:
http://ftp.ua.postgresql.org/pub/linux/kernel/v2.6/longterm/v2.6.35/
The 2.6.35.7 vanilla kernel can be found directly on the ftp server of kernel.org
Diewi said:
Hey netchip,
of course I can
First you need to run this command for every incremental patch:
BZIP compressed:
Code:
bzip2 -dc patch-2.6.35.X-Y.bz2 | patch -p1
uncompressed:
Code:
patch -p1 < patch-2.6.35.X-Y.patch
The X stands for the minor version you already have, Y for the one you want to patch to - usually Y = X + 1 for "official" patches.
After every application of a incremental patch you need to check weather a "hunk" failed. Normally, this happens if you get a warning about parts of the patch already being applied. You will recognize the failed parts by their ending: .rej. You'll need to check those files against the to-be-patched source file and maybe do some changes to it.
After you gone through all patches, unpack the unmodified kernel again and compare both directories with the following command:
Code:
diff -uNrB GT-N7000_Kernel_orig GT-N7000_Kernel > SGN_2.6.35.X-Z.patch
Then you'll get a patch that includes all the single ones.
BTW, I'm assuming you're in a UNIX environment.
(@all)
In order to apply the patch you can simply take the commands listed in the beginning of the post. The patch uploaded in the OP (.7-.14) is uncompressed.
I'll just attach the incremental patchset for completeness (bzip compressed patches)
Click to expand...
Click to collapse
thanks!!
i'm build galaxy s2 kernel
i hope patch 2.6.35.7 to 2.6.35.14
no problem at use Incr_PatchSet_2.6.35.7-14.zip file?
and SGN_2.6.35.7-14.patch.zip better than Incr_PatchSet_2.6.35.7-14.zip?
(sorry my bad english)
As you are trying to apply the patch to a s2-kernel, I would advise you to use the original incremental patchset. You only need to go through the *.rej files and check weather the source needs a modification (see http://linuxhaven.de/dlhp/HOWTO/DE-Kernel-HOWTO-5.html). The all-in-one patch is made by a diff of the original and the patched Galaxy Note kernel, so you might miss something.
Diewi said:
As you are trying to apply the patch to a s2-kernel, I would advise you to use the original incremental patchset. You only need to go through the *.rej files and check weather the source needs a modification (see http://linuxhaven.de/dlhp/HOWTO/DE-Kernel-HOWTO-5.html). The all-in-one patch is made by a diff of the original and the patched Galaxy Note kernel, so you might miss something.
Click to expand...
Click to collapse
successful upgrade to 2.6.35.14
thanks
Dude... Will this work on Galaxy y ?? or this is device specific ????
Nachiket.Namjoshi said:
Dude... Will this work on Galaxy y ?? or this is device specific ????
Click to expand...
Click to collapse
No.
Sent from my GT-N7000 using Tapatalk 2
I'd like to try the CloudOn office suite app out on my Touchpad, however when I find it on the Play Store it says none of my devices are compatible.
Is it a hardware or software issue?
16GB Touchpad
Android Ver: 4.0.3
Kernal Ver: 2.6.35-palm-tenderloin, [email protected] #12
CM Ver: 9.0.0-RC0-Touchpad-alpha2
Build Date: Mon Feb 20
Build No: IML74K
purplegreendave said:
I'd like to try the CloudOn office suite app out on my Touchpad, however when I find it on the Play Store it says none of my devices are compatible.
Is it a hardware or software issue?
16GB Touchpad
Android Ver: 4.0.3
Kernal Ver: 2.6.35-palm-tenderloin, [email protected] #12
CM Ver: 9.0.0-RC0-Touchpad-alpha2
Build Date: Mon Feb 20
Build No: IML74K
Click to expand...
Click to collapse
I couldn't get the app to come up in the playstore either.
Make a backup,,just in case, and try updating to the latest CM nightly http://forum.xda-developers.com/showthread.php?t=1568685, it's been stable for me. The Feb version you're running is outdated. You should notice the improvement.
I just updated to the latest nightly, and there's definitely some improvement!
I found a CloudOn apk and installed it, ran through the set up process, and when that was done it said the version I had was no longer supported.
I can't find a newer apk anywhere, any ideas where I might source it?
purplegreendave said:
I just updated to the latest nightly, and there's definitely some improvement!
I found a CloudOn apk and installed it, ran through the set up process, and when that was done it said the version I had was no longer supported.
I can't find a newer apk anywhere, any ideas where I might source it?
Click to expand...
Click to collapse
+1 please
Enviado desde mi Nexus 7 usando Tapatalk 2
This thread is a bit old, but I found the apk for the latest CloudOn 2.5.1 (November 3rd) and it works great on the Touchpad. It scales perfectly to the display aspect ratio and for being a glorified remote desktop app it does a pretty good job at feeling like a native app. At least with this you get 100% Office compatibility since your using Microsoft Office, although they have changed the ribbons a bit to make it more touch friendly.
For free this app is a bargain, its great for quick edits when you want to preserve formatting. I've attached the apk for you so you can install it since Google Play still won't let us install.
People are already recieving their units.
Every other wear prior to this one so far has had roms made directly by goog, I dont expect this is any different.
TheManii said:
Android wear runs, well android.
I would like to request that someone that has a wear to dump the rom that is preinstalled on it, and to make note if there it prompts for an ota on first setup.
I don't know how to enable adb on it, but I would expect that it would be available, for the moment merely doing a
Code:
adb pull /system
will be as much as anyone can expect.
In the event it actually supports fastboot, I'd also like to request a
Code:
fastboot get-var all
Click to expand...
Click to collapse
Here's a guide on enabling adb on wear, it's not specific to any one device:
[How-To] Android Wear: Enable Debugging, Take Screenshots, Unlock The Bootloader, And Root The LG G Watch
You won't be able to root it however for the time being, you need a custom recovery specifically for your device.
I don't know if there's an OTA out yet or not, but I would not be surprised if there is/will be one soon.
Please make note of if you got an ota if you upload a dump.
TheManii said:
People are already recieving their units.
Every other wear prior to this one so far has had roms made directly by goog, I dont expect this is any different.
Here's a guide on enabling adb on wear, it's not specific to any one device:
[How-To] Android Wear: Enable Debugging, Take Screenshots, Unlock The Bootloader, And Root The LG G Watch
You won't be able to root it however for the time being, you need a custom recovery specifically for your device.
I don't know if there's an OTA out yet or not, but I would not be surprised if there is/will be one soon.
Please make note of if you got an ota if you upload a dump.
Click to expand...
Click to collapse
Hi ill try and do this later this evening when i get home. I have a lot of meeting so wont be until later so if someone is going to beat me to it go for it!
when i want to pull the system..
command line is giving error: more than one device and emulator..i have managed to link the watch to localhost:4444
doki81 said:
when i want to pull the system..
command line is giving error: more than one device and emulator..i have managed to link the watch to localhost:4444
Click to expand...
Click to collapse
U trying to adb over blue tooth?
im dumping the system now. give me some time to upload
Sent from my GT-I9505 using XDA Premium 4 mobile app
---------- Post added at 06:50 PM ---------- Previous post was at 06:36 PM ----------
system dump
W110_4.4W.2_System_Dump.zip - 206.78 MB
Hawke84 said:
system dump
W110_4.4W.2_System_Dump.zip - 206.78 MB
Click to expand...
Click to collapse
Thanks, did you have any otas before getting this? I assume there is one but I need confirmation.
Also, what is the bootloader version? Most reliable way is to check in fastboot mode.
TheManii said:
Thanks, did you have any otas before getting this? I assume there is one but I need confirmation.
Also, what is the bootloader version? Most reliable way is to check in fastboot mode.
Click to expand...
Click to collapse
yeah had 1 OTA
Hawke84 said:
yeah had 1 OTA
Click to expand...
Click to collapse
Could you check the bootloader version and kernel version?
The kernel version can be found with:
Code:
adb shell cat /proc/version
TheManii said:
Could you check the bootloader version and kernel version?
The kernel version can be found with:
Code:
adb shell cat /proc/version
Click to expand...
Click to collapse
Linux version 3.10.0-g7326b80 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Thu Oct 9 17:43:04 PDT 2014
---------- Post added at 07:19 PM ---------- Previous post was at 07:15 PM ----------
Hawke84 said:
Linux version 3.10.0-g7326b80 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Thu Oct 9 17:43:04 PDT 2014
Click to expand...
Click to collapse
Is it same kernel as original g watch? I'm wondering if we can use the same root exploit
Sent from my GT-I9505 using XDA Premium 4 mobile app
No they're not the same kernel:
android / kernel/msm / android-msm-dory-3.10-kitkat-wear
android / kernel/msm / android-msm-lenok-3.10-kitkat-wear
lenok's kernel is currently newer then sprat's.
I cant tell you what you can do with the differences, I assume it's a matter of waiting for a custom recovery to be ported.
How long ago have you updated your gwar? If it was very recent, could you do an "adb bugreport" and post that?
If it's recent enough it may still have the ota details inside.
TheManii said:
No they're not the same kernel:
android / kernel/msm / android-msm-dory-3.10-kitkat-wear
android / kernel/msm / android-msm-lenok-3.10-kitkat-wear
lenok's kernel is currently newer then sprat's.
I cant tell you what you can do with the differences, I assume it's a matter of waiting for a custom recovery to be ported.
How long ago have you updated your gwar? If it was very recent, could you do an "adb bugreport" and post that?
If it's recent enough it may still have the ota details inside.
Click to expand...
Click to collapse
i was about a week ago, havent read the log yet
http://d-h.st/0hq
Hawke84 said:
i was about a week ago, havent read the log yet
Click to expand...
Click to collapse
Thanks for uploading it, but it's been too long and it's not in there.
Also: android / kernel/msm / android-msm-dory-3.10-kitkat-wear
I had the wrong repo, dory is the gwa and lenok is the gwar.
Sprat is the gear live, the same conclusion is drawn however: lenok is still newer then dory as far as kernels go.
TheManii said:
Also: android / kernel/msm / android-msm-dory-3.10-kitkat-wear
I had the wrong repo, dory is the gwa and lenok is the gwar.
Sprat is the gear live, the same conclusion is drawn however: lenok is still newer then dory as far as kernels go.
Click to expand...
Click to collapse
as far as i can tell (and im not a dev) the toolkit to root the original g watch uses an insecure custom kernel to allow for root access so we need a kernel dev or something good with compiling from source to build for g watch r
Request 4.4W.1 Rom
would be great if someone could manage to pull the original rom the LGWR comes with
the update to 4.4W.2 introduces a nasty bug that no longer updates the time every minute in ambient mode
(someone still running 4.4W.1 and able to confirm the bug isn't there?)
I learned about this too late and immediately updated my watch on arrival
I still need a dump of KIW52H if anyone still has an unupdated gwar
Cool, dev talk. Well here is my progress. I used the pulled boot.img someone posted here amd I made it insecure and I compiled the insecure boot.img. i am calling it a night but will work on it more this week when I have more time. Although it looks promising.
I also have looked at the oroginal lg g watch tweaks made and think i know how to boost the vibration setting on our device.