yashsingh1/xdaforums huggingface dataset:
[Xperia Z2 Q&A, Help & Troubleshooting] Envious_Data:
It seems generaly normal

Try this, flash a FTF using flashtool (exclude data)

Once its done flashing leave your phone to sit for a while 10mins-45mins

It should start improving battery life over time from there onwards
[Xperia Z2 Q&A, Help & Troubleshooting] hteinlay:
If I update 4.4.4,could battery life be better? I didn't know how to use flash tool. Thanks you very much for replying me.
[Xperia Z2 Q&A, Help & Troubleshooting] Envious_Data:
4.4.4 needs a settle period/run in time before battery life becomes good

It seemed like it took a week or two before it ran good for me
[Nexus 5 Q&A, Help & Troubleshooting] qwerp_:
Hi, can i ask if this is just me or its happening to others as well.

I updated to LRX21O and now google push service stop working.

What i mean is, for example, i no longer get instant hangout (gtalk) message or inbox notification when an email arrives.

anyone else experiencing the same or its just me?

please help.
[P3300, MDA Compact III General] SiperX:
:confused: I use the Bluetooth connection between the HTC and the Parrot and it works just fine in my car…. As far as the phone hand-free functions are concerned.

When I installed TomTom (ver. 6) on the HTC I assumed that the voice of the navigator would also come out through the car speakers connected to the Parrot.

This is not happening! The phone conversations are going through the Parrot and INDEPENDENTLY the TomTom voice comes out of the HTC! :eek:

This creates quite a mess when I am driving (while TomTom navigates) and I get a phone call: TomTom keeps on talking over the phone conversation and most of the HTC screen is covered by the “incoming phone call” notification!

Moreover the ringtone of the HTC does not seem to work when connected to the Parrot and only a very feeble chime is there to signal an incoming call.

Does anyone have a solution to fix this inconvenient situation?

Thanks in advance for the insight!
[P3300, MDA Compact III General] w0mbat:
I've got the same setup as you and have the TomTom voices coming out of the phone which has been the same with my previous phones such as the SPV C550 and he HTC wizard. I think it's down to the bluetooth stack implementation on the Windows Mobile phone. My mobile mutes TomTom when I am in a call and I get a flashing mute icon shown on the TomTom screen.

One thing to try is the Jetware bluetooth extension http://www.jetwaremobile.com/ which is designed to improve compatability with the Parrot systems. It will certainly help you get the correct ringtones through the speakers, though I'm not sure if it will help with TomTom voices.

Neil
[P3300, MDA Compact III General] hotatomic:
Hello

There is a tool cald btaudio i have installed it on my p3300 and when i am connected with my parrot i switch btaudio on and i have tomtom voice true my speakers :)

I dont know were i dl it but when you google on btaudio sure you be able to find it !!

Greetz
[P3300, MDA Compact III General] SiperX:
Thanks guys

Sorry I have been so busy lately I barely logged in the Forum. Just wanted to let you know that I have seen your replies and will look into the solutions you suggested. THANKS.. will get back to you soon with (hopefully positive)feedback
[P3300, MDA Compact III General] debully:
Vaguely related and possibly usefull information here:

http://www.modaco.com/Guide-to-usin...oneer-Bluetooth-Car-Stereoand39s-t252613.html
[P3300, MDA Compact III General] SiperX:
Thanks hotatomic! I have installed that appz and it works!!! Great tip!

Any other useful tools for the P3300 we could exchange?

Cheers!

SiperX
[Nexus 7 (2013) Accessories] avinashdelhi900:
hi. can we charge nexus 7 2013 with 2012's charger??

the 2012' rating is

I/P 100-240V 0.3A

O/P 5.0V 2.0A

please match with your nexus 2013 charger and let me know asap.

also, from experience u can tell me. thanks reply asap
[Nexus 7 (2013) Accessories] neo5468:
I am using nexus 7 2013 charger for my galaxy s3, and it charges the phone way faster than stock charger. Should be the same for previous generation of tablet I guess, but I dunno, since original nexus actually has bigger battery than the new one. I would use 1 charger with the biggest output you have available.
[Nexus 7 (2013) Accessories] ChauncyG:
Yes, in fact the 2012 (2.0A output) charger will charge the 2013 tablet faster than the one (1.35A) that came with it. Just make sure you use a good usb cable no matter which charger you use.
[Galaxy S III General] f0xy:
All this looks knowledgeable :)

How are you at ROM/Kernel building? :)
[Galaxy S III General] scholbert:
Hi f0xy!

Thanks for this feedback!

I know these experiments are only for the fearless with good eyes.

For the average user there's no need to hack boot mode or stuff, unless there's some evil bricked device :o

I guess folks need pix ;)

Depends...

On a hobbyist level i build many kernels, tweaked drivers and kernel code for personal use over the years.

Little less if we speak about building ROMs.

I might help out on some issues, but don't count on me for bigger projects.

Time is always lacking and often i'm too lazy to clean up the code for git :D

Cheers,

scholbert
[Galaxy S III General] scholbert:
Hi,

just added the complete partition table for GT-I9305 and some other stuff in the second post...

I try to sum up facts floating around as well and put it in the context of GT-I9305, so some info here is no breaking news :p

Anyway, enjoy the tech ride!

Regards,

scholbert
[Galaxy S III General] f0xy:
[MENTION=971570]mad_ady[/MENTION] I seen your post in boeffla, some info here may be of help? Or maybe the [MENTION=225651]op[/MENTION] can provide some help for you?

Regards
[Galaxy S III General] mad_ady:
Thanks for the references. It helped me better understand where the partitioning information is kept. I didn't know our devices (I own a GT-9300) had a MBR/GPT table. I wonder, do other (non-samsung) devices use similar partitioning schemes? Or are there also other ways of keeping the partition layout that are in use?
[Galaxy S III General] scholbert:
Hi mad_ady!

Yeah i guess other devices with onboard eMMC use GPT tables as well.

Though it is not completely clear at which level these are accessed.

I assume that the bootloader or even kernel is able to read this table during start up and is also aware of the sizes and boundaries.

The PIT table plays another role in this game.

AFAIK this is the reference for Odin/Heimdall and should match GPT boundaries.

Some experts are needed to confirm this or i'll have to dig a little deeper myself ;)

Regards,

scholbert
[Galaxy S III General] scholbert:
Hi there,

i made a comparison between the cmdline passed to the kernel by "old" and "new" bootloaders.

Just started some investigation to fix "offline charging" with KK stock running on devices which still got the old bootloader.

Here's the default cmdline "old" vs. "new":

[SIZE="2"]JB 4.1.2 (I9305XXBME3) KK 4.4.4 (I9305XXUFNJ1)

console=ram console=ram
loglevel=4 loglevel=4
androidboot.baseband=mdm androidboot.baseband=mdm
sec_debug.level=0 sec_debug.level=0
sec_watchdog.sec_pet=5 sec_watchdog.sec_pet=5
androidboot.debug_level=0x4f4c androidboot.debug_level=0x4f4c
sec_log=0x200000@0x43000000 sec_log=0x200000@0x46000000
- sec_tima_log=0x200000@0x46202000
- sec_avc_log=0x40000@0x46404000
s3cfb.bootloaderfb=0x5ec00000 s3cfb.bootloaderfb=0x5ec00000
lcdtype=96 lcdtype=96
consoleblank=0 consoleblank=0
lpcharge=0 -
lpj=3981312 lpj=3981312
vmalloc=144m vmalloc=176m
oops=panic oops=panic
pmic_info=67 pmic_info=67
cordon=<32-Byte hash value> cordon=<32-Byte hash value>
- connie=GT-I9305_OPEN_EUR_<32-Byte hash value>
androidboot.emmc_checksum=3 androidboot.emmc_checksum=3
- androidboot.boot_salescode=
- androidboot.odin_download=1
androidboot.bootloader=I9305XXBME3 androidboot.bootloader=I9305XXUFNJ1
- androidboot.selinux=enforcing
- androidboot.warranty_bit=1
- androidboot.sec_atd.tty=/dev/ttySAC2
androidboot.serialno=<16-Byte serial> androidboot.serialno=<16-Byte serial>
snd_soc_core.pmdown_time=1000 snd_soc_core.pmdown_time=1000[/SIZE]

As you might see there's the keyword lpcharge, which is not present on the "new" bootloaders.

On the new bootloaders there's the additional parameter android.bootmode=charger, if you start up with a charger plugged in.

On KK stock some proprietary binaries identify this keyword to activate offline charging.

Some kernel drivers (battery) react to this string as well and there's a patch already.

There'd been some attempts to fix this in initial ramdisk by hi-jacking cmdline present in /proc/cmdline and replace lpcharge=1 with android.bootmode=charger .

My first idea was, to make use of a similar function at kernel level and append android.bootmode=charger to the "old" bootloader cmdline, if lpcharge is set to 1 (similar to a conditional CONFIG_CMDLINE_EXTEND function).

The kernel itself will put this in /proc/cmdline afterwards and user space tools will be satisfied.

Some years ago i tweaked some kernel code for Archos tablets, which made use of custom ATAG keys to hand over some device specific parameters. Maybe i'll get something out of it :p

For my personal reference:

http://xdaforums.com/galaxy-tab-3/general/kitkat-t31x-t2892792/post55863790#post55863790

TBC

Cheers,

scholbert
[Galaxy S III General] adfree:
Hello.

Thanx for your Thread. For some summary about I9300 and I9305.

:good:

Please I need some input for my low brain...

I'm playing with I9300 and Tizen RD-PQ stuff...

My questions.

How to dump whole mmcblk0 ? Without direct eMMC Hardware...

Maximum 11 GB I can dump in internal sdcard...

http://xdaforums.com/showpost.php?p=59503847&postcount=14

If I try to dump to external SD... I can only dump 4 GB...

RD-PQ sboot seems to work with I9300...

RD-PQ dump shows uboot at address 0x10000 and Tizen PIT is at 0x8000...

Tizen 32 MB dump for study...

http://xdaforums.com/showpost.php?p=55514573&postcount=36

My theory... sboot is maybe at end of eMMC... :o

I can only check if I dump whole eMMC...

Thanx for every input.

Best Regards
[Galaxy S III General] mad_ady:
The 4GB is a FAT32 limitation. You can try to format your external SD to ext3 or you can try to mount (via CIFS/NFS) a remote storage on which to dump.

Or, you can dump the device in blocks, starting with a specific offset and having a specific length:

http://superuser.com/questions/3807...m-the-specified-offset-but-not-dd-bs-1-skip-n
[Galaxy S III General] scholbert:
Hi!

See mad_ady's comment:

From kernel level it is only possible to dump user area (unless you use a specific kernel with mmcblk0boot0 and mmcblk0boot1 enabled).

Read again this quote form my second post:

Interesting geek stuff... did you made any progress here, e.g. booting with RD-PQ?

Nope... it's at the very start of eMMC in a seperate area, normally hidden from user (see my comments above).

See datasheet attached, maybe this helps to understand how eMMC works.

EDIT:

Found the exact part which is soldered on my GT-I9305 mainboard.

See second post for reference as well:

http://xdaforums.com/showpost.php?p=56747098&postcount=2

I'll leave this older datasheet her as well... this is at least a similar part.

Good luck and best regards,

scholbert
[Galaxy S III General] adfree:
I have problems to check my progress... because broken/damaged Display...

I see only black...

In Android I can use ADB stuff to see something...

Writing 32 MB RD-PQ dump not kill I9300... (no idea if this could kill IMEI, EFS or other Security stuff)

But I can't see where it hangs or if something is on Display... :rolleyes:

Writing only s-boot-mmc.bin (200 KB sboot) from RD-PQ...

I have no idea yet, how to check if really written or ignored by I9300 sboot... :rolleyes:

getprop ro.bootloader

Gives no anwser...

And this feature looks like Kernel related stuff...

Example why I am unsure if 200 KB sboot is accepted...

In I9300 you can find easily string ODIN in sboot...

But in RD-PQ is no ODIN text string... then why my I9300 works without problems with Odin...

:confused:

I need some time to buy cheap working Display...

So I can see "visual effects" on Display...

1 goal would be this:

In Tizen world it seems mandatory to restore uboot... it contain the THOR string for THOR Downloader...

https://lists.tizen.org/pipermail/general/2013-November/002707.html

For me it is not clear enough... if RD-PQ sboot loads uboot...

sboot AND uboot is executed...

OR it is or feature... :o

Only uboot could be enough to executed...

:confused: :confused: :confused:

About dump mmcblk0...

dd if=/dev/block/mmcblk0 skip=0 count=10000000 of=/sdcard/dump_v1.bin
dd if=/dev/block/mmcblk0 skip=10000000 count=10000000 of=/sdcard/dump_v2.bin
dd if=/dev/block/mmcblk0 skip=20000000 of=/sdcard/dump_v3.bin

This seems to work... but last 1 is again 11 GB + big...

It starts after with beginning...

I need proper count value... need some time and calculator...

I hope next week I have working Display for my testdevice...

Best Regards
[Galaxy S III General] scholbert:
....grrrr

Hi again!

First of all, nice to see that at least two guys follow my binary surgery.

Second, i must admit that the platform is not that responsive as i first thought.

Due to all this signing stuff, it is easy to break something and CPU simply stops executing code.

So for now there's nothing, than further logging outputs from the console.

1. I removed some of the start up commands from BL2, which leaves TN M0|PMIC & INIT2 3|init2|TEST for ASB code.

This is what i got then:

TN default
<OK>
<OK>
[DVFS] INT(1) : 0
DRAM Type : LPDDR2 16G
[DVFS] MIF(3) : 0
[EPLL][VPLL][CLK_DIV] OK
<OK>

[CHIPID] E4412 EVT1.1
LOTID WNO X Y IDS HPM ASV_GRP FUSE SHIFT
[LOG]N571A 18 201 195 22 22 8 -1 100000 80

There's no auto booting anymore at this point.

2. I put anything back, apart from the RUN command.

During this test i used a modified ASB binary with sboot from I9305XXALI4 put in the right place.

Unfortunately the output stops after "FW Booting"

The device kept being powered though. Which is a good thing from my guess.

Here's the log:

TN default
<OK>
<OK>
[DVFS] INT(1) : 0
DRAM Type : LPDDR2 16G
[DVFS] MIF(3) : 0
[EPLL][VPLL][CLK_DIV] OK
<OK>
[LOCK SW/HW]ARM:0/0 INT:0/0 G3D:0/0 MIF:0/0 SHIFT:0/0
[DVFS] ARM(0) : 5
[DVFS] INT(1) : 0
[DVFS] G3D(2) : 0
[DVFS] MIF(3) : 0
[SD_INIT
SDMMC_HighSpeed:DONE]
SD_READ: 20000 20000 0x40008000 -> 422818 usec
<OK>
Inp32(uAddr) : 0xea00007e
FW Booting

Right now it's a bit to early for further conclusions, but maybe the signing stuff got broken at some point in both cases.

It could also be that some of the signatures is especially for GT-I9300, or in other words the CPU on GT-I9305 uses a different key set.

That's it by now, but i won't give up yet :p

Cheers,

scholbert
[Galaxy S III General] Rebellos:
Wow, that's one of the most insightful threads about 4412 I've seen for a while.

Replying here on OP's PM for further reference:

* At LenovoK860 uboot sources:

These seem to contain private keys for some batch of 4412 - that's the first time I see private signing keys of any Exynos to leak. Previous leaks were just wild security-dropping bootloader stages signed with private keys, but no keys included.

These keys can either match batch customized for Lenovo or match all 4412 (Exynos4 public key hash fuses, in theory, meant to be factory/OEM customizable) - I'd say the latter since neither GS3 or any common device built on S5PC2xx I've seen was expected to have any grade of real security, so probably neither Lenovo or Samsung cared to customize any of Exynoses used around.

There is a way to check it by comparing dumps from 0x10100000 area between GS3 and LenovoK860 CPUs (I'm uncertain, as I'm really rusty). Probably there's also other way by comparing Lenovo stage1 public keys with GS3 0x1010_0000 dumps, considering how pubkey is validated against these bits (no idea, don't remember).

* At My and Adam's tries:

We were quite succesfull in running UBoot on I9300 and GalaxyCam GC100.

What we couldn't achieve was kernel booting - Exynos4 kernels require TZSW to be fully operating and communicating with it. I couldn't get it to load up properly.

There's quite of history of our tries under https://github.com/Rebell/exynos4_uboot/commits/master

Another option is, of course, disabling TZSW support in kernel and not booting it at all - it doesn't seem to work out-of-the-box either, and would make impossible to boot any non-modded kernels.

AFAIR (and boy, was it while ago), referenced sources were building and fusing to the SD card flawelessly and supporting both fastboot and UART terminal with most (all?) of the commands working (yes, it can do raw R/W to eMMC and whatnot in SVC mode without TrustZone supervisor interfering, because it's not loaded at all yet). Just kernel wouldn't boot. I'd say you should give it a try (if you didn't already).

The crucial part we used there was FWBL1 (there https://github.com/Rebell/exynos4_uboot/tree/master/sd_fuse) - first, already signed, stage of bootloader hat's doing nothing but loading another stage of bootloader without any security (kudos to Odroid).

We couldn't find any equivalent of signed FWBL1 for Exynos4210 (GS2 CPU) that would allow us booting eMMC hardbricked GS2 devices.

* At ASB:

First time I hear of it. Never seen this stuff before.
[Galaxy S III General] adfree:
[MENTION=557802]scholbert[/MENTION]

Please, need collection of GT-I9305 Bootloader....

Something like this:

http://xdaforums.com/galaxy-s3/general/guide-extract-bootloader-make-flashable-t2864264

http://xdaforums.com/galaxy-s3/general/ref-galaxy-s3-stock-kernel-bootloaders-t2189063

For now I was only able to find

RESTORE_BOOTLOADER_I9305XXALI4.zip

http://xdaforums.com/showpost.php?p=32760677&postcount=1

I need few more for stupid tests. :D

For now my test GT-I9300 PCB is able to start this sboot.bin from GT-I9305... with tweezer.

sboot.bin is copied successfully... but not start in "normal mode"...

Here I can see other method... sboot.bin is not copied to eMMC but fully executed from eMMC, with Boot menu:

http://xdaforums.com/showpost.php?p=64664423&postcount=278

I will check if GT-I9305 has similar Bootloader and if it will executed on my GT-I9300 test PCBs.

Thanx in advance.

Best Regards
[Galaxy S III General] adfree:
I found this:

I9305XXUFNL1-DBT.zip

Here is sboot.bin from GT-I9305 inside... I have attached.

Search for text String THOR... you can find:

- Thor is connected!

This could mean... I9305 is Tizen enebled... not only this...

Chance to play with U-Boot.

Tried on I9300 with no luck...

Volume + or Volume - do nothing... maybe Hardware Keys different... :(

I hope to find something working for my I9300...

Btw.

First time I saw THOR string also in Note 4 N910C:

http://xdaforums.com/showpost.php?p=64663039&postcount=65

Best Regards
[Samsung Galaxy Star] aashishK:
Please please please developers help me root my phone. Its a request and will be very thankful. Please :rolleyes::rolleyes:
[Samsung Galaxy Star] T3snake:
1st try all one click root problems like

Framaroot

Towelroot (gud chance of working)

And so on
[Samsung Galaxy Star] aashishK:
Already tried farma root, vroot and failed. But lets see how towelroot responds to my phone.:D Thanks atleast one reply. :(
[Samsung Galaxy Star] App Developer:
Do you have USB cable?
[Samsung Galaxy Star] aashishK:
Yeah I do have a USB cable. :)
[Samsung Galaxy Star] aashishK:
Towelroot failed too :( :(
[Samsung Galaxy Star] T3snake:
it might be root proof for now
[Samsung Galaxy Star] aashishK:
Such things do happen ???? If so will I have to wait to get rooted ?? :rolleyes:
[Samsung Galaxy Star] T3snake:
possibly until some1 releases a nice software.

Keep an eye on the root methods of the samsung kitkat devices too (if theyre rooted without a cwm) it will most probably work
[Samsung Galaxy Star] aashishK:
will keep eye on it and urge you to post here if you find any. I am begineer on rooting, not so much experience, expecting your help too. :):)
[Samsung Galaxy Star] aashishK:
and one more question, why is there no any seperate forum for my phone, I will have to manage to ask question on this forum. :confused:
[Samsung Galaxy Star] T3snake:
Thats simply because this phone isnt popular if a lot of threaads pile up u will probably have another section
[Samsung Galaxy Star] aashishK:
Praying to have soon :(
[Samsung Galaxy Star] Prtk002:
Has anyone been able to root this phone? have been waiting for long now. :(
[Samsung Galaxy Star] red devil97:
use I-root mySM-G130E was sucessfully rootd
[Samsung Galaxy Star] omkar Ranbhise:
i root I try it

not root my sm-g130e
[Samsung Galaxy Star] ERROR:
Use Kingoroot app on windows and ur mobile
[Samsung Galaxy Star] ARN:
Try Using Mobogenie-PC. It is an android device manager which has a feature of 1-click root. Hope it would work for your device. Well switch on USB-Debugging and then connect the device to your PC and make sure that Mobogenie recognized your device and then in Toolkit menu click 'One-Click Root' it may take some time to download the package and installing (Approx. 10 min or sometimes more depending on your internet speed) and then you are done.
[Samsung Galaxy Star] omkar Ranbhise:
Get Root try Pc method Only
[Samsung Galaxy Star] mahheesh:
how to root samsung star 2 g130e
[Samsung Galaxy Star] OmkarR:
My sm-g130e is rooted but .....lolipop jellybean marshmelwo rom update not in google

Plessssss help
[Samsung Galaxy Star] chaoticmess2609:
How did you root your samsung galaxy star sm-g130e???Is your build no. KOT49H.G130EXXU0AOE2??

Kingoroot, framaroot, towel root,oneclick root is not working for me.
[Samsung Galaxy Star] Rakesh Mahto:
To Root Samaung star 2 (SM-G130E)

Download kingo Root for PC and USB driver or your phone need good internet connection during Root only for Samsung galaxy star 2 to know more information search Google user on your Facebook page and follow share your problem.
[Samsung Galaxy Star] rxb2017:
Try 360 root
[Verizon Motorola Droid Turbo General] bturkel:
Does anyone else have this issue - I will be on a call and voice is fine then it will drop out and come back up - same area as whwn I had my droid maxx with no issues - so I am guessign I have issues with the device? My sim card was swapped and it did not seem to solve anything.
[General Topics] riyasrawther:
I am wondering what is going on inside when we first open a Android phone... We are official distributor of a well known brand. We are only authorized to sell in our region only. But we sold some thousands of phones outside our region. After a month the phone company contacted us and warned that their system shows these number of phones are activated outside your region...

How they know?

We already opened all the phones and inserted the SIM and called 20 seconds to our carrier help-line.

All phones are already SIM unlocked.

The android really sending some data to the manufacturer server like imei?

Thank you!
[G 2014 Q&A, Help & Troubleshooting] Hugo Caixeta:
how to adapt to xt1068 lollipop for xt1069?
[Android Apps and Games] Kahun:
Feeling nice today so the first 5 people to post here will get an invite to Inbox by Gmail.

--------

Giving away 5 Invites...

0 left out of 5 NONE LEFT :( might do a giveaway again another day!!

Don't forget to click Thanks after receiving the invite.
[Android Apps and Games] robo4130:
Please!
[Android Apps and Games] huonggiangtrinhh:
Please invite me :p

Thank you ^^

My email is huonggiangtrinhh@gmail.com
[Android Apps and Games] dimension3000:
One more if you can please!

glennjosy@gmail.com
[Android Apps and Games] Kahun:
Email?
[Android Apps and Games] Kahun:
Only because you said please ;)
[Android Apps and Games] huonggiangtrinhh:
Thank you, I just received the invitation.

You're the best :highfive: :highfive: :highfive:
[Android Apps and Games] Kahun:
No problem :)
[Android Apps and Games] nightfireblaze8:
If you have any more left, can I please have one?

Thanks!
[Android Apps and Games] Kahun:
PM me your email.
[Android Apps and Games] bharathreddii:
kbharathsreddy@gmail.com

Thanks!
[Android Apps and Games] Bruno_Tec:
Can you please invite me? taralinga@gmail.com . thanks!!
[Android Apps and Games] spyne82:
Invite send
[Android Apps and Games] dimension3000:
Thank you very much:)

Sent from my HTC One M8