yashsingh1/xdaforums huggingface dataset:
[Nexus 7 3G Android Development] Synman:
jfmcbrayer took the time to rebuild his kernel at our request and has addressed all tangible items we've brought to the table. I see no reason why I would venture beyond his contribution at this time.

However, you are more than welcome to experiment and flash whatever kernel you would like. Please share your experiences.
[Nexus 7 3G Android Development] paolocorpo:
If you see my previous post

http://xdaforums.com/showpost.php?p=58566684&postcount=331

i already addressed others request that are:

More performance (i noted several small lag ... acceptable .. but they are present) and double tap to awake or swipe to sleep ...
[Nexus 7 3G Android Development] Synman:
You're going to have to be more specific. A volkswagon will never be a porsche.
[Nexus 7 3G Android Development] paolocorpo:
You are right ... but the hope is the last to die :)
[Nexus 7 3G Android Development] Synman:
lots of hope has died over the years with the N7s
[Nexus 7 3G Android Development] jfmcbrayer:
Oxydo also fixes the baseband wakelock issue. I wrote the initial patch to disable it, Sgt. Meow wrote one that replaced that with a customizable timeout, and I adapted that to include disabling it if the timeout is set to 0. So you do have a choice with this patch.

I can't do much on performance without a more specific diagnosis, I'm afraid. You might want to try tuning the smartmax CPU governor to scale up more aggressively, maybe play around with the IO scheduler.

I'm not going to implement double tap or swipe to wake, because they introduce a wakelock that can affect battery life negatively. I thought swipe to sleep is a ROM feature, not a kernel feature, but if you can point me to a kernel that has it, I could cherry pick it.
[Nexus 7 3G Android Development] Synman:
there's likely a framework sleep feature others have tied into. Sounds reasonable that a ROM should be able to put itself to sleep.
[Nexus 7 3G Android Development] paolocorpo:
Elementalx kernel (suitable for several device but not for N7 Tilapia) has these two features: double tap to awake and swipe to sleep

I just reinstalled Carcosa a33 ... and i will try to set it to have more performance

Have i to use TriksterMod ?? i think so

I have increased voltage for all frequences (+50) and i have increased max frequence (from 1500000 to 1600000)

I don't know others triks .. I am not able to do more ... :(

Inviato da Lumia820 con Tapatalk
[Nexus 7 3G Android Development] jfmcbrayer:
Open TricksterMod, and go to the 'general' page. Make sure the governor is 'smartmax', and if you have to change it, click 'apply' before the next step. Click on the 'Governor Control' button. Raise 'awake_ideal_freq' to 910000. Raise 'boost frequency' to 1150000. Reduce 'max_cpu_load' to 70. Reduce 'min_cpu_load' to 40. Raise 'touch_poke_freq' to 1150000. Click apply. These settings should increase cpu responsivity a bit at the cost of battery life.

You could also fool around with the IO scheduler. I think the default choice (SIO) is the best one, but you could also try noop and deadline to see what works best for you. It does not hurt to lower read ahead buffer size to 512.

Let me say that after a bit of use, I am finding performance under Synman's GwT to be quite adequate. I was concerned with bad screen-on time, but I actually measured it, then went back to OmniROM 4.4.4 for a couple of days, and found that my impressions were wrong, and the SOT was about the same on both. I also noticed lags in 4.4.4 that I hadn't noticed previously. So except for the slow task overview (which others have said is also present in stock), I'm finding this Lollipop ROM to be no slower than a notably fast KitKat ROM.

One more battery life tip. I did have some battery drain and slow charging associated with Google Play Services. The AnalyticsService was running 100% of the time; I disabled it with the DisableService app (use with caution), and my battery life and slow charging improved markedly.
[Nexus 7 3G Android Development] paolocorpo:
I have done what you suggested in red

I ahve a dubt: i have to disable GOOGLE PLAY SERVICE using Disable service app ???

I will come back to give my feedback

Many thanks

Paolo
[Nexus 7 3G Android Development] jfmcbrayer:
Google Play Services isn't just one service; it contains dozens of services. The only one I'm recommending to disable is AnalyticsService. You don't even need to do that unless "geeky process stats" under developer options shows that it's running 100% of the time.
[Nexus 7 3G Android Development] paolocorpo:
I don't found AnalyticsService into folder System App inside Disable Service app :(
[Nexus 7 3G Android Development] jfmcbrayer:
It's one more level down, under Google Play Services.
[Nexus 7 3G Android Development] paolocorpo:
founded it :)
[Nexus 7 3G Android Development] paolocorpo:
i dont believe in app for benchmark as Antutu but ...

.... the score was around 20000 and now it is around 24000 :)

Very good

it seems run better now

No lag and mor eperformance

Very good

many thanks to SYNMAN and jfmcbrayer
[Nexus 7 3G Android Development] JROppenheimer:
How is battery life affected?
[Nexus 7 3G Android Development] paolocorpo:
I need more time to understand if there is a smaller life of battery as price for better performance

I will come back again asap

Inviato da Lumia820 con Tapatalk
[Nexus 7 3G Android Development] whole.earth:
Yay! I just did the thing with analyticsService and charging became faster! Cannot tell now about battery life, but I'll be testing.

BTW I'm on Franco's kernel, but they are almost the same with caracosa.
[Nexus 7 3G Android Development] brainvision:
hey mate, do you plan to go on developing the ROM? Last build is from January 8: will you build a new one with the updated CM repo?

thanks a lot! ;)
[Nexus 7 3G Android Development] paolocorpo:
I noted a smaller drainage of battery during normal usage and during standby

I am using Carcosa on Synman
[Nexus 7 3G Android Development] Synman:
Only thing I can add is that GwT is based on AOSP not CM. Good luck finding an AOSP build newer than LRX22G atm ;)

https://source.android.com/source/build-numbers.html
[Nexus 7 3G Android Development] brainvision:
Woop! Obviously I made a big mistake! I thought it was based on CM!! ??
[Nexus 7 3G Android Development] hcarrega:
Love your ROM nothing to say :)
[Nexus 7 3G Android Development] 3XTR3M1ST:
I cant get my PC (win 7) to detect the nakasig even after installing the google usb driver (http://developer.android.com/sdk/win-usb.html)

help?
[Nexus 7 3G Android Development] Tommmii:
Has any one managed to get F2FS working with this ROM ?
[Nexus 7 3G Android Development] Xenon.Kay:
Is there a simple way to switch between the AOSP and carcosa kernels built for GwT? The 3G radio on my N7 is exhibiting some odd behavior on the carcosa version and I'd like to be able to test whether AOSP does the same thing under the same conditions.

I've done this on my N7 but AnalyticsService just restarts itself after a while, despite having been disabled by Disable Service. Seems like a more aggressive approach involving Xposed might be necessary to make the service stay down.
[Nexus 7 3G Android Development] fishwithlungs:
Sound quality from built in speakers

[MENTION=3129719]Synman[/MENTION] - great work,the ROM is really smooth and fast.

One thing I've noticed,the built in speakers do have a problem,the buzzing and distortion makes it impossible to turn the volume more than halfway up,headphones are working fine.

No such problem on 4.4.4.

Am I the only one with this problem,or is there a fix for built in audio?
[Nexus 7 3G Android Development] jfmcbrayer:
I'd install the AOSP version of the ROM, then back up your not partition, and install carcosa kernel from the zip file on the thread in my sig. Alternatively, to install the AOSP kernel over the carcosa kernel, extract the boot.img from the ROM zip and flash it with Flashify.

I've noticed this, too.
[Nexus 7 3G Android Development] Xenon.Kay:
Thanks for that. I'll test for a bit and see if the behavior I've experienced persists under different kernels. I'll document what I've been seeing once I'm sure I know myself.
[Nexus 7 3G Android Development] jfmcbrayer:
I'll be interested in seeing your results. If there is a difference, I'll have another test for you.
[Nexus 7 3G Android Development] Xenon.Kay:
Okay, I'm putting the AOSP kernel through the same routine and with only this change there are already some noticeable differences.

Both kernels:

The tablet is connected to wifi in a location overnight where it doesn't get cell reception (a good 8 hours or so typically). When later taken away from the wifi signal and into an area with reception, it does not roll over to mobile data gracefully. The cell radio indicator shows a good signal but with the exclamation mark indicating that mobile data is not available. Turning airplane mode on for a few seconds and then turning it off again to cycle the radio while already within cell reception causes it to correct itself.

Carcosa only:

After the tablet has been asleep for a while (maybe half-hour to hour range), it loses mobile data and does not recover after wakeup even though it's under good reception the whole time. The radio icon indicates a good signal but mobile data is not available, similar to the above behavior. It will repeat this all day long, every time it sleeps long enough. Cycling airplane mode usually allows it to recover, but not always. Which leads to the strange bit:

Sometimes when the mobile data is down and airplane mode is switched on, the radio instead stays on and will not turn off, as though it were stuck. It would have airplane mode on yet the radio would stay up and indicate a signal. It would even still visibly switch between HSPA and 3G according to tower availability. Once this behavior occurs it persists indefinitely until the tablet is rebooted.
[Nexus 7 3G Android Development] jfmcbrayer:
Good, thanks!

Now try this. On carcosa kernel, do the following as root:

echo 20 > /sys/module/baseband_xmm_power/parameters/bb_timeout

See if this affects the connection loss you're seeing. This will re-introduce the baseband_xmm_power wakelock, but with a 2 second timeout.
[Nexus 7 3G Android Development] Xenon.Kay:
Cool, I've made a note of that and added it to-do list.

I still need to test the AOSP kernel a bit more though because I'm not convinced it's unaffected by the stuck radio behavior. It could be it just hasn't cropped up yet since it only drops the mobile data connection once a day. And presumably the reason for that is the wakelock keeping the radio up all day while it has reception.

edit:

I haven't been able to duplicate the radio sticking in airplane mode under AOSP so far and this test may take quite a while, so I've gone ahead and switched back to the carcosa kernel with the suggested timeout applied and will be monitoring its behavior.

update:

OK, with the carcosa kernel and bb_timeout set to 20 the internet connection failed to reestablish the first time the tablet was woken up after screen off for about one hour. The radio indicator shows a good 3G/HSPA signal but there's also the exclamation point and a lack of internet connectivity. Airplane mode on and off to cycle the radio restores internet connectivity. I'll be testing this some more to see if the frequency of this behavior has changed with the new timeout parameter. The radio hasn't gotten stuck "on" yet but the sample size for this test is still a bit small.
[Nexus 7 3G Android Development] jfmcbrayer:
Thanks; just to clarify, does carcosa with the timeout work like stock for you, or is the signal loss still different from stock?
[Nexus 7 3G Android Development] Xenon.Kay:
After testing carcosa with the suggested bb_timeout parameter for a couple more days it seems like it happens less often than without that change. Maybe 3-4 times per day now, as opposed to upwards of 10 before enabling the 2sec wakelock timeout.

This is still more often than on stock though, which would exhibit the behavior at most once per day after being asleep on the charger for approx. eight hours.

The tablet also did something different this morning: It crashed and rebooted after being taken off the charger. The screen came on as normal when the charger was disconnected, but a few seconds later it suddenly went blank. A few seconds after that it displayed the Google logo and started booting back up. This was with a full battery and still on the carcosa kernel with bb_timeout set to 20.

The only apps on the tablet consist of what comes with the GwT ROM, CM12 GAPPS package, SuperSU, K-9 Mail, Netflix, Terminal Emulator, VX ConnectBot, Hacker's Keyboard, DisableService and Flashify.
[Nexus 7 3G Android Development] jfmcbrayer:
You can keep tweaking the wakelock timeout, of course. Use any value you want, in tenths of a second. The trade-off is, of course, that eventually the battery usage due to the wakelock will also be the same as stock.

The crash sounds like it was just random, but if you had a last_kmsg, I could look at it.
[Nexus 7 3G Android Development] Xenon.Kay:
The timeout does seem to have some kind of effect, so I'll keep playing with it. There's a long way to go before I reach the stock timeout.

I didn't think to check /proc/last_kmsg at the time, but I'll keep it in mind for next time. I think that was probably the first time I've ever seen this tablet crash during normal operation though, so I'd be surprised if it happens again.
[Nexus 7 3G Android Development] spideytan:
thanks for the rom. just flashed it, and would like to ask how to get usb-otg to work, cos last i used omni rom usb-otg is working. help needed.
[Nexus 7 3G Android Development] tedr108:
With a stock rom, I think you will have to use an app: StickMount by ChainFire works for me. Honestly, I have not used it on Lollipop, yet.
[Nexus 7 3G Android Development] spideytan:
Have installed StickMount and problem persists. Hope this problem will be resolved soon, and I guess its really Lollipop issues with OTG. Cos this problem never exists before in official KitKat and Omni Roms running 4.4.4
[Nexus 7 3G Android Development] jfmcbrayer:
Synman, it looks like 5.1.0 sources are available for tilapia (https://android.googlesource.com/device/asus/tilapia/+/android-5.1.0_r1). Will you be updating GwT ROM?

I'm currently running a carcosa kernel with 5.1 updates (experimental build) with GwT 5.0.2, and so far, all is shiny.
[Nexus 7 3G Android Development] paolocorpo:
It would be super!!!

I am tour italian supporter

[MENTION=4075479]jfmcbrayer[/MENTION] : Have you already shared tour last updated kernel ?
[Nexus 7 3G Android Development] jfmcbrayer:
I have not, but I will when I get some time. The updates are not actually that significant, IMO. They add support for hardware acceleration of in-kernel encryption routines, which might be helpful to people with device encryption. On the other hand, the stock kernel then disables that support, so maybe it's not fully baked.

EDIT: It's now updated.
[Nexus 7 3G Android Development] Polarfuchs:
Read 7 posts above yours.

#12 http://xdaforums.com/showpost.php?p=35266943&postcount=12

No you can't make voice calls.
[Nexus 7 3G Android Development] ChocolateBurmese:
Does that mean I don't need Google Voice and don't need to tether?

Does this mean I can send test messages without a Google Voice number and without tethering the Nexus to my mobile phone?

I live in Australia and don't have access to Google Voice, not do I want to tether.

Thanks in advance.
[Nexus 7 3G Android Development] kenkiller:
No. No.

No.

Yes. Yes

Yes.
[Nexus 7 3G Android Development] manekineko:
Holy ****, coming from a non-Nexus device, I wasn't expect this.

Did flashing the system image using the included instructions wipe out my internal storage? It sure looks like it just wiped out my internal storage including clockworkmod backups.

For future reference, what is the proper way to try ROMs and flash updates without wiping out my whole internal storage?

---------- Post added at 05:20 PM ---------- Previous post was at 04:28 PM ----------

Incidentally, after trying it the notification pull down for settings on the right doesn't seem to work. I can't figure out how to pull it down.

Also, for some reason my tablet seems to think I have a voicemail waiting for me on my tablet data-only plan with T-Mobile.
[Nexus 7 3G Android Development] Synman:
Flash GAPPs ... This is a vanilla ROM. The Google apps pack referenced in the first post will get the right side fly out back.

Guess you have a voicemail LOL :)
[Nexus 7 3G Android Development] Synman:
Also to stem the flood.... Make sure you have text on your tablet only plan. If T-Mobile is anything like AT&T you're going to get charged something like 15 cents a text without it.

You've been warned.

Also not doing the wipe (-w) in fastboot with system.img would likely preserve your userdata. It is always better to understand the mechanics of a process prior to executing it...
[Nexus 7 3G Android Development] Synman:
Got a handful of changes queuing up for V4:

Added CellBroadcastService (The new National Emergency SMS service)

Changed PRODUCT_NAME from full_tilapia to nakasig. Doing so keeps DeviceCapabilityManagerImpl from complaining about an unknown device profile

Added "Read on Receipt - Dictate SMS messages using TTS" to Mms.apk. This is a preference driven setting defaulting to Disabled. With it enabled any SMS messages you receive will be voiced back to you as they are being added to the notification bar
[Nexus 7 3G Android Development] Synman:
A couple more additions to V4:

APN Settings Editor Preference no longer a dialog (exposed actions)

Phone Settings (and its children) no longer dialogs (fixes SIP Providers Editor)

A couple screenshots:

​
[Nexus 7 3G Android Development] maconsultant:
where is v4..? i thought i could edit my apn settings and sip info.. but i see its not implemented in v3.. eta for v4..? i dont want to have to change the DPI everytime i need to switch APN's and sip accounts...

UPDATE

Any chance of getting the email.apk which supports exchange included.. i have tried to transplant mine but seem to be missing a part.. i am trying to track down what i am missing..

UPDATE

Also the word Google at boot seems to be off center and the clock widget on the lock screen is also off center.. not sure if you knew this already.. but if not just a heads up..

Thanks for your time and effort on this..
[Nexus 7 3G Android Development] Synman:
You just broke the first rule of XDA, dude. Never, EVER, ask for release dates. I do this 100% gratis, have a real job, and family, and fit in this stuff as time permits.

Get me a couple mil to my family and I over for the next couple years and I'll provide a release schedule, no problem.

With that said, a day or two on V4... Will likely provide alternate (cwm) install method too.

Will also likely rebrand it as RC1.

Also. If you haven't noticed by following the GSM Dev thread I modem bricked my n7 yesterday and have had to order a replacement.
[Nexus 7 3G Android Development] Synman:
I have validated exchange using my own exchange domain and can assure you it works.

Have no clue how the Google splash would be off center... Perhaps its a side effect of being unlocked as nothing in my ROM even remotely touches that.

Hope this helps.
[Nexus 7 3G Android Development] maconsultant:
weird the email.apk was not installed when i flashed it.. i have it going for the most part.. i just keep getting exchange service has stopped from time to time.. any way you can zip me

UPDATE

No need for the zip i think i fixed it have seen the exhange quit message since my last edit and reboot. thanks for responding..
[Nexus 7 3G Android Development] Synman:
Which version? I do believe it was missing in v1... Around V2 time I added it to the packages list and validated functionality.

I'll take a look regardless.
[Nexus 7 3G Android Development] Synman:
Take look at the screenshot of the app drawer on page 1 and let me know how your v3 drawer differs.
[Nexus 7 3G Android Development] maconsultant:
i installed v3... The file name is Synman_GwT_V3

UPDATE

The cpu utilization is better on your ROM than stock for me i would get crackling when playing google music and doing anything else on the tablet.. since flashing your rom i have not experienced this.. Thanks..!
[Nexus 7 3G Android Development] Synman:
And your app drawer...
[Nexus 7 3G Android Development] maconsultant:
i had to install it.. it was not on my tab after initial flash... No worries as v4 is going to be released soon.. could have been an anomaly..
[Nexus 7 3G Android Development] kRt_uK:
Cool! Just found this thread.

Thanks Synman to put everything together in one flashable ROM

I hope soon we could experiment the final one with voice calls.

Good luck with your imei research.

Cheers!
[Nexus 7 3G Android Development] manolohd:
Synman can you make your V4 build in cwm .zip flashable file? i hope that you do this for try your rom. :)
[Nexus 7 3G Android Development] maconsultant:
I'm following the Dev thread now.. Keep up the awesome work.!

Sent from another Nexus..

7 3G...
[Nexus 7 3G Android Development] Synman:
So I'm considering a revisit of this ROM to take it to the latest AOSP branch and including BT 4.0 support in addition to my other normal mods. Any interest?
[Nexus 7 3G Android Development] DaBe77:
Yes, of course! :D:thumbup:
[Nexus 7 3G Android Development] Tommmii:
you better believe it there's interest!

and...f2fs anyone ? :p
[Nexus 7 3G Android Development] Scirwode:
I'm very interested! I've lost count of the ways of trying to get my Nexus 7 to run smoothly on the stock ROM :( .

Scirwode
[Nexus 7 3G Android Development] tedr108:
Interest here, too...
[Nexus 7 3G Android Development] Synman:
pulled down LMY48G and did a base build with BT 4.0 enabled. Works great! I may have something available for download this weekend. Will need to reach out to [MENTION=4075479]jfmcbrayer[/MENTION] to see about including carcosa again.
[Nexus 7 3G Android Development] jfmcbrayer:
I haven't built a new carcosa kernel based on the 5.1.1 sources, just because the merge is hairy. But the last released one (5.1.0 sources) works fine with stock 5.1.1.
[Nexus 7 3G Android Development] Synman:
New build is ready but I'm having problems with the XDA upload service. I may have to host offsite.
[Nexus 7 3G Android Development] Synman:
OP updated with LMY48G (external) link
[Nexus 7 3G Android Development] GtrCraft:
Can you update your source too? I want to try to build it for grouper :D
[Nexus 7 3G Android Development] Synman:
Will do but you'll find it already installs just fine on grouper :)
[Nexus 7 3G Android Development] jfmcbrayer:
I'm on GwT LMY48G now, and everything seems pretty smooth. I'm trying going GApps-free for a while, to see if Google Play Services is to blame for my atrociously slow charging on 5.1.1 stock. I've got MicroG location services and BlankStore installed, and everything is shiny and fast.
[Nexus 7 3G Android Development] Synman:
XDA Direct download link added. Looks like XDA corrected whatever it was that was hosing the uploader.
[Nexus 7 3G Android Development] vital21:
Hi guys,

First of all i would like to say "MUCH THANKS and RESPECT" to TS, as this ROM is 100% clean, fast and do his job!

Secondly, I need an advice...

"There is an application which somehow running a Phone Capability Test, and report a result somethin like ##has_phone=true## or ##has_phone=false##.

Unfortunately I cant understand which method it uses for such test, but I always lose with ##false## result...even with this brilliant ROM.

1) Could anyone advice me how could I detect the test method, so it would be easier to pass it...

2) Any ideas how such compatibility test could be passed with Nexus 7 2012 3G?

Hope for your help community!

Cheers ;)
[Nexus 7 3G Android Development] optimusodd:
Can you please elaborate, what do you mean by that ? I am intending to flash a different ROM on a different device.I extracted the firmware zip and checked every file but couldn't find "wipe (-w) in fastboot with system.img".

Thank you