yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] justyjust:
hi people

Can anyone help me, i have a htc one mini but i think this is the same for htc one and mini. on the apps page when i create a folder for my apps it only display 4 little app icons in each folder, is there anyway of increasing the amount of apps you can see in the folder. maybe a bit similar to iOS where you can see 9 apps not just 4, i appreciate the help

thanks j
[One (M7) Q&A, Help & Troubleshooting] majmoz:
I don't have a mini but on the One M7 when you create a folder you can add more than four apps to the folder. However, only four apps show when compressed. When you touch the folder, then all the apps show in the folder.
[One (M7) Q&A, Help & Troubleshooting] justyjust:
That's the same with with mini but you cannot see all what's in the folder without touching the icon, I would like to see what's inside to save me keep searching. My mates s5 has nine preview icons
[G2 Q&A, Help & Troubleshooting] Faakarna:
Hi guys.

I did something really stupid with my brand new lg g2. Wanted a custom rom, so flashed twrp recovery.

Then i wanted to flash the downloaded custom rom, but i somehow deleted everything on the phone.

Then i connected my device to the pc, and tried to sideload the rom. That didn't go well, so now i can't enter recovery or anything.

The phone only shows the LG logo or bootlooping.

Is there any hope?

(I tried to send in my phone during warranty, but they said i needed a new mainboard - which is very costly)
[G2 Q&A, Help & Troubleshooting] redduc900:
You don't sideload a ROM, you instead push it to internal storage via ADB so it can be installed via recovery (TWRP, PhilZ CWM, etc.). So this would be the command from a command prompt, run from the AndroidSDK\Tools directory or from the directory containing the ADB executable...

adb push ROM.zip /sdcard/ROM.zip

... replacing ROM with the EXACT name of the ROM file. If besides not being able to access recovery using this method...

... you can't access download mode to restore using either the *.tot or *.kdz method, then this may be your only alternative:

http://xdaforums.com/showthread.php?t=2582142
[G2 Q&A, Help & Troubleshooting] Faakarna:
Thank you very much. I was able to reach twrp again, pretty easy. I pushed a custom rom to my device, but even though the rom is installed OK, i wasn't supposed to make my device boot into the rom. The device only boots to twrp. I Installed several roms to see, if this was because of a bad flash, but that wasnt the answer. I wiped everything, and reached the aroma installer for cloudyfas rom. Installed without problems, but when rebooting, it still only boots up TWRP. Can't do anything to reach the rom (s). Any suggestions?
[G2 Q&A, Help & Troubleshooting] redduc900:
You may need to flash the KitKat baseband. The link is in the OP of the CloudyG3 thread.
[G2 Q&A, Help & Troubleshooting] Faakarna:
Thanks for answer. I did flash the baseband first.

And Tried several roms. Now Im back to stock and Wonder If i really should try again. On my first lgg2, screen Damage appeared When i was flashing a custom rom. I just don't understand Why i Couldnt load the rom after i flashed in twrp.
[Xperia Z Q&A, Help & Troubleshooting] shad0wboss:
So i received Z today and was quite happy to see all the accessories (pogo charger etc) and I also came across two plastic "covers" from the box but my guess is that those two thin plastic sheets are for shatter proofing the phone rather than avoiding normal scratches. I was thinking if they're necessary because the air bubbles at the back around a button, are impossible to remove and it kind of looks ugly too.

Any thoughts about what these plastic sheets are?
[Xperia Z Q&A, Help & Troubleshooting] androidtweaker1:
they are shatterproof films.

if you want to remove it from your phone you can remove it uing a guitar pic.

there are lot of videos showing how to do it
[Xperia Z Q&A, Help & Troubleshooting] shad0wboss:
no no not that. I don't want to remove anything from the phone. There were these plastic covers like things for the front and back which I attached to the phone. I am not sure if they serve any purpose as they have a lot of air bubbles in between and they're (air bubbles) quite hard to remove.
[Xperia Z Q&A, Help & Troubleshooting] kingvortex:
The films supplied in the box are simply screen protectors. The anti shatter films are already applied to the phone.
[Xperia Z Q&A, Help & Troubleshooting] shad0wboss:
Yeah, figured as much but my actual question was whether you need those films on a gorrila glass as they look quite ugly tbh with all the bubbles etc.
[Xperia Z Q&A, Help & Troubleshooting] kingvortex:
You actually just asked what they were for, so I told you. :D

If you don't put a screen protector on, the anti shatter film gets scratched quite easily and looks terrible. If I were you, I would get some more screen protectors and apply them more carefully.
[Xperia Z Q&A, Help & Troubleshooting] shad0wboss:
Thanks!

well I think I didn't pay much care and i have messed up the other films. The film I have applied on the front has too many bubbles and on the back, there's a huge bubble around the nfc which looks ugly.
[Xperia Z Q&A, Help & Troubleshooting] kingvortex:
You should remove that NFC sticker. It's only a cosmetic sticker to indicate where the NFC chip is located inside the phone. I removed mine straight away, before applying my screen protectors.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I think I understand the theory behind what you are trying to explain here, but I dont think this will make a difference.

First though, how did you come to the conclusion that older builds format that partition differently, or more specifically, as vFAT? And that older modems can only read this format?

The reason I dont believe this will make any difference is because much of the data everyone seems to think is located on the EFS partition is not there on the Qualcomm model S3's. For example, the IMEI. On older devices, and maybe some newer ones (dont know for sure), it was moved. If I remember correctly, some of the NV Data is stored on modemst1, some on modemst2, some on param, and some one hidden boot partitions, (and possibly elsewhere). (Dont quote me on those, its been a while since ive looked at all of this so im going by memory and may be slightly off.) But the EFS partition, as best as I can remember, mostly contains data related to DRM, factory mode, carrier info, s/n, and a few other things. I believe there is some important data there related to the modem and network, but not all of it.

The other reason I dont think this would make a difference is I dont see how the system could read and write to other partitions that are vFAT or ext4, but not EFS. It should be able to do so (and is able to do so for the data that is there) regardless of which format it is using. Both formats have been used on this device since day 1.

I am also not certain about the EFS having been re-formatted to a different filesystem at some point. To my knowledge, Odin does not touch that partition, and I've never seen any indication that it has ever formatted anything unexpected in the past. Besides, wouldnt this change its size on disk and thus require the re-formatting of other partitions to compensate? (Im not saying i am right or you are wrong about this, just there are things that aren't making sense to me here.)

I also dont know how comfortable I would be re-formatting ANY partition to a different filesystem. Let alone one that probably cannot be repaired with Odin. For the $5-6 that you might save, it just doesnt seem to be worth the risk to me. (Risk vs reward)

I do apologize if any of this has come off as too argumentative. If your theory does prove to be correct, thats awesome, but I just want to make sure all points are covered before telling anyone something like this is safe to attempt.

Thanks for the post either way though. I do find it interesting!
[T-Mobile, Samsung Galaxy SIII] RevMike:
I'm trying to retrace my google searches to find the exact reference. It was not a post focused on the SGH-T999, but another similar device. When I find it I'll update to point there.

It is my impression, and please correct me if I am wrong, that the baseband software does not run inside the linux kernel that primarily operates the phone. The low level radio functions have their own system with their own CPU functions and such. There are several reasons this makes sense.

First, interaction with the mobile radio infrastructure is very timing dependent. The software that operates the radios needs to be "real time" - meaning that every task that the system performs must complete in a predictable, determinable amount of time. General purpose, multitasking operating systems like Linux, virtually all Unix systems, and Windows don't do this well. If a general purpose system has specific subsystems that require real time operation, the common solution is put those operations onto a small purpose built hardware with its own processor and software. Even in your standard PC, the ethernet adapters and disk drives have their own processors and firmware.

Second, if the interaction with the radio network was happening in-kernel, then the GPL would require that the software to run this would be open source. The source code for the baseband is not freely available. That suggests that the baseband is separate. It is possible that the code to run the radios could be in a userland process, not in-kernel, and so sidestep the GPL issue. That is unlikely, however, since it would make the timing issues even more difficult.

So if the baseband is software running on a separate CPU, it doesn't matter that the kernel has the modules to read both vfat and ext4. The baseband would need the modules to read that. If certain baseband revisions did not include the modules to read ext4, then the baseband process could not read that data.

Other partitions would need to be changed if the size of the EFS partition was increased, but if the size of the EFS partition was not increases, the format could be changed. That process doesn't have to happen in Odin. It could be done at first boot with a particular software revision. The system would need to backup the data on the EFS partition that needs to be saved, reformat the partition using the equivalent of the mkfs command, adjust the partition table and/or the fstab so that the system could mount it properly, remount it, and write back the EFS data - possibly in a new format. All this could be done by any process that had root privs on the system. The baseband could do this itself, even, before the Linux kernel was loaded.

I definitely don't suggest that anyone tries this unless they are really really really comfortable with this kind of hacking.

BTW - some additional reading in a different T999 thread mentioned that once you go to the NC2 baseband-firmware it is not possible to go back. Makes me think that NC2 is the dividing line if I'm correct about this.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Afaik, you are correct on how the modem operates independently from the rest of the system. That was a good point I didn't take into account, so I will agree that what you stated about the filesystem format being changed is possible. In helping people around here I do periodically run into folks who have never updated beyond 4.1.1 or 4.1.2, so ill try to remember to ask them to check what format the efs partition uses next time. That would probably be the best way to confirm whether or not it was changed somewhere along the way.

As for the sizing of the partition, I do see what you are saying. I was thinking in terms of keeping the usable space the same, which if I am not mistaken would require more space on disk for vFAT.

One other reason I dont think it was changed btw, is I have compared the partition tables of older vs newer builds in the past. It has been a while though, and I wasn't focusing on the efs at the time so I may have overlooked something, but I didnt notice anything different. I was doing this while helping with our debricking process, so it is possible I just didnt see the change, but I kind of feel like I would have had it been there. But, as I just said, it is possible I overlooked it since I wasnt specifically looking for that kind of change.

The inability to downgrade firmware began with our first 4.3 update (MJC). This was done to help prevent tampering and attempts to break into the Knox secure containers.

Something else that just came to mind, is that while you cannot use an older baseband for that reason (Knox), you can use the 4.3 baseband on pre-knox builds (4.1.2 and earlier). So if you were running 4.1.1, for example, you could use the 4.3 baseband. So if your theory is correct wouldnt it mean the 4.3 baseband is capable of reading both formats? And if that is the case, it would mean its something different blocking the SIM unlock in the menu, right?

We do not have 4.4.2 yet, but I have been very active in AT&T's forums lately and can say it is almost the same. You still cannot use older modems as they just wont function, but you can use the 4.4.2 modem on a 4.1.2 or earlier build. The difference, is that while trying the 4.3 baseband on 4.4.2 firmware just doesnt work, if you put a 4.4.2 modem on 4.3 firmware you get an irrecoverable hard brick. Not even jtag will fix it. (right now the only fix is to replace the motherboard). I know that last bit doesn't have much bearing on the topic at hand, but thought I'd throw it in there since on the subject.

So anyway, if the newer basebands will function on older firmware, and the formatting of the efs had been changed, that means the new modems are capable of reading both formats. If all of that is true, the changing from vFAT to ext4 really wouldn't make a difference.

I hope I explained all of that well enough!
[Palm Treo 750] zaxxon:
Hi,

Do any of you 750 owners have seen this before?

Lately (a week or so ago) I started to get calls and the "notification" popup won't come up. I hear the ring and vibrate and there is a phonecall icon on the top bar next to the data arrows but the notification is missing so I can't see who's calling.

If/when I answer I can finally see the caller information.

This doesn't happen with every call (probably with about half of them per day).

Any idea or did you hear about something similar?

Thanks,

Zax.
[Palm Treo 750] fredkf:
Haven't had that particular problem, but I've had other issues when calls come in.

Sometimes (after I've put the device from silent to regular mode using the top slider) the phone doesn't ring and doesn't vibrate although the call notification is showing on screen. This gets fixed after one or more soft resets.

On a fair few other occasions - this is intermittent and extremely annoying - the phone doesn't react at all when someone calls me (no notification, no vibrate, no ring - nothing) but I get a audible and visible missed call notification after the caller has given up / been diverted to voicemail. This problem goes away of its own accord eventually; restarts don't seem to have any effect.

Seriously, if this device wasn't a fairly good PDA as well as a phone, I'd put it in the bin.
[HTC Desire S] VnnAmed:
​

#include warranty.h

/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Download​

XDA:DevDB Information

Unofficial CM11 for Saga, ROM for the HTC Desire S

Contributors

VnnAmed, Flinny, devil-kin, jackeagle

ROM OS Version: 4.4.x KitKat

ROM Kernel: Linux 3.0.x

Based On: CyanogenMod

Version Information

Status: Testing

Created 2014-08-12

Last Updated 2014-09-25
[HTC Desire S] Ammiraglio:
Hello thank you for your build,

Before installing this rom, can you please tell what's new in terms of bugs fixing?

Thanks

Ciao
[HTC Desire S] VnnAmed:
Actually for now it has all the flaws devil-kin's builds had, it's just synced with CM. Will try to work on the bugs though.
[HTC Desire S] VnnAmed:
Ok so while everything is still not fixed I am posting some manual solutions.

For ringtone and gps download the fix attached.

For headphones issues with canals not beeing equal: RoccoDev Beats. Install the app and turn on the service under the headphones panel.

My settings are 1,6GHz, 16bit graphic and purging of assets.

Would you be interested in me posting new build allready bareboned and posting bareboned GAPPS?
[HTC Desire S] kitaro2003:
how to make transparent status bar?
[HTC Desire S] VnnAmed:
Settings->performance->force highendgraphicd
[HTC Desire S] kitaro2003:
thank you, I know. The firmware [ROM] [4.4.x] [UNOFFICIAL] [SAGA] MoKee have this item. But in your firmware is not ...
[HTC Desire S] albertoajuria:
Is it posible to enable the OTG suport in this ROM? Thanks you for this new rom :)
[HTC Desire S] VnnAmed:
Have u enabled settings?
[HTC Desire S] VnnAmed:
Otg is kernel specific. Someone would have to make a kernel with otg support
[HTC Desire S] kitaro2003:
no item >performance
[HTC Desire S] VnnAmed:
Go to settings, about phone and tap 9 times on build number
[HTC Desire S] kitaro2003:
thank you my friend! it worked! :laugh:
[HTC Desire S] Schkisz:
is this one the update from 20140716? can i make just dirty flash or is it better to make clean install?
[HTC Desire S] devil-kin:
Well, strictly speaking, OTG is enabled in the kernel from Flinny. I don't really see why it doesn't work.

I'll see to sync the work I was doing to get a new kernel (being the one from Ace Enablement Project) running on the Saga.

Question: do you want commit access to my trees, or are you going to start your own?
[HTC Desire S] VnnAmed:
For now I am very happy that I managed to bake this build. I think I will fork your repos and try to work on them. Also I remembered that u said something about that new kernel. How hard is it to make it work for saga? I mean kernel would be good but AEP is will propably still be working on other stuff and we have same hardware like in DHD. Also where would I change CPU speeds? So that it would be overclocked from the first boot? BTW if I use your unchanged manifest, you do no changes and I do repo sync. Now if I compile again will the new build be different if manifest didn't change? I mean will it contain changes made in CM?
[HTC Desire S] docertabum:
In Titanium Backup System Rom part is full on 99.99% full. Is it ok? I dont think it was so packed in other releases like Devil-kin etc...
[HTC Desire S] Ammiraglio:
Hello, it happens (on all kk builds I've tried so far) that if i make research through Google search widget (for example to ask for weather forecast), it is much slower in showing results on the display, respect to JB. Most of the time, the graphic is even corrupted, something like very bold fonts, and after a while it returns back to normal. But this takes a while. Same thing happens when browsing through stock browser....pages are rendered very slowly. Is this because our device is not enough powerful tomanage kk or is it due to graphics driver issues? Clean install always...

Grazie
[HTC Desire S] devil-kin:
The stock browser should be 'doable', chrome is too slow for my likings. The Saga just doesn't have the power. You might want to look to overclock the device to give it a bit more umph, but keep in mind, it's old.

I kept mine clocked at 1.5ghz, stable.
[HTC Desire S] Ammiraglio:
Thank you for your explanation
[HTC Desire S] Ammiraglio:
Hello, who can compile the new files, please?

Is it possible to do that under windows 8.1?
[HTC Desire S] kylon:
Lol, windows?

after 9hrs, my first build:good: (next will require 2-3 hrs, don t worry :o )

https://mega.co.nz/#!ywkSiLQL!I8agSB4cUP0lvMLQb88x4KcW3cvZpoyTZFUc7rocaEE

test and log

as always CLEAN install
[HTC Desire S] Ammiraglio:
Thank you very much,,,,

So, flash cm11, flash gapps and in bootloader the boot.img included in the file attached? Is that correct? No wifi fix?

Thanks
[HTC Desire S] kylon:
Yes, no fix
[HTC Desire S] sHAKaJaada:
Thank you 1000!

While flashing it says: No file_contexts -- result: [/system] but everything went good...

Kylon you're GREAT!!!
[HTC Desire S] Ammiraglio:
Here is what I found:

warning: No file contexts during cmm1 flashing....is it normal?

3g signal bar is stiked at 1 bar

the headset mic does not work

front camera does not work, if you switch it just shows the image from the back camera upsidedown

i tried to reboot and now it's frozen in to a black screen....i have to remove the battery

overall, no lags, very smooth and the ringtone and wifi work good

Thank you for this work!
[HTC Desire S] sHAKaJaada:
Confirmed... GPS and MIC issue too! (Other side can't hear)! Mic doesn't record in call but Sound Recorder works! Music and ringer sounds are ok...

[edit]

btw first 4.4.4 ROM where Torch remain on with screen turned off!

+ data traffic monitoring functional!

Kernel 2-WCR ready + Deep Sleep!:good:

[edit]
[HTC Desire S] kylon:
Logs

So, audio is working? Music and call? Mic in call? Bluethoot? Graphical glitches?

Edit: try with twrp recovery, it should be only a warning.
[HTC Desire S] Ammiraglio:
Well, as this is my unique device, I had to go back to JB again, at the moment.

Anyway, calls work but i could not test device mic (i just tried headset mic which does not work). No graphical glitches, but the rendering is much slower compared to jb. I mean: I used google search asking the weather (by voice) and, although the results came out immediately by voice, the graphics took a while to be showed and at the begin text was bold and blurred,,,soon after it became ok....after a couple of seconds.

What prevented me to keep it installed is also the problem with the front camera.

Sorry, but I could not test more, since I have only this device.

Will try to test again as soon as these major issues will be fixed.

This rom is very smooth and no lags...for what I could see and test

Thank you
[HTC Desire S] kylon:
I would like to see logs...also, i don t have a desire s so i need a tester

Anyone?
[HTC Desire S] kchaisu:
Thanks Kylon for your support to the DS community. I made a clean install of the latest ROM , ROM, PA-Apps Nano (latest one). The Rom is very fast and smooth, however, the signal strength is only one bar at my place when with other ROMs I got full signal strength. When calling other side would here me until I turn the speaker on. I have tried to get logcat for you without success the access denies shownup. My PC is running Windows 8.1 though. I apologize for that.

Thank you very much for your effort.
[HTC Desire S] kchaisu:
Here is the logcat.
[HTC Desire S] kylon:
https://mega.co.nz/#!7k0AjbBT!WXMW8VicsQxkOxknIqY3v5DvI1mTjcFWRt_HBQOdhjw

audio and camera test
[HTC Desire S] sHAKaJaada:
I'll test it immediately...

THX

[edit] Again Warning: No file_contexts but flashing went ok...

WiFi issue at startup settings... but works!

Camera FC on change to front

Mic in call not working... (otherside can't hear voice, only microphony)

2WCR is ok

GPS can't connect

Signal bar shows only 1st bar

Log attached

View attachment 2979318

Camera

View attachment 2979325

More logs

View attachment 2979369
[HTC Desire S] kylon:
new build

https://mega.co.nz/#!6pkl3QjQ!nb9jP57LK8UxINFM8kB88Oek5pEP8o1ytLyllo-UF2s
[HTC Desire S] sHAKaJaada:
Have same issues like in previous... just a moment...

Camera have same issues - FC on change to front, no GPS, GSM signal status ...

WiFi theter - Hot-Spot non working...

Mic working in call but only with loudspeaker enabled, when turn-off speaker (vivavoce), otherside can't hear me.

[edit] dam'n IP operator! I was without net for about 2hrs. :mad:

View attachment 2979756
[HTC Desire S] kylon:
What about wifi error on boot

Is 3g working?
[HTC Desire S] toni_mon:
What improvement does the new kernel bribgs?
[HTC Desire S] kchaisu:
Thanks for the new build. 3G is working for me. Other issues are the same as Shak mentioned. Here is the logcat