yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Fenix46:
Hi guys ... I have read all the theard, and I see that the work stop all on display, I have downloaded the source of [MENTION=4443334]Grarak[/MENTION] https://github.com/Fenix46/grakernel-tuna-3.4, I have a build the kernel without error, turn on the terminal, pauses 5/ written on google, and then with a fade effect is removed and nothing is displayed. I thought the problem might be that the kernel does not fill the part related to the display, or rather, the fill, except that the code is different from a 3.4 kernel and therefore is not read properly, and we have the black screen . I will try to inform on other kernel 3.4 (with Soc 4460) and I will try to put some commit to the display.

I have update the Board_tuna_display.c and panel-s6e8aa0.c/.h From this repository https://github.com/freshgiammi/omap by [MENTION=4986658]freshgiammi[/MENTION]... after a couple of mistakes that I fixed in build, I managed to compile the zImage without error, and with the new update (board_tuna_display And panel_s6e8aa0), but still the same error
[Samsung Galaxy Nexus] bsmitty83:
its because the source your using , try [MENTION=4243514]Hashcode[/MENTION] omap branch
[Samsung Galaxy Nexus] Fenix46:
tell the kernel sources kindle fire HD 7? I read that it has the same Soc 4460, theoretically you could carry on GNEX, and a kernel but for tablets and do not think that would work. but try not cost anything and thanked you for your help :) I wish you Merry Christmas, I will let you know how it goes these days development
[Samsung Galaxy Nexus] aosp:
https://github.com/icepeda/omap/commits/icepeda-tuna-3.4
[Samsung Galaxy Nexus] Fenix46:
Thanks:) ... today I tried with these sources (forked from [MENTION=4243514]Hashcode[/MENTION])https://github.com/Fenix46/kernel_omap... I added the tuna_defconfig, I fixed the errors build and I created the zImage, I try with a flash, but nothing does not start, usually error. This kernel includes all board_tuna in Arc / arm / mach-OMAP2 ... includes panel-s6 ... for the board_tuna ... but it does not work equally. Tomorrow I try with the sources that you advise me [MENTION=2838735]aosp[/MENTION] and see if I can get it started, but there is more hope now
[Samsung Galaxy Nexus] Fenix46:
Guys, I post the new build that I have prepared, are always sources Grarak, I added the new DDK 1.9, I prepared the build and I loaded into a zip package, the file zImage with modules ... I can not try it for now ... if someone wants to try and let me know if it works I would be very grateful ... :D

PS: I have loaded the zImage because I do not know how to create the boot.img :p
[Samsung Galaxy Nexus] massoudsh:
If someone convert it to boot.img l am ready for test it[emoji6]
[Samsung Galaxy Nexus] christianpeso:
Would this be for Lollipop or Kit Kat or doesn't matter?
[Samsung Galaxy Nexus] Fenix46:
I do not know ... I think it should work with KK, with JB and sure it works... let me know if it works on display
[Samsung Galaxy Nexus] piterdemon:
Any one test it ? Im on lollipop so I cant test it :/
[Samsung Galaxy Nexus] Fenix46:
I have partitions in f2fs and I can't prove it for now ... if anyone can prove that let us know with a post

Thanks
[Samsung Galaxy Nexus] jhonnyx:
quick question, did you even try it on your phone or it's a blind build?
[Samsung Galaxy Nexus] Fenix46:
No I have not tried, because as I said in the previous post, I have my partitions f2fs and the kernel does not support f2fs and I can not prove
[Samsung Galaxy Nexus] n1kolaa:
Then remove kernel link, we all dont like to someone brocke becouse your bad kernel. As develoer i first test private then relase somthing you shoud try same. As looking your comming i dont know how you eaven compiled it.

ATTATION DONT TRY IT. THERE IS NO REASON WHAY YOU SHULD REISK TO HARD BRICK OR EAVEN DEMAGE YOUR HARDWERE.(sory for bad english)
[Samsung Galaxy Nexus] Fenix46:
but have you tried the kernel?
[Samsung Galaxy Nexus] n1kolaa:
whay i shoud try it if you eaven didnt try it, you didnt add eaven flags to files to be compiled that is the reason you got same errors
[Samsung Galaxy Nexus] Fenix46:
whats? i don't understand
[Samsung Galaxy Nexus] jhonnyx:
If you don't try the kernel. I won't risk my device. Sorry.

Devs have a reputation for something. If I were you (sorry guys if you start hating me for this) I'd do a backup of my device, all files, go back to EXT4. then flash your kernel. If not, there is no point. If the dev does not do it, it's kind of..... weird, you know?

Let's say I make an anthidote for a disease but I don't test it and i put it for sale. Would you even buy it if it's not a success?
[Samsung Galaxy Nexus] Fenix46:
you're right in what you say, but I now I have not been able to try the kernel because I had a lot of commitments, I loaded equally because I believed that someone in confidence it tried, but do not worry, tomorrow I an backups of all my data, I go back to EXT4, install a Rom 4.3 and I try the kernel... not and nothing serious happened ;)
[Samsung Galaxy Nexus] jhonnyx:
You have my thanks
[Samsung Galaxy Nexus] freshgiammi:
As a dev, you always have to test what you do, unless you've got a phone that has recently broken or so.

You can't do stuff (especially this, 3.4 kernel porting) blinded. So get back to EXT4 and test before you release builds.

Also, would you mind explaining the commits in your repo? I see you just committed files without an explanation or so, how did you do it? Did you just grab the kernel from kernel.org and pasted the files from 3.0 kernel?
[Samsung Galaxy Nexus] Fenix46:
Not and nothing serious happened, try the kernel and will let you know if it works ... anyway, forget my repo, because I used another kernel, I just added the drivers DDK 1.9 and prepared. Tomorrow I will tell you something.
[Samsung Galaxy Nexus] ashclepdia:
just curious if you had any information/results of if it had booted or what happened.

if he had s working USB port into my gnex I probably would have jumped up and been a lab rat, but considering I have to be very careful cuz I have no way to install factory img if I Bork device, I have to be patient instead
[Samsung Galaxy Nexus] Fenix46:
Do not install, still does not work, the problem and the usual, the display does not turn on ... and maybe I think I understand what the problem is ... I just have to figure out how to do a build with a device tree
[Samsung Galaxy Nexus] Fenix46:
I did several tests, I created a boot.img with the ramdisk rom FML 5.0 with various commit taken [MENTION=4243514]Hashcode[/MENTION] ....

https://github.com/Hashcode/android_device_samsung_tuna/commit/0e7e291b941965421205fdcce0d5dfb28621a54a

and this:

https://github.com/Hashcode/android_device_samsung_tuna/commit/aaa24e6101aa3b1163a7331bedff79cba8e117ef

But it still does not work, the problem usually, after the word google, nothing is displayed. I believe that the problem is related to the ramdisk ... but I'm not sure. Now I tried to download this kernel,http://omappedia.org/wiki/4AJ.2.5_OMAP4-Panda_Jelly_Bean_Release_Notes which is working for the PandaBoard ... we work on, and see what comes out ... if I could find a ramdisk for a kernel omap 3.4 would be the best, because I'd be sure not both the ramdisk...
[Samsung Galaxy Nexus] nikodr:
I asked in the dedicated thread but it's been a long time. Now that 5.1 is out do we have any good news for tuna?
[Samsung Galaxy Nexus] n1kolaa:
No. Its dead project :(
[Samsung Galaxy Nexus] xaifer:
http://xdaforums.com/showthread.php?p=59445653
[Samsung Galaxy Nexus] nikodr:
While i was searching online for 3.4 kernel development i came accross this pastebin logs for tuna.

http://pastebin.com/5a8Ry51P

http://pastebin.com/BBVuG6Nc

http://pastebin.com/B2pDWtR8

http://pastebin.com/qD2uwKwM

it seems that someone is working for this kernel.I cant seem to figure out the problem after the screen goes black,the usb debugging works but what then?

I think we need to ressurect this thread.
[Samsung Galaxy Nexus] Ziyan:
We were all working on 3.4, whilst it's just the screen remaining black on toro, maguro has serious problems causing emmc not to be recognized, and random deadlocks. So yeah, it's a very hard job to get it working on maguros.... I wonder what's so different in these variants...
[Samsung Galaxy Nexus] Fenix46:
Yeah it's an hard work... Last night, i've check an couple of initial commit from 3.0, but with no results for eMMC
[Samsung Galaxy Nexus] nikodr:
so would it be possible to just concentrate on toro and fix black screen?the emmc errors are maguro only related?
[Samsung Galaxy Nexus] Ziyan:
Certainly. It's impossible to work on maguros until the deadlock issue is fixed.
[Samsung Galaxy Nexus] nikodr:
Does it mean that only a few maguros could have problem ?like the bug of the emmc chip that prevented kernels from working and you had to make new kernel with the fix for the emmc chip?was this tested on all maguros?

IF you need help we could cerntainly go flash stuff and with adb and usb debbuging to provide logs.

I mean toros did not have problem with old incompatible emmc chips and kernels not working ?
[Samsung Galaxy Nexus] ILA:
It's not only a few, but quite a few maguros, like a half (mine included :( ) that have that chip. As for the fix, AFAIK it was just a matter of switching to an older toolchain, so no real code fix, it just works...
[Samsung Galaxy Nexus] nikodr:
Does this have to do with 3.4 kernel too ? i mean the reason we have the deadlocks on maguro is because of those incompatible emmc chips?So a change of toolchain would fix ?or is it something else?We should look to find differences between maguro and toro if that is the case.
[Samsung Galaxy Nexus] Ziyan:
I use the Google GCC 4.7 for 3.4 as well, which shouldn't cause emmc issues. I'm not sure at all if the problem is emmc related thought (deadlock -> no logs at all)... I might need to bring up a fresh 3.4 with only the bare minimum stuff for usb debugging to see if it randomly locks up too. Lockdep didn't help either.
[Samsung Galaxy Nexus] nikodr:
Any toro users willing to test kernel ? If toro does not have deadlock and only the display is dark i think you should move toward that direction,then after toro works you can come back to maguro.

Maybe the pandaboard http://omappedia.org/wiki/4AJ.2.5_OMAP4-Panda_Jelly_Bean_Release_Notes it has a 3.4 kernel.

The problem is the texas instrument omap that was out of bussiness right?so the panda could help you?

it has a kernel 3.4 and the following are working

Current status

Device is booting up to UI

HDMI connection: works

DVI connection: works

USB Host: works

Mouse connected to USB works

Ethernet: not done yet

Audio/Video playback: not done yet

WiFi/Bluetooth: not done yet
[Samsung Galaxy Nexus] KShion619:
Sure willing to try it out, what's the progress so far?
[Samsung Galaxy Nexus] Nephilim:
Well, since I have an N6 now my Gnex is kinda collecting dust so I'm willing to help out.
[Samsung Galaxy Nexus] christianpeso:
On Toro and for sure able to test out a new kernel. Let us know please.
[Samsung Galaxy Nexus] nikodr:
Well like i posted above the pandaboard has a 4460 omap chipset and has the features i posted working with a 3.4 kernel. On android 4.2.2. The thing is to port anythong that could enable existimg kernel to continue booting and fix the black screen after google logo [MENTION=2633638]Ziyan[/MENTION] could that kernel of pandaboard assist?
[Samsung Galaxy Nexus] bsmitty83:
Everyone has know about pandaboard for a looong time . the problem is getting the display to fire up . nothing else uses the same LCD , so its one thing to get a kernel to boot to the command line , but to have the display actually work is the challenge . nothing can be simply ported over , new code needs to be written
[Samsung Galaxy Nexus] nikodr:
Problem is not only the display but the deadlocks. I mentioned panda because it has a 3.4 kernel on the same chipset i assune that we could fix the deadlocks if we compare the source of pandaboard?

---------- Post added at 09:48 PM ---------- Previous post was at 09:47 PM ----------

Also it says that panda boits to ui
[Samsung Galaxy Nexus] nikodr:
I remember there was a guy with an uart cable that could help with debugging is he still here?Can you send him the new compiled kernel and he could check with it?

Sorry for so many posts but i think motivation and some people nagging a little about 3.4 kernel may bring something in the end.

If there is the guy with the uart cable.Please help us.!!

Gnex needs 3.4
[Samsung Galaxy Nexus] Ziyan:
UART won't help in this case (I have an UART cable as well) :rolleyes:
[Samsung Galaxy Nexus] nikodr:
So could it be that part of source is missing? Are all parts needed for 3.4 in place? Are there maybe source commits present on 3.0.x that are absent? What happened to icepeda? I feel sad. Come on let's fix it :)
[Samsung Galaxy Nexus] pattyboi:):
if a kernel builds,its source is there. theres something missing specifically for us because we were never meant to use 3.4. and trying to mix and match code from 3.0 and 3.4 isnt gonna really help much unless its a driver that needs to be forward ported,especially if we are talk mmc since the drivers for omap hsmmc and emmc in general were changed alot in 3.4,BUT it shouldnt be anything to stop a boot. [MENTION=2633638]Ziyan[/MENTION] arent the mmc for toro on a different board? i remember mw saying something about that in the google chat before.
[Samsung Galaxy Nexus] nikodr:
What would cause a dead lock?A kernel that has something missing?'is there a way to debug and find out what is causing that?That's why i mentioned the uart cable but ziyan said that it wouldn't help.

If we check other kernels 3.4 for other devices maybe we can find what is missing?

let's check a kernel 3.0.x for a phone that had a 3.0.x that latter was upgraded to 3.4 and see what changes were in the kernel source.I know different chipset different stuff but the general mapping should be similar for an android phone that has a 3.4 kernel.The source organization i mean.

Most probably a 3.0.x to 3.4 would have lots of changes.

The reason for this is to check wether there is something that is not present on 3.4

here is one link from the htc,that has the kernel source for many phones that have 3.4 if we can find on one of the same phones the kernel source for 3.0 and compare wouldn't that help?

http://www.htcdev.com/devcenter/downloads

---------- Post added at 04:46 AM ---------- Previous post was at 04:22 AM ----------

https://www.kernel.org/pub/linux/kernel/v3.x/incr/

this site has incremental updates to the kernel from 3.0.x to 3.19

and here is the kernel source https://www.kernel.org/pub/linux/kernel/v3.x/

i assume that if we patch from 3.0.72 that was the official last of nexus we could go to 3.1 or 3.2 first and see when it stops working?

something like

put in the source dir .. cd to source dir apply patch

patch -p1 < ../patch-x.y.z

that would work for example if i had an ubunt pc running a linux kernel.

The same method somehow could it be used to apply patches to android 3.0.x kernel?

What is the way to go to 3.1 from 3.0.x ?to i need to remove patches from 3.0.101 to 3.0.0 to go from 3.0.101 to 3.1 via 3.0.0?

I suppose many patches would be obsolete in newer versions?

In the same way if we want to go from 3.0.x to 3.4 do we really need the inbetween patches of linux kernel 3.1 3.2 and 3.3 ?

sorry if this is offtopic but the idea of having a 3.4 kernel for galaxy nexus made me want to learn how a kernel is compiled .Would love to try to understand all the knowledge of how updates could be applied.
[Samsung Galaxy Nexus] nikodr:
I downloaded linux kernel 3.4.48 from kernel org as i saw that the gifthub of nexus 3.4 kernel said so.

I downloaded all source from israel cepeda gifthub.and wanted to ask something.

From what i remember the latest official kernel of galaxy nexus from google is based on 3.0.72 right?

i checked the file linux-3.4.48\linux-3.4.48\drivers\mmc\card\Kconfig that i downloaded from kernel.org to the file

omap-icepeda-tuna-3.4\omap-icepeda-tuna-3.4\drivers\mmc\card\Kconfig

the last one i think is based on the 3.0.72 of jellybean and has this extra lines

config MMC_BLOCK_DEFERRED_RESUME

bool "Deferr MMC layer resume until I/O is requested"

depends on MMC_BLOCK

default n

help

Say Y here to enable deferred MMC resume until I/O

is requested. This will reduce overall resume latency and

save power when theres an SD card inserted but not being used.

Now i downloaded the source files of nexus 5 that has official kernel 3.4 and the same file

located on nexus5\linux3.4.y\drivers\mmc\card\Kconfig has this lines added to the end that are missing from our source of 3.4

i checked that on our source the config MMC_BLOCK_TEST is there but is never defined on the end of file.

config MMC_BLOCK_TEST

tristate "MMC block test"

depends on MMC_BLOCK && IOSCHED_TEST

help

MMC block test can be used with test iosched to test the MMC block

device.

Currently used to test eMMC 4.5 features (packed commands, sanitize,

BKOPs).

So i used a utility to check the three files and see similarities on code.

Could there be other files that are missing stuff or are old?

in the kernel 3.4 test of nexus5 it has those lines.Do we need them?

Could there be other stuff like this that need to be ported?
[Samsung Galaxy Nexus] bamtan2:
The fastest and possibly best way to do this job could be to recruit an expert to help, like an experienced kernel hacker who has already done similar work, or whatever. This way the big hurdles could be jumped, and then the community could refine it from there.

Is there a way for us to draw attention to the project? To find people who worked on Galaxy Nexus originally? Can we assemble a team and crowd-fund the development of the kernel? Maybe we can crowdfund first and then give some of the money to whoever sticks their head up to help?

It may not make much money, but a "Galaxy Nexus revival" campaign might still cause the right people to notice.
[Samsung Galaxy Nexus] ILA:
That would be great, but we've already tried that with Israel Cepeda ( he worked on the device originally ) and Hashcode ( he made the 3.4 kernel for other devices on the same chipset ) but it was not paid and they run out of time for that...

I would really love to see this thread get going again!
[Samsung Galaxy Nexus] nikodr:
Just raise some funds and pay them to fix the display? Its where the develipent stopped right?
[Samsung Galaxy Nexus] nixholas:
Greetings my friends!

Sorry for intruding the development of the 3.4 kernel, I am terribly apologetic for wandering out of XDA's developments for almost a year (due to my nexus getting fried) but I sure have been looking up on the threads here.

I guess its time I should come back and help anything new is up?
[Samsung Galaxy Nexus] nikodr:
Amperific nice to have you back. Thanks for answering my pm :) i think ziyan btsmitty83 aosp and others can quickly tell you the news in development.

In quick i just want to say that kernel loads usb works but on maguro there are deadlocks and on toro i think it works. From ypur thread i remember you said you managed to have distorted display on this kernel.maybe you can tell the good guys here your way of doing this. We are stuck on display. Mmc partition is not recognised and display is blank.
[Samsung Galaxy Nexus] nixholas:
Ah there is a drawback on my side,

MMC partition is is not recognised, Display is distorted BUT debugging broke

I believe fixing the MMC first is best. Leave the display the last
[Samsung Galaxy Nexus] nikodr:
I remember grarak said that if a recovery can be built with a working dsiplay with 3.4 it will be a good step.

What did you do to enable display?
[Samsung Galaxy Nexus] nixholas:
I went to fix up the SGX drivers that I think is deemed to fit with the rest of the kernel. However, I only managed to get a distorted display as the relevant drivers to fully make the display function are still dysfunctional.
[Samsung Galaxy Nexus] nikodr:
Maybe we should donate or if someone has a spare galaxy nexus maguro to give to Amperific.Do you have a paypal account?I think the omap aosp team would certainly need someone like you .

What do you people say?Should we promote it to existing threads so people would help?I think amperific had a maguro but no longer. [MENTION=554001]bts[/MENTION]mitty83 [MENTION=2838735]aosp[/MENTION] [MENTION=2633638]Ziyan[/MENTION] [MENTION=4986658]freshgiammi[/MENTION] [MENTION=3390093]MWisBest[/MENTION] [MENTION=4022928]Carlos_Manuel[/MENTION]

Regarding the status of the kernel 3.4 iI sent an email to Israel Cepeda but he didnt reply yet.I am sure many of you would consider this a difficult project but it we have any help we can get it can easily be done.

Let's hope we can get a maguro for Amperific [MENTION=5310723]nixholas[/MENTION]
[Samsung Galaxy Nexus] bamtan2:
I suspect there are people who think no one is interested in Galaxy Nexus. If they knew people were interested, they'd become interested too. This is why I think a "proof of concept" crowdfunding could be a good idea. If 100 people donated $10, we could split $100 across 10 developers and this would prove there is interest in sustaining Galaxy Nexus.
[Samsung Galaxy Nexus] bsmitty83:
I think its simply because of the age of the device , being a nexus , most devs got a n4 , then n5 , etc. Nobody's left to Dev on the device due to age. Many people have had 2 or 3 devices since the galaxy nexus came out . adding a bounty might get someone to do it solely for monetary gain , but most of the people who are willing to work on a 3.4 kernel are present . personally I haven't gotten a 3.4 kernel to boot past the google logo , which isn't booting at all . I really don't have the proper seat time to throw myself at it . I'm married , 2 kids and a 40+hr / week job prototyping for the auto industry , hopefully someone will get it booting and displaying properly, then I can customize the hell out of it .
[Samsung Galaxy Nexus] nikodr:
[MENTION=4608636]bsmitty83[/MENTION] amperific did so he has a working display with kernel 3.4 but his nexus was fried. So do you think it coyld be possible to find him a maguro?
[Samsung Galaxy Nexus] Fenix46:
I appreciate the spirit you put to this device, I appreciate that you want to find a device to Amperific, but the much bigger problem to solve for maguro is the MMC, the display is a big problem to solve, but if we do not solve the MMC we did nothing.It is a very difficult job, because you can not find the problem to the MMC, and not daydream guys, there are so many things to sort out, before moving to the display, even though it is a big problem.
[Samsung Galaxy Nexus] bamtan2:
Certainly! I consider Galaxy Nexus historically important to maintain, as it is among the first truly "great" android phones. I think there are developers who would be interested in participating once they realize how well it is working.

I've measured the hardware performance, and it is similar to new phones today, albeit not the high-end ones. The software just needs some tender loving care. IMO Google should not drop support for devices so fast. Can you imagine the original corded telephones stopping working after a few years? Our culture is just spoiled rotten!

IMO Galaxy Nexus is comparable to a ~$100 phone today. But more importantly, it is a classic from 2011, and it can be kept running well until 2021, with the right help. :) I think maybe we just need some crowdfunding to PROVE public interest. It takes only 100 people giving $10 to make $100 for 10 developers, and sometimes only 1 breakthrough is necessary to enable everyone else's work! =)
[Samsung Galaxy Nexus] nikodr:
My nexus is without charge for over 96 hours , r21 kernel nephelim settings applied. I didnt use any data or 3g went only a little wifi. I wanted to test it as a phone and send sms. More than 4 days is not bad. Imagine if we had a kernel 3.4 with customizations and proper drivers. It would last even more.

I mainly used it for some phone calls and maybe ten sms. :)
[Samsung Galaxy Nexus] nikodr:
Pic
[Samsung Galaxy Nexus] nikodr:
Battery usage