yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Steve Punter:
Perhaps I'm missing something, but when I look at crash reports in the "Crashes & ANRs" section of Goolge Play for my published app, I can't find reference to the Version Code of the app that reported the crash. Without knowing the BUILD NUMBER I can't determine which set of ProGuard files to use to de-obfuscate the report, nor can I determine if the user had a version prior to when the bug was actually fixed.

All the crash report tells me is the "version" of my app, which is still 1.0, and will stay that way for MANY builds to come. Does this mean Google wants us to make up long version numbers (like 1.00.34) to distinguish one release from another? If so, why bother with the Version Code at all?
[Nexus 9 Q&A, Help & Troubleshooting] kopasiak:
I'm trying to access my Nexus 9 using UART hidden in headset jack. I have USB -> UART adapter and I have prepared suitable adapter using this instruction (I have to paste it like this due to forum security rules: accuvant.com/blog/building-a-nexus-4-uart-debug-cable).

To make anything working I had to disable FIQ in kernel config and add console=ttyS0,115200n8 to cmd line. Now I'm able to see all the logs from bootloader and from kernel but when I'm trying to write anything in terminal I get only:

[ 901.015785] [HS_BOARD] (headset_get_debug) AUD_DEBUG_EN=1

[ 901.183302] [HS_BOARD] (headset_get_debug) AUD_DEBUG_EN=1

[ 901.359637] [HS_BOARD] (headset_get_debug) AUD_DEBUG_EN=1

[ 901.525347] [HS_BOARD] (headset_get_debug) AUD_DEBUG_EN=1

[ 901.823791] [HS_BOARD] (headset_get_debug) AUD_DEBUG_EN=1

[ 901.991483] [HS_BOARD] (headset_get_debug) AUD_DEBUG_EN=1

[ 902.135675] [HS_BOARD] (headset_get_debug) AUD_DEBUG_EN=1

[ 902.303744] [HS_BOARD] (headset_get_debug) AUD_DEBUG_EN=1

[ 902.654816] [HS_BOARD] (headset_get_debug) AUD_DEBUG_EN=1

logs from kernel but nothing more (one more for one pressed key). I have tried to add androidboot.console=ttyS0 to cmdline but it also didn't help.

Does anyone know what could be wrong?
[Xperia Z2 General] PRO>KOMP.<:
I delete apps on Xperia Z2 but memory does not reduce? I have 1GB free and install 5 apps(800mb Free) after I delete this 5 apps I still have 800mb?

How to fix this?

Greeting
[Xperia Z2 General] kunaltyagii:
Try clearing the cache from the storage option, if that does not work try installing ccleanr and running that. usually apps leave out cache memory even after uninstalling them..
[Xperia Z2 General] PRO>KOMP.<:
Thanks for help I installed ccleaner and delete 680mb!
[G3 Q&A, Help & Troubleshooting] walkerbeasty13:
I have a Verizon G3 running stock 4.4.2 rom, it is also rooted with stump root. I have not changed anything extreme with the root only used G3 TweaksBox to change colors and themes. I also installed the google dialer and contacts apps by downloading the .apk files and moving them manually, these have been working fine. I tried to change the LgInCallUI.apk with a different black themed one I found on the forums and overwrote the original one however it is not working now (also forgot to backup the original one). When I try to make a call I hear the call connect tone however the screen never changes and stays in the dialer app, It also does not change when a call comes in, the ringtone goes off but there is no way to answer the call. I tried removing the file from the priv app folder and trying to manually move it again by changing the permissions and moving it back to the folder but this did not help. There is also a file in the priv app folder called LGInCallUI.odex that I think was a part of the old version since it is dated a few months old like all of the other files. Any assistance would be appreciated, thank you.
[General Topics] hlabbad:
as mentioned here: (Android turn On/Off WiFi HotSpot programmatically) (http://stackoverflow.com/questions/6394599/android-turn-on-off-wifi-hotspot-programmatically) a comment say,the Reflection api is not working in Lollipop.

I want to know is there a way to do this in Lollipop
[General Topics] miked63017:
I am currently working on this and I think you need to use the WifiStateMachine class. But haven't fully verified yet.
[General Topics] hlabbad:
Thanks

thank you, i will try doing it and see if it worked. :)
[General Topics] hlabbad:
and yes

by the way i you finished your project please let me know

have a nice day :)
[General Topics] shyampsunder:
The normal reflection API works

The regular reflection calls mentioned on stackoverflow works on lolipop, just make sure to have all the correct permissions. The ones I have used are:

<uses-permission android:name="android.permission.INTERNET" />

<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />

<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />

<uses-permission android:name="android.permission.CHANGE_WIFI_STATE" />

<uses-permission android:name="android.permission.CHANGE_NETWORK_STATE" />
[Android Q&A, Help & Troubleshooting] idle0095:
Is there a launcher out there that is up to date and allows me to slide over like google now does but allow me to use that page for widgets? I basically want a launcher that is just like the new 5.0 lollipop launchers out there but google now will be replaced with a page for me to place widgets. Kind of like what Blur Launcher does.
[Fire TV Q&A, Help & Troubleshooting] flipper2006:
Not sure where to post this so if its not correct, please move it.

I have fire tv, rooted, current Rom as of 1 month ago. using gotham 14x. never had any problems, but today got message amazon fire tv is low on memory. (I have it using xposed to boot right to xbmc) so as soon a I cleared the message, it goes back to Launch Xbmc and I get the default blue splash screen, but there is no menu, and without any menu, I have no way to control anything, i can't get to any other menus. Kind of stuck, lol.

I got the low on memory message but before then everything was working fine earlier today, i went to watch a movie, got the normal, please wait popup in bottom right, it never went away, i powered down, powered back up, but now it loads xbmc without any menu.

I hope this makes sense, i tried looking for the same type of issue but i couldn't find it.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Olipro:
ok, if anyone has bad blocks, I have finally managed to patch the SPL to allow you to flash a valid SPL and repair them.

later this will be integrated into Hard-SPL... so now, you can flash garbage, and not worry!
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] lpsi2000:
Wow, that is great work. I just feel like flashing just cause :)
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] zohaer21:
BRILLIANT... i think the biggest reason for most ppl (not me though.. im on my second tytn ! ) not playing and cooking their own rom versions was the fear ....WHAT IF???

so let the cooking begin for the masses!
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Olipro:
yes, we're celebrating over in the IRC at the moment after this little triumph.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] hdubli:
Where is the SPL..I think I am the one who needs it most cos I hv only 13 MB of storage left
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Olipro:
yes... I'm not releasing this for general consumption, I'm going to port it into Hard-SPL and release that properly.

However people such as yourself who have a pressing need for it should PM me with your e-mail address and I'll send it to you.

to use it; you need either to have a booting OS, or Hard-SPL installed, either will do, but please note that SPL-1.11.Oli is not ideal, so if you can get into windows mobile to flash it via SSPL, then please do so.

also, when you message me, if you're not terribly competent, then tell me so and I'll make an RUU for you
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] silent_killa:
Wahoooo!!!!

This truely is the time for Hermes.

Olipro, you cease to amaze me my friend. Your work just gets better and better. Look forward to a release.

S.K.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] jasjamming:
well done Oli you are always on the ball. I hav a couple questions for you as I am quite interested in your work.

A bit of history first ..

Bad blocks are usually a result of process varieances in manufacturing of the NAND ROM and are marked by factory to identify them. To overcome low yields, companies that design ROM memory include extra or redundant blocks that can be addressed in the need to overcome bad blocks. (hence u dont lose storage space)

If we obtain bad blocks during the lifetime of our device that were not already there during initial manufacturing/fabrication, it is because a physical failure has occured while writing to that block numerous times.

So as there are reduntandant blocks in our ROM to suffice for bad blocks, does your technique use the "skip block method" where it identifies physically damaged bad blocks (that were a result of many read/writes) or does it use the "reverse area block method" where one good NAND block is used to keep track of all bad blocks in the ROM and the others not listed in the block table are used for data storage etc...

Or on the other hand, a block may not be defective (physically that is in its silicon process) but the value FFh may have been written to it at byte 517 in the first two pages of the block. In this case, the hermes will identify it as a bad block but in reality it isnt. Reason is that the value FFh at byte 517 is what is written to the first two pages of the block at the manufacturing factory to identfy blocks that have a manufacturing defect.

Looking forward to your reply.

Cheers,
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Olipro:
if the SPL fails to write an address, it marks the block down as being ****e, therefore, if you flash with mine, whilst it will ignore them, if a write fails too, it'll just get re-marked as being bollocksed.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Arktronic:
While I know virtually nothing about NAND ROM, I know that with regular ol' bad SDRAM, sometimes writing works, but then when you read a value back in, it's different from what you just wrote. So things like memtest86 write and read back to make sure it's all good. If the same or something similar is true for NAND, maybe the bad block verification should be changed to be safer.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] randomelements:
Awesome work :D
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] mrvanx:
Most excellent work olipro!!!!

We are coming even closer to the unbrickable device!!!!!

LOL once this is all widely used the manufacturers will notice a drop in repairs hehehe, thanks to the hard work of people like yourself ;)
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] jasjamming:
thanks OLI, understood, btw, i love the brit terminology, it has actually worn off one me, i tend to use ****e a lot in my everyday life.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] pof:
Transcript of the glory moment

-:- [Users(#xda-devs:8)]

[ pof ] [ rob-ix ] [ erg_ ] [ bwesty ] [ mouseym ]

[ Olipro ] [@ChanServ ] [ LegolasThe]

[...]

[03:37am]<pof> ok, flashing 3%

[03:38am]<pof> now, for the 2nd time this night.. if it works i go to england & kiss your ass :P

[03:38am]<pof> 33%

[03:38am]<Olipro> haha

[03:39am]<Olipro> "if not, I go to england and kick you in the balls for keeping me awake"

[03:39am]<pof> LOL

[03:40am]<pof> 100%

[03:40am]<Olipro> don't hold your breath

[03:40am]<Olipro> :P

[03:41am]<pof> OLIPRO OLIPRO OLIPRO!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[03:41am]<pof> YOU DID IT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[03:41am]<Olipro> \o/

[03:41am]<pof> :D :D :D :D :D :D

[03:41am]<LegolasTheElf> oli - you rock!

[03:41am]<pof> back on normal SPL without bad blocks!!!! :D

[03:42am]<LegolasTheElf> and factory marked are ther still?

[03:42am]<pof> LegolasTheElf: yes :)

[03:42am]<Olipro> now I have to port that into SPL-1.11, **** it

[03:42am]<pof> hahah :D

[03:42am]<Olipro> nah, it's ok

[03:42am]<Olipro> I'll do it in a pinch

[03:42am]<Olipro> but no ****ing way am I doing it tonight

[03:42am]<Olipro> I'm buggered

[...]​
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] ZakMcRofl:
I'm not sure if I fully comprehend it:

Your SPL simply ignores the bad blocks and does not touch they "bad block flag". Therefore your SPL will have no way of knowing if a block is indeed bad or just wrongly flashed?

Wouldn't a "proper" repair solution be a tool that resets all "bad block flags" so that the real SPL will remarkt they only if they are actually bad?

The way I understand it this SPL is a workaround to get a bad block-bricked device back to work:

1) Flash your fixed SPL

2) Flash a proper ROM

3) Revert to original SPL (or Hard-SPL that doesn't ignore bad blocks)

Or is it meant to be left on the device, ignoring bad blocks forever? If yes that would somehow question the neccessaty of bad block flags in the first place.

I hope you understand my question and I look forward to your reply.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Olipro:
where it physically can't write data to the block (because it actually is bad) the idea is that this block is still not written to and moved to the next block since it's genuinely bad and a write fail has occured.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] ZakMcRofl:
I see, so why did HTC use the flags anyways? If the SPL detects wrong flashes and skips those blocks?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] jasjamming:
because HTC are morons, and they have chimps working for them.

bad block checker algorithms are standard in the NAND flash ROM industry, for e.g samsung has developed algorithms to avoid bad blocks.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Olipro:
probably just wanted to save time during a flash and thought they were being clever by auto-skipping non FF blocks
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] pof:
As I understand it, Olipro's patch removes the bad block checking implemented on the SPL by HTC; the standard SPL checks if the byte 517th of a NAND page is != FF and subsequently stops writing into it, so they _are_ actually avoiding to write into "bad" blocks.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] dutty:
congrats oli :)
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] lpsi2000:
Next time I going to join this party, it seems as it was too much fun

Great Job Olipro
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] abe505:
GREAT, this is what I can't help waiting :p :)

THANKS Oli
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Sleuth255:
just posting to register my shock and awe :eek: :D
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Wam7:
Ah this is great timing! I just created a bad block when changing the Main Splash screen and accidentally pressing enter before putting the address!!

I can wait till it is incorporated in HardSPL as I managed to unbrick and the phone is working without too many problems at the moment.

Do you guys ever get bored of the thanks and praise for time, dedication and efforts! :p
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Olipro:
you can have it right now if you want... I'm spending tonight optimizing it, with pof doing the usual flashing business for me, but the one I know works you're free to use to recover your device.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] eznil:
Hi Olipro.

Similar problem here. Just posted in BlackBerry Connect Hacking thread.

I have created 3 bad blocks - see http://xdaforums.com/showthread.php?t=294218&page=13.

I read this thread, however not sure understand what to do.

I flashed SPL-1.13.Oli and now no bad blocks shown.

BTW - Trying to run ROM_Upgrade resulted in Security Problem and something about JIT debugger, so I extracted with NBHExtract and used mtty with "lnb".

What next?

Can I flash the original ROM and this will fix the problem?

Please advise.

Thanks in advance
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Olipro:
SPL-1.13 is much like an unlocked Radio ROM; the Radio ROM will show you SuperCID no matter what CID you have; similarly, you will not have any bad blocks shown while you're running SPL-1.13; what you need to do is flash a valid and working OS ROM onto your Hermes while running SPL-1.13 to actually recover your blocks.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] vp3G:
This can happen if you try to run it from a remote machine (i.e., across network instead of locally) without proper security set. It's a .NET thing.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] eznil:
Thanks, but here is another problem.

SPL-1.13 doesn't allow "lnb" to flash OS.nb. Flashing without mtty is not possible, as ActiveSync can't connect to device - 'USB device not recognized'.

Another question about bad blocks - what those addresses relate to - OS, Radio, etc?

Block 0x3A8(936) is BAD block !!!

Block 0x3A9(937) is BAD block !!!

Block 0x3AA(938) is BAD block !!!

Any suggestions?

Thanks
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] chymmylt:
Being a stupid American where most people only reconize Football as a game with a pigskin, I never knew there was an Emoticon for GGGGGGGGGGGGOOOOOOOOOOOOOOOOOOOAAAAAAAAAAAAAAAAAAALLLLLLLLLLLLLLLLLLLLLLLL!!!!!!!!!!!!!!!!!!!!!!!!! :P I love it!

Great work as always Oli!
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] chymmylt:
I just keep wondering how long until HTC starts ripping off this forum and release a new SPL with Oli's hardwork put in it (not that I think anybody would be upset by that if it saves people from the start) - maybe HTC will even send a donation to Oli (Ok I think I'm getting too far into wishful thinking!)
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Olipro:
I hate football, or soccer, or whatever you call it, but thanks :D
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] abe505:
Thanks to Oli

Oli, Oli you're the man :D

I've just install your Hard-SPL-v3 and it works flawlessly. All my bad blocks were gone and I tried to install the rom, Voila! the extended rom was installed automatically as if it were never had bad blocks.......:o :) Thanks dude for your great job
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] chymmylt:
That's just because we bought Beckham :) Sorry - I think I'm the only person in the US who follows football! I'm used to everybody hating it though (being from the US!) Anyways, thanks again!
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Olipro:
David Beckham? hah!

here, you'll like this:

David Beckham goes up to a vending machine, slots 50p in, and presses the button for a coke.

a coke comes out, he does the same again, out comes another coke.

eventually, a queue forms behind him and a bloke taps him on the shoulder and says "hurry up, other people want a drink"

David just says "shush, can't you see I'm winning?"
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] eznil:
Hi Olipro.

Can you please refer to my last post - page 3, last one?

Although there are no bad blocks thanks to SPL-1.13.Oli, I don't know how to flash a good ROM. (lnb flash is not supported in that SPL and USB connection via ActiveSync doesn't work).

Thanks
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] chymmylt:
hahahaha - all I can say is if it means we start winning (through beckham) I wont mind standing in line! :)

Anyways, I just realized that maybe football is slightly off topic (ya think?) so enough with my babblin :)
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] joelwu:
KITL Mode

Hi :

My friend X01HT have problem that, when he power up the device he saw the WINDOWS MOBILE screen and then enter to KITL mode. how to fix it, do u know?

his device info is

HERM200 IPL-1.01

SPL-1.09 BootLoader
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Olipro:
yeah... throw it out the window.

seriously though... read the wiki and follow KITL instructions.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Olipro:
oh, in other news, task 2a will repair bad blocks... I haven't released a ROM with the command enabled, but I might if anyone cares enough to want it, but it's mostly pointless now.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] pof:
Here's how a 'task 2a' enabled command looks:

USB>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0xDF(223) is BAD block !!!
Block 0xE0(224) is BAD block !!!
Block 0xE1(225) is BAD block !!!
Block 0xE2(226) is BAD block !!!
Block 0xE3(227) is BAD block !!!
Block 0xE4(228) is BAD block !!!
Block 0xE5(229) is BAD block !!!
Block 0xE6(230) is BAD block !!!
Block 0x2B8(696) is BAD block !!!

USB>task 2a
Check block : 223 - Good

Check block : 224 - Good

Check block : 225 - Good

Check block : 226 - Good

Check block : 227 - Good

Check block : 228 - Good

Check block : 229 - Good

Check block : 230 - Good

Check block : 696 - Bad

USB>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x2B8(696) is BAD block !!!

USB>
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] ghz:
Please release it. I want the ROMS.:D