G Pad 8.3 Lines on screen with NON Stock Kernels.. topic

Hi everyone, ive had my g pad 8.3 for about 6 months and the whole time i have had this problem intermittently only when using a custom Kernel or Kernel/Rom..

I get a horizontal line (or 2, also sometimes at different heights on the screen) what looks like dead/stuck Green pixels, but the lines/pixels usually move with the graphic/picture they are sitting on..

I dont think its actually a hardware problem as a Screenshot reveals the problem, also i have NEVER seen this screen problem while in Recovery, or during Boot, Also it has never happened while on the stock Kernel..

It happened while i was on Stock V20D rom with AIC gamma fix Kernel, its happening now on adrianom's AOSP Lollipop Rom (which i REALLY want to stay on!!..)

Ive tried different stock firmware base's (V20A,B,D) also different TWRP versions before flashing, i ALWAYS fully wipe when flashing new roms..

Sometimes it can go perfect for a week, other times it happens every day (a reboot fixes it for a while)

Im out of ideas! Hopefully someone else has had this issue and knows what the cause is, please see my screenshot and video.. Thanks in advance.

https://www.youtube.com/watch?v=5Rzea_W37P8

https://www.dropbox.com/s/v3bqep2omj...17-25.png?dl=0
View the above Screenshot in full size to see the problem.

By: dd On 13:42

Continue Reading

[Q] Compiling kernel's tun.ko module topic

Hello: I'm very new at this. I'm trying to compile tun module for my android kernel.
To do this: I've install Debian 7 on second partition hard disk as a second OS. (I am a Window user).
After that, I've updated my Debian libraries and install SDK tools and NDK toolchains from Developers Android. Also I have the kernel's source for my cell phone kernel from code aurora. I have configured ADB and manage to pull the config.gz of my phone.
I get the cross compiling action and that I need to set a path in bashrc in Debian to set my environment. Here is where I get stuck.
This would be the path in bashrc file, right?:

Code:

---

PATH=$PATH:~/android/ndk/android-ndk-XX-linux-x86/toolchains/arm-linux-androideabi-XXXXX/prebuilt/linux-x86/bin

---

But when I'm in /toolchains directory of /android-ndk-r10d-linux-x86 directory I see three directories/folders: arm-linux-androideabi-4.6, arm-linux-androideabi-4.8 and arm-linux-androideabi-4.9.
Which one of the three folders should I set the path?
There are others directories: Image attached. But I don't think the rest of them are meant for my cell phone android kernel.
This is my kernel: Linux localhost 2.6.35.7-perf-CL700532 #1 PREEMPT Wed Nov 2 01:11:19 kst 2011 armv61 GNU/Linux. And my cell phone: Samsung Galaxy Fit GT-S5670L
Any light over this WILL BE VERY MUCH APPRECIATE!!

By: dd On 16:03

Continue Reading

[Q] Read the Sticky, still can't flash stock or lollipop kernels topic

I wonder whether there is help for someone who thought he knew how to flash a kernel but apparently is deluded. I have the original nexus seven Wi-Fi tablet android version 4.3 build number JWR66V. The system still wants to update me to 4.3 because I ripped some files out of the cache directory to prevent OTA updates. I have both fastboot and adb. I have read the stickies about flashing.

The phone is rooted and the bootloader is unlocked. I use TWRP custom recovery, and it's a good thing, because I solidly bricked myself up just trying to get my lollipop. I know there are tools to root a nexus seven even with stock lollipop, so I thought I'd upgrade my phone to stock lollipop and then use one of those methods. I tried both the stock lollipop kernel and the one provided by chain fire, which I understand is rooted already. (I'm assuming upgrading to lollipop will lose me my root, unless I want to recover back to 4.3.)

I tried to do these things a couple of different ways. When I tried fast boot, I got the message "error: neither -p product specified nor ANDROID_PRODUCT_OUT set". There was a YouTube video suggesting how to deal with this error message. I'm pretty sure I followed the instructions but no go. (I was using the "flash all" command.) This was after I had put the file containing lollipop in the directory, both zipped and unzipped (so that I had an .img file instead of a zip file). I tried using both the zip file with all of the lollipop partitions and the system image file individually. No go. I also had a message that android-info.txt could not be found, even though it was in the same, working directory.

I could be wrong but I don't think you can install a complete updated kernel from a file on the device. I think that works only with update.zip.

I'm still thinking fastboot is my best bet, but there are dependencies apparently and I don't know what files to include in its directory. Then, am I wise to go to stock and then root, or should I simply flash the stock kernel already rooted? I assume that's what chainfire is providing, correct?

I notice the lollipop official ROM nor Chainfire’s supposedly-rooted image have any file named nakasi. I have only .img files, no .zip files.

I found a dozen sets of instructions on how to flash a kernel but something I need is missing from all of them. Does anyone know what it is or can anyone offer some helpful advice?

Thank you,

Leon M.

By: dd On 16:58

Continue Reading