yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] benrees21:
I saw his post on G+ is there a more detailed post stating exactly why he is leaving?
[Nexus 4 Original Android Development] RCDuke:
Android police did an article on his departure.
[Nexus 4 Original Android Development] BitteredBro:
Random Reboots across ROMS and Kernels

Hi guys.

Sorry for derail your regular off-topic chat with a different off-topic subject.

I'm getting random reboots on both 4.2 and 4.3 ROMS and kernels. I've tried with everything that came to my mind. I'm back to stock now and still having those issues.

I've attached some last_kmsg generated while on different setups.

Please, please help me out! I can't use the phone because it turns off after a couple of minutes if unplugged and my boss will rip me a new one if i'm not available.
[Nexus 4 Original Android Development] pikachukaki:
Its normal on ondemand/deadline all 4 cores work all the time even on 0%?

ΣΕΝΤ ΦΡΟΜ ΜΥ ΝΕΧΥΣ 4!!ΥΣΙΝΓ ΤΑΠΑΤΑΛΚ ΒΕΤΑ
[Nexus 4 Original Android Development] qu3becker:
Yes, that's how trinity works. That's why it's down clocked by default to 1024.
[Nexus 4 Original Android Development] simms22:
ok, first two are moles kernel, keyboard reset both. i dont know what that is, ive never seen a keyboard reset. and the third is the stock kernel, lots of craziness going on there it seems like.. :eek:

---------- Post added at 03:53 PM ---------- Previous post was at 03:43 PM ----------

it is how it supposed to be. and thats not why its at 1026mhz. its at 1026mhz because thats how i use it for daily use. 4 cores always on doesnt use more battery than the 4 cores hotplugging. it actually probably uses less. this way it does not waste time constantly turning the cores off and on when hotplugging. this time thats not wasted is theoretically saving you battery(and time).
[Nexus 4 Original Android Development] BitteredBro:
A lot of craziness summarizes my life at this particular space/time conjunction. I've tried changing Kernels, ROMS (4.2.2 & 4.3), going back to stock (4.2.2) and every single time those darn "keyboard reset" show up.

What can survive going back to stock ROM?

Recovery? i did replaced it with stock using a toolkit

bootloader? i used the google images that include it.

Modem? Same as above

What can it be?!

An issue with the partitions?
[Nexus 4 Original Android Development] simms22:
are you using the same apps every time? are you using a customized keyboard? from my experience, apps themselves can wreak havok and cause reboots. next time you wipe, dont restore your apps for a while, see if you get reboots. also, try rasbean 4.3. its very close to stock aosp, and a very clean rom too. maybe the craziness on the third last_kmsg is from whatever rom it was.
[Nexus 4 Original Android Development] italia0101:
Quick question guys, does anyone actually run at 1.7ghz for normal use?
[Nexus 4 Original Android Development] simms22:
on occasion here(when home mostly), but 80% of tbe time at 1026.
[Nexus 4 Original Android Development] BitteredBro:
Hi again.

I just flashed Jwr66 factory image and the phone turned off by itself immediately after unplugging and opening the camera app.

No apps besides the ones installed by the factory image. Nothing plugged in besides the computer.

I'll try RasBean as you said.

Did you saw anything interesting in the last_Ksmg pointing to the culprit? Some indication inside the craziness?
[Nexus 4 Original Android Development] simms22:
"watchdog" was initiated. watchdog will reboot the device. its not the issue, watchdog just does its job rebooting the device when it detects something weird. maybe theres an issue with your battery? are you sure that its charged? the batterystats can become inaccurate.
[Nexus 4 Original Android Development] Vangelis13:
I always run 'em maxed out. There's a charger everywhere around me so no bother with battery.
[Nexus 4 Original Android Development] kepapas:
1.2 GHz -1.7ghz at work
[Nexus 4 Original Android Development] BitteredBro:
The phone is fairly new. Just 4 months old. The battery souldn't be an issue BUT is the only constant in this mess...

I just hoped it wasn't that.

I'll have to buy a crappy phone and use it for the time the N4 stays at warranty. That with my telephone company means one month al least!!!

MSM Watchdog gets initialized after "clock_late_init: Removing enables held for handed-off clocks" Could that mean something?

*I tried cleaning battery stats before (recovery) and after (root explorer) but i got the power off still.
[Nexus 4 Original Android Development] ceejay83:
qualcomm won't release binaries for the new n7. JBQ is getting the blame for it, even though it's qualcomm's fault and so he decided to leave.
[Nexus 4 Original Android Development] albundy2010:
Its easy to blame Qualcomm for anything when in actuality its all Google's fault.

Quite frankly. Its just one thing on the laundry list of things that Google is pathetic at handling with android. And I see it as getting worse not better in the recent years.
[Nexus 4 Original Android Development] simms22:
do you use twrp or cwm recovery? twrp shows battery percent, and its gailrly accurate, sometimes differs from what the system shows when the phone is booted.
[Nexus 4 Original Android Development] Grand Prix:
This, quite frankly, is simply not true. Google actually does a very good job with handling android. It constantly maintains its source, and set it up to be customized by manufacturers because it is open source. Google's goal was never to have an iOS type os (one phone, one manufacturer). The source is updated everytime, it's been refined into a very stable os and Google's goal of spreading it's services to as many different devices as possible has always been what android is about. To blame google for qualcomm not allowing drivers to be released is like blaming your car running out of gas instead of yourself for not filling it up.

Same thing happened with the nexus 4, it's all a legal issue.
[Nexus 4 Original Android Development] BitteredBro:
I use TWRP and it shows good level after the power off.

Lets say I disconect the phone at 100%. It does these thing and powers off. I plug it again, reboot to recovery to take the last_Ksmg and I found battery at 85% at least, so I try to boot on battery only and it powers off during or after the bootanimation. If I plug the phone to boot it and then unplug it, it could run. So I'm getting confusing signals here. The symptoms points to a defective battery, but the data doesn't. Have you looked at the baterry readings on the last_ksmg? Shows there's juice there, and a couple of seconds later the phone powers off by itself.

I just can't stand not knowing whats wrong with this. It's frustrating. If it was something clear and defined I could accept it, but it isn't. Something like "Oh I did this wrong and now I will have to pay for it. OK, my bad, moving on"

BUT no! I've done everything that is supposed to be done and the thing refuses to work, I'm in complete ignorance and back to square one.

Sorry for the banter. It's the OCD kicking in.

And thank you as always!!!
[Nexus 4 Original Android Development] Vortex1969:
So is it easy to say that the JSS builds kernel is some what incomplete.
[Nexus 4 Original Android Development] simms22:
i seem to think its the battery too. the phone doesnt know that the battery is faulty, so its trying to be accurate(this is what i think). and yea, my ocd gets me occasionally too.
[Nexus 4 Original Android Development] ceejay83:
every qualcomm nexus device (n1, n4, n7) has had issues with sources being released, it's not a coincidence.
[Nexus 4 Original Android Development] simms22:
incomplete?
[Nexus 4 Original Android Development] Vortex1969:
Well talking stock JSS Kernel. Meaning is it not optimized as it was intended to be because of missing drivers. Just trying to get a better understanding.
[Nexus 4 Original Android Development] simms22:
drivers for the nexus 7 are missing, i dont think they are missing for the n4(were when the n4 just came out), they were released the same day that the 4.3 rom hit aosp.
[Nexus 4 Original Android Development] albundy2010:
No. First of all this has nothing to do with iOS or other android skins etc.

Its their fault they run into legal issues with nexus devices. They pick the silicon, the OEM etc. They do this well well in advance and know of the legal troubles / agreements etc. Yet they constantly screw it up.

The source being updated is irrelevant. They handle it terribly. No matter how many bugs or problems arise on the nexus devices they sit on the fixes until they push out a new android os. Some simple recent examples. Trim, WiFi ARP, touchscreen driver, display calibration, the exploits and so on.

No updates / bug fixes were issued to fix a damn thing.

And yes I will blame Google for allowing the entire legal mess to begin with. Its their product. Its their responsibility to handle all this. This entire idea of Google basically tossing its hands up in the air and blaming Qualcomm is dead wrong. Big ol google has plenty of lawyers and time to iron all this stuff out. Also if they truly cared about all this stuff they wouldn't get into this situation time and time again.

Btw your car comparison makes no sense.

But let's point out one mor issue with android itself just for fun. It cant even manage 60fps second on the damn launcher after all these years with a 1.5 GHz krait 300 cores.

And it seems ever since 2.2 - 2.3 days Google has been solely focused on getting the os and its services on as many devices as possible all while managing it like crap. Making people like jbq loose his damn mind dealing with the nonsense
[Nexus 4 Original Android Development] albundy2010:
And while this isn't directly Google. Its them.

http://www.droid-life.com/2013/08/0...isplay-calls-lcd-inferior-to-amoled-and-more/

Pure garbage. And it actually really did start with Google on stage at last year's I/O. With Hugo mentioning the amount of GPU cores in tegra 3.

They need to start paying attention to that entire don't be evil crap.

---------- Post added at 01:54 AM ---------- Previous post was at 01:26 AM ----------

And so did the nexus s and the Xoom. Neither had anything to do with Qualcomm.

Like it said. It's all fun and easy to blame Qualcomm. When in fact its googles damn fault. Hell they NEVER had factory images and binaries available for the Xoom. Which was their GED / aosp tablet launch platform. Google is a pathetic. Making excuses for them as well.

This is the crap that jbq has been dealing with for years. And its over his head AT GOOGLE! . Not a third party.
[Nexus 4 Original Android Development] morfic:
I would love to try the X to see how much of it is huffing and how much of it is actually doing things right.

Nexus 10 had delays too iirc.

Which release was it that really had to twist their arm for Google to release source? Gingerbread? Don't remember, but it was a big stink back then, guess they wore him out and he's tired of fighting.
[Nexus 4 Original Android Development] hp13:
#Rose
[Nexus 4 Original Android Development] joeyk240:
Can someone link me to the newest set of kernels por favor?

I'm currently on 133-1836, if that is the newest one(experimental or not), great.

I've read back about as far as I can and haven't seen anything mentioned.

TIA, and as always, fantastic kernel, Morfic.
[Nexus 4 Original Android Development] simms22:
tf4c is the latest, but its a real test kernel. something to use while waiting for the next. and its only for 4.3 http://goo.gl/hONIdT
[Nexus 4 Original Android Development] flaviocc:
Simms,

i found a fix to google backup issue:

works ok for me:

in terminal type this:

su (press enter)

bmgr transport com.google.android.backup/.BackupTransportService (press enter)

(exit terminal)

source:http://forums.androidcentral.com/sp...-aosp-jellybutt-v2-4-jro03l-8-25-12-a-13.html

This is an old bug....and I do not understand why the 4.3 release has this bug.

Tks.
[Nexus 4 Original Android Development] albundy2010:
X ain't doing anything right IMHO, it's the 500 million dollar marketing moneys at work. That engineer is a clown. Sounds like a PR guy. Straight clown.

And they never released source for 3.x. Such a damn fail. Oh the code was a mess, it wasn't ready etc. Yet they had no problems selling a device with it.
[Nexus 4 Original Android Development] sub1287:
Aside from the 4.3 one Simms posted about. I believe TF152 is the last one put out for 4.2.2, I may be wrong though.
[Nexus 4 Original Android Development] simms22:
theres a android device manager thread in q&a, you might want to post this there. i know a few people that cant get the android device manager to fully work(either wont ring them or wont find them), and they are all missing their google account in backup and restore. maybe this can help them as well(i think its related, but seems no one else noticed).

anyways, thank you :)

---------- Post added at 10:13 PM ---------- Previous post was at 10:09 PM ----------

yup tf152 is the latest 4.2.2 kernel http://goo.gl/CDAGV7

---------- Post added at 10:16 PM ---------- Previous post was at 10:13 PM ----------

pink!

and im out of thanks.. thanks :)

---------- Post added at 10:40 PM ---------- Previous post was at 10:16 PM ----------

lol
[Nexus 4 Original Android Development] sub1287:
I'd wear it.
[Nexus 4 Original Android Development] morfic:
I'm not talking about 3.x, was probably GB. I just am not sure, I just remember it took a lot of pushing from jbq to get it.

Btw, if they invested some time on working on android, they could maybe get some nice difference out of some nice cores?

Since it's hard making a splash in a market where core numbers are pushed beyond reason,I can understand that "they ain't all that" attempt.
[Nexus 4 Original Android Development] simms22:
that was one of the gingerbread versions, i dont remember which.
[Nexus 4 Original Android Development] joeyk240:
Much obliged gentleman.

:highfive:
[Nexus 4 Original Android Development] albundy2010:
Maybe it was one of those device specific updates. Different things were pushed out to the different crespos at in the late 2s

I don't mind them using a dual core chip at all. What I do mind is the running of the mouth that it isnt a mid range chip in todays market and so on.
[Nexus 4 Original Android Development] melbourne408:
Time to downgrade for me. Chillin' shirt design.
[Nexus 4 Original Android Development] Grand Prix:
2.3.5 I believe
[Nexus 4 Original Android Development] I_Am_Lorde:
Can anyone tell me how I would change the color settings for the kernel? I tried in trickstermod, but it doesn't allow me to change the preset?
[Nexus 4 Original Android Development] sub1287:
Trickster let's you change it however you like. Make sure you select enable on boot.
[Nexus 4 Original Android Development] I_Am_Lorde:
Thanks for the quick response. How would I go about changing it? It doesn't allow me to select anything other than the unnamed preset.
[Nexus 4 Original Android Development] zephiK:
http://xdaforums.com/showpost.php?p=44408650&postcount=4
[Nexus 4 Original Android Development] eminembdg:
Thanks for this! Been driving me nuts. I'll try it when I flash back to 4.3.

Tho even on 4.2 now I can't get the location to find me and it won't ring my phone. I think it's still rolling out maybe. Cuz obviously on 4.2 my account shows in backup and restore
[Nexus 4 Original Android Development] flaviocc:
No problem !

This fix it´s ROM side ?? Or Gapps side ??

:good:
[Nexus 4 Original Android Development] eminembdg:
Idk. I've used two different gapps and same issue .

Also tried two different 4.3 roms still same thing. But Simms was on same rom and gapps and DIDN'T have the issue. So Idk what's going on

---------- Post added at 08:10 AM ---------- Previous post was at 07:58 AM ----------

There was one difference tho, Simms dirty flashed 4.3 over 4.2. I did clean wipe
[Nexus 4 Original Android Development] Vangelis13:
(For the love of goodness, don't tell simms he actually avoided an issue by dirty flashing. Please, don't..)
[Nexus 4 Original Android Development] eminembdg:
Can't stress enough how much I love this thread and most of the people in it LOL.

In seriousness this IS THE best thread on xda, period.
[Nexus 4 Original Android Development] simms22:
this isnt the first time :D
[Nexus 4 Original Android Development] Kocai:
I imagine you on a press conference saying "My phone is special." like Jose Mourinho did back on 2004.

Edit: couldn't make a meme for it.

Sent from my Nexus⁴
[Nexus 4 Original Android Development] trillo69:
Anyone knows if that "freeze bug" on keyboars in JSS15J build is kernel related or keyboard app in 4.3? My use is mostly whatsapp and tapatalk, so it is pretty annoying. :(
[Nexus 4 Original Android Development] simms22:
4.3 jss related.
[Nexus 4 Original Android Development] Kocai:
What ROM and what kernel? I've been using PSX and different kernel but only encountered it once with Swiftkey. And I use WhatsApp most of the time. Does it happen to you very often?
[Nexus 4 Original Android Development] sub1287:
Yeah it happens no matter what kernel you throw on.

I've jumped back on 4.3 rasbean and did a clean flash and it hasn't happened to me yet. (But now that I said that...)
[Nexus 4 Original Android Development] ctfrommn:
I have yet to see it myself, lucky I guess.
[Nexus 4 Original Android Development] sub1287:
I've actually got a worse issue my phones rebooting randomly and it doesn't seem to matter what ROM I'm on, or what kernel and after clean installs. I may need to restore factory image I suppose.

Just can't figure out what's causing it.
[Nexus 4 Original Android Development] trillo69:
It happened to me in every rom with every kernel I've tried for JSS15J, so I don't know if it is a JSS15J problem or a gapps one. It happens enough often to think about flashing a JWR66V rom again.
[Nexus 4 Original Android Development] simms22:
post a last_kmsg after a reboot, lets look. maybe itll be like the person yesterday that gets reboots/powering down with all the roms.
[Nexus 4 Original Android Development] sub1287:
Will do, just never know when it'll happen. Sometimes it seems fine for hours and I think I fixed it then surprise! Lol
[Nexus 4 Original Android Development] Vortex1969:
Both on PSX and RasBean with Trinity I had been useing my phone and set it down. When I came back it was off then it took holding the power button for what seemed like a long time to finally get it to boot. It took so long to boot that I looked at my wife and said well I guess I will be hooking the phone up to the computer lol.

Not saying it's ROM's or Trinity I know everything is a work in progress. :thumbup:
[Nexus 4 Original Android Development] Vangelis13:
There was never any doubt about that.
[Nexus 4 Original Android Development] n2d551:
Night blooming cereus only blooms 1 night a year for a couple hours. I guess tonight's the night!

https://www.youtube.com/watch?v=Zbzi8XydHQc&feature=youtube_gdata_player
[Nexus 4 Original Android Development] Kocai:
The 3-5 seconds freeze happens often? That's bad. What keyboard? AOSP or Google keyboard? Have you tried with Google keyboard? You can get it from PA GAPPS or Banks. The one time it happened to me, it showed that SwiftKey isn't responding do you want to close it etc so I'm thinking it can be related to the keyboard...

Sent from my Nexus⁴
[Nexus 4 Original Android Development] ctfrommn:
Some phones are obviously more prone to this than others....Im looking into some master branch commits that seem related to this. [MENTION=4700347]trillo69[/MENTION] would you be willing to do some testing as we work on this?
[Nexus 4 Original Android Development] melbourne408:
Is that like the one from Dennis the menace?
[Nexus 4 Original Android Development] n2d551:
Yeah same one from Dennis the menace. Wow! Surprise that someone remembered that
[Nexus 4 Original Android Development] ctfrommn:
This is the oldster thread ;)
[Nexus 4 Original Android Development] stark_br:
[MENTION=1811927]simms22[/MENTION]

Hi, been testing any new version?

If yes, what improvements?

Can you share something with us?

tks:good:
[Nexus 4 Original Android Development] trillo69:
Sure, feel free to PM. I'm currently running lastest PSX build with semaphore, just let me know what you need me to test.
[Nexus 4 Original Android Development] ctfrommn:
Cool....I havent started yet, but tonight probably.
[Nexus 4 Original Android Development] simms22:
no, morfic has been busy this week. this weekend we are going after 1836 plus more maybe :)
[Nexus 4 Original Android Development] smacksa:
Might look into this commit, but it does say it is in a blind attempt so.....

https://github.com/ParanoidAndroid/...mmit/6f8dd2c6b5f602d7ad088da2813782fe2d0ed2c9
[Nexus 4 Original Android Development] ctfrommn:
We already have that one...thanks though. G is aware of the issue and seems to be looking into fixing it. Fingers crossed.
[Nexus 4 Original Android Development] pikachukaki:
For some strange reason im having screenoff drain..as you can see im only 1H SOT with 1H 2G call...and i lost 54%!!
[Nexus 4 Original Android Development] simms22:
your screen off drain is fine.. its your voice call that draining your battery. 37% was lost due to voice calls, and only 16% to the screen! unfortunately, thats normal. phone calls do use the most battery. luckily, i dont talk on the phone much, about 2-3 hours or so all month :angel:
[Nexus 4 Original Android Development] pikachukaki:
So now i get the % after the apps name...anyhow...i never had vertical drop on off screen...the call i make was at the beginning of the battery life...all other 9-10H are with no call!
[Nexus 4 Original Android Development] rickbosch:
This thing can make phonecalls ?!? :eek:

sent via mako
[Nexus 4 Original Android Development] simms22:
lol, truth!
[Nexus 4 Original Android Development] ctfrommn:
What is this "phonecall" thing you speak of? Surely youre not suggesting actual verbal dialog with another human...shiver :D
[Nexus 4 Original Android Development] simms22:
weird..

the battery graph doent show that :eek:

---------- Post added at 05:33 PM ---------- Previous post was at 05:27 PM ----------

thats when that mr bell guy picked up a can attached to a wire with another can on the other side, then spoke into it. if there was someone else on the other side, that is debatable ;)
[Nexus 4 Original Android Development] ctfrommn:
Haha....sad thing is were likely 2 of the few that remember corded phones and rotary dials. ;)
[Nexus 4 Original Android Development] simms22:
oh gosh, rotary dialing :)
[Nexus 4 Original Android Development] smacksa:
What do your partial wakelocks look like. The PowerManagerService.Wakelocks on the Kernel Wakelocks screen are for wakelocks caused by apps in user land. 12.7% of your battery must mean you are syncing/pushing quite a bit. I have lots of apps syncing and it only hits 3% of my battery life. Looks like the drops are correlated with signal drops so it could be location provider.
[Nexus 4 Original Android Development] DontPushButtons:
Hah, remember dialing popcorn to set the correct time? Ohhh the days before pocket-satellite up link.
[Nexus 4 Original Android Development] Vangelis13:
Pf. Elitist crew here..
[Nexus 4 Original Android Development] maverick_hunter:
These 5 second freezes are really starting to get on my nerves. Almost enough to send me back to CM10.1. :mad:
[Nexus 4 Original Android Development] ctfrommn:
Lol....you even have phones over there :p
[Nexus 4 Original Android Development] n2d551:
I remember going to my grandmother's and having to use the archaic rotary dialer

Or calling to get the correct time & weather. Anyone remember the party line
[Nexus 4 Original Android Development] pikachukaki:
See thats whats im talking!!
[Nexus 4 Original Android Development] n2d551:
Party line oldest hangouts app

http://en.m.wikipedia.org/wiki/Party_line_(telephony)
[Nexus 4 Original Android Development] ctfrommn:
Haha....yep. And dialing an actual "operator" for stuff....oh man, we are old. Next we'll start talking walkmans(the real ones with cassettes) and boomboxes :D