I was wondering if anyone has experience in Virtual Laser key boards such as i-Techs VKB?
http://www.amazon.com/iTech-Bluetooth-Virtual-Keyboard/dp/B00142C4O8
If so, are they compatible with our phones?
I am slowly moving towards using my phone as a full mobile PC. I would like to be as productive as possible and having a full size key board would be monumental... especially when editing documents. Sure, a laptop would be the best bet but this is the future.
As a side note, I would also like to note that this is why the iPad is a step back. Technology should be getting smaller, not bigger. You can see this with the invention of micro-projectors (google "Sixth Sense Project") or the paper-thin, clear, flexible LCD displays that are emerging. I don't want to load around some cumbersome device like the iPad or even a netbook. Smart phones are the future!
/rant
Anyway, if the laser keyboard is not compatible can someone point me in the right direction for any type of key board... preferably one that rolls up or something.
Thanks!
Found this that should work for you:
https://barbourelectronicstore.com/index.php?main_page=product_info&cPath=2&products_id=6
I see no reason why it would not work. Does our phone support a normal bluetooth keyboard?
Those keyboard are not great. They have a hard time keeping track of everything.
So even if you get it working, it will only kinda sorta work.
...Come to think of it, I'm going to try to sync a bluetooth keyboard we have in the shop right now.
Edit: Dell has neglected to give me the passkey to pair the keyboard. No dice.
Dell won't give you the pass key? Shouldn't it be a set standard for that model? I figured it would be on the website of the manufacturer under the support section.
outcome69 said:
Dell won't give you the pass key? Shouldn't it be a set standard for that model? I figured it would be on the website of the manufacturer under the support section.
Click to expand...
Click to collapse
I'm trying to use a Model Number: Y-RAQ-DEL2 keyboard.
http://support.dell.com/support/edocs/acc/P109356/en/index.htm
It comes with a reciever which pair it automatically to PC's. It can also be paired with laptops that have built in modules because the computers generates the Passkey and you eneter it on the Keyboard.
Our phones, however, don't generate one but instead ask for the Keyboard Passkey itself.
I chatted with Dell to get it, they told me to call wireless tech support. I called wireless tech support and they said the passkey has to be "0000". This does not work, however. The guy was an idiot. He was obviously reading off of a screen. There must be a shared code between the Dell BT reciever and the Keyboard that I can find use to pair the device.
Ugh.
It won't work. Even if you get it to pair, no current ROM or kernel known to exist as of this moment supports HID, and the commercial BT keyboard driver in Market (which supports SPP) doesn't work on the Hero.
As far as the PIN goes (when/if it ever becomes possible to use a BT keyboard on our phones), try this:
* Make the keyboard discoverable
* Tell the phone to scan
* When the phone finds the keyboard, try setting the PIN on the keyboard by pressing 4 digit keys then enter/return. That seems to be the way most of them work.
Unlike mice and gamepads, most (newer) keyboards WON'T allow you to pair as 0000 due to the risk of password interception.
if you are looking to go completely remote, i would advice waiting for the evo. snapdragon+gi.s.+a sd card and hdmi connectivity and whats sure to be our native sense experience in a fully functioning 2.1 playing ground that will have more than enuff support or what should be simple. things such as bt (...AND THE KICKSTAND) i think it will be your most likely option to suceed. good luck, i like my laptop.
Update: it turns out, there IS a driver to use bluetooth HID keyboards with Android -- BlueInput (teksoftco.com). Unsurprisingly, it doesn't work (yet) on the Hero, either
This has gotten me wondering... Has anyone figured out WHY nothing Bluetooth-related besides audio seems to work on the Hero (compared to other Android phones that don't seem to be similarly-afflicted)?
Is it a case of distros like DamageControl having kernels with BlueZ 3.x compiled in when apps like BlueInput(HID) and KeyPro(SPP) need 4.x, or vice-versa?
Has anyone with the background knowledge necessary to build a 2.6.29 Hero kernel from scratch and troubleshoot bluetooth problems even looked at the way the kernel is getting built for distros like DamageControl? It seems like right now, nobody even knows whether this is something as trivial as a bad option at build time, or a problem that's huge and hopeless.
Sigh. It's times like this that I really hate Sprint for not letting us have R-UIM cards. I seriously think SIM cards are a major part of the reason why we (CDMA users) seem to have so many kernel-level problems that GSM Android users don't. They can just swap SIMs, and experiment all weekend if they like without metaphorically leaving their phones "off the hook" in the meantime.
I am betting those features where compiled out of our kernel. It should be easy to put them back in but then the question is will it work with the hardware... and we all know from the camera that that isn't a given.
fatkitty420 said:
...Come to think of it, I'm going to try to sync a bluetooth keyboard we have in the shop right now.
Edit: Dell has neglected to give me the passkey to pair the keyboard. No dice.
Click to expand...
Click to collapse
passkey is 0000 noob
scirio said:
passkey is 0000 noob
Click to expand...
Click to collapse
Open mouth insert foot
http://forum.xda-developers.com/showpost.php?p=6103433&postcount=7
I chatted with Dell to get it, they told me to call wireless tech support. I called wireless tech support and they said the passkey has to be "0000". This does not work, however. The guy was an idiot. He was obviously reading off of a screen. There must be a shared code between the Dell BT reciever and the Keyboard that I can find use to pair the device.
Click to expand...
Click to collapse
Hmmm. Has anyone ever tried taking a distro like DamageControl and using it with a scratch-built kernel known to have been compiled with everything BlueZ-related included and enabled? From the research I've done, it looks like we kind of have a catch-22 situation:
* All of the popular 2.1 distros seem to be using the same signed kernel. If that kernel's bluetooth support is dysfunctional, everything that relies on it for bluetooth will be dysfunctional as well.
* In theory, AOSP should be easy to experiment with bluetooth on... but NONE of the AOSP builds seem to really support bluetooth at all. At least, more than maybe being able to limp along with handsfree+headset mono. It seems to be kind of a vicious cycle -- most of the support apps needed to implement bluetooth and make it work aren't opensource, so the leaders (in a very oldschool Debian-like way) want nothing to do with them, even if it means doing without it entirely in the meantime. But since there are no ripped apps to bootstrap bluetooth support with until replacements can be written, nobody has any real incentive to work on tweaking the kernel to make them work... and since there's no real bluetooth support overall, anyone who really CARES about bluetooth (and would otherwise be the most motivated to work on improving it) shows up, looks around, and runs for the door. Oh, and the fact that even AOSP still has to deal with mystery binary blobs, because most of the HeroC's actual hardware is itself proprietary to Qualcomm and unavailable to peons like us (who merely own a phone that uses their chips).
I really wish I knew enough about both Bluetooth and the Linux kernel in general to try troubleshooting it myself, but realistically I'm still a long way from achieving that goal. I've learned a lot over the past month, but so far the only visible light in the tunnel is coming from the phone's backlight ;-)
Htc has not released source for the .29 kernel, so no one can really modify it. Maybe the .27 in the overclocked roms if you could convince a dev to help out.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Htc has not released source for the .29 kernel, so no one can really modify it
Click to expand...
Click to collapse
(palm hits forehead)
Oh god, I completely forgot about that. We don't actually have the actual 2.6.29 source yet. I got so caught up in the 2.1 celebrations a month or so ago that I totally forgot about that important little detail
here is a 1.5 kernel that says it has usb hosting. But requires doing a little extra for the drivers.
http://forum.androidcentral.com/51730-post2.html
Yes, there is one post that follows the process that I used for my SK17i Mini Pro a couple months ago.
I'm new to Android. Yup a Noob. I don't mind saying as we all have to start to learn somewhere and somehow.
Long story short. I've damaged my Very well liked SK17i. Physical is what I mean here.
I rooted it according to some instructions along the lines of:
1. upgrade to firmware xxx.
2. grab image xxx. etc.
3. use the tool to root it.
I diverged... I just installed Doomloards Custom Kernel after step 2 or so and installed it as it was already rooted! It has overclocking though I didn't use it and of course it had Boot recovery. Plenty of other useful tools aready in the .img.
I basically want the same thing for my Pro.
My whole purpose of rooting is for the rights root grants, and to use aps2sd. Sufficient for my functions. (CM mod etc, will have to be a lot more stable for me to consider them which is going to be some time down the road for this device.)
I kept everything else stock. I don't do custom roms etc. This is a daily phone and I need it to function and work for communication.
bboof posted something like what I'd prefer to do. I'm waiting for a reply as to whether his kernel will support aps2sd. (I do mean the XDAversion not anything from Android apps store unless there has been something wonderfully new there in the last 2 months since I bought my Mini Pro.)
I was fighting the Internet here and a machine with HDD problems making for a serious dog dog slow experience here. I'm in CHINA. Censorship and random sites blocked for the fun of it.
I have searched and searched. I have broken out my little 10in Computer here cause it's at least not so mind numbingly painfully slow. (haha Now just fighting the internet. At the moment XDA is not blocked! Started out that way earlier? Had to use a proxy.)
I have been at this for several hours. About 7 so far.
I have FOUND no info on a Custom Kernel for the Xperia Pro MK16i? SO other than bboofs, is there none? Yet I've found comments in others that there are? Even that doomlord has made one. I can find no link? I found such a comment in his one step guide and someone said, why? We already have kernels with root available to be flashed to the device? (Please I want this kernel? how to find it?)
I've googled any number of search parameters i could think of. I can't find.
If there's a Doomlord kernel, just like with my SK17i, I would guess specific firmware is needed? Please tell me which and where to get it... Thank you to any and all who can shed some light here. I live in a different time zone and if I can get an answer that enables me to do what I want... I might be able to order this MK16i tomorrow.It seems a great piece of kit with some nice 'upgrades' compared to my SK17i. (It was not available in Oct.)
What I have found so far. CM7 or was it 9? There's a custom kernel that seems to be required to be installed before trying the CM7 ROM.
So anyone with more experience in Android. Can I use that CM7 Kernel for MK16i? What does it support? (I read back with my SK17i some problems with CM and aps2sd. Something about scripts clashing and all that.) I will not install CM Rom. I will keep stock ROM and I am guessing there may be some conflicts? Yes, no? Maybe?
As I'm asking about using custom kernels... WE all know that the Neo and Pro are the same unit. Just like the Mini and Mini pro were. With the physical difference of a keyboard.
Anyone have a clue or has anyone even TRIED! (Someone adventurous perhaps?) the Kernels for the Xperia Neo on the Xperia Pro? I am a noob, and I do use linux 98% of the time. I don't really work in Windows anymore. However, I'm not a coder or script writer. Also Android for lack of a better term has a few mods.
More or less, in Android, from my simple understanding and yes, correct me if I'm totally wrong or even partially, so I can gain understanding, the ROM is basically where all your program functions and such are. SO when we're talking about the keyboard for example. Parameters and such I would guess are in the ROM?
If all else being equal, I should be able to use a Neo Custom Kernel on my SK16i to achieve my simple result? Or do I have it confused?
What I understand is at least with aps2sd, a ramdisk mod is needed? Does the bboof kernel not only offer root but the modded ramdisk to support other features with everything else being stock? (Actually I'm guessing it should because of mods that should still have been made to allow for the recovery. Though everything else is 'stock'. Of course totally not sure or I wouldn't be here asking.)
Anyone know? I'm more or less sitting here spinning my wheels. I want to order the replacement and at the price difference, it seems silly not to buy the MK16i. (However basically want to be 100% certain I can manage my same little basic setup.)
Also, if anyone with more experience has some idea, I'll be happy to use another tool to gain the ability to put aps on my SD card and not take up the limited space on the device. So please recommend a tool that isn't too complicated.
How about link2sd? Does it also require a modded ramdisk space?
I just want to keep it simple. I don't often need so far, any great mods on my devices. Just root so being in CHINA I can actually use the appstore.
My SK17i does work despite the damage. SO I have ROMmanager the back up program. I haven't really used it yet. (Unable to pay for paid version again other limitations of CHINA. Including an inability to pay for VPN at the moment to stop fighting with the internet. Last time to work with my SK17i took me about 5 days! Coz every link to download the files was blocked!! It only took me about 3min following the instructions to actually update firmware. unlock bootloader, add Doomlords custom kernel. ) Hoping I can use Rom Manager to back up just my programs and shift them right over to the MK16i. Can I do that? Anyone with a bit more experience using the program and does this work with the unpaid version?
Hoping to do the same here... if there's no custom kernels or such available. Please tell me. If there are, links where to download etc.
All those who use various ways to put aps on your SDcard please let me know what works well and stable. Also the real way, not like some of the app store aps. I'll make a ext partition, that kind of approach, on my SD card.
THis is likely by far an advance question... what about running debian or some linux image in chroot on Android and obviously an Xperia. In particular the pro but has anyone tried with anything else? I saw a few links about it a few months ago and even someone has an app in appstore supposed to automate it. (Uh not so important as the primary. Getting root in a kernel and aps2sd support.)
Sorry if this post is long. I'm trying to save you guys wondering what I want, and having to ask me more questions.
In case it's important. I am buying a sim unlocked non carrier specific unit. I buy from Expansys. I live in China so buy from HK. Their products are good and stuff not made for CHINA! Which is the absolute must to avoid. Unless you like fiddling and trying to bypass the limitations they put on their products. Android units sold in CHINA of course are locked by carrier. of course remove Android app store!
Not even going into the necessity to have root so I can 'pretend' I'm in some other country to reach apps that google censors from China anyway.
I hope I've been detailed enough and someone can point me in the right direction.
I've got flashtool and other tools from when I did my SK17i back in October. (Fortunately. I dread to think of the internet fight if I had to try to get them all over again. I'll only need the files specific to MK16i and links to them.)
Please use the Q&A Forum for questions Thanks
Moving to Q&A
So I got a tablet for free: Allview 3 Speed Quad HD (specifications)
When I received it someone tried to install another ROM to "update" it, but the wi-fi wasn't working anymore, which probably means it was the wrong ROM for it. I tried finding the stock ROM for it, but ended up only finding an update for the stock ROM, not the ROM itself.
Contacting the Allview company, they told me they're not making public the stock ROMs anymore, the only way to get it is to go to their service and pay them for the reflash. I would do this, but I'm not in the country anymore, not even on the same continent.
So apparently this Allview company tends to clone cheap tablets from China, then make modifications and ROMs for them, so I ended up flashing a ROM for an Onda v975s tablet, which was the only ROM that I was able to flash successfully, but the wi-fi still wasn't enabling. Everything else pretty much works and performance is actually pretty good.
Apparently this tablet has a very rare wi-fi chipset, because Onda uses another chipset on their tablets, so I assume Allview changed it.
So I opened it up and took some pictures, maybe this could help me identify what wi-fi drivers this ROM could need?
https://i.imgur.com/eGQ0Jpq.jpg
https://i.imgur.com/dO68BiR.jpg
https://i.imgur.com/GQoBeKB.jpg
Someone was saying that the only way to get this is to find another tablet like this with working wi-fi and extract the wi-fi driver/source code or just copy that entire ROM. Is that the only way? Because that's pretty unlikely since this is a pretty old piece of hardware.
So, does anyone have any idea if this is solvable or should I just give up? I'm a complete newbie, I only know the basic of flashing/rooting, so I apologise if this was a stupid thing to do. But I honestly don't know where else to ask about this. I know it's a long shot with these ****ty cheap tablets.
Please tell me if I should provide anything else.
Cheers
I am now running stock Android 8 with ezV2020 kernel for the DS version. Boot loader unlocked and Rooted.
As far as I can see, it is pretty stable. It was a long and tough process, but having already done the LG F800K it just took some hours to do the LG H990N and not days as the former did to break free.
So... just wanted to tell you guys, and let you know, it is possible. Both Sims are working, screen working, seems smooth and stable and all that.
Well, it was a lot of hoops, but I did think it might be possible - and it was and is.
Used my experience from the F800K on this little guy, and it seemed to have payed off, even if I had forgotten a lot of things or had to gather my thoughts on it.
But what a fight... But there you go.
Although it seems like it might be locked on the 4G, and I wanna have it run 3G as the radiation is much much much smaller compared to 4G. Like it is amazing to see the difference between the 2, one being nearly always in the Green by the testing instrument and the other nearly always in the Red. Just utter terrible. But I a have an app that should work that out, or maybe it just need a code and adjustment. dunno what they done to this. But should be workable. There was this code with putting the mobile number into it that got you into a menu... But I found an application for my new used LG mobile that could do the trick which name alludes me... but wait a minute and I will get it. That will most likely be my first try to fix the issue. 4G Switcher is the name of the app and it should be all clean and free!
Dearly regards
- Darkijah
Update... the good news first.
The H990N is running very smooth with the A8 Rooted with the DS kernel of ezV2020... The bad news... the Rotation and Camera does not work.
Not sure if this was something that happened after I installed Lineage 17.1 A10 and then stored it or if it was a problem before that. I just don't know. It looked like it did fine for me, and yet... apparently some issues. I tried to install a foreign kernel like I had done before, but TWRP would not flash it because the kernel file was foreign to the system. Which is odd as I flashed the mobile with the F800K kernel to get it working first hand, ezV2020 1.0 if I recall correct.
Maybe fastboot or something could installed it, adb whatever - still confused by it all...
Lineage by the way was somewhat horrible, and when I found out the sound from the Phone Jack was utter horrible I quickly turned around back to A8 stock. Although now witnessing these issues. I don't know if those issues where there before or not - or if it was something coming after the restoration from Lineage. A lot of factors can make issues.
But the mobile overall, works with network and it does run very smooth compared to my F800K, at least I seem to feel a difference here. One is slower to react, and the other is just butter smooth.
Not sure if I should toy more around with the stuff... I still have my new mobile incoming at some point when they change the broken screen. Getting a little sick and tired of the Android nonsense everywhere, which is literally is, everywhere. Issues, and looking for work arounds and what not, it is never ending.
Rooting should be as easy as pushing a button - and in my opinion should be default out of the box. No user should need to tinker and toy around with there expensive device to get things in order - the criminal companies purposely working against the users on so many levels. Highjacked the whole thing and filling it up with nonsense in the name of security or what not.
To early to say, but I might have found a fix. That took hours and hours... And still at it. But I have the Camera working and the rotation and it seems to still be running smooth. So... Hopefully no more issues, but I will further test it and try some things. It seems this issue is in all H990N20h stock Roms - I have one left to try out. I just tried a DS stock Rom and after installing the kernel and all, doing all the steps I am now into the system, need more testing if everything works, but... Well the Kernel ezV2020 is DS and now the system is DS, also known as Global if I recall. The TWRP is H990 another dual variant. There are absolutely some options to do, but they only allow 2 images being downloaded from the site and it takes a lot of time trying things out, installing it and making it work in the first place. Hours and hours wasted on this :/
But... just wanted to make an update for you guys Found a solution it seems - although there might come up new issues, usual do with Android, but hopefully it everything works!
You have to use the old version of TWRP to fix the lock issue if you get a screen like that. Very annoying, but the oldest version I have breaks it, and then you can install another higher version thereafter. Wipe out the data, and I have wiped out all else except system, not sure if it is needed overall... But in any case, that is my observations for now. I have used TWRP versions before 3.3.0 to unlock this locking issue.
Another issue is that if you go into the system it seems to delete TWRP, so... There are all these steps to do to make it work, *Sigh*.
H990N20f_00_OPEN_HK_DS_OP_1214 - camera and rotation not working.kdz
H990N20h_00_OPEN_HK_DS_OP_0225 - camera and rotation not working.kdz
H990ds20b_00_OPEN_AU_DS_OP_1108 - Newest DS version and working.kdz
H990N20d_00_OPEN_HK_DS_OP_0920 - Oldest H990N A8 but working.kdz
Here are my data so far.
I don't get it, Android is a madhouse. So after having tried things to get the Camera and the rotation to work in the stock A8, kernels and all... Then now installing the newest that did not work. Now it work all of the sudden. Makes zero sense and typical Android. I thought it might work and just for lunacy of it all I tried to install it to verify it still did not work - and now all of the sudden things that did not work, works even if I did the exact same things. It is an utter madhouse. And just typical Android...
After trying different kernels and what not... Downloading another version that did not work, downloading another and another variant of the DS... Then trying the DS that worked, then trying the oldest of the H990N working, and then trying the Newest of the H990N, and now working...
So once again I seemingly wasted hours and hours on something that now just works... Like this is something that happens all the time working with Android I have found out.
The only thing I can conclude by this, is that the installation of the DS in Partioning DL with boot and recovery unchecked, 4 unchecked in total. Must have done something to it, so it could apparently work for the other main images. At least, that's the best I can do, although I don't see why it would be related to fixing it, but it works now with the main and newest H990N image...
I wonder if my old backups would work with camera and rotation if I installed them... but... I'm not so sure I wanna try... But then again... If so, it would make zero sense. In any case I am now making a backup of the one I know 100% to work with camera and rotation H990N. Then I can always try to restore my old backups and see if the problem is there.
First older backup with the camera and rotation not working, restoring crashed the system now before being restored. *Sigh* Trying the first backup that also had the camera and rotation issue.
Well... At least I got it working, it seems. So, so far so good I guess...
My oldest backup got restored, and the Camera and rotation now works... Seems far out, but it is android so not a big surprize I guess. Faulty by design.
Anyway I will try to restore my second backup again and hope for the best... It must have been the H990DS Rom that fixed something while installing it, although have no idea why, and can make no sense of it.
Got my second backup up restored this time... The Camera and Rotation works... Like... I just don't know what could change here. But it started out working when I installed the H990ds stock so I guess it must have something to do with that, beside that I have no idea.
Seems the sickness went away from one mobile and planted itself on the other... I feel more and more that Satans minions are doing these things... Whatever the case, now my daily working mobile is having Camera problems all of the sudden... This is insane, 2 mobiles which should have nothing to do with each other, one mobile having a camera issue, and solving itself all of the sudden, and now the other mobile is infected... Like, just, just give me a break...
You gotta be kidding me, it now also have the turn issue!... This is utter insanity... Like seriously.... *Sigh* What is going on here.
Thinking seriously that a hammer can fix everything!
I downloaded US996 now that US996 is used so much for the F800 mobiles variants, well my F800K did absolutely not like that, I tried it twice and got nothing. It changes partitions apparently - It never loaded up in the system at all.
Anyway, so knowing that the H990DS stock seemed to have fixed the screen issue and rotation issue on my H990N version, I installed that on the F800K and the system worked, and with camera and rotation, although you need a lower version of TWRP to get through the security nonsense as seems to be standard. Well, the H990DS version worked on the F800K and I wonder if it might be a better choice overall to use for it. But it did look pretty good and no Korean nonsense text. Well... I am now restoring my backup of my former system with the sickness that I made before all this, and see if it has fixed it like it did with my H990N. Need to restore +50 GB because of TWRP programming nonsense and then we will see if the Camera and rotation has sorted itself out.
Interesting if it fixes both variant phones... And maybe then it might be better just to use that version on both phones, not sure...
If it sorts it out at least, I think we have a good indication that the DS version H990ds20b_00_OPEN_AU_DS_OP_1108 is a cure for this sickness, it seems.
The F800K seemed to become more sick and skype did not work and it was terrible slow to respond :/ And then of cause the camera and the rotation did not work either. Not sure what is up with that sadly. Not sure what the overall issue is. Maybe I need to keep to the older versions of TWRP or... Dunno...
But I might try the DS version on both systems, if it fixes the 2 main issues, it might not ever come on it. Maybe... Or maybe it just fixes it overall after having been installed, no idea.
I wonder if twrp-3.2.3-0-h990 might also be used on the F800K - if the US996 is not so compatible with the phone, maybe the TWRP is not so compatible either... And the H990 should be close to the DS and H990N version as far as I know...
Restoration failed.... ohh no.... hmmm - might be that the H990DS is different in regards of partitions I wonder...
I will try again and if it fails again, I will install the right stock image and see if it wanna change some partitions and thereby show if there is anything different which might break the beta full partitioning backup. The foolish nonsense of backing up a lot of empty space. Utter insane, but overall Android is insanity.
I feel that the TWRP programmers are lead by Satan, some of these choices that is found is just outrageous. But if you wipe out the competition you can rule over it all, the same with Magisk if there is no competition then it is easy for them to stir the boat. If programs takes the lead and crush everybody else, then they can begin to play tyrants and promote insanity.
Anyway, most likely will get another fail with the backup, partitioning being different in size or something. As TWRP forces this bull**** on the users, and many other things. But can't complain about it, then the blotting pen comes by here on the forum. Censorship, as always, nothing new these Satanic days of hating Truth.
Anyway, I will fix the F800K image and then restore things, that should do it. Then again, it might be better to jump on that DS image overall... *Sigh*
And see if I can get my data with me... Usually also makes issues, because programmers makes it near impossible for users to easily do what they wanna do.
We can't have to much freedom you see...
58 GB's... insanity and waste of time. Programmers love to put that bull**** on us, Android is faulty by design and the programmers outrageous following blindly along pushing more garbage - oh how I wish the Linux Pine or Librem phones had been closer to running as a daily. I would not be on this Android jail bull****, and insanity land of wasting my time with things which should have taken 1 second to fix without breaking anything and yet ends up taking months. Sick sick sick.
Android seem nothing related to Linux, no freedom, no nothing. Just Tyrant companies and programmers, ads all over and other filth. Well the progress is 42 GB and going, getting close to the breaking point I guess.
XDA is full of ads as well, same as all the website with any android stuff - ugly and disgusting filth. Because no website can be run without any ads, apparently...
Yup the restoration failed... but if the partitioning is different then it is no surprise when TWRP programmers program like drunkards full of demons.
Hopefully will soon have figure this out so I can wipe out windows 10 and get on linux... but using LGUP which is running on windows. Don't think there is a Linux version as far as I know. Okay system installed, although it did not give me any warnings of changing the partitioning... I wonder... If it will now restore my backup and if not... then I am in trouble. As this was my main phone... I should have copied everything from the internal to the Micro SD card before doing this.
Should have taken my precautions as Android never seem to do what is expected of it. Always new wacky loony things incoming from all sides. A backup should work but don't expect it too.... Because, Bull****.
Insanity: doing the same thing over and over again and expecting different results. Albert Einstein
I guess he never tried Android...
The error restoration in TWRP could also be related to the version of TWRP, dunno I might have used the old version. Can't remember, but have to take that into consideration as well... As it did not seem to do anything with any partitioning when I ran the H990N stock image.
In any case the H990N stock image is loaded this time - I will restore it with the old TWRP, and if that fails again try a newer version of TWRP and redo it again again again...
So many factors play in, and downgrading for this and upgrading for that. Because... that's Android.
Well, it restored it although with some errors, but not the overall error. Something about some folders it could not enter, which I have seen before. I don't think it is a problem but... I will just test out the Camera and rotation and then go back and restore it with the newest version of TWRP that I have working and see if I get the same issues. The BIG moment... Have it worked? Rotation works... next... Camera works!
Whatever seems to be the issue the H990ds20b_00_OPEN_AU_DS_OP_1108.kdz takes care of it and one can just return to the former stock version or restore the backup.
And I do wonder if I should just install the H990ds20b version on both mobiles really... Seems to be able to run on both variants of the LG that I have.