yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] jaswinky:
What drexe service is? You mean 3G version, isn't it?

---------- Post added at 02:28 AM ---------- Previous post was at 02:16 AM ----------

Ok AAccount, about the boot issue, looking for differences between 1.2 version and 1.4 version codes, I've found something that could help:

File tegra2_dvfs.c, at beggining, these array defs:

1.2GHz version:

static const int cpu_speedo_nominal_millivolts[] =

/* spedo_id 0, 1, 2 */

{ 1100, 1025, 1125 };

static const int core_speedo_nominal_millivolts[] =

/* spedo_id 0, 1, 2 */

{ 1225, 1225, 1300 };

1.4GHz version:

static const int cpu_speedo_nominal_millivolts[] =

/* spedo_id 0, 1, 2 */

{ 1100, 1250, 1125 };

static const int core_speedo_nominal_millivolts[] =

/* spedo_id 0, 1, 2 */

{ 1225, 1275, 1300 };

These arrays are only used in this funcion: void __init tegra_soc_init_dvfs(void), which suspectly has the label "init" in his name... this function is probably called at the boot to set initial values.

See also the comment inside this funcition:

/*

* VDD_CORE must always be at least 50 mV higher than VDD_CPU

* Fill out cpu_core_millivolts based on cpu_millivolts

*/

It is, 1,4GHz version is exactly in the limit, less than 50mV difference could cause a freeze because the voltage difference would be very low, and then the current from core to CPU would be almost cero...

Now, see the values defined in the previous arrays, in 1.2GHz version the differences between all three cons are greater than 50mV, but in 1,4GHz version, the spedo_id 1 is only 25mV diff, what could be causing the error at boot. Maybe the second value in cpu_speedo_nominal_millivolts could be set to 1150...

EDIT: Also here could be a CPU-CORE voltage difference problem:

static struct dvfs_rail tegra2_dvfs_rail_vdd_cpu = {

.reg_id = "vdd_cpu",

.max_millivolts = 1250,

.min_millivolts = 900,

.nominal_millivolts = 1250,

};

static struct dvfs_rail tegra2_dvfs_rail_vdd_core = {

.reg_id = "vdd_core",

.max_millivolts = 1300,

.min_millivolts = 950,

.nominal_millivolts = 1225,

.step = 150, /* step vdd_core by 150 mV to allow vdd_aon to follow */

};

Note that the difference in values in bold is -25mV (yes, negative)... this is, not only less than 50mv, but also CPU nominal voltage is greater than core (this is not allowed and would produce a big and sure freeze). I would change .nominal_millivolts = 1250 to 1175.

EDIT 2: Please, be carefull with the CPU-core voltage differences, you could burn the CPU if any of them is too big (it will be better freeze than burn it :D)

Regards,
[Galaxy Tab 10.1 Android Development] AAccount:
Very interesting find there. I will try that and report back. Also, I'm trying to address the AC charger issue by creating a variable like pershoot's force_usb_charging. In the function

static ssize_t p3_bat_store(struct device *dev,
struct device_attribute *attr,
const char *buf, size_t count)

It looks like the variables are written there. I copied the lines for force_usb_charging but changed it to acmod. I added the appropriate lines elsewhere and modified p3_get_cable_status to

if (check_ta_conn(battery)) {
if (battery->pdata->check_dedicated_charger())
battery->current_cable_status = CHARGER_AC;
else
if(battery->info.acmod)
{
battery->current_cable_status = CHARGER_AC;
irq_set_irq_type(gpio_to_irq(battery->pdata->charger.connect_line),IRQ_TYPE_LEVEL_HIGH);
}
else
{
battery->current_cable_status = CHARGER_USB;
irq_set_irq_type(gpio_to_irq(battery->pdata->charger.connect_line),IRQ_TYPE_LEVEL_HIGH);
}

But for some reason my sysfs variable always has an error reading. I checked the other samusng defined variables in p3_bat_store that also has their values read by they also have the exact same error as mine.

-------Edit----------------

Your tegra2_dvfs.c suggestion is proving to be VERY promising. As a beginner, I think the tests I do for the kernels before releasing are fairly rudimentary but as I get more feedback, I add more tests and checks in hope that the final product is at its best. Now, with that information, let's see if we can hit 1600MHz and red line it to the max!!
[Galaxy Tab 10.1 Android Development] jaswinky:
Interesting but, ¿how do you fill or, who fills the var acmod? The user can set it?
[Galaxy Tab 10.1 Android Development] AAccount:
It's supposed to be done by "echo 1> /sys/class/power_supply/battery/acmod" like the original force_usb_charging. Unfortunately, none of the variables set in that function actually work, even the samsung stock ones. Oh, and check out my first 1.6GHz attempt. It booted and is running right now. Your suggestions was very helpful. :good::fingers-crossed:
[Galaxy Tab 10.1 Android Development] AAccount:
GPU OC is included in 1.3 and above.
[Galaxy Tab 10.1 Android Development] AAccount:
Download the original pershoot zip. Look at the script. I've removed the lines that copy in the kernel modules. Remove all pershoot's kernel modules and add yours in.
[Galaxy Tab 10.1 Android Development] jaswinky:
Guau! That way is cleaner and user configurable... did you tried here: /sys/class/power_supply/battery/device /power_supply/battery/acmod and others subdirs (im also novate in this...)?

1.6GHz!! Be carefull!! Je je....

Enviado desde mi GT-P7510 usando Tapatalk 2
[Galaxy Tab 10.1 Android Development] AAccount:
I copied and pasted the pershoot's voodoo sound. I think the solution for that was just to disable the smart amplifier.
[Galaxy Tab 10.1 Android Development] jaswinky:
Are you sure that files in sys are not only for read as info? If you write here the system will take the change inmediatly?

Enviado desde mi GT-P7510 usando Tapatalk 2
[Galaxy Tab 10.1 Android Development] kordellas:
Hi AAccount thank you for this kernel. Are you going to release a newer version soon ?
[Galaxy Tab 10.1 Android Development] AAccount:
I did this as root. I got an "invalid file length" from the cat command. I also got this error for the samsung variables. I think permissions were 644 (owner read/write, group read, everyone else read). I think the owner was also root. I no longer have that mod in but here's what the terminal says:

root@android:/sys/class/power_supply/battery # cat batt_reset_soc
batt_reset_soc: invalid length
1|root@android:/sys/class/power_supply/battery #

batt_reset_soc is a samsung variable.
[Galaxy Tab 10.1 Android Development] jaswinky:
Mmmm, i am not too experimented in linux... is the file size due to the var type size?

Enviado desde mi GT-P7510 usando Tapatalk 2

---------- Post added at 05:37 AM ---------- Previous post was at 05:22 AM ----------

I am sorry but, i really think those files in sys/class are only info files, one way files, a kind of log or trace of all vars... the content origin should be in other place.

You meanwhile could use a compile definition and using #ifdef sentences compile both AC and noAC versions over the same c file, so it would be easy for you to control the versions...

Enviado desde mi GT-P7510 usando Tapatalk 2
[Galaxy Tab 10.1 Android Development] AAccount:
I'm working on this right now. You're right wifi doesn't actually turn off. I compiled them as modules and now I'm working on getting the modules sent in with the kernel. Thank you for this insight.

------------------------Edit------------------------

I got kernel modules to install. Wifi will now be compiled as a module and not built in.
[Galaxy Tab 10.1 Android Development] sc00ter98:
Flashed new version and I getting every reboot, updating system.

Gesendet von meinem GT-P7500 mit Tapatalk 2
[Galaxy Tab 10.1 Android Development] AAccount:
You mean that android is upgrading thing? I thought that had to do with upgrading roms? Kinda weird since 1.5 and 1.5.2 are identical except for jaswinky's voltage fix.
[Galaxy Tab 10.1 Android Development] kashortiexda:
AAcount once wifi module compiled, will there be a new test build, or do we need to insmod the new module ?
[Galaxy Tab 10.1 Android Development] AAccount:
New 1.5.3. build will be out after I'm done testing it. Life's nicer when you don't have to insmod and let the tablet take care of all operations :cyclops: Waiting for tests to complete while I listen to iheartradio on my I9300.
[Galaxy Tab 10.1 Android Development] kashortiexda:
AAccount sent you pm
[Galaxy Tab 10.1 Android Development] sc00ter98:
Thanks for reply. After I flashed the kernel and at the first reboot, Android OS is upgrading and optimizing application and counting all application up. After secound reboot and follows only "Android OS upgrading. This message is coming every reboot.

Only for info: In the OP is the last kernel version 1.5.2, in CWM I see after flashing, the kernel version is 1.6.
[Galaxy Tab 10.1 Android Development] AAccount:
That's a mistake from my config file. I am working on 1.6 and forgot to switch the string when compiling 1.5.2. No, 1.6 has not been released yet.
[Galaxy Tab 10.1 Android Development] RJ200X:
Installed latest kernel, installed antutu to overclock and did a test too. Managed to score a 6794 with it.
[Galaxy Tab 10.1 Android Development] steveman29:
Just delete any odex files within "data/app" directory with root explorer and reboot. There will be no more optimizing applications message.
[Nexus 7 Q&A, Help & Troubleshooting] ed2020:
Hi,

Sorry if this is a stupid question. The Nexus 7 is my first Android device and something has got me a little stumped:

I am using ES File Explorer to access the file system on my Nexus 7 (not rooted, stock JB). If I connect my Nexus 7 to Windows Vista and create a new directory in Windows Explorer I can see the directory in ES File Explorer however if I create the directory in ES File Explorer I can't then see it in Windows Explorer. Why is this....?

I have also noticed that files I have deleted from /sdcard/Download (deleted from within Android) are sometimes still visible in Windows Explorer.

Am I missing something?

TIA,

Ed
[Verizon Samsung Galaxy S III] beautosoichi:
Flashed SynergyROM v1.7 last night, came back to work and tried to re-connect my MightyText and i get an error saying 'unable to connect'

rebooted into cwm recovery, backed up, full wipe, reflashed previous stock rooted, mightytext worked fine.

rebooted into cwm recovery, full wipe, reflashed synergy 1.7, redownloaded mightytext, not working.

went through various iterations of the above, still no dice.

any suggestions? wouldve posted this in the dev forum but since im a new baby deer, no can. Thanks in advance.
[Galaxy Note 10.1 General] upperkingjr:
Att only will give you two options

1. 50.00 5gig a mobile laptop plan

2. 69.00 3gig 400 minute voice phone plan.

I couldnt get the 30.00 3 gig mobile tablet plan because its a unknow device in the system.

Make sure they dont add a 2 year contract. Keep it at a month to month..
[Galaxy Note 10.1 General] BarryH_GEG:
I posted this in another thread but I'll post it here too. You can add the Note to your existing AT&T account as a dumb phone. Since it's foriegn, AT&T doesn't recognize the IMEI as either a tablet or smartphone. It's $9.99 for the additional line and $10 for unlimited (no soft cap) HSPA+ data. Data is $15 if you don't have unlimited messaging on your existing account. I've used this just for data on my OG Tab 10.1 for over year.
[Galaxy Note 10.1 General] upperkingjr:
Thats a great deal.but I only have a ipad on 30.00 month to month non plan.

My phones on sprint...
[T-Mobile, Samsung Galaxy SIII] Five0nIt:
Anyone else having gapps crash repeatedly? Seems like after a few min of usage the phone will freeze and a pop up will show saying gapps has stopped unexpectedly. I'm rooted running stock. On the same note both the xda and tapatalk app will go to a black screen and crash.
[T-Mobile, Samsung Galaxy SIII] sarni84:
Samsung derp...go to settings/accounts/google/and uncheck internet. Idk y it does it but something is borked with that and syncing internet. Only thing is if u run stock browser i think your bookmarks wont sync...but it will stop gapps from crashing
[T-Mobile, Samsung Galaxy SIII] Five0nIt:
Thanks man. I was getting irritated.
[T-Mobile, Samsung Galaxy SIII] sarni84:
No problem man
[T-Mobile, Samsung Galaxy SIII] Abbens:
Same thing happened to me and I am stock. I cleared internet cache and its all better
[T-Mobile, Samsung Galaxy SIII] kmdub:
Yeah, this happened to me also. Turning off "Internet" sync did in fact solve the problem, but no bookmark sync with the stock browser. However, I solved this by turning off "Internet" sync and rebooting. Then, I cleared the "Internet" app's (stock web browser) cache and data, and turned "Internet" sync back on after a reboot. Works perfect now, no crash, and bookmarks sync fine. Not sure if all the reboots are needed, but that is what worked for me.
[T-Mobile, Samsung Galaxy SIII] jrwingate6:
Damn, I was wondering what the hell was going on with Gapps crashing sometimes. It didn't happen much, maybe 2-3 times a week but it was annoying. Just unchecked Internet Sync so hopefully it works.

Thanks.
[LG Optimus 2x] PentagonVS:
I keep on accidentally pressing the hold button when i answer a call. I have found solutions for other phones, but they do not seem to work for the O2X.

Does someone know how to disable our remove this button. Could it be changed with skin customizations?

If not, where is the app located so that i can try to modify it if that is even possible.

Thank you

Michael
[LG Optimus 2x] xExabyte:
I think CM7 has a setting for disabling the hold button. Should be in the call settings menu. I'm not sure though.
[LG Optimus 2x] PentagonVS:
I am on stock rom unfortunately. There is no option there.
[LG Optimus 2x] tonyp:
You have to decompile the phone.apk, it should be in there.

If you're lucky there's an entry to disable it in the bool.xml, if not you have to search a little.

Keyword for google:apktool
[Samsung Infuse 4G] cat2115:
From ICS to JB and still no camera recording fix at 720p. I thought i read somewhere in xda infuse that 720p recording was fixed, maybe i'm wrong.
[Samsung Infuse 4G] elliot.newnham:
It's a damn hard problem to fix. If you think about it it's a deep down driver level issue that requires a pretty broad skill base to diagnose and fix. Years of coding experience to understand yet alone begin to fix it... It doesn't help that this isn't supported by Samsung nor the camera developer.

So it's incredible that the damn thing even turns on. I'd say Entropy and jt are smart enough to fix it in time though :)
[Samsung Infuse 4G] SMiGGs:
I miss 720, imo its the only thing holding me back from flashing any other ICS Roms. I wonder if the camera can be fixed with an aftermarket app, like how TORCH was fixed by using an app.
[Samsung Infuse 4G] rodrigoalumno:
I guess this could help you https://www.box.com/s/e122d0f656ea949f58c2 It's from this forum http://www.htcmania.com/showthread.php?t=432576&highlight=Fix+grabacion+720p+JB
[Samsung Infuse 4G] mg2195:
in likely...I could be wrong but I believe the problem relays in the drivers/kernel

NOOOOOOOOO DON'T USE THAT YOU WILL LIKELY BRICK OR BREAK THINGS!!!

That was taking from an HTC website...we have Samsung...two COMPLETLY different company's with COMPLETLY different hardware....
[Samsung Infuse 4G] rodrigoalumno:
Sorry, but this forum is not only to HTC devices. If you take a moment, you see that it's like this web. The only mistake I maked is that this patch is for the Samsung Galaxy S i9000GT, but I post it just to help you. Maybe this patch could give you some idea to make one by yourself.
[Samsung Infuse 4G] mg2195:
I wasn't mad at you or anything...I knew you were trying to help, I mainly made such a big deal to ward off newbs...they may flash it. May break something then they freak out...wanted to save them.the trouble :)

Anyways...some of our best devs have been trying to fix it for quite a few months (entropy, jt1134...).theyve tried to use/adjust the I9000 camera patches...but still nothing :/

I just saw HTC in the address and assumed it was an HTC patch :P

---------- Post added at 07:48 PM ---------- Previous post was at 07:32 PM ----------

Actually...720p is A LOT smoother then it used to be (haven't used it in months :P) and just for the heck if it I flashed your linked I9000 zip...well after the flash it was back to how bad I had remembered (neither were good)
[Samsung Infuse 4G] SMiGGs:
Goodbye sweet 720p :(
[Samsung Infuse 4G] qkster:
Here's the fix for 720p recording. :)
[Samsung Infuse 4G] SirAndroid:
I am also torn over the missing 720p recording, but I am still incredibly happy with JB! The only other major issue is the banding I get in photos, although someone had mentioned that possibly JB changed the shutter/refresh speed in the camera which produces the banding under fluorescent lighting conditions. Unfortunately I saw nowhere to manually adjust this.

The other major issue was the darn thing disconnecting from Bluetooth in my Toyota Entune system, but supposedly version 2.12 and the OC V2 Kernel fix the issue. Will be testing it out today. :)
[Samsung Infuse 4G] SMiGGs:
I get the same lighting effect on my pics as well. Paranoid Android, is working flawlessly. Besides 720 and other issues, its a great rom, and good on battery life.

Everything is almost fixed, so we might get lucky w/ 720 :)
[Samsung Infuse 4G] SirAndroid:
I just wanted to update and say that the banding lines I was receiving seem to be isolated to a specific building at my university. I am guessing the JB Rom somehow changed the shutter rate setting and in doing so it introduced a "flicker" banding line effect due to the fluorescent lighting in the building. If I go outside, or to other buildings with fluorescent lighting it does not do this, so the bulbs in the original building must be perfectly attuned to a rate that interferes with the imaging sensor.

I haven't found a way to tweak or fix this issue, but as long as photos in most other lighting and outside are fine I am alright with it.

Please try this out and let me know if this is also your issue. :)
[Samsung Infuse 4G] Whizzpopper:
That's cool! I wish I could find a way to reproduce that!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Jahcure:
Greetings everyone I would like to know if its possible to modify a value to enable a brightness setting lower than 25% as a minimum?

I ask this because if I am in a pitch black room and turn on the phone even the minimum brightness setting is enough to blind me

Do these settings reside in the from or kernel?

Thanks

Sent from my Skyrocket
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] DoctorQMM:
Check out "Screen Filter" (by Haxor Industry) in the PlayStore (Market)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Jahcure:
Thanks il check it out but it would be neat if the rom can do that since it relies on the light sensor to adjust the power of the screen it would be cool if the auto setting was able to read from a lower value than 25%
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kirbee213:
Gsam has an app that might be to your liking. on my kindle it can drop the brightness to below the minimum level. Search Gsam in the play store and then scroll to "other aps by:".
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] lnfound:
Screen filter is good. Lux if you want to set some manual points for brightness but I'm not sure if the sensor will limit your ability to distinguish from pitch black and dim since the phone itself will emit light in pitch black. Worth a shot though.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Jahcure:
I am currently using screen filter and it works pretty good I don't go blind at night trying to read my phone its just that I have to remember to turn it on I tried the app by gsam but even at .5% the screen is still very bright so far screen filter does the job

Sent from my Skyrocket
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] T.J. Bender:
There's a new app out there (XDA story on it today) called Galactic Night that's designed specifically for ultra-low-light settings. It's also in the Play Store now. It says it works with Galaxy S2 "devices" running GB and ICS. Not sure if that includes the Skyrocket, but no harm in asking the dev if it's what you're looking for.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kchen96:
+1 on screen filter
[LG Optimus 3D] ratluci:
Anything specific with body of phone?

Software (is stock important?), battery heating and indicator checking somehow, display?

Stuff like that, you know what i mean... :)
[LG Optimus 3D] TylDurden:
Focus on why you even want an LG Thrill/O3D in the first place.

I love the 3D, with Promethius or Thiaz you can get this phone screamin, but at the same time you suffer some wifi, tether, blutooth bugs that may not be worth the trade off. If you plan to run stock than you're completely crazy cause Froyo and GB both have major bugs that make them pretty much unusable stock. Other than that there really aren't any Thrill specific issues to look out for. Just what you'd look for with any phone, scuff marks, missing pixels, cracked screen, etc.

I'm personally in the process of warranty exchanges with ATT to hopefully get a Nitro or something else with an upgrade reset. The physical build quality of this phone is awesome but unfortunately the software is terrible without the mod community and even they can only do so much with what they have.
[LG Optimus 3D] ratluci:
Well thanks for advice.

I was planning to buy HTC Desire HD. And then i saw benchmarks and hardware on LG 3d. But again i don't know, i'm scared of those problems with software. I readed a lot about issues on LG 3d and don't know if it's worth that money.
[LG Optimus 3D] skilovan:
If you love to tweak or fix stuf, you will love O3D! :)

I love it because of that.If you are not ready for fixing software, then do not buy it.:)
[LG Optimus 3D] sc0use:
Buy something else :D
[LG Optimus 3D] BigBadSheep:
My advices

First of all - exterior look: scratches, hits, look on the back of the phone at the speaker. Open it up and look under the battery if it was opened - the waranty seal should be intact.

Power it up - normally should vibrate when it stopped loading the system.

See how fast hooks up the network and, important, if it works with your SIM - no SIM Lock or Network Lock I mean.

Look for dead pixels or burned pixels. Use a white background and a black one.

Make some calls to check the speakers, microphones and other things related to the talking part. Call someone and get called.

Turn on the bluetooth and wifi to see if they work properly.

Check the state of the buttons - especially Power Button and see how responsive is the screen and if it was - or better yet IS, protected with some screen protection.

Hook up the headphones and see if everything is ok.

Anyway - look for the obvious!
[LG Optimus 3D] ratluci:
I really like hardware of LG 3d, benchmarks are equal to HTC Sensation. Display is great 4.3 is size that i want. But i'm only afraid of software.

So if i flash rom without bugs, with good kernel will my phone be 100% functional?

And what do you think will ICS fix all the bugs?
[LG Optimus 3D] skilovan:
Yes, you have some grat rom's for p920.You will have to flash baseband to21e, then flash rom.Snd it's all good.:D
[LG Optimus 3D] ratluci:
Thanks.

So only to flash to baseband 21e, and then flash stable rom? No problem with wifi, ghosts calls, restarting, stuff like that?

That i wanna hear. I'm not total noob, i'll find out how to do that, if i buy phone.
[LG Optimus 3D] yourguitarist:
Most roms have been updated to be based off v21e. As long as you have v21e, you won't have ghost calls.