I think that this error needs no intorduction for POLA100 users who tried running latest Android kernels using Haret.
It also seems that this error is caused by the double vibration at the beginning of boot process and was solved once by paipo (see this post) by commenting out the vibration part and rebuilding. But those kernel is outdated and misses some latest features and fixes.
So I did the same as paipo but with the latest kernel from the git repository (as of 19.07.2010, revision d5d0a56fae6df779443a82e2d90b7ec8097cb332). zImage is attached to this post. I'll try to update the kernel from time to time.
Please, note that the attached kernel image is optimized for Eclair (CONFIG_ECLAIR=y in .config or System Type/Android Optimization is set to Eclair in make menuconfig).
And yes, you can do it yourself. Just follow the guide in the second post
Disabling the vibration and rebuilding the kernel yourself
So how do you do this?
First of all, follow the steps 1 to 4 of Building kernel For Vogue, Kaiser, and Polaris part from this guide to prepare your building environment.
Now you need to open the arch/arm/mach-msm/board-htcpolaris.c file in your favourite text editor.
Search for vibrate word (it was line 1019). You'll see something like this:
Code:
// vibrate
for (i=0; i<2; i++) {
while(msm_proc_comm(PCOM_VIBRA_ON,0)==-EAGAIN);
mdelay(150);
while(msm_proc_comm(PCOM_VIBRA_OFF,0)==-EAGAIN);
mdelay(75);
}
Remove this part or replace with the following:
Code:
// vibrate
// for (i=0; i<2; i++) {
// while(msm_proc_comm(PCOM_VIBRA_ON,0)==-EAGAIN);
// mdelay(150);
// while(msm_proc_comm(PCOM_VIBRA_OFF,0)==-EAGAIN);
// mdelay(75);
// }
As you can see, all lines now start with two slashes.
Now follow step 5 from the guide, mentioned above. You'll see a menu.
Go to System Type and select Android Optimization accroding to your needs. Then select Exit, than again Exit, then Yes.
Now follow step 6 from the guide. This will take some time. At the end you should see:
Code:
Kernel: arch/arm/boot/zImage is ready
Copy zImage from arch/arm/boot folder to \Storage Card\andboot folder on your device and use it
I update this option in the kernel.
Now double vibration is disable by default.
You are great !!!
leppa said:
I think that this error needs no intorduction for POLA100 users who tried running latest Android kernels using Haret.
...
Please, note that the attached kernel image is optimized for Eclair (CONFIG_ECLAIR=y in .config or System Type/Android Optimization is set to Eclair in make menuconfig).
And yes, you can do it yourself. Just follow the guide in the second post
Click to expand...
Click to collapse
YOU ARE GREAT !!!
THANKS A LOT A LOT A LOT !!!
THIS EVENING I WILL TRY SURELY !!!!!!!
Only a question: Optimized for Eclair is equal to Optimize to FROYO ?
Can I use your zImage to Froyo RLS 11 ?
Thanks in advance.
Bye
This flag now do nothing, so it's indifferent
GGGGGGGGGGGGGGRRRRRRRRRRRRRRRRRREEEEEEEEEEEEEEEEEAAAAAAAAATTTTTTT !!!!!!
I Have Just tested zImage in attached files.
Froyo seems better reactive, more smooth and rock stable.
Thanks a lot ...
When Video Playback will be solved... I will flash immediately Froyo to give a new life to my Cruise!!!
Thanks thanks thanks!
@foxct2005 : you can flash it month ago!
All these problems are only for haret!
l1q1d said:
I update this option in the kernel.
Now double vibration is disable by default.
Click to expand...
Click to collapse
This change isn't yet in the git repository, is it?
I was thinking about how to make this option available to any user without having to recompile the kernel. And came up with the idea of the new kernel parameter. So I added board-htcpolaris.no_boot_vibration parameter.
The attached kernel images work as they did before - with double vibration on boot and "waiting for notbusy" error. To disable the double vibration (and get rid of the error) add board-htcpolaris.no_boot_vibration=1 to default.txt so this line:
Code:
set cmdline "board-htcpolaris.panel_type=1 ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51"
will look like this:
Code:
set cmdline "board-htcpolaris.panel_type=1 [COLOR="Red"]board-htcpolaris.no_boot_vibration=1[/COLOR] ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51"
Adding this parameter is mandatory if you suffer from "waiting for notbusy" error.
big thanks for that patch!
I started a new try with android and my polaris yesterday but froyo doesn't work (with haret). Now with this patch it work and even booting and boot logo is much faster on my Pola200! Great! Thanks!
leppa said:
I was thinking about how to make this option available to any user without having to recompile the kernel. And came up with the idea of the new kernel parameter. So I added board-htcpolaris.no_boot_vibration parameter.
Click to expand...
Click to collapse
Good idea!
I have long think why developers not added it to the cmdline.
Thank you, thank you, thank you..
I almost sold my Polaris in despair that this problem will never get fixed..
DmK75 said:
Good idea!
I have long think why developers not added it to the cmdline.
Click to expand...
Click to collapse
I think, they have much more other, more serious, things to do
michasch said:
big thanks for that patch!
I started a new try with android and my polaris yesterday but froyo doesn't work (with haret). Now with this patch it work and even booting and boot logo is much faster on my Pola200! Great! Thanks!
Click to expand...
Click to collapse
nikiiv said:
Thank you, thank you, thank you..
I almost sold my Polaris in despair that this problem will never get fixed..
Click to expand...
Click to collapse
You're welcome
If this patch gets upstream, we will not need to rebuild the kernel every time a new build comes out. I already posted it in the Polaris Android Linux Kernel Development Project thread.
thanks leppa,
i tried the froyo one, but for me doesn't work. last days i used the last dzo one, it worked for 2 or 3 days, and now doesn't work again. the only zimage that works is the 29-04 one, but my battery doesn't like it so much
loscassapalle said:
thanks leppa,
i tried the froyo one, but for me doesn't work.
Click to expand...
Click to collapse
What do you mean by that? Do you still get "waiting for notbusy" error?
If yes, did you add the kernel parameter board-htcpolaris.no_boot_vibration=1?
If no, than I can't help, cause this is the only thing I changed in the kernel.
leppa said:
What do you mean by that? Do you still get "waiting for notbusy" error?
If yes, did you add the kernel parameter board-htcpolaris.no_boot_vibration=1?
If no, than I can't help, cause this is the only thing I changed in the kernel.
Click to expand...
Click to collapse
maybe is not my problem...i can't see an error string, the problem is the animation at the start that never end.
loscassapalle said:
maybe is not my problem...i can't see an error string, the problem is the animation at the start that never end.
Click to expand...
Click to collapse
Then this is some other problem. Cause "waiting for notbusy" error occurs almost at the very beginning of the boot process (while text is running, before even "Hold down Volume Up or DPad..." message).
How long do you wait? At first boot the animation may run for five and even more minutes. Try reinstalling from scratch (i.e., wiping system and data partitions).
leppa said:
Then this is some other problem. Cause "waiting for notbusy" error occurs almost at the very beginning of the boot process (while text is running, before even "Hold down Volume Up or DPad..." message).
How long do you wait? At first boot the animation may run for five and even more minutes. Try reinstalling from scratch (i.e., wiping system and data partitions).
Click to expand...
Click to collapse
i checked now, i also have this string that you said (now i'm using the froyo image you uploaded in 8# post).
the animation problem is strange. the zimage of 29-4 works, the animation ends in a few seconds, but the battery life is very short. the last dzo zimage worked for a couple of days, then i had the same problem after a softreset...and this one is the same...
EDIT: now it works... lol
loscassapalle said:
i checked now, i also have this string that you said (now i'm using the froyo image you uploaded in 8# post).
Click to expand...
Click to collapse
I didn't test the Froyo image, cause I'm playing with Eclair. Does it vibrate on start? It shouldn't or you forgot to put the kernel parameter.
loscassapalle said:
EDIT: now it works... lol
Click to expand...
Click to collapse
So, it started working?
leppa said:
I didn't test the Froyo image, cause I'm playing with Eclair. Does it vibrate on start? It shouldn't or you forgot to put the kernel parameter.
So, it started working?
Click to expand...
Click to collapse
i don't know how to edit the zimage...but now it works...i didn't change anything...
loscassapalle said:
i don't know how to edit the zimage...
Click to expand...
Click to collapse
You don't need to. I was talking about editing default.txt as I described in post 8.
Related
Hello all
I've been using haret method to boot android on a Pola100 device for a long time. Until now, I've never had problems at all with this kind of booting. With recent kernels, it has stopped working and now I can't boot android anymore.
After pressing "Run" in haret, the phone makes a double vibration and screen turns off inmediately. The phone get stucked at this step and I need to recover it by removing battery.
I'm using Myn's Warm Donut with latest kernel from dzo repository (only FAT partition in my SD card) and default.txt with panel=1.
Do you know any solution for this issue?
Thanks in advance
Hi,
I've also problems with the newest DZO kernels. I found a solution for me.
I use panel=3 (230x320) with the kernel 23-06-2010. This works perfectly on my XDA Orbit 2.
I don't know how, but now it works. I'm using panel=1 and new kernel (20100623)
@osilvan
... Which device have you ?
I see that no problem with Pola200, but with Pola100 as mine .... same problem.
Or Double vibrate and shoutdown; or "error for not busy".
Anyone with pola100 can post his default.txt and Zimage ?
Thanks a lots.
Regards.
I have a pola100, as soon as I return home I'll post my default.txt. But the problem is a bit strange because I've no changed my default.txt since it stopped working, and now suddenly it begins to work again.
osilvan said:
I have a pola100, as soon as I return home I'll post my default.txt. But the problem is a bit strange because I've no changed my default.txt since it stopped working, and now suddenly it begins to work again.
Click to expand...
Click to collapse
Please post also your zImage, so I could try your identical configuration.
Thanks !
My kernel is zImage-23-06-10 from dzo repository: http://cs-alb-pc3.massey.ac.nz/vogue/files/?C=M;O=D
osilvan said:
I have a pola100, as soon as I return home I'll post my default.txt. But the problem is a bit strange because I've no changed my default.txt since it stopped working, and now suddenly it begins to work again.
Click to expand...
Click to collapse
Thanks again to DZO!
Issues in boot corrected in new zImage-25-06-10
My kernel is zImage-23-06-10 from dzo repository: http://cs-alb-pc3.massey.ac.nz/vogue/files/?C=M;O=D
Nothing to do :-(
DmK75 said:
Thanks again to DZO!
Issues in boot corrected in new zImage-25-06-10
Click to expand...
Click to collapse
Both 25/06/10 and 23/06/10 zImage
In my Pola100 I have always double vibration and "error waiting for not busy" , android starts after a lot of time, and Ask me for kill process or wait.
Nothing has changed for me :-(
WHY ????
I have downloaded 25.06.2010 twice: once at 7.00(UMT), then in 13.00(UMT). First gave me double vibe, second runs well now. I have change nothing in configs, so maybe there were some changes between my two downloads, try download kernel again.
And, thanks dzo!
idreadful said:
I have downloaded 25.06.2010 twice: once at 7.00(UMT), then in 13.00(UMT). First gave me double vibe, second runs well now. I have change nothing in configs, so maybe there were some changes between my two downloads, try download kernel again.
And, thanks dzo!
Click to expand...
Click to collapse
I downloaded the file right NOW ... some minutes ago ... :-(
is it possible to you upload in this thread the WORKING version of file ?
Can you post it ?
Thanks a lots.
In any case ... I ask to Paipo to customize latest kernel for us....
foxct2005 said:
I downloaded the file right NOW ... some minutes ago ... :-(
is it possible to you upload in this thread the WORKING version of file ?
Can you post it ?
Thanks a lots.
In any case ... I ask to Paipo to customize latest kernel for us....
Click to expand...
Click to collapse
I get these errors with 23-06-10 and more earliest, but with 25-06-10 is booting normal.
Already 3 bootup passed.
DmK75 said:
I get these errors with 23-06-10 and more earliest, but with 25-06-10 is booting normal.
Already 3 bootup passed.
Click to expand...
Click to collapse
I tried also your zImage posted ...
... DOUBLE VIBE and SAME ERROR.
Maybe I had to change my default.txt ???
Maybe it's a rom (WinMo) problem ?
Maybe it's not caused from zImage ?
But... Why Paipo zImage works and the other not ?
Maybe can be Useful to zip and post ALL andboot folder (except big files:androidinstall, data and system)... including initdr, default.txt, haret.exe ....
... I need to understand why I have this problem.
Thanks in advance...
:-(
foxct2005 said:
I tried also your zImage posted ...
... DOUBLE VIBE and SAME ERROR.
Maybe I had to change my default.txt ???
Maybe it's a rom (WinMo) problem ?
Maybe it's not caused from zImage ?
But... Why Paipo zImage works and the other not ?
:-(
Click to expand...
Click to collapse
There is my startup.txt:
#alloctest 0x2000
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz
set cmdline "board-htcpolaris.panel_type=1 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51 hw3d.version=1"
boot
foxct2005 said:
is it possible to you upload in this thread the WORKING version of file ?
Can you post it ?
Click to expand...
Click to collapse
Here are my files.
idreadful said:
Here are my files.
Click to expand...
Click to collapse
Idreadful your basefile are "wrong".
In your DEFAULT.TXT you recall the last kernel working ("set KERNEL zImage-29-04-10"").
Infact if you edit your default and set for last kernel (of today) always the same history: double vibe, error and no start android.
:-(
I am sorry
foxct2005 said:
Idreadful your basefile are "wrong".
In your DEFAULT.TXT you recall the last kernel working ("set KERNEL zImage-29-04-10"").
Infact if you edit your default and set for last kernel (of today) always the same history: double vibe, error and no start android.
:-(
I am sorry
Click to expand...
Click to collapse
Yup. You are right, my mistake. Sorry...
foxct2005 said:
I tried also your zImage posted ...
... DOUBLE VIBE and SAME ERROR.
:-(
Click to expand...
Click to collapse
Yes, i also getting these errors again...
But i found out, need run Haret.exe as soon possible after reboot.
Then i getting a 100% boot without errors.
Hi,
I've found a solution for my XDA Orbit 2.
Sometimes I've also the problem with the boot from sdcard. With all sdcards.
Than I must short remove the battery an than tthe boot is okay.
But only with kernel 23-06-2010. All newer kernels don't boot correctly.
I don't know why...
I have tried both Incubus26jc's Super Froyo (RLS8) and VaniljEclair RLS7c . I manage to install them in sd card (I want to use them via haret.exe) but when I reach the welcome screen where I have to touch the android to continue, the screen does not respond ( D-pad and center button work). Could someone help me? I decided to open a new thread because of what I have searched, I found only one member with a similar (but not the same) problem
The installation method I follow is this (mostly copied from a SuperJMN's post):
1º Run HaRET
2º From the installer, select Install System
3º Choose install update (if any)
4º Choose to fix permissions (if there had been an update)
5º Reset (don't select "Quit", just reset, this is to avoid problems)
6º Wait for Windows Mobile to start and run HaRET again.
Although I am flashing to nand and you are using haret/zimage, we may have the same problem with the unified touch screen driver that DZO implemented around 16 June. Is there is a way to use the kernel .nbh and system .tar with haret, rather than zimage? If so, you might try using an older kernel from before 16 June ... or perhaps an older zimage.
I have similar problem, if not the exactly the same. Using an older kernel seems to be a workaround of this problem. hxxp://forum.xda-developers.com/showpost.php?p=7041656&postcount=21 (You need to fix the hxxp as appropriate as I am not allowed to link URL yet)
i have the similar problem too, havent fixed it :/
I tried zImage-12-06-10 (the last one before the 16th of June) and installation procedure did not even start. But zImage-29-04-10 worked for me. However, Froyo is not that fast. If I change any files (zImage or something else) is it possible to have a speed improvement?
Same problems.
All Android realeases work on my pola100 only with zImage 29.04.10.
No work with other kernel.
I suggest to developers to analyse 29.04.10 and try to understand WHY this works and others no.
Regards.
regarding screen response, panel and changes on kernel module for touchscreen please see this post from dzo
also check this for solution from k_k
HTH
mensa07 said:
regarding screen response, panel and changes on kernel module for touchscreen please see this post from dzo
Click to expand...
Click to collapse
Those are the changes after which my touchscreen stopped working.
mensa07 said:
also check this for solution from k_k
Click to expand...
Click to collapse
It would be nice if this worked for the Polaris ... how would I change the value of this parameter before flashing the kernel? Thanks!
tmcfarland said:
Those are the changes after which my touchscreen stopped working.
It would be nice if this worked for the Polaris ... how would I change the value of this parameter before flashing the kernel? Thanks!
Click to expand...
Click to collapse
you can use terminal or adb to change the value
files for a fast android version
Could someone with a fast and stable version of eclair or froyo please tell us what files did he/she used to make that happen because I installed incubus froyo build and it is a bit slow? I am talking about installing it in my sd card and run it using haret.exe
I did dirty hack: insert msleep(1) after each input thread synchonization in mcs6000 driver.
Now hack is not dirty, just found that driver has native implementation of "sleep".
Result: 15-30% cpu use with tap down.
Included all tweaks from GNM OC Kernel.
Packaged in koush's anykernel for compatibility with any rom.
Do not forget to make nandroid backup first.
Probably fixed "scroll bug".
v1.1: added pressure sensitivity (works correctly only for single touch because of our touchscreen).
Link: http://www.mediafire.com/?li7aviy6awdebs5
Sources: https://github.com/mik9/ThunderG-Kernel
I triwd to flash it,but when i flash i have error,one file isn't in the zip
Redownload. I updated zip few minutes ago.
Do i need to clean all my data, or i only need to flash the Kernel?
Got errors while flashing the zip.
Code:
E:Wrong digest: META-INF/com/google/android/updater-script
E:Verification failed
Installation aborted.
RevengeFNF said:
Do i need to clean all my data, or i only need to flash the Kernel?
Click to expand...
Click to collapse
No. Only apply kernel.zip via recovery (that flash new kernel).
domenic_s said:
Got errors while flashing the zip.
Code:
E:Wrong digest: META-INF/com/google/android/updater-script
E:Verification failed
Installation aborted.
Click to expand...
Click to collapse
Ok, so i need to sign it. Will fix this in a few minutes.
it does not work, just tried to flash in custom recovery, it says missing something. turned off verification and again the same problem.
mik_os said:
No. Only apply kernel.zip via recovery (that flash new kernel).
Ok, so i need to sign it. Will fix this in a few minutes.
Click to expand...
Click to collapse
i have this problem please fix it thank
ok did post it too late haha hope that u have done a great step mike thx for everything
Updated link in first post.
About unsigned zip files
You can flash unsigned zips. In the recovery menu just select Other -> Toggle Signature Verify. It will disable this verify.
About this hack. It's working. BUT the scroll works buggy now. For example, you cannot make the contacts menu scroll from the beginning to the end fast now
I flashed it...and hey: IT WORKS. Well done mik_os.
//edit: just recocknized the bugs on scrolling...that sucks.
kashtancheg said:
You can flash unsigned zips. In the recovery menu just select Other -> Toggle Signature Verify. It will disable this verify.
About this hack. It's working. BUT the scroll works buggy now. For example, you cannot make the contacts menu scroll from the beginning to the end fast now
Click to expand...
Click to collapse
I would not say that it became too buggy, only a little bit (very little). And maybe you have too much contacts in youe contact list
nope it works really nice here mik thx alot for fixing this
unbelievable, it works!
miki, is it possible insert some double or something with float value? I mean if it is possible do less that 1 millisecond? For example msleep(0.5)? It will be faster for scrolling, but will not do loop on touch.
//Edit:
It should be possible... http://www.handyboard.com/oldhb/software/icmanual/node86.html
//Edit2:
or maybe use usleep(microsecond)
We can't use usleep in kernel level code because it is libc function. And msleep accept only integer (int/long).
Genius things are always simple! The bug wich couldn't be solved for 3 years!
Mik, I think you should work in google
NFS Shift runs perfectly now when applying the brake!
kashtancheg said:
Genius things are always simple! The bug wich couldn't be solved for 3 years!
Mic, I think you should work in google
NFS Shift runs perfectly now when applying the brake!
Click to expand...
Click to collapse
The bug in our phone is not related to famous bug in android issue tracker. And my hack is little bit crappy
Mik os you are a god XD thank you for this kernel work very very good
This should probably be posted here, but I sadly don't have the required 10 posts to do so.
There's one issue that I noticed that is actual in 0.2.2alpha. When you choose to flash Jhinta 3.1x kernel and not 2.6x kernel, it is still linux.img that is being flashed, instead of jlinux.img.
Also there's one question (or rather a feature request). Once you have dual boot up and running it would be nice to be able to flash linux rootfs only (ubuntu.img) without changing the partition table and loosing current android install. You can't currently do that with Tubuntu, right?
Best regards,
Alex
Serkenar said:
This should probably be posted here, but I sadly don't have the required 10 posts to do so.
There's one issue that I noticed that is actual in 0.2.2alpha. When you choose to flash Jhinta 3.1x kernel and not 2.6x kernel, it is still linux.img that is being flashed, instead of jlinux.img.
Also there's one question (or rather a feature request). Once you have dual boot up and running it would be nice to be able to flash linux rootfs only (ubuntu.img) without changing the partition table and loosing current android install. You can't currently do that with Tubuntu, right?
Best regards,
Alex
Click to expand...
Click to collapse
hi!
that will be on my next release cause i flash my tubuntu image so much. i'm trying to push out a backup menu along with that new rootfs option
x3maniac said:
hi!
that will be on my next release cause i flash my tubuntu image so much. i'm trying to push out a backup menu along with that new rootfs option
Click to expand...
Click to collapse
Hi,
I'm really glad to hear that! Looking forward to the next Tubuntu release
I'd also like to ask to include cifs kernel module in your kernel build.
Thank you
Serkenar said:
Hi,
I'm really glad to hear that! Looking forward to the next Tubuntu release
I'd also like to ask to include cifs kernel module in your kernel build.
Thank you
Click to expand...
Click to collapse
new version is up with Flash rootfs only :laugh:
future release of kernel i will put cifs. right now i'm trying to get zram and overclocking right 1st.
lol i feel like a one man operation. make the program to flash ubuntu images, didn't find one i liked. so i went ahead and made one. feel that the kernel is missing too much stuff. and went ahead and i'm making that now lol... am i missing anything else i need to learn/do? hahahaha
but i'm loving it!
thanks for the support
x3maniac said:
new version is up with Flash rootfs only :laugh:
future release of kernel i will put cifs. right now i'm trying to get zram and overclocking right 1st.
lol i feel like a one man operation. make the program to flash ubuntu images, didn't find one i liked. so i went ahead and made one. feel that the kernel is missing too much stuff. and went ahead and i'm making that now lol... am i missing anything else i need to learn/do? hahahaha
but i'm loving it!
thanks for the support
Click to expand...
Click to collapse
Thank you for your effort
Speaking about your own kernel, I tried compiling one from Jhinta source, but I received odd errors at boot time. First it was this kind of errors:
lists.litmus-rt.org/pipermail/litmus-dev/2012/000215.html
it was suggested there to try changing CONFIG_DEVTMPFS_MOUNT kernel config value, I did that, and then I got some other odd errors, so I gave up
Right now I have a more or less stable 12.04 kubuntu+3.10.1 jhanti kernel with hw acceleration, sound, zram (used netinstall 0.6). I'm only missing overclocking and a cifs module, that's why I tried building my own kernel, but never got it booting. I don't know any sane methods of backing up and restoring linux on tf101 (well, dd + gzip should work, but that's rather stupid), so I'm a little hesitant about flashing your lubuntu right now. I think I'll still give it a go, but before I do that, don't you know any easy way to back up my current linux install?
Thank you
Serkenar said:
Thank you for your effort
Speaking about your own kernel, I tried compiling one from Jhinta source, but I received odd errors at boot time. First it was this kind of errors:
lists.litmus-rt.org/pipermail/litmus-dev/2012/000215.html
it was suggested there to try changing CONFIG_DEVTMPFS_MOUNT kernel config value, I did that, and then I got some other odd errors, so I gave up
Right now I have a more or less stable 12.04 kubuntu+3.10.1 jhanti kernel with hw acceleration, sound, zram (used netinstall 0.6). I'm only missing overclocking and a cifs module, that's why I tried building my own kernel, but never got it booting. I don't know any sane methods of backing up and restoring linux on tf101 (well, dd + gzip should work, but that's rather stupid), so I'm a little hesitant about flashing your lubuntu right now. I think I'll still give it a go, but before I do that, don't you know any easy way to back up my current linux install?
Thank you
Click to expand...
Click to collapse
i'm now compiling from his source. for the 3.1.10 kernel i'm using. why try to reinvent the wheel? i just recompiled and added oc and cifs, i didn't run into any compile issues but i did run into boot issues so changing the kernel to compress with lzmo instead of gzip fixed it. hope that helps
Thank you for your work on this
x3maniac said:
i'm now compiling from his source. for the 3.1.10 kernel i'm using. why try to reinvent the wheel? i just recompiled and added oc and cifs, i didn't run into any compile issues but i did run into boot issues so changing the kernel to compress with lzmo instead of gzip fixed it. hope that helps
Click to expand...
Click to collapse
x3maniac I was wondering if you have ever checked out openELEC linux. They just pushed out a new version on Distrowatch and it looks like it will have support for ARM devices. It is very lightweight at 106mb and is made to run XBMC out of the box. Might be worth a try due to its size and media streaming abilities.
Thanks
thelangosta said:
x3maniac I was wondering if you have ever checked out openELEC linux. They just pushed out a new version on Distrowatch and it looks like it will have support for ARM devices. It is very lightweight at 106mb and is made to run XBMC out of the box. Might be worth a try due to its size and media streaming abilities.
Thanks
Click to expand...
Click to collapse
thanks for the info. i will look into it, i do have a arch linux version working with 3.1 which is only about 200mb.
edit:
they have a arm version 83mb! lols
Cool
x3maniac said:
thanks for the info. i will look into it, i do have a arch linux version working with 3.1 which is only about 200mb.
edit:
they have a arm version 83mb! lols
Click to expand...
Click to collapse
Wow that is small. I have seen Roms that small but never an os. Wait, is that openELEC or Arch you are talking about.
On another note if I do end up getting around to trying your method with arch which desktop would you recommend?
Thanks
thelangosta said:
Wow that is small. I have seen Roms that small but never an os. Wait, is that openELEC or Arch you are talking about.
On another note if I do end up getting around to trying your method with arch which desktop would you recommend?
Thanks
Click to expand...
Click to collapse
openelec(rasbery pi)
if you want it to look nice then enlightment e17. for a light weight DE they make it very pretty with all the effects like compiz
or lxde
x3maniac said:
i'm now compiling from his source. for the 3.1.10 kernel i'm using. why try to reinvent the wheel? i just recompiled and added oc and cifs, i didn't run into any compile issues but i did run into boot issues so changing the kernel to compress with lzmo instead of gzip fixed it. hope that helps
Click to expand...
Click to collapse
Compression was already set to lzma. I can't figure out what I was doing wrong. Yet, you're right, no point to reinvent the wheel.
I see you've recently released your Lubuntu V1.1-rc1. The specs sound great! Could you please post the rootfs download link and also post your kernel img?
Thank you for the great work you're doing!
Serkenar said:
Compression was already set to lzma. I can't figure out what I was doing wrong. Yet, you're right, no point to reinvent the wheel.
I see you've recently released your Lubuntu V1.1-rc1. The specs sound great! Could you please post the rootfs download link and also post your kernel img?
Thank you for the great work you're doing!
Click to expand...
Click to collapse
the link to image and kernel is up. http://forum.xda-developers.com/showthread.php?t=1995157
x3maniac said:
the link to image and kernel is up. http://forum.xda-developers.com/showthread.php?t=1995157
Click to expand...
Click to collapse
I gave it a go First of all, Tubuntu flashes .\images\linux.img when choosing to flash "2.6x x3maniac kernel", I assume it should flash .\images\xlinux.img
That's not a big issue, but should be fixed
A quick list of things I noticed.
1. Things that work:
-1.2 GHz OC
-Usb mouse (when plugged before system boots, otherwise not - that's due to 3.1.10 kernel, I guess)
-cifs module
-chromium
-terminal (right clicking on your tf101linux gadget -> Shortcuts -> Terminal)
-screen brightness up/down buttons. You just have to be mindful to avoid turning the screen off this way - it won't turn on afterwards and you'll have to force reboot.
-ntfs read/write
2. Things that don't work:
-touchpad
-XF86poweroff button
-System Tools -> XTerm/UXTerm
-sound: Audacious complains "ALSA error. No suitable mixer element found. snd_mixer_find_selem failed". Gnome MPlayer just won't produce any sound, and youtube html5 videos too.
-plugging in an external usb drive. It's totally ignored. A pen drive doesn't even blink, nor the drive appears in /dev it works now. It didn't during initial launch. Don't know why, but a reboot cured this.
Also, it happens quite often that system freezes for no apparent reason and only force reboot helps. It happened twice with me already, although it's been less then an hour since I flashed lubuntu.
Tell me if you need some additional info
Regards
Serkenar said:
I gave it a go First of all, Tubuntu flashes .\images\linux.img when choosing to flash "2.6x x3maniac kernel", I assume it should flash .\images\xlinux.img
That's not a big issue, but should be fixed
A quick list of things I noticed.
1. Things that work:
-1.2 GHz OC
-Usb mouse (when plugged before system boots, otherwise not - that's due to 3.1.10 kernel, I guess)
-cifs module
-chromium
-terminal (right clicking on your tf101linux gadget -> Shortcuts -> Terminal)
-screen brightness up/down buttons. You just have to be mindful to avoid turning the screen off this way - it won't turn on afterwards and you'll have to force reboot.
-ntfs read/write
2. Things that don't work:
-touchpad
-XF86poweroff button
-System Tools -> XTerm/UXTerm
-sound: Audacious complains "ALSA error. No suitable mixer element found. snd_mixer_find_selem failed". Gnome MPlayer just won't produce any sound, and youtube html5 videos too.
-plugging in an external usb drive. It's totally ignored. A pen drive doesn't even blink, nor the drive appears in /dev it works now. It didn't during initial launch. Don't know why, but a reboot cured this.
Also, it happens quite often that system freezes for no apparent reason and only force reboot helps. It happened twice with me already, although it's been less then an hour since I flashed lubuntu.
Tell me if you need some additional info
Regards
Click to expand...
Click to collapse
i love your report! keep up the good work. this helps me narrow down the problems but without a dock i can't fix some of the issues. but try this
touchpad:
edit /etc/X11/Xorg.conf
Code:
Section "InputClass"
MatchIsTouchpad "on"
Identifier "Touchpads"
Driver "mtrack"
EndSection
should fix the touchpad issue.
i will look into fixing my script for the brightness issue. located int /usr/local/bin/tfbright
what were you doing when you freeze? i don't have a dock(still waiting for it in the mail) so i don't know if it's related to that.
i've been looking at nvidia git and downloaded there source for the linux4tegra kernel. it' compiled fine but wont boot. don't know why yet
x3maniac, I know it is off topic a bit but I just wanted to mention that I appreciate your attitude towards your work and especially criticism (aka feedback) from others about your work. Reminds me of my EVO 4G days running tommytomato's classic rom. His threads were always friendly and optimistic, much like your own.
Sent from my SPH-L710 using Tapatalk 2
x3maniac said:
i love your report! keep up the good work. this helps me narrow down the problems but without a dock i can't fix some of the issues. but try this
touchpad:
edit /etc/X11/Xorg.conf
Code:
Section "InputClass"
MatchIsTouchpad "on"
Identifier "Touchpads"
Driver "mtrack"
EndSection
should fix the touchpad issue.
i will look into fixing my script for the brightness issue. located int /usr/local/bin/tfbright
what were you doing when you freeze? i don't have a dock(still waiting for it in the mail) so i don't know if it's related to that.
i've been looking at nvidia git and downloaded there source for the linux4tegra kernel. it' compiled fine but wont boot. don't know why yet
Click to expand...
Click to collapse
Strange, but there's no /etc/X11/xorg.conf
I tried creating it with `Xorg :1 -configure`, but I get "No devices to configure. Configuration failed."
I also tried creating /etc/X11/xorg.conf with the following content
Code:
Section "InputClass"
MatchIsTouchpad "on"
Identifier "Touchpads"
Driver "mtrack"
EndSection
but touchpad wont' work.
Like I said, there appears to be no apparent reason for those freezes The only things they had in common are the following:
(as far as I can remember)
-I had a cifs share mounted
-pen drive was plugged in
-chromium was opened
I understand that isn't helpful at all, but atm I can't reproduce those freezes myself. They occur kind of randomly.
I hope linux4tegra kernel does boot after all
Thank you for your work
EDIT: 30 minutes without freezes, I hope they're gone for good! :laugh:
djlenoir said:
x3maniac, I know it is off topic a bit but I just wanted to mention that I appreciate your attitude towards your work and especially criticism (aka feedback) from others about your work. Reminds me of my EVO 4G days running tommytomato's classic rom. His threads were always friendly and optimistic, much like your own.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
+1 Totally agree
djlenoir said:
x3maniac, I know it is off topic a bit but I just wanted to mention that I appreciate your attitude towards your work and especially criticism (aka feedback) from others about your work. Reminds me of my EVO 4G days running tommytomato's classic rom. His threads were always friendly and optimistic, much like your own.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Serkenar said:
+1 Totally agree
Click to expand...
Click to collapse
as far as i see it, you guys are helping me get a working version. user/tester are as important as the devs making them. or else dev's would be out of the job. lols that's how i see it
I let lubuntu running and it froze smth like 20 minutes ago Without me doing anything. Chromium was running, pen drive plugged in and a cifs share mounted.
I'll leave it running without a pen drive plugged in, shares mounted and chromium running to see if it freezes eventually.
Serkenar said:
I let lubuntu running and it froze smth like 20 minutes ago Without me doing anything. Chromium was running, pen drive plugged in and a cifs share mounted.
I'll leave it running without a pen drive plugged in, shares mounted and chromium running to see if it freezes eventually.
Click to expand...
Click to collapse
i'm guessing jhanti's kernel is not stable. i was starting to use it more and got a random freeze. cpu1 went to sleep and wont wake up. looking into that.. i might just take nvidia's kernel 3.1.10 and try to get that working.
3.0
given up using peoples dirty code, so downloaded nvidias dirty code instead lol
cleaned the code up best i could, things ive noticed while playing games on the tablet is -
when i play "nitro nation" the first race no longer stutters
when popups appear they dont take a while to appear..
when i play "word mind" it doesnt take ages to load with crackling sound
when using "kernel auditor" if you set the GPU max and min values high (i only did this trying to keep the values standard), when the GPU gets hot, it cant scale down the GPU frequency so it starts trying to kill tasks.
i dont think you need to download/flash blobs as they are for flashing binary stuff, but i cant find a need for it, think its more of a precaution to ensure the kernel boots.. but dont think i have flashed them
-----------------------------------------------------------------------------------------
3.1 : FINAL,
dunno what changes i made but ive recently upgraded my tablet so figured id upload my latest and last
obveously i have had to start again running 3.10.96 but done alot of work to make it as fast as i can so far, but i deleted all references to my old code and cant find them anymore,
GPU is now at 914 MAX as ive found its the GPU that generates a lot of heat, which causes it to throttle, and found values higher than this just degraded performance.
ive known for a long time that "DT2W" works great while connected to USB, due to the custom USB wakelock, i know the app "wakelock revamp - power manager" would resolve it. but ive found tapping where "notifications" would be wakes the screen (ive found bottom right where the camera would be is a good spot) im trying to figure out how to apply the wake lock better.
scores on PCMARK are above the scale on most values
scores on 3DMARK are around 3250 ~ 3320
=========================================
if you want to create your own, i created a guide, also the website i used to help me understand
https://************/how-to-build-android-kernel-on-windows-10/ appuals . com
-----------------------------------------------------------------
Thanks to :
-----------------------------------------------------------------
"hazel nut" for his support, as if he never said "cant wait for it to come out" i dont think it would of pushed me so much
----------------------------------------------------------------
"BitOBSessiOn" for his source code
https://github.com/BitOBsessiOn/android_kernel_nvidia_shieldtablet
-----------------------------------------------------------------
"laufersteppenwolf" for his source code and commits to overclocking and DT2W/STW
https://github.com/laufersteppenwolf/android_kernel_nvidia_shieldtablet
-----------------------------------------------------------------
"Christopher83" for his cross compiler
https://github.com/Christopher83/arm-cortex_a15-linux-gnueabihf-linaro_4.9
-----------------------------------------------------------------
Microsoft, if i didnt hate windows 10 so much, and didnt get a message regarding dropping support for windows 7,
i would still be using a virtual machine which due to it being so slow, i would of probably given up a long time ago
----------------------------------------------------------------
thanks to everyone that has said thank you
Nice to see that you open a thread.
Appreciate a bit companionship here.
In your guide didn't you specify how you create thr zip file.
I used the nethunter installer, which is based on lazy flashed in regard of the external modules, this come in handy, but I found relatively little among the Shield kernel support.
I noticed that you set the make command with the addition of the specifications of the number of CPUs, which are to be used, before every command.
Is this a typo, or is this the correct procedure when you compile with Windows?
Did you mean with
"bin-bash-command"
Click to expand...
Click to collapse
-
cd ~
Click to expand...
Click to collapse
?
PS
1
response
That's just how I make the command, as if you tap the up key, you can scroll through previous inputs, if it makes it faster- that's a bonus.. but you're right about being very little support.
With regards to the zip file - you could use mine or any other zip that is a kernel flash - as long as you drop it into the kernel folder.. I believe there is an "anykernel.zip" somewhere if you prefer to use that.. also if you wish to add your own personal touch, you can modify the script file in the metadata folder
Response
I also chose different colours in the guide and placed it in a separate line so people could understand the exact typing.. or they could copy and paste..
But with regards to support it is one of the reasons I made the guide, in hopes the Nvidia community could follow it, understand how to achieve their own kernel, and improve the tablet. As there seems to be a serious lack of support..
I had to learn on my own, through Google and YouTube, but hopefully this will speed up what took me a month of trial and error..
Is it compatible with stock based fw (5.4)? Just need to flash blobs, then kernel and reboot?
Respond
Yeah, extract the blobs before flashing.. only available for stock/stock+ rom
Reply
Oh, by the way, you can’t compile with windows unless you’re using a virtual machine.. has to be Linux/terminal
Bleeblun said:
Yeah, extract the blobs before flashing.. only available for stock/stock+ rom
Click to expand...
Click to collapse
Thank you, I will try out as soon as I can get to my computer. I have downloaded the wakelock v3 app and kernel adiutor an I can't enable wakelock in kernel adiutor (I can't see any option for it). Only this new kernel will support this option, am I right?
Reply
attom93 said:
Thank you, I will try out as soon as I can get to my computer. I have downloaded the wakelock v3 app and kernel adiutor an I can't enable wakelock in kernel adiutor (I can't see any option for it). Only this new kernel will support this option, am I right?
Click to expand...
Click to collapse
You must of done something wrong as “wake” is below “gpu”
You extract> then flash the blob at the fastboot menu via typing - fastboot flash staging <blobfilename>
Then via TWRP recovery you install the “OC K1” kernel without extracting.. I have 3 tablets and it’s worked on them all.. hope this helps,
Bleeblun said:
You must of done something wrong as “wake” is below “gpu”
You extract> then flash the blob at the fastboot menu via typing - fastboot flash staging <blobfilename>
Then via TWRP recovery you install the “OC K1” kernel without extracting.. I have 3 tablets and it’s worked on them all.. hope this helps,
Click to expand...
Click to collapse
Yeah, everything worked, awesome, thank you!!
Response
attom93 said:
Yeah, everything worked, awesome, thank you!!
Click to expand...
Click to collapse
Thanks for letting me know, originally you wouldn’t of needed the “wake v3” app, but I started fresh, which gained performance, and I decided to look for an easier way to stop the tablet “deep sleeping” on me.. less of a headache this way :laugh: