yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] aostrom:
Yeah. Like he said... I'm always afraid to try new ROMs because I'm afraid I'll end up screwed. People here tlak about baouncing back and forth like it's no big deal, but when I've tried it I seem to end up having to start from scratch.
[General Questions and Answers] aretwokay:
I just did a factory data reset yesterday and I was calibrating the battery for the new ROM. When I let the phone die all the way, I left it unplugged for a little while because I was in the middle of a movie. When I got around to plugging it back in, I am getting a flashing LED, no charge indicator, and it won't boot up. Every once in a while, the HTC boot logo will pop up and my phone will vibrate like it's turning on, then it will just go back to the flashing LED. I can get it to jig into fastboot ever so often, but when I try to boot into recovery from there, it just turns off and goes back to the flashing LED. Everything I have read says to hook it up to my computer and use ADB to reboot it, but when I bring up the command prompt, it says that ADB isn't a recognizable action or something like that. My laptop also doesn't recognize my device as being plugged in. I've perused the forums on here and to no avail so here I am asking for help... HELP!?
[General Questions and Answers] MRsf27:
hve you tried posting this in the htc sensation forum? maybe someone had the same problem...
[Galaxy S III Q&A, Help & Troubleshooting] oxidil:
hi

i am unable to sign in google account on my s3. i use different custom roms. today i install 2 new customs rom LIB. i had same problem. i restored the preivous rom in which google account was already registerd. signing in was also failed in my old rom. even google play is also not opening. my Gmail account is opening on my PC.

i have a s 2 phone with stock rom. google mail and google play is also failed to open in s 2 also. I am from pakistan and i want to ask that is any body else is havin this problem? any solution?
[Galaxy S III Q&A, Help & Troubleshooting] iqsoft:
AoA,

I too am having the same problem. The only ROM in which I can sign google account into is a stock ROM. Download a stock rom from http://xdaforums.com/showthread.php?t=1646610 and install it using ODIN... Once installed, allow Samsung to update files i.e. let Samsung Software Updater run... You will be able to sign into google etc... However if you try going back to a custom ROM, it will be the same problem... Beyond this I too am stuck!!!
[Galaxy S III Q&A, Help & Troubleshooting] Nas Eiesefpi:
So what you are saying is you unable to use your google account on both the S2 and S3? I think there might a problem with your account. Check your account settings.

Did you just enable the 2 step verification for your account?
[Galaxy S III Q&A, Help & Troubleshooting] oxidil:
No problem with account. I have already mentioned that I can sign in from my laptop
[Galaxy S III Q&A, Help & Troubleshooting] bludestiny:
me too, no problem for me in same case like you...it's strange...
[Galaxy S III Q&A, Help & Troubleshooting] oxidil:
But people with stock rom on HTC also facing same problem

Moreover people all over the world not complaining this issue. It's strange
[Galaxy S III Q&A, Help & Troubleshooting] oxidil:
I am having stock rom on s2
[Galaxy S III Q&A, Help & Troubleshooting] iqsoft:
Solution

All people living in pakistan have this issue and here is the only solution. Download "hotspot shield vpn" , install it and then start protection. It will solve all your google related issues, even you can access youtube by [sohebq]
[Galaxy S III Q&A, Help & Troubleshooting] oxidil:
Google is back again. Google play is opening now but download/update is still not possible
[Galaxy S III Q&A, Help & Troubleshooting] iqsoft:
Try what I said above.. And don't forget to press THANKS once it works!!!
[Galaxy S III Q&A, Help & Troubleshooting] oxidil:
Google play is also working and download /update is possible again
[Asus  Eee Pad Transformer Prime] Snook321:
Once I updated my TF201 to Jellybean, I noticed my Backfacing Camera will not function properly. It will flicker multiple colors and sometimes just show green. My front facing camera is working flawlessly. Anyone having the same problem? If not, then I know it isn't a software issue...
[Asus  Eee Pad Transformer Prime] nygmam:
This is a hardware issue, just a coincidence you noticed it now. There is a thread here about the back green camera. I had to RMA mine to get it fixed. Nothing to do with JB, I think. Now, if only i could get mine updated. Initial update failed, and now it wont find it again :(
[Asus  Eee Pad Transformer Prime] lamboboy732:
Yea, as already stated it is hardware, I had the same freaking problem. Luckily the RMA only took 5 days though.
[Asus  Eee Pad Transformer Prime] Hanshananigan:
Happened to me the day I OTAed Jelly Bean, soit sure seems related. Any fixes posted other than RMA?
[Asus  Eee Pad Transformer Prime] HumpinJack:
I got my prime second hand from the old lady and when I went to use the camera I got the same green camera photo :(

I find if I pinch the case by the camera I can get it to work. Now I'm debating on the RMA. Will they ship me a new one or a refurb? I'm quite happy with my Prime and I'd hate to get a lemon that everyone else is complaining about. Not too excited about loosing all my customization either.
[Vibrant Q&A, Help & Troubleshooting] Iam2Smooth:
Good afternoon, brethren!

I saw this posted in another phone's forum, but I've been wondering the same thing.. Any of you more development-savvy users know a way?
[Vibrant Q&A, Help & Troubleshooting] Romcrazguy:
check out at&t s3 thread in development section
[Kindle Fire Q&A, Help & Troubleshooting] saiihtam:
Ok, so I had TWRP including FFF installed, as well as all the other features that comes with kindle fire utility, when I decided that I wanted to restore to stock firmware.

I placed the update.bin in kindleupdates folder on the Kindle itself, and launched TWRP Recovery to install the rom/firmware.

When it was done installing, I was such a nutjob not thinking, that I decided to also delete everything (system, sdcard, cache, dalvik-cache), as well as to tell it to restore to factory settings, where I immediately after told it to reboot. Totally dumb, I know it, so now it's stuck at the "original"/orange Kindle Fire-logo, and just hanging there (i'm able to turn it on/off though), hence it can't restore stock firmware since I deleted everything off the kindle after I installed that stock firmware. It doesn't even have TWRP anymore (boot options doesn't appear when turning the kindle on.)

I also tried to connect it to the USB-port on my PC, (already have drivers installed), but it just gives me the "badom"-sound implying that a USB has been connected, nothing else. I can't even access the Kindle as an external storage device anymore now.

HELP!

PS: I'm running Windows 7 x64!
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Are you unable to reinstall FFF and TWRP?
[Kindle Fire Q&A, Help & Troubleshooting] saiihtam:
Yes ):

Yes because my PC won't even detect my Kindle now!
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Fix your drivers.

Otherwise you can use SoupKit w/Linux Live USB to save yourself some hassle in getting ADB to connect. Either way, it's very likely your shell is missing or corrupt, requiring a factory cable to get into fastboot.
[Kindle Fire Q&A, Help & Troubleshooting] kishorev:
You said u heard the beep when u connect.. did u check it in the Device Manager..

You might see it under other devices or under USB devices?

If you are able to see it then you might have a chance
[Kindle Fire Q&A, Help & Troubleshooting] guangzhouboy:
lol

lol this reminds me of someone..........(me)

http://xdaforums.com/showthread.php?t=1888581 read
[Milestone 2 Android Development] czechop:
It seems that finally I was able to boot custom kernel with working radio:)

It's not very stable yet(it stops/crashes at bootanimation quite frequently), and is quite laggy just after boot, but once it boots it seems to be almost usable. Wifi works, sdcard also. Haven't checked bluetooth.

Credits for this goes to:

* milestone1 devs... for sharing 2ndboot source code and providing so much info regarding milestone1/2 phones

* Motorola:) ... for providing source code(not fully working, but was a great help anyway) for enabling UART over micro usb for debugging purposes(without this I woudn't make any progress)

* tezet... for making quite good;) roms used by 2ndboot

If you wish to try it(BEWARE THAT IT MIGHT BRICK YOUR PHONE, SO DON'T SAY THAT I HAVEN'T WARNED YOU :D), then do as follows:

Please let me know if someone actually run it and was able to boot(so that to find out if I haven't forgot to include some more files(see changelog for 03.10.2012:D)

KNOWN LIMITATIONS

CHANGELOG

NOTES for devs

In milestone2(as probably in many others UMTS phones made by Motorola) the BP is somehow very sensible and does not like to be disconnected/reenumerated. The main goal of this 2ndboot is then to not allow it to be disconnected. To do this, in the new kernel I've skipped a few resets(EHCI, TLL, individual port resets), and instead of enumerating BP, I've used the hardcoded usb device address(which for milestone2 seems to be equal to 2).

I attach patch(radio.patch) with the changes I've done to the kernel sources from here:

http://sourceforge.net/projects/milestone.motorola/files/MILS2_U6_4.1-22/

This seems to work(sometime:D) for both milestone2 and defy.

For other motorola phones:

1. First of all, check with lsusb what's the address and vendor/product id of your BP(for milestone2 it's 0x22b8 and 0x40e6).

2. If the BP usb device address is 2, then just apply the patch(probably it will need some small modifications), and check if it works.

3. If the BP usb device address is not 2, then edit usb/core/hub.c function hub_port_init(providing that it's there for your kernel), and replace 0x02 in the place where usb_control_msg to get descriptors is sent with address of your device

If it does not work, then you can try the following:

Create a procedure to send usb GetDescriptors request using omap3 ehci registers, and call it at different boot stages/usb initialization stages to find out how long the radio remains attached, and comment/change appropriate fragments of kernel code, to preserve this until usb port is initialized. If you wish, I can share the procedure I've written(in the patch file this is that czecho_get_descriptors called in many places) for milestone2, but it probably would need some modification to work with your device).

2ndboot module sources are here:

https://github.com/czechop/2ndboot
[Milestone 2 Android Development] Anonymous_:
Wow, thats perfect :) This could bring M2 development to another level.

Holding thumbs up and keep it up!
[Milestone 2 Android Development] tezet:
Great news! Thx for your work. I've just bought an OTG cable to start playing with kernel stuff and here's a surprise :)
[Milestone 2 Android Development] JoseBerga:
Fabulous! That means it starts a new era in the development of our MS2 Roms!

:D
[Milestone 2 Android Development] djlooka:
Wonderful job man :)
[Milestone 2 Android Development] handsomeboy1702:
Brilliant
[Milestone 2 Android Development] skeevydude:
I'm gonna try on the Motorola Bravo as soon as PA is done uploading. Hopefully this'll work on Froyo kernels as well :fingers-crossed:

What kernel are you using? A recompiled MS2 GB kernel unmodified?

Awesome job man. This could possibly be the start of a new generation of roms for our common platform if this works on other similar phones like the Defy\Bravo. Only time will tell :D.
[Milestone 2 Android Development] nidhish91:
Well good work OP, can this be implemented on other Moto phones like Defy?
[Milestone 2 Android Development] boorce.com:
Great work !

I see that your work is based on Moto's Linux kernel (2.6 branch as far as I remember...)

Any hope of using another kernel source one day ?
[Milestone 2 Android Development] Quarx:
Great News!, Thanks:)

Waiting for source code:)
[Milestone 2 Android Development] Megalith27:
Wow! Tezet and Quarx on the same thread?! :) I feel like up on the Mount Olypmus lol

Great job, man!...been following your work from General section.

P.S. add Kabaldan to the list :) Clash of the Moto Titans
[Milestone 2 Android Development] czechop:
Yes, I use MS2 GB U6_4.1-22(http://sourceforge.net/projects/milestone.motorola/files/MILS2_U6_4.1-22/) kernel... but with modified usb host driver.
[Milestone 2 Android Development] czechop:
I think it can be.

With defy it probably should be easy, as I've seen there was 2ndboot(without radio) already build for it, so most likely only new kernel would need some tuning:)
[Milestone 2 Android Development] fjfalcon:
XT720 users also waiting for instructions for new kernel tuning, cause we have working 2ndboot without radio. =)
[Milestone 2 Android Development] czechop:
It should be easy to apply some(perhaps most) 2.6.32 upstream patches to the motorola kernel sources.

Don't know however how difficult it would be to start from another kernel version. Don't know also how motorola proprietary modules/libs would behave with newever kernel version. But, as they say, impossible is nothing:)
[Milestone 2 Android Development] Quarx:
In kernel only modified usb driver or some more changes for boot?
[Milestone 2 Android Development] czechop:
Will share source code probably early next week(currently am at work, and during weekend most likely won't be sober enough;)
[Milestone 2 Android Development] czechop:
In 2ndboot module I've added code to disable lcd before starting new kernel(otherwise new kernel could not initialise properly dss), and in new kernel I've only modified usb driver(perhaps more things will need to be modified, as I'm facing problem with BATTD sayins something about power ic fail, BTW, does someone know what that could mean?), so that it skips restaring EHCI, TLL and don't start enumeration, but just used the old usb device address(assigned by the original kernel), which for M2 is always 2(at least during my tests).
[Milestone 2 Android Development] Quarx:
I2c Fail can be caused by wrong permissions for /dev/cpp*

I tried your prebuilt binaries on defy http://pastebin.com/jKjQ2ykn

Black screen + buttons lights and reboot after ~20sec
[Milestone 2 Android Development] czechop:
Thanks for hint regarding permissions...will check that:)

Regarding prebuilt binaries on defy, hard to say what's wrong(not sure how much the phones differ). Anyway, you probably would need to use devtree from your device. Also you could unpack ramdisk, and check the init.*.rc scripts if they are ok(e.g. I mount system partion using p21, not sure if that's the same for defy, and staff like that).
[Milestone 2 Android Development] Quarx:
Yes, system no mounted, because NAND is not initialised.

http://quarx2k.ru/clean_log.txt clean log
[Milestone 2 Android Development] walter79:
you could try to mount sdcard. (system

img, like 2nd-system)
[Milestone 2 Android Development] Skrilax_CZ:
Quarx: fix your cmdline (read it from cdt.bin or CG31.smg if you split SBF).
[Milestone 2 Android Development] Quarx:
I use this cmdline for stock kernel and it works.

mmcparts=mmcblk1:p7(pds),p16(recovery),p17(cdrom),p18(misc),p19(cid),p20(kpanic),p21(system),p22(prek),p23(pkbackup),p24(cache),p25(userdata)

This need only for moto init binary, but i tried anyway, it's not help.

I'll add more debug in init binary.
[Milestone 2 Android Development] espaciosalter20:
It's seems that the new kernel iteration uses a different way to access init.rc on the phone. Maybe, as skrilaz suggest, using a different cmdline may help...

Enviado desde mi MB526 usando Tapatalk 2
[Milestone 2 Android Development] Skrilax_CZ:
<5>Kernel command line: console=/dev/null mem=498M init=/init ip=off brdrev=P3A omapfb.vram=0:4M

Either you have there very bad hack or you don't use that, anyway full cmdline from stock kernel is fine, you can brick your phone if you will tamper with the partitions (and swap mbm with system etc.). Secondly, MS2 has eMMC, not NAND.

Anyway, nice progress. :)
[Milestone 2 Android Development] Quarx:
For fix emmc/mmc, first need fix devtree

"<3>Unable to read node /System@0/GPIO@0 from device tree!"

I think it's because kernel got incorrect address for devtree.

HBBOT: 0x8f090000, Kernel: 0x80c00100

And kernel found my sd-card :)

<6>mmc0: new SD card at address caea

<6>mmcblk0: mmc0:caea SU02G 1.84 GiB

Upd: nand fixed:) http://quarx2k.ru/uart.txt

And looks like it start boot android:)
[Milestone 2 Android Development] espaciosalter20:
It's looks like you almost there!!!! (Wow!!! I'm really impress about your skills).

Anyway, there are a couple things that worried me from your log :

<3>init: could not import file '/init.trace.rc' from '/init.rc'

<3>init: could not import file '/system/etc/init.local.rc' from '/init.rc'

<6> mmcblk1boot1: unknown partition table

<6> mmcblk1boot0: unknown partition table

<3>init: could not open /dev/keychord

<3>init: cannot open '/initlogo.rle'

warning: maximal mount count reached, running e2fsck is recommended

<3>elevator: type sio not found

<3>elevator: switch to sio

failed

<3>elevator: type sio not found

<3>elevator: switch to sio

failed

<3>_dvfs_scale:mpu_iva: Bad Current voltage data

<6>PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet. [4836, drivers/gpu/pvr/bridged_pvr_bridge.c]

<3>_dvfs_scale:mpu_iva: Bad Current voltage data

<6>warning: `battd' uses 32-bit capabilities (legacy support in use)

<3>_dvfs_scale:mpu_iva: Bad Current voltage data

<3>api_call_dev_ioctl: Incompatible dspbridge ioctl number

<3>api_call_dev_ioctl: Incompatible dspbridge ioctl number

<3>_dvfs_scale:mpu_iva: Bad Current voltage data

<7>uart_open(0) called

In sum, init.rc, pvr driver not loading, bad readings on partition tables ... but looks like you're almost there

Enviado desde mi MB526 usando Tapatalk 2
[Milestone 2 Android Development] ppero196:
Well he's not quite there yet
[Milestone 2 Android Development] espaciosalter20:
At least kernel recognized sd and NAND. For me, that's a great step forward!

Enviado desde mi MB526 usando Tapatalk 2
[Milestone 2 Android Development] ppero196:
Been talking to him

Said that he needs to backport PVR drivers and USB drivers
[Milestone 2 Android Development] Quarx:
Agree with espaciosalter20.

PVR not initialized because no display for it:)

It will work after dispaly.

USB will work after port moto features.

Just wait.
[Milestone 2 Android Development] bige93:
Quarx, is there any possibility of getting USB-host working on Defy?
[Milestone 2 Android Development] Skrilax_CZ:
You may want to check Motorola RAZR ICS kernel sources (as it's 3.0.8 - yeah sounds like they used OMAP3 branch for OMAP4 phone :| ).

Also there is some issue with "dvfs" (hard to tell if that should be solved with priority). Motorola USB drivers need their gadget driver (mot-android.c or smth like that, perhaps RAZR kernel will be better for that, but don't forget to patch PID / VID for Defy). Some part is also in board-mapphone.c file (yeah, it's mess). But well, that's done as the latest thing when there is no need for UART.
[Milestone 2 Android Development] Skrilax_CZ:
This patch appears to have helped with performance issues with PVR 1.7 and 1.8 drivers on MS1: https://github.com/nadlabak/android_hardware_ti_sgx/commit/57b9e77caafe6ff398be8ce483551b467792a6b7

A little note, not sure if the cpu_is_omap3630() might need some fixing for Defy as it has omap3610.
[Milestone 2 Android Development] ppero196:
Its 3630....
[Milestone 2 Android Development] Quarx:
Thanks, kernel detect defy cpu as 3630.
[Milestone 2 Android Development] adiq_ambro:
Quick question Quarx.

Will this 3.x kernel run on GB roms? I'm asking because there are plenty of people still using CM7.
[Milestone 2 Android Development] hackergnome:
no according to my knowledge
[Milestone 2 Android Development] m11kkaa:
It wouldn't be useful because 3.x kernel is made for >=ICS only.
[Milestone 2 Android Development] Skrilax_CZ:
Lol no. Of course it will run on GB.
[Milestone 2 Android Development] adiq_ambro:
It just wondered why not. Kernel should be more or less universal. That's why we have JB roms running on older kernel. However I thought that there may be some incompatibility of interfaces on newest Android patches.

Anyway, thanks for clarification.
[Milestone 2 Android Development] m11kkaa:
The reason why we can run JB with old kernel is because we're using many android-HAL patches and kernel-mods.

old system's on new kernel would result in the same. Android wouldn't be able to communicate with the new drivers.
[Milestone 2 Android Development] Burn02:
But, if we could not use a 3.0 kernel, perhaps you could build a 2.6.35 kernel (or 2.6.37, i do not remember extactly), that is the "normal" GB kernel, and that bring some feature about graphics and memory usage.

Not? :) That could be better for people who wanted to stay on GB, if JB could not be enouth fluid for defy.:p
[Milestone 2 Android Development] Skrilax_CZ:
Well yeah, of course drivers used for ICS and GB will differ somewhere - for instance PVR 1.7 for GB and PVR 1.8 for ICS, but there isn't a problem with having PVR 1.7 drivers on 3.0 kernel.

But in general, there is no "stickyness" between Android version and Linux kernel version.
[Milestone 2 Android Development] josuearisty:
You have a very good idea, but I think we should not make suggestions now, we must let the devs finish there hard work with the kernel and we should just see what is happening, we still shouldnt be asking something that maybe you and me want, but most people want a completly working jb and I think we should let them finish and then suggest some things.

Thanks god we know this post because most defy users dont know it, so I think we should stay in passive mode.
[Milestone 2 Android Development] ppero196:
Not all users have discovered this thread..

Mind guys if we share it with them :D (JK)
[Milestone 2 Android Development] Burn02:
Of course, it's just a suggestion, that as nothing to do for the moment! We still waiting, and we still are patient. I am really happy to read this thread and all the news, and will be patient.

There is no problem and nothing urgent, it was just idea on the moment, but there is more important things to do before working on this idea of course! :good:

And of course i wan't to says thanks a lot to the people who are working on this thread!!! Keep working, you are on the good way. :)
[Milestone 2 Android Development] gedhe:
I really enjoy reading this thread and am keeping my fingers crossed that our devs will keep on improving our devices BUT I wouldn`t want this thread to be spammed like the CM10-Defy one so I would keep it "secret" - anybody who is really reading across xda and is interested in this development CAN find it.

Rein haun,

David
[Milestone 2 Android Development] tezet:
There are problems with booting M2 when emu_uart is disabled - it freezes after bootlogo. It used to work randomly, but now after merging latest version of hboot* it never works. It always boot with enabled uart. If that will be any useful information, M2 never worked without disable_dss() and with disabled tearing elimination with similiar result.

Do you have any clue what could be the problem?
[Milestone 2 Android Development] Quarx:
Did you use new kernel module(don't forget change params for load module)? It will work only with new hboot.

And you should set 512 here: https://github.com/Quarx2k/android_...2ndboot/modules/sources/hbootmod/hboot.c#L202
[Milestone 2 Android Development] tezet:
Yes, I did both of them. It seems that with the old module it happend rarely, but now it happens all the time. What is really different when UART is enabled? Maybe it's a timing issue?
[Milestone 2 Android Development] Quarx:
Can you post uart log? It will be useful.

Also you can try disable CONFIG_FB_OMAP_BOOTLOADER_INIT. May it can help with display.