yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] alen1901:
What the.. XDA is really becoming strange place. No words to say.

Sent from Sparkling Nexus 4
[Nexus 4 Original Android Development] Koraboros:
I'm using R146 with AOKP M1, and I noticed that msm-hsic_host was up again, to 1 hour after only 3 hours of battery time....

Then last night the signal started going out... anyone have similar issue?
[Nexus 4 Original Android Development] republitarian:
I'm on cm 10.1 RC2 and had the same msm_hsic problem with r146. My recommendation is to use greenify and disable notifications u don't need. Also being in a better signal area helps.

The above solutions fixed my problem as msm was up to 16% but now its @ 2% on BBS.
[Nexus 4 Original Android Development] nachordez:
I said it previously... Don't feed the troll!

If fed, it grows up...

Franco, you know what's really all that, so forget, and enjoy your nice work :beer:

nexus4 / stock / Franco.kernel / V4A sound

gt-p5110 / CM 10.1 / Dhollmen kernel / V4A sound
[Nexus 4 Original Android Development] drakester09:
I'm an user and I respect franco's work. I'm not a fan in the sense that I would follow him blindly or defend him if he was wrong, as matter of fact, this is my first Nexus and franco kernel usage.

So, no strings attached.

Please, stop referencing my post as a basis of your argument, I never pointed out anything about franco's app.

Again, I can tell you with my full honesty: your application is very functional, seems well constructed but really poorly designed and a huge mess in terms of UI and cohesiveness.

You use your own iconography which is taken out of Windows or Iconfinder, that feels terribly out of place in Android.

You use icons in tabs, where they serve no functional or aid purpose as they are barely readable and blurry.

You use custom (+) and (-) icons where you could have used something, heck, anything that looks less out of place. A regular, small and square button widget for example.

Gradients in bars, that look out of place, a flatter look or something more subdued would look more in line with the rest (see Data Usage bars for an example)

Icons in the action bar, that do not fit or resemble anything else in Android. Despite that there are several icon packs that are thought with the design in mind, even in the site: http://developer.android.com/design/downloads/index.html

The icons do not fit at all with the Iconography and your justification is oversimplifying it. See how Icons should look like:

Buttons without labels and the aforementioned blurry icons, in the same size and next to others that do have text. (I know the app is still in beta, see Terminal Emulator for that).

Sure the APIs give you leverage to construct whatever eldritch abomination of an application you can think about, but it's all about looking consistent towards the OS or the direction.

I recommend you to look at this site for apps that use the Holo language in a good measure:

http://www.holoeverywhere.com/

Out of respect of franco's work and this thread, I will not address you here anymore, if you want to keep discussing this, please via PM.

I won't reply to you anymore in this thread or feed your trolling attempts.
[Nexus 4 Original Android Development] admiez:
Hey 3c I disagree with the users that say this is a kernel development thread only and thus think your comments do not belong here. It's obvious that Franco uses this thread to get feedback for both the kernel and the app. So you're right on that.

However, the issue is that you may have come across to many as just wanting to follow guidelines just to follow them, and just because he happened to mention the benefits of following Google's guidelines.

What I mean by this is that, for example, on your first point about using the Preferences functionality. Obviously he does so because it makes sense from a coding standpoint to take advantage of that built-in functionality; a lot of the app is just that, settings for the kernel. What you can do better is to provide examples of content, or other functionality that can be achieved if he does it in a different way; explain the advantages, if any, as they apply for this case, not just in the general sense. As if he changes it and it will just contain the same, and look the same, then there's no point in doing that extra work just to be able to say it follows the guidelines to perfection.

Franco is good at directly answering for himself these inquiries, my comment has to do only with how you can get your point across better. Also, other users should not just start to bash one another when you see that Franco himself addresses the questions in a good manner and listens to the feedback even if he disagrees.
[Nexus 4 Original Android Development] admiez:
I know that at least some other users have posted about this. Did anything change in r143 that could affect wireless connectivity? I thought, as others did, that the issue must be with the network, but now I'm thinking there has to be something up with the phone.

My basis for this is that:

- I haven't changed anything else, I am at the same place and never had any problems whatsoever in the past.

- I have another device connected to the same network that is not exhibiting any connectivity issues (the signal bar under Battery settings stays green throughout vs green with tens of red lines).

- Once the issue starts to occur, a reboot fixes it for a long while. Toggling Airplane mode makes no difference.

The log just shows a repeating pattern of system errors that involve a USB device (/dev/ttyUSB0). https://www.dropbox.com/s/0aco710t1jlecr2/2013-06-02-15-28-47.txt

Keep in mind I'm still in r143, just in case it has been fixed since then. I just didn't see any acknowledge of changes related to this with the latest versions.
[Nexus 4 Original Android Development] Mo'HAWK:
I'm trying that new radio suggested earlier in the thread. Hopefully it helps me out because my signal is pretty bad where I'm at and it drops quite a bit.
[Nexus 4 Original Android Development] ricey1986:
Gotta love this kernel, it just works, tried others on XDA but always come back to this. Its great for the noobs but also great for us who want to tinker
[Nexus 4 Original Android Development] thebryceee:
I'd use the new radio if I could access LTE. My signal has been consistent tho on 146.
[Nexus 4 Original Android Development] Zainiak:
A little off topic, but what font and rom is that? it looks nice...
[Nexus 4 Original Android Development] justibasa:
I'm actually having the signal issues on 146 also. When I'm on it I can't use mobile data at all. Wi-Fi seems to work great though. Really strange. Went back to the test kernel and all is back to normal. I have went back to 146 3 other times to test this and lose mobile data every time. Thanks for the great kernel Franco!

Don't like me........BITE ME!!!
[Nexus 4 Original Android Development] Mo'HAWK:
I do like that font also what is that? Possible download link too?
[Nexus 4 Original Android Development] thebryceee:
Sony Sketch. Font Installer on Google Play.

https://play.google.com/store/apps/details?id=com.jrummy.font.installer
[Nexus 4 Original Android Development] strikelight:
I sincerely hope that the other obvious user was given the same reprimand by the moderators, for sticking around this thread with an immature and provocative motive.

Otherwise, I would give a friendly suggestion to the xda mods, that they re-evaluate their current investigative procedures.
[Nexus 4 Original Android Development] melbourne408:
[MENTION=3292224]franciscofranco[/MENTION]

My love for XDA started after my sk2 service went out, and the limitless idea of, something so stunning as Swype came into play, years ago. Look how long it took for them to finally get their crown, a couple months back.

You've fought the odds.

My captivate kernel Dev was TheEscapist, then for my I777 was tkglitch, and ktoonsez.

You face any mountain, climb it.

Keep your head up, oil is always crude when the numbers trace back. Have you ever been issued an apology?
[Nexus 4 Original Android Development] LibiSC:
The problem appears when the optimization misinterprete the code and eat parts that is not supposed to.... I think is dangerous for kernel code not for applications or ROMs.. But let's see how it goes :thumbup:
[Nexus 4 Original Android Development] RandomDude:
I just wanted to advise that I'm on r146 UV only with cm10.1 recent nightly and I use PIN unlock on the lock screen.

Quite often the first digit of the PIN is not detected (I start typing as soon as I can see the numbers). I suspect that this is due to with touch input CPU settings causing a touch recognition delay on screen on. Is anyone able to confirm this behaviour?
[Nexus 4 Original Android Development] admiez:
I was looking more into it. It seems that there is some kickstart process that goes off and it all goes wrong from there on, and the same pattern keeps repeating itself over and over again every few minutes.

Check out this short log (I have removed the irrelevant stuff) to show once instance of when the issue occurs. Do you see the same?

https://www.dropbox.com/s/4iya8xsxiqa992y/2013-06-02-16-47-37.txt

You see messages such as:

06-02 16:46:38.389 E/kickstart(3415): ERROR: function: connect_and_configure_device:332 Not Connected to the device: /dev/ttyUSB0

The thing is, I enabled Airplane mode to remain in Wi-Fi only, and noticed the Wi-Fi cycle off and on too. When I checked the log, it shows the same pattern, but I have not rebooted yet, which seems to get rid of the issue for some time. It appears that once it happens it just keeps happening until a reboot.

The signal bar image shows how even after airplane mode was turned on, the resets kept occurring.
[Nexus 4 Original Android Development] melbourne408:
Do you use sleep2wake?

And, could be too much of an -uv that's giving you stutters

(Just tested it out myself, as I'm too lazy to load my uv settings. Everything works fine with no lag at all. )

(This is with 146 and sabermod.)
[Nexus 4 Original Android Development] biggofer:
Hi , I would like to try your new version , can you share link ? Thank you
[Nexus 4 Original Android Development] ledionkoci:
+1
[Nexus 4 Original Android Development] markd0wn:
Here.
[Nexus 4 Original Android Development] LaboDJ:
No...

New one with -O3 optimization is private... i'm testing it to see if there is any problem... release tomorrow morning, tonight i'm trying to build cross compiler from sources.
[Nexus 4 Original Android Development] biggofer:
His last post makes me believed there is newer one , but thank you
[Nexus 4 Original Android Development] markd0wn:
Oh didn't realize that, thanks, looking forward to it.
[Nexus 4 Original Android Development] Utini:
randomly have to unlock my SIM card. Happens since r146 (used M2 before that). Well I flashed today, since my battery went to 35% i get this random SIM-Unlock request every few minutes :o
[Nexus 4 Original Android Development] drawde40599:
Don't think its kernel related , but try disable the lock , settings/ sim card lock, remove it , reboot . then set up agn if still want that feature it should stop , u may need new sim , had this problem on my Gs2 , the lock was more of a pain then what its worth , try cerberus app in play store i find it much more convenient for locking down phone
[Nexus 4 Original Android Development] Beremus:
His version with Linaro does indeed feel smoother.
[Nexus 4 Original Android Development] morfic:
If linaro is at 4.8.1, that might very well be.

Works great on manta and even mako.

4.7 you'd find Google 4.7 produced better results than linaro 4.7

Would love to see a Google 4.8 reason. :)
[Nexus 4 Original Android Development] franciscofranco:
Will happen sooner than later you'll see!
[Nexus 4 Original Android Development] Barguast:
Is 'Conservative' still the best governor for battery? I know a lot of work has gone into the others lately, so wondered if there were any real differences these days?
[Nexus 4 Original Android Development] peikojose:
I can confirm this.
[Nexus 4 Original Android Development] thracemerin:
I don't seem to be able to produce a bootable mako kernel of any sort with Linaro 4.8 unless I change the allocator from SLUB to SLAB.
[Nexus 4 Original Android Development] jassycliq:
Showp1984s kernels have always been running -O3 without issue. The only problem tends to be loading the modules though that tends to be ROM specific.
[Nexus 4 Original Android Development] eddy4823:
used to change fonts by rom toolbox pro and used to stuck at boot animation for infinity time. i fear this app will act the same.
[Nexus 4 Original Android Development] mitchdickson:
Then nandrood before?

Sent from my iPad 4
[Nexus 4 Original Android Development] eddy4823:
sorry what ?
[Nexus 4 Original Android Development] ÜBER™:
Nandroid. Backup in recovery.
[Nexus 4 Original Android Development] LaboDJ:
I opened a new thread for Linaro O3 compiled franco nightlies...

I don't want to pollute franco thread anymore with my talks about toolchains, optimizations and so on, sorry Franco , I know you don't like these kind of talks in your threads.

Please everyone who want to try out Linaro builds to come HERE.
[Nexus 4 Original Android Development] manulemaboul:
OMG, did only 2h SOT... Playing lol :p

wich is awesome, I was like "how long I've been playing ? Have I dismissed the low batt notification already or what ? :p

Halfed the gap Franco :p, I'm getting better :D

10 000 points to go now,

Envoyé depuis mon Nexus 4
[Nexus 4 Original Android Development] pkelly517:
See? Maybe.

Believe? I don't know :)
[Nexus 4 Original Android Development] alanwyl:
I don't have any problems in the last few days. Maybe it is a regional problem for network.
[Nexus 4 Original Android Development] thebryceee:
Probably, cause I never had any problems either
[Nexus 4 Original Android Development] santeana:
Loving the new beta app franco! Thank you :)
[Nexus 4 Original Android Development] morfic:
Ditto.

Haven't had a chance yet to ask linaro why.

Something I wouldn't have guessed without simms22's last_kmsg.
[Nexus 4 Original Android Development] morfic:
We have time.

Since I don't see the origin of the -O3, I'll just add this here: the larger object code is not always better, that something built with -O3 runs and that -O3 is a higher optimization level doesn't mean it's better.
[Nexus 4 Original Android Development] thracemerin:
I noticed that my first attempt failed, then noticed that stratosk switched from SLUB to SLAB on the same day that he started using 4.8.1 and inferred that his attempts to use SLUB failed in the same way.
[Nexus 4 Original Android Development] franciscofranco:
To be honest I have no issues with that stuff on this thread at all. Constructive criticism and constructive development and experimentation is always welcomed here :)
[Nexus 4 Original Android Development] franciscofranco:
It unfortunate seeing SLUB is the default memory allocator for a while on Linux. I don't know how to measure differences between both allocators but if SLUB is default then it must have a reason. Its sad that a Kernel compiled with Linaro doesn't boot with SLUB.
[Nexus 4 Original Android Development] thracemerin:
Gotta be an issue with the toolchain, I'm assuming they'd fix this since there doesn't seem to be an explanation of why.
[Nexus 4 Original Android Development] noneabove:
Hope you recompile for n7 and n10 toooo! :)
[Nexus 4 Original Android Development] franciscofranco:
I'm really tight on time, all other devices besides the N4 will be updated with stuff that I've been working on the N4 on the latest nightlies once I finish the app update ;)
[Nexus 4 Original Android Development] LibiSC:
Mine enters in a bootloop when I changed it from slub to slab and used linaro 4.8.1

I'm on PA
[Nexus 4 Original Android Development] noneabove:
Glad to hear it, all I wanted to know, looking forward to it ;) already get best performance on n10 with your kernel but I know for sure stuff you've done since for the n4 made it much better :D
[Nexus 4 Original Android Development] LibiSC:
SLUB it's the improved version of SLAB... SLUB handles more processors better if I remember well and other stuff... And the other SLOB is for devices with low memory

---------- Post added at 02:43 AM ---------- Previous post was at 02:34 AM ----------

Makes sense... My concerns come from my days in Galaxy Ace where I used o3 and The device started acting weird but i used a bunch of modules there.
[Nexus 4 Original Android Development] admiez:
I thought it was the network until I noticed my other device is not having issues. And, the fact that it just takes a reboot for the issue to disappear for while.. is suspicious.
[Nexus 4 Original Android Development] LibiSC:
Makes sense... My concerns come from my days in Galaxy Ace where I used o3 and The device started acting weird but i used a bunch of modules there.
[Nexus 4 Original Android Development] thracemerin:
So it boots with SLUB using the 4.8.1 toolchain? cuz mine won't (all I get is stuck at the Google logo for an infinite period of time) but it boots fine with SLAB.
[Nexus 4 Original Android Development] manulemaboul:
From my point of view, based on personnal observations, newer gcc indeed seems to help, for linaro toolchain I don't know.

And now I know what to edit to make it with gcc 4.7.3 :)

Envoyé depuis mon Nexus 4
[Nexus 4 Original Android Development] LibiSC:
It doesn't boot with SLUB either... With slab I get to the boot animation

And then bootloop... I'll check the warnings I deactivated a couple of thing in the makefile
[Nexus 4 Original Android Development] tebower:
I'd like to throw in my name to confirm the data connection issues as well. Since 146, I have seen mobile data drop out every few minutes. Bars go blank and take minutes to reconnect. Sometimes inexplicably in a full 3G area, I am suddenly on Edge. Not sure if that's related, but after a few minutes, it finally reconnects to 3G.
[Nexus 4 Original Android Development] espionage724:
I've had no (noticeable) cellular connection issues at all with r146 + rasbeanjelly + .54 radio + T-Mobile.
[Nexus 4 Original Android Development] franciscofranco:
I'm aware of some strange network problems. Will be fixed on r147.
[Nexus 4 Original Android Development] kyokeun1234:
I had this mobile data loss problem in r143 but since than, I see no problem like that happening again. And if it does happen, it is very minimal.
[Nexus 4 Original Android Development] sir*mez:
Awesome thought I was the only one. Even with the new .54 radio. I had to revert to back to .48 to get my t-mobile service to work.
[Nexus 4 Original Android Development] franciscofranco:
Another beta has been pushed:

- Improves the back button action in the work flow of the app

- Fixes the Color Control FC for the Galaxy Nexus

- The Support tab is moved to the bottom of the list and the new default fragment is a a Status list of important info like max/min/io_sched/temperature/selected power mode/selected color profile. I'm open for suggestions of what kind of info I can add here for easy check of info when someone opens the app and if this panel is useful at all

- Fixed a bug where the app could be frozen after installing the latest beta update

- Lots of smaller and not user noticeable bugs and kinks

Changes will be less noticeable from now on, I want to concentrate on bugs so that I can ship this soon for production so that I can work on new and promised features.
[Nexus 4 Original Android Development] admiez:
In my case it started about half a day of running r143. It wouldn't drop to Edge, just cycle off and on, and not take too long to reconnect. Yours might indeed be network related.

Toggling the radio off would not help. With a reboot would the problem would go away right away and would not show up again for hours. After today's incident, I upgraded to r146 from r143, and rebooted. Thus, I have not had the issue since then, but it's only been a few hours. This is on stock rom and radio with AT&T.

Great!
[Nexus 4 Original Android Development] Mo'HAWK:
Where can I get the beta on Google+?
[Nexus 4 Original Android Development] trailblazerz11:
I tried several days ago with the exact same results :( Opps error I'm too lazy to dig into...

Odd thing is 4.8.1 compiled image is smaller than 4.7, 5.3MB vs. 5.6MB
[Nexus 4 Original Android Development] franciscofranco:
Join https://plus.google.com/u/0/communities/117966512071636110546

and click here https://play.google.com/apps/testing/com.franco.kernel Google policy, only community members can access the beta.
[Nexus 4 Original Android Development] 3dupunk:
I installed the test updater and i gotta say it's an improvement, quite nice. My only complaint at this time is the back/return button.
[Nexus 4 Original Android Development] Redneck Trash:
I had all kinds of issues with the .54 radio. Data connection, downloads, uploads. It was a mess.
[Nexus 4 Original Android Development] Mo'HAWK:
I already follow ya but wasn't sure where to get it. Thanks
[Nexus 4 Original Android Development] thebryceee:
Google takes forever to update!
[Nexus 4 Original Android Development] yokuyuki:
I can't really explain but the phone is getting awfully hot on r146 while wirelessly charging. I know that wireless charging does it make it warm due to induction, but it's way hotter than usual like the cores are running at max speed while asleep or something like that. Looking at the temperatures, while charging the battery is at 42 C and the CPU is at 50 C.
[Nexus 4 Original Android Development] markd0wn:
Were these network problems introduced in #146? or earlier? any chance they existed on #140? I had some mobile data problem while using #140 and wasn't sure if it's rom/kernel/something else, so I'm wondering if there's a chance that was introduced in 140 or only in recent builds. Waiting for the fix either way...
[Nexus 4 Original Android Development] drawde40599:
Not seeing this on Francos 146 , orb actually quite cool , ill check actuall temps here later for comparison if u want
[Nexus 4 Original Android Development] Are.Two:
[MENTION=3292224]franciscofranco[/MENTION] The new update looks great and runs very smooth and fluid. Having the status screen be the first page is great. The only thing I noticed, and again has to do with the headers. When you push the back button from whatever option you choose in the menu, the header doesn't change when you reach the main status screen. Example, choosing the color control option on the menu then pressing the back button. You get the main status screen, but the header still says color control.
[Nexus 4 Original Android Development] immunityx:
edited moving to color thread
[Nexus 4 Original Android Development] ben_pyett:
There is a dedicated thread regarding colors in the general section I think, that would be a more suitable place for the color discussion and postings.

Edit

http://xdaforums.com/showthread.php?t=2039607
[Nexus 4 Original Android Development] terranox:
Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] terranox:
250

240

255

The best for me!

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] immunityx:
Looks like people with pre-yellowed tint screens might want to try the cooler settings (more blue)

And people that didnt have the yellow tint screens use the first settings monkeybrew posted.

back on topic... wakelock bug seems to be rally gone in R22 so far!
[Nexus 4 Original Android Development] kitch9:
My phone is stock... Is there any way of getting this kernel onto my phone without wiping it?
[Nexus 4 Original Android Development] phositadc:
Could people post some BBB screen shots showing hsic wake lock? I'm not rooted or unlocked but if the fix really worked now might be the time.
[Nexus 4 Original Android Development] mundixx:
@franco,

If I am in an area with bad/no signal, is the msim wakelocks expected to appear?
[Nexus 4 Original Android Development] ben_pyett:
sorry for double post..... Hoping is read this time, There is a dedicated thread regarding colors, see

http://xdaforums.com/showthread.php?t=2039607 , that would be a more suitable place for the color discussion and postings.

if you are not presently unlocked then i don't believe so as initial unlock will wipe.