yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] MrVJTod:
I replaced my gnex USB connector a few weeks ago. Had to take the phone apart, but ifixit had pictures, the kit was cheap and included necessary tools and the process was pretty easy. I used to have tons of cable and charge problems and always assumed it was the cable, but it seems that all of my cables will charge me now.
[Samsung Galaxy Nexus] LibertyMonger:
I've had this issue about 10 times since I have owned my nexus and it has been because it is sensitive to moisture and dust. Also using a different charging cable than the oem can cause battery drain. But I am sure he is smarter than me with phones and has already figured out what is wrong.
[Samsung Galaxy Nexus] dhiru1602:
That is because the newer DDK 1.9+ drivers for PVR should be built as an external module rather than having it built into the kernel. The pvrsrvinit binary will load the kernel module automatically during boot.

I have recently ported DDK 1.9 drivers to another OMAP4 device. The build is something like this: https://github.com/dhiru1602/android_device_lge_u2-common/blob/cm-11.0/BoardCommonConfig.mk#L99 and here is the PVR version: https://github.com/dhiru1602/androi.../cm-11.0/sgx-module/include4/pvrversion.h#L61
[Samsung Galaxy Nexus] Ziyan:
Thanks, we've managed to make it work, the only problem is that camera got broken... our ducati is very old, so we need some additional changes to make it work with the required ion changes. As Hashcode is helping, I'm sure we'll figure it out sooner or later, but if you'd like to join us, you're welcome :)
[Samsung Galaxy Nexus] AgentSmith:
Are you saying that besides the camera everything else is actually working?? Are you willing to start sharing flashable test kernel if that's the case?

This is still one of my favorite threads. Thanks guys!!
[Samsung Galaxy Nexus] ScardracS:
We have expect for lots of time something doing that work... We can expect some more weeks and have a better work with a working camera

Check out my G+ profile: https://plus.google.com/+MarcoScardovi
[Samsung Galaxy Nexus] Ziyan:
Yes, check my thread. Only a test kernel won't be enough, as newer vendor files are required, but with including those, it could work. Everything's on my github if you're interested, but it's still incomplete, as camera isn't working.

Hope it won't take weeks, we've still got some quicker ideas :)
[Samsung Galaxy Nexus] blmvxer:
Can we merge anything from these?

Official TI-Ubuntu git tree:*

*#git clone git://dev.omapzoom.org/pub/scm/integration/kernel-ubuntu.git

*#cd kernel-ubuntu

*#git checkout -b release_GLP1.6.8 ti-ubuntu-3.4.0-1489.22
[Samsung Galaxy Nexus] wisefreakz:
Looks like Tuna's Angels forgot about us... ?
[Samsung Galaxy Nexus] Culex316:
Patience is a virtue
[Samsung Galaxy Nexus] Ziyan:
Why do you think this? I see lots of tuna related commits here ;)
[Samsung Galaxy Nexus] wisefreakz:
I saw it.... But is it all for the Tuna?
[Samsung Galaxy Nexus] ILA:
No, not all... He is writting for multiple devices that have the same CPU (e.q. kindle fire HD). But the good thing is that he's doing something for us as well :)
[Samsung Galaxy Nexus] kivi001:
Kernel 3.4 :(

When provide?
[Samsung Galaxy Nexus] bsmitty83:
Really ? [emoji107]
[Samsung Galaxy Nexus] pattyboi:):
90% of the posts here are "wen kan we haz dis 3.4 kernel make it done nowwww"

if every person that requested the damn thing worked on it we would've had it done last year.
[Samsung Galaxy Nexus] Carlos_Manuel:
Everyone doesn't have knowledge about kernels, so those who don't have any knowledge, can't really do nothing with this... ;)

Currently only Ice and hash can make k3.4 working on tuna... :fingers-crossed:
[Samsung Galaxy Nexus] ScardracS:
Lots of people here don't know what's a kernel... They think build a kernel is really simple and they don't think devs need to write new codes for fix all the problems.

For all

What do you expect? A magician who fix all the codes? Why you don't breack the b***s a Texas Instrument and ask if it want upload the codes
[Samsung Galaxy Nexus] pattyboi:):
isn't one of the rules no eta's? just cause they don't know how to help don't justify asking constantly when it'll be ready :P
[Samsung Galaxy Nexus] Carlos_Manuel:
everyone doesn't know that rule.. ;) in xda there is noobs, devs, geeks, etc.

:good:
[Samsung Galaxy Nexus] HONG86:
Not really
[Samsung Galaxy Nexus] jhonnyx:
Not trying to be a bad guy (I'm trying really hard)

You have many options:

- Pay to the devs

- Recruit a dev and pay him a salary

- Ask same thing to Samsung/Google. They have built the phone.

- Learn some grammar/english then learn how to request trying not to be so harsh in the process. We're very sensitive (yeah, I include myself).

- Build it yourself if you're in a rush

- Wait until you hear the news from the guys here on the thread.
[Samsung Galaxy Nexus] Culex316:
That's still no excuse.

Let's just patiently wait for the kernel. It will be ready when it's ready. Patience everybody.

In the meantime, go read a book or something.
[Samsung Galaxy Nexus] AgentSmith:
- Can't afford it.

- Can't afford it.

- I know it's pointless so I choose not to.

- Absolutely!

- I wish I could.

- Now that's exactly what the silent majority is doing. So I ask anyone working on the kernel here to please ignore the few whiners here who can't resist to ask for an ETA. We are waiting very patiently for whatever you come up with and what not. In this topic there is no such thing as bad news. We are already utterly grateful for all the development going on around this device. Anything else is nothing but a huge bonus.

I actually just bought a new battery for my Gnex so it is ready to last another 3 years. That is what everyone here is doing for us noobs: have a phone that lasts much longer than Google and Samsung anticipated. For that we are forever grateful!
[Samsung Galaxy Nexus] times_infinity:
Hashcode got a new job.

See here and here

He explains that a lot of his community projects will come to a halt.

Although he has stated that, he is still pushing changes, albeit not as often but still pushing, to the omap kernel and tuna repos.

So just be patient and let the man work his magic.
[Samsung Galaxy Nexus] pattyboi:):
cough cough ice is working on getting usb working and hes getting close cough cough
[Samsung Galaxy Nexus] Carlos_Manuel:
That's no News for me. :p I already knew that. ;)

:good: :)
[Samsung Galaxy Nexus] ILA:
Well don't keep it for your self then :P
[Samsung Galaxy Nexus] Carlos_Manuel:
Lol. ;)
[Samsung Galaxy Nexus] dhiru1602:
So I have picked up a broken I9250 today for $30. The Glass is broken but the touchscreen and display works fine. Cameras are not working (They don't get detected at all. Remoteproc trace shows some errors related to Camera PMIC. So mostly it's a hardware issue). Apart from these, everything else "appears" to work fine.

I have managed to get the bootloader log using UART. I assume I would require FIQ Debugger and Early Printk enabled in kernel for the actual kernel log to appear.

Now since I have UART, we can debug the kernel and find out if there are any crashes very early during the boot process. We won't require USB to gather the logs.

[sbl_board_charger_init_post] : Succeed set model data : 0x78!!!!!
====== VCELL : 405125, SOC : 93, nType : 4 ======
[Charger] nScaledVCELL : 405125000, nDesriedSOC, : 93, nMaxSOC : 113, nMinSOC : 73
[ omap_power_get_reset_source :47] PRM_RSTST : 0x1
[ __omap_usbacc_test_donwload_by_musb :280] nDeviceType : 0x4
[ omap_usbacc_get_reboot_reason :333] nJigStatus = 0x00000001
[ __sbl_board_hw_init_late :710] final reboot mode in cable = 0x20000
[ __sbl_board_hw_init_late :721] Wake up by TA / USB / JIG
* FB base addr = 0xbea70000!
lock PLL Done
* PANEL_S6E8AA0_ID_READ : 0xa2, 0x8e, 0x9b.
message.command =
message.status =
message.recovery =
<hit enter twice to activate fiq debugger>

AST_POWERON
[Samsung Galaxy Nexus] Carlos_Manuel:
[MENTION=2838735]aosp[/MENTION] you know what to do ;) add him to your hangouts group...
[Samsung Galaxy Nexus] freshgiammi:
He was already in ;)
[Samsung Galaxy Nexus] sgspluss:
Just amazing if dev's started to work hand in hand (like the [MENTION=5292938]DevConnection_Team[/MENTION] for samsung galaxy s plus do)

Few dev's made this old phone fly, same are building here up.

Wish you guys all the best and hope you'll get it work as it has to :good:
[Samsung Galaxy Nexus] Ziyan:
TEAMOMAP4 is strong too :highfive: https://github.com/freshgiammi/omap/commit/3daf78872bd9f78640682275238b59bc27eee0ec you'll drop your phone from the butter it will eventually become, working together is nice :fingers-crossed:
[Samsung Galaxy Nexus] aosp:
Very nice brother msg me on hangouts when you can I'm sure the XDA GNeX community can help get you a fully working phone better yet maybe [MENTION=5310723]Amperific[/MENTION] can you send you one of the GNeX's the community sent him that he is not developing on amirite [MENTION=5380162]pattyboi:)[/MENTION]
[Samsung Galaxy Nexus] sgspluss:
Yes my friend, its always nice to see that dev's started work together :good:

Thats one of the reason why i still love this phone more and more :p
[Samsung Galaxy Nexus] IceVip:
Could someone please name me the advantages of getting 3.4 on our nexuses? I'm sorry if the question is too lame but i seriously have no idea whats all the fuzz about making it capable with the ti omap i just don't see any reason..
[Samsung Galaxy Nexus] TinyFeather:
Same question here, most of the important 3.4 kernel stuff is already backported to our 3.0.x kernel..
[Samsung Galaxy Nexus] Godra:
3.0.x is almost at EOL (end of life) and 3.4.x is going to be developed for atleast another year or two
[Samsung Galaxy Nexus] nixholas:
End of Line :)

3.4 is much more optimized than 3.0. That's the simplest form of defining the difference
[Samsung Galaxy Nexus] Gil Smash:
That'd be end of life. But, similar concept haha.
[Samsung Galaxy Nexus] ashclepdia:
why do it?

Cuz is fun, and that's all that matters, do it up devs! is great to see people still pushing forward with ideas and bringing new things to what is starting to be considered "an aging device" to some.

(i still consider this one of the best Nexus ever due to the simple fact of the amount of people/carriers it came out on. which allowed so many awesome devs to make this thing thrive)

/rambling sorry :D

edit... i knew i saw this thread before lol, been a while...
[Samsung Galaxy Nexus] :
Aye, used the Nexus S and Nexus 4, and although the N4 is sweet, it has its own issues. Love the more, can't wait for N5. Ready to be blown away for the second time!
[Samsung Galaxy Nexus] ScardracS:
Please do not leave this awesome project.. If che makes a "booting" se fan try a chance.. Personally i don't know "how to" make that rom but i can learn if you'll help me

Inviato dal futuro con il Nexus 7 && Android 20.4
[Samsung Galaxy Nexus] Sparx639:
People are working on it behind the scenes just be a little patient :p

Sent from my sock drawer
[Samsung Galaxy Nexus] Scandy:
any proofs?
[Samsung Galaxy Nexus] :
They're not answerable to you, me, or any of us.
[Samsung Galaxy Nexus] mrgnex:
From the golden kernel thread:

- Jeeko
[Samsung Galaxy Nexus] razi914:
Im no dev , what will a 3.4 kernel really do?
[Samsung Galaxy Nexus] ScardracS:
It is more optimized and more have more feature than 3.0.x's kernel

Inviato dal futuro con il Nexus 7 && Android 20.4
[Samsung Galaxy Nexus] razi914:
What "features" exactly? :confused:
[Samsung Galaxy Nexus] Sparx639:
Better system management, such as ram, CPU, and power management

Sent from my sock drawer
[Samsung Galaxy Nexus] andQlimax:
none of those features are mentioned here: http://kernelnewbies.org/Linux_3.4

3.4 big changes, if you do a search, are : graphics (amd /invidia new drivers), X32 ABI ( good for x86 mobile architectures), improvement to Btrfs file system, yama security mode

none of this feature will specificly give us something special, and lot of that changes does not affect android at all, if not some little fixes or improvement, which not worth a port

most of you still don't get that a 3.4 PORT, will just give a lot of non-working things
[Samsung Galaxy Nexus] :
lx-3.4 also has alot of features like, i7&i5 improvements, that we don't need.
[Samsung Galaxy Nexus] Scandy:
But it's not 3.4 kernel itself. It's just another mix of 3.0.x and 3.4.x
[Samsung Galaxy Nexus] drive2droad:
I simply fail to understand that why an enterprising individual who wishes to bring something new to the community is being stopped from doing his work . If you don't wish to upgrade , it's your choice .
[Samsung Galaxy Nexus] Shidell:
I wanted to pose a question here because it's related to Galaxy Nexus on 4.4 and beyond, related to the GPU drivers.

Since moving to 4.4, I've noticed that the GPU performance has degraded as compared to 4.3 and earlier. I expect that this is related to under-the-hood changes in 4.4 that the 4.3 binaries and kernel don't support (for example, the black box issue we dealt with earlier) and the work-arounds that were implemented to fix it might also play a part.

Specifically, Navigating while charging with the GNex is no longer feasible. The device will overheat in less than 10 minutes, and once it does, the phone will hold a charge, but no longer actually charge. This "feature" is a product of the device overheating, which I think is a result of the SoC doing extra work / the work-arounds involved in making the GPU 4.4 compatible.

The performance changes are also noticeable while using Live Wallpapers and other render-intensive tasks; for example, if you use the Google Now Launcher on 4.3 with a live wallpaper, like Phase Beam, the transition from the Google Now page on the left to the center live wallpaper is smooth and stutter-free. With 4.4 there is significant stutter, which is just further evidence.

So, the real point is, is there any hope with a newer kernel of remedying these issues? I've made a post for Ziyan, who is working on DDK 1.9 drivers for the Galaxy Nexus here what his opinion is.

I'd really like to continue using the GNex, especially into L, so what can we do to fix the GPU issues?
[Samsung Galaxy Nexus] sergialess:
Yeah, either it is a seasonal problem, or latest gnex stuff overheats the device too easily, IMHO :rolleyes:
[Samsung Galaxy Nexus] freshgiammi:
There is nothing users can do. Actually, DDK1.9 are working. the only problem is ducati. We could say that Ducati= Camera and Video Playback. And Ducati is not working good actually because it needs to get updated, but since it's closed source, it can't. We're trying to figure out a way to "hack" this.

Also, the black box get fixed with DDK 1.12. DDK1.9 is just an overall GPU improvement (which brings less heat, gpu governors stockish, not like faux's ones, and improved performance.)

Actually, every 4.4 based rom suffers from overheating. Switch back to 4.3 and you'll notice it's much cooler. Sadly, this is some "improvement" kitkat gave us, aswell as "black boxes" and audio buffer problems.
[Samsung Galaxy Nexus] sergialess:
So... would you seriously recommend to go back to 4.3?

I know it's a personal choice, but I wonder what's yours.
[Samsung Galaxy Nexus] pattyboi:):
if heat is a factor to you,its not a choice,4.3 ran wayyyyyyyyyyyy cooler,and if long term life of the phone is something your really worried about,4.3 might be the best bet
[Samsung Galaxy Nexus] sergialess:
Understood. Thanks for your prompt insight. I'll give a try to 4.3 again.
[Samsung Galaxy Nexus] Shidell:
[MENTION=4986658]freshgiammi[/MENTION] Forgive my ignorance, but can you enlighten some of us regarding the overheating issue in 4.4?

In 4.3, with the 4.3 stock kernel, everything works wonderfully. In 4.4, changes were made to the kernel to work properly, including resolving the black box issue. Were other changes made that are causing the overheating? Or does KitKat do things much differently, and without proper driver support, is the cause of the overheating issue?

Finally, as dumb as this might sound, could we use the stock 4.3 kernel in 4.4, or with minor changes, as a remedy to the overheating problem?
[Samsung Galaxy Nexus] Ziyan:
Again: the black box issue was very minor! It was a problem with the screenshot function - and only the screenshot function, it only appeared when the phone took screenshots, eg. for the rotation animation. The fix "simply" changes it to use the CPU path to take screenshots, instead doing it with the help of the GPU. It does nothing else. This is needed because our outdated GPU driver doesn't support this feature correctly.

No kernel changes are needed for kitkat, even the stock 4.3 kernel works fine. No-one did anything that could cause overheating, that may have came with 4.4 from google (or you're using zram, which is very CPU intensive).

Btw, I didn't notice major overheats... However, I use the stock thermal throttling, which throttles the CPU at 63 °C (the stock OMAP temp limit), so the phone doesn't get too hot. Some custom kernels modify it to higher values - as I said in the other thread, I disagree with them, and always set it below 70 °C, as it doesn't only heat up the CPU, but the modem, battery, emmc, and everything else on the motherboard too, so it does reduce the phone's life... and the battery will stop charging when it reaches 50 °C, so check if you're using such custom kernel that doesn't throttle below 70 °C (I recommend 63-67 °C, as the slowdown isn't noticeable at all unless you're gaming).
[Samsung Galaxy Nexus] sergialess:
Sorry for my ignorance, but how do you set the thermal throttling?.

A drawback for switching to 4.3 is that currently there aren't any devs supporting custom roms, AFAIK.
[Samsung Galaxy Nexus] ILA:
Use kernel tuner for that :)
[Samsung Galaxy Nexus] sergialess:
Using Trickster Mod:

- Temperature Limit = 63

- Temperature Throttling = ON

I'll let you know! =)
[Samsung Galaxy Nexus] freshgiammi:
Damn, i sleep too much. However, y'all got answered ;)
[Samsung Galaxy Nexus] Shidell:
So it should be possible to use the 4.3 stock kernel with KitKat, and hopefully alleviate the overheating/GPU stuttering issues? I was under the impression that kernel/driver changes were necessary to make 4.4-based builds work; as the drivers are compiled into the kernel, correct?
[Samsung Galaxy Nexus] freshgiammi:
All kernels on 4.4 are 4.3 based. Also, all the changes are rom related. Flashing 4.3 stock 3.0.73 gives no less heat or anything.
[Samsung Galaxy Nexus] Shidell:
Thanks [MENTION=2838735]aosp[/MENTION] and [MENTION=4986658]freshgiammi[/MENTION].

If the problems are in fact not kernel or driver related, and solely ROM-related, does anyone have any idea as to what the culprit is?
[Samsung Galaxy Nexus] Ziyan:
Do you use your rom's stock kernel? AFAIK most roms use a 95% stock 4.3 kernel, which should have thermal throttling enabled by default on 63 °C. It should prevent you from any issues coming from heat... it's designed exactly for that, I'd bet there's no Android phone that doesn't throttle while navigating (especially when the sun is also heating the phone). You may want to check your temps when the phone stops charging, use trickster mod for that, which shows the CPU and battery temps on the stock kernel too. Also, if you have a car with aircon, push some cold air to the windshield too, it may cool down the phone (and you won't catch cold, as it won't blow your face with freezing air :highfive: )

tl;dr I can only imagine the situation you have (phone stops charging while navigating with stock kernel), when the sun is shining the phone strongly, as it may heat up the battery without even turning the phone on to 50 °C, especially if your phone is covered with a case or something. Navigation alone simply can't do this, as throttling is designed to avoid such issues...
[Samsung Galaxy Nexus] Shidell:
I am using my ROM's stock kernel; being CM11 (M9), and their kernel version being 3.0.101.

I agree with everything you said--but what doesn't make sense is this: Using CM11, this problem occurs immediately--within 3 minutes of Navigating and charging. Even at night, with no sun, and a cool car and Galaxy Nexus dock.

If I flash the stock Toroplus factory image from Google (4.2) and perform the OTA to 4.3 and use Maps, it works perfectly. No problems at all, even during the day (assuming I have air on or the windows open in the car.) I would imagine that if it was just sitting in the car with sun beating down on it, it would probably overheat.

It's perplexing because this issue happens within minutes on 4.4, but doesn't happen at all with stock 4.3. The problem must be somewhere, right? Kernel, Drivers, or ROM? Does it make sense that the ROM would be culprit, though?
[Samsung Galaxy Nexus] aosp:
Install OSMonitor and check processes for high cpu usage

https://play.google.com/store/apps/details?id=com.eolwral.osmonitor
[Samsung Galaxy Nexus] pattyboi:):
its just how 4.4 runs for us,period,thats just it.
[Samsung Galaxy Nexus] Shidell:
I'm going to test with this tomorrow and report back on 4.4 vs 4.3. Thanks for the reference, [MENTION=2838735]aosp[/MENTION].
[Samsung Galaxy Nexus] rajputrajat:
I am anxious to see the results. could give some clues.

Thanks.
[Samsung Galaxy Nexus] ILA:
Hi, sorry to be a party breaker, but could you please open a new thread for that (maybe in general) since that has nothing to do with the 3.4 kernel development, and I (and probably others here) get very excited when this thread lights up, so don't play with our feels by posting OT :)
[Samsung Galaxy Nexus] Shidell:
I agree. I've made a new thread here hoping to follow up on this issue, as it appears that many Galaxy Nexus owners are facing it. I posed it here initially because i assumed it to be related to kernel/driver problems (associated with 4.4 compatibility), although [MENTION=2633638]Ziyan[/MENTION] and [MENTION=4986658]freshgiammi[/MENTION] have indicated otherwise, so there is more to troubleshoot.
[Samsung Galaxy Nexus] dehein:
Is this thread still alive

So i am here not asking for an ETA, but would love to hear what happens at the moment in the development for our GNEX. Are you guys still working on it? Or is it hopeless to wait for a 3.4 Kernel.
[Samsung Galaxy Nexus] Ziyan:
I think we're almost done with 3.0 (new pvr + camera), there are some minor things remaining, but after that, I'm joining the 3.4 party too ;)
[Samsung Galaxy Nexus] freshgiammi:
Aye [MENTION=2633638]Ziyan[/MENTION], we're working on fixing Camera on PVR. Once it's done, OZ-Rebased kernel will be released as the "New Stock".

ATM, 3.4 Developement is not our target, because 3.0 is maximum priority. When 3.0 is good to go, the whole OMAP4XXXTEAM will start to focus on 3.4 again ;)
[Samsung Galaxy Nexus] wisefreakz:
Nice to hear that, buuut what happened to the guy who won a GNex only to help us? Thought he was our biggest hope as he used to work for TI.....
[Samsung Galaxy Nexus] nikodr:
I think he continued to bring source commits and fixes for the kernel. 3.4 kernel is not only gfx but many other stuff too. The development isn't over yet. In fact I think now the good stuff shall happen :)
[Samsung Galaxy Nexus] freshgiammi:
You probably refer to Icepeda: he's working on a UART cable do debug at a lower level than ADB.
[Samsung Galaxy Nexus] Scandy:
Guys, is it worth it to work under 3.4.x branch? Maybe it's better to try compile 3.14? As far as I know, stock Android L kernel has been updated to linux 3.14 branch
[Samsung Galaxy Nexus] nikodr:
I suppose we have to wait to listen from the kernel gurus.
[Samsung Galaxy Nexus] Master94ga:
If is hard to port 3.4x imagine how can be 3.14 :D
[Samsung Galaxy Nexus] freshgiammi:
There is NO device with 3.14.

Lastest kernel is 3.10, which will be useless because there is no OMAP chip optimized on 3.10.. actually, it's not much optimized even on 3.4.. 3.0 is the most optimized.